From one machine to the whole estate.
Rollout runs in four stages. Each one has to hold on a real fleet before the next one starts.
Survey the estate
We inventory the machines in scope, confirm hardware support, and write down with the organization which systems the OS is expected to cover and which are deliberately left alone.
Build the image
The ISO is assembled for that estate — the offline start page, the browser's portal and support links, and the software set the organization actually uses. One image, reproducible, versioned.
Run a pilot fleet
A bounded group of machines runs the OS as their daily driver, including with the network pulled. What breaks is logged and reported as found, not smoothed over before the review.
Extend across the estate
Imaging widens machine by machine. The organization's own IT owns provisioning and updates, with our engineers on hand rather than in control.
Three things, before stage one.
A named owner
One person inside the organization who can approve access and sign off the scope of the estate.
An estate inventory
The machines in scope, their hardware, and the software the people on them cannot do their job without.
A stated boundary
Written agreement on what the deployment is expected to protect against, set before it starts.