The Nationwide Desktop Rollout, Step by Step

A nationwide desktop rollout is the most standardisable project in IT, thousands of near-identical swaps, and still manages to humble organisations regularly, because the difficulty was never the desktops. It's the nationwide part. Here's the arc, end to end.

Step 1: the build before the boxes

Everything starts with the SOE: one standard build, tested against the incoming hardware models and the application estate. Fleet purchases without a finished, piloted build turn the staging facility into a development lab with a freight deadline. Build first, buy against it.

Step 2: the data migration decision

The fork that shapes the whole program: what follows the user to the new machine? Cloud-profile estates (roaming settings, OneDrive-style data) make swaps nearly stateless, fast, repeatable, low-risk. Legacy estates with local data need per-seat migration steps that multiply visit time and failure modes. Know which estate you are, honestly, before timing anything, and if the answer is "mixed," segment the waves accordingly.

Step 3: imaging at industrial scale

Devices flow through staging: serialised at receipt, DOA-screened, imaged in parallel benches, asset-tagged, and kitted per site with peripherals and cabling. Hundreds of units a week is routine on a proper line; the same throughput attempted on-site would colonise every branch's back room for a quarter.

Step 4: waves across the map

Delivery follows the national wave logic: pilot, metro velocity, regional circuits, cleanup. Desktop swaps run efficiently in business hours alongside users (with scheduling courtesy) or after hours for counter positions. Per-seat time is the metric that rules the schedule; the pilot establishes it truthfully, and everything downstream compounds from that number.

Step 5: the leg most plans forget

Every new desktop displaces an old one, full of data and residual value. The retired fleet leaves through the same visits, serialised into custody, then wiped, remarketed or recycled with certificates to close each serial. Fleets that skip this planning finish the rollout twice: once for the new machines, once, months later and grudgingly, for the stockpiles.

The 2026 accelerant

Many current desktop programs carry a hard external deadline: Windows 10's ESU cliff in October 2026 and its escalating commercial pricing beyond. Fleets migrating under that clock get no credit for good intentions, only for completed waves, the migration-specific plan covers the deadline maths.

Done right, a national desktop program is almost boring: a pipeline humming from dock to desk to disposal, visible serial by serial, finishing when the plan said. Boring took preparation. It always does.

Fleet-scale swap ahead? Speak to an expert.