Support and lifecycle
Support and lifecycle
Who helps when something goes wrong, how fast, how long each version is kept safe, and how every pilot is tested. Published here so you can check it before the first conversation.
Hours and response times
| Priority | When | First answer within |
|---|---|---|
| Critical | Workstations cannot be used, or a security issue is being exploited | 4 business hours |
| High | An important function is disrupted for a group of users | 1 business day |
| Normal | Questions, requests and issues for a single user | 2 business days |
Business hours are Monday to Friday, 09:00 to 17:00 Brussels time, outside Belgian public holidays. Response time is the time to a first answer from an engineer; the fix follows as fast as the issue allows. TresBizz gives first-line support itself, as one supplier under one contract. These terms apply to every pilot and every contract. Write to nexzos@tresbizz.com.
Five years per version
Every major version of NEXZOS gets five years of support from its release: security updates, fixes and support under the times above. A new major version arrives about every four years, so two versions overlap for about a year, which gives you room to move in rings.
Security updates
The foundation follows Ubuntu LTS, with five years of standard security updates per release. NEXZOS updates arrive through your own management tooling, in the update windows you set.
Upgrades
Moving to the next major version is part of support and upgrades, the next release included, as on the pricing page.
End of support
The end date of each version is published here at its release, so you can plan the move in your own budget cycle.
How every pilot is tested
| Area | What is tested | Passes when | Evidence |
|---|---|---|---|
| Hardware | Every model in the pilot: start, sleep and wake, screens, sound, Wi-Fi, docking | Each model works for a full working week | Hardware report per serial number |
| Identity | Login with Active Directory or LDAP, group rights, password change | Every pilot account logs in with its own rights | Test log per account |
| Network drives and printing | Shares mount automatically, printing and scanning on your office devices | Each share and device in the pilot list works | Checklist per location |
| Applications | Every application on the pilot list on its route: native, browser, VDI or Windows layer | Users do their daily work with it | Catalogue entry updated with the pilot result |
| Management | Configuration with Ansible, updates with Landscape, rolling back a test update | An update and a rollback complete in the update window | Management log |
| Security | Hardening baseline, disk encryption where in scope, an independent security test | No open finding rated high or critical | Test report from the independent party |
| Performance | Start-up and application start compared with the same machine on Windows | Recorded figures, judged against your acceptance criteria | Measurement sheet |
| Users | Feedback from the pilot users after two and six weeks | Your acceptance criteria are met | Survey results |
You set the acceptance criteria before the pilot starts. The results go into the pilot report for your organisation and appear on this site only with your consent. A line on the roadmap moves from planned to working only after it has passed this plan at a customer.
Report a security issue
Send it to nexzos@tresbizz.com with Security in the subject. We confirm receipt within one business day, treat it as critical, and keep you informed until it is fixed.