November 1, 2026 • Centoffer Editorial • 15 min read
End-User Device Deployment: Running a Deskside Laptop Refresh Across Many Sites
End-user device deployment is the planned replacement of laptops and desktops for employees, from procurement and provisioning through deskside handover to retiring old devices. Across many sites, a refresh succeeds when it runs in waves with a pilot, uses a provisioning model matched to each site, follows one deskside runbook with proof of delivery, and sanitises every returned device against a named standard.
End-User Device Deployment: Running a Deskside Laptop Refresh Across Many Sites
Replacing one laptop is a routine task. Replacing four thousand across forty offices in eight countries, while people keep working, is a programme — and it fails in ways that are entirely predictable: devices arrive at the wrong site, users lose files, engineers run out of time, old laptops disappear, and the help desk spends a month absorbing the fallout. Device deployment done well looks quiet. Users get a working machine on an agreed day, their data and peripherals come across, the old device is recovered and wiped, and the asset register is right at the end.
This guide is for IT leaders planning an end-user device deployment or laptop refresh across many sites. It explains why so many organisations are refreshing now, the phases of a multi-site rollout, how to choose a provisioning model, what a deskside runbook should contain, how to retire old devices safely, and which KPIs show whether the programme is working.
What is end-user device deployment?
End-user device deployment is the end-to-end process of putting new computing devices into employees’ hands ready to work, and retiring the devices they replace. It spans procurement, staging, provisioning, scheduling, deskside handover, data migration, user support and disposal.
It is worth separating deployment from two neighbouring activities. Day-to-day installs, moves, adds and changes are covered by IMAC services: individual, catalogue-driven requests. A refresh is different because it is a time-bound programme with hundreds or thousands of identical tasks, so it needs wave planning, capacity modelling and programme governance. And unlike break-fix, nothing has failed; the work is planned, which means quality problems are almost always planning problems.
A “deskside” rollout is one where an engineer physically meets the user, either at their desk or at a scheduled handover point, to complete the swap. It contrasts with “drop-ship” models, where a pre-configured device is couriered directly to the user, who sets it up themselves. Most multi-site refreshes end up as a blend of the two.
Why are so many organisations refreshing devices now?
The immediate driver for many organisations is the end of Windows 10 support combined with Windows 11’s stricter hardware requirements. Microsoft’s lifecycle documentation states that Windows 10 Home and Pro reached end of support on 14 October 2025, after which those editions no longer receive monthly security updates.
Organisations that cannot move every device in time can buy a bridge. Microsoft states that commercial and educational organisations can enrol Windows 10 PCs in Extended Security Updates (ESU) for a maximum of three years after end of support, at US$61 per device for Year One through volume licensing, with the price doubling every consecutive year. ESU buys time; it does not remove the need to refresh, and its rising price makes the bridge progressively more expensive.
The second factor is eligibility. Microsoft’s published minimum requirements for Windows 11 include a 1 GHz or faster processor with at least two cores on a supported 64-bit processor, 4 GB of RAM, 64 GB of storage, UEFI firmware with Secure Boot capability, and TPM (Trusted Platform Module) version 2.0. Older devices that fail these checks cannot simply be upgraded in place, which turns an operating-system migration into a hardware replacement programme.
The market data reflects the shift. IDC reported preliminary worldwide PC shipments of 75.8 million units in the third quarter of 2025, up 9.4% year on year, citing the need to replace an ageing installed base and the Windows 11 transition as supports for demand, and naming Windows 10 end of support as a driver of the refresh in Japan. Even organisations that have finished their Windows 11 migration will face the same programme again at the end of their next device lifecycle, so the operating model is worth getting right once.
What are the phases of a multi-site laptop refresh?
A multi-site laptop refresh runs in seven phases: discovery, design, pilot, site readiness, wave execution, recovery and disposal, and close-out. Skipping or compressing the early phases is the most reliable way to make the later ones expensive.
- Discovery. Build an accurate inventory: every in-scope device, its user, location, age, eligibility, and any special requirements (engineering software, accessibility needs, shared or kiosk use). Reconcile it against HR and directory data, because the asset register is rarely as clean as it looks.
- Design. Define the device standard, provisioning model, data-migration approach, deskside runbook, evidence standard and disposal process. Agree the KPIs and the commercial model for field work.
- Pilot. Deploy to a small, representative group — ideally one large site and one awkward one — and measure everything. The pilot exists to find problems, so plan time to fix them.
- Site readiness. Before each site’s wave, confirm devices delivered and checked in, secure storage available, network capacity for provisioning, a site contact, access arrangements, and a published user schedule.
- Wave execution. Run deskside swaps against the schedule, with daily reporting and a short daily review of failures.
- Recovery and disposal. Collect every old device against its serial number, maintain chain of custody, and route it to redeployment or sanitisation and recycling.
- Close-out. Reconcile devices deployed, devices recovered and records updated; resolve exceptions; capture lessons for the next wave or the next refresh.
Which provisioning model should you use?
Choose the provisioning model per user group and per site, not once for the whole estate: modern cloud provisioning suits most knowledge workers on good networks, while pre-provisioning or traditional imaging can still make sense for constrained sites and specialist builds. The model you choose determines how much work happens before the device reaches the site, and therefore how long each deskside visit takes.
Microsoft describes Windows Autopilot as “a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use,” using the OEM’s preinstalled Windows rather than re-imaging, and says that the only interaction required from the end user is to connect to a network and verify their credentials. Its pre-provisioned deployment option splits the process so that, in Microsoft’s words, “the time-consuming portions are done by IT, partners, or OEMs,” after which the device is resealed and shipped to the user; Microsoft lists TPM 2.0-capable physical devices and an Intune subscription among its requirements.
| Model | How it works | Best fit | Deskside implications |
|---|---|---|---|
| Traditional imaging | A standard image is applied in a staging area or on site, then apps and settings are added | Specialist builds, isolated networks, legacy apps | Longest pre-work; staging space and image maintenance needed |
| Cloud user-driven (e.g. Autopilot) | Device ships with OEM Windows; user signs in and policies and apps are applied from the cloud | Knowledge workers on reliable networks | Short visit focused on handover, data and peripherals |
| Pre-provisioned (e.g. Autopilot pre-provisioning) | A technician or partner completes most provisioning before handover, then reseals the device | Sites with limited bandwidth; users who need a ready device on arrival | Staging time before the visit; very short user setup at the desk |
| Drop-ship self-service | Pre-configured device couriered to the user, who sets it up | Remote and home workers | No deskside visit; separate plan for old-device return |
| Deskside white-glove | Engineer completes setup, data migration and peripherals with the user present | Executives, shared or specialist devices, low-confidence users | Longest visit; highest satisfaction for complex users |
Most estates use two or three of these at once. The design phase should assign each user group a model explicitly, because the field schedule, the parts list and the cost all follow from that decision.
How should you plan waves across many sites?
Plan waves around business calendars and site readiness first, and engineer capacity second. A wave plan that looks efficient on a spreadsheet will fail if it puts finance users on their month-end close or schedules a site whose devices are still in customs.
Useful principles for multi-site wave planning:
- Start with a pilot, then a “friendly” wave. After the pilot, deploy to a site with a supportive local manager and good facilities before tackling the hardest locations.
- Group by geography and logistics, not just by organisation. Engineers’ travel time is capacity you cannot get back; cluster nearby sites into the same wave.
- Respect local calendars. Public holidays, fiscal deadlines and seasonal peaks differ by country; build them into the plan from the start.
- Gate every site on readiness. No engineers are booked until the readiness checklist is signed off, including devices delivered and checked against the manifest.
- Keep buffer capacity. Reserve a slice of each wave for no-shows, failed swaps and VIP rescheduling, rather than letting them spill into the next site.
- Publish user appointments early. Users who know their slot will back up their data, clear their desks and turn up; users who do not will not.
What happens at the desk? A deskside swap runbook
A deskside swap should follow the same runbook for every user at every site, so that quality does not depend on which engineer turns up. The runbook is the operational heart of device deployment.
- Pre-visit check. The day before, confirm the new device is provisioned and assigned, the user’s appointment is confirmed, and any data-migration prerequisites are complete.
- Check-in. The engineer checks in at the site and the user’s location, with a verified timestamp.
- Identify both devices. Record serial numbers or asset tags of the new and old devices against the user.
- Handover and sign-in. Power on the new device with the user, complete sign-in, and confirm that policies and core apps have applied.
- Data and settings. Confirm that the user’s files, browser data and any locally stored items are available, according to the migration approach agreed in design.
- Peripherals. Connect and test docks, displays, headsets and printers; record any peripheral replacements.
- Functional test. Run a short, standard test: network, email, collaboration tools, a line-of-business app, printing, camera and audio.
- Recover the old device. Take the old device, its charger and accessories; tag and seal it for the chain of custody.
- User sign-off. Capture the user’s confirmation that they can work, or record the outstanding issue as a follow-up ticket.
- Close with evidence. Upload the proof of delivery and update the asset record for both devices before the ticket closes.
Steps 3, 8 and 10 are the ones most often skipped under time pressure, and they are precisely the ones that determine whether the organisation can account for its devices afterwards. A proof of delivery — a verifiable record of who did what, where and when (see the POD glossary entry) — is what turns a busy week of swaps into an auditable programme.
How do you handle data migration and user acceptance?
Decide the data-migration approach in design and communicate it to users before their appointment, so that the deskside visit is a handover rather than a rescue. Most problems in this phase are surprises: files saved locally that nobody knew about, or a specialist application missing from the new build.
Where users’ files already live in cloud storage or managed network locations, migration is mainly confirmation. Where they do not, set a clear rule — for example, that users move documents to managed storage before their slot — and give engineers a defined, time-boxed procedure for exceptions rather than leaving it to individual judgement.
User acceptance should be explicit. A short, standard sign-off at the desk, followed by a hypercare window in which post-deployment issues are prioritised, gives users confidence and gives the programme early warning. Track the issues raised during that window by category; a cluster of the same issue at one site usually points to a build or readiness problem that can be fixed before the next wave.
What happens to the old devices?
Every returned device is a data-security liability until it has been sanitised or securely redeployed, so recovery and disposal need the same discipline as deployment. The old laptop is not finished when it leaves the desk; it is finished when there is a record that its data has been dealt with and it has been written off or reassigned.
For sanitisation, the US National Institute of Standards and Technology published Guidelines for Media Sanitization, SP 800-88 Revision 2, on 26 September 2025, to help organisations build a sanitisation programme and select appropriate techniques — such as secure erase and cryptographic erase — according to the sensitivity of the data. Naming a standard like this in your contract, and requiring a per-serial record, is the practical step.
Disposal also carries an environmental dimension that boards increasingly ask about. The UN’s Global E-waste Monitor 2024, published by ITU and UNITAR, reported that a record 62 million tonnes of e-waste was produced in 2022 and that only 22.3% was documented as properly collected and recycled. A refresh programme that uses certified recyclers and keeps disposal records can answer that question with evidence.
Redeployment is often the better route for devices that remain eligible and serviceable. Microsoft notes that Windows Autopilot Reset can quickly prepare an existing device for a new user, which makes cascading still-capable machines to other roles or sites a practical option.
Which KPIs prove a device deployment is working?
The KPIs that matter measure whether users are productive on the new device and whether every old device is accounted for — not just how many boxes were opened.
| KPI | What it measures | Why it matters |
|---|---|---|
| Devices deployed vs. plan (per wave) | Throughput against the schedule | Early warning of capacity or readiness problems |
| First-visit completion | Share of swaps completed in one visit | Best single measure of preparation and runbook quality |
| User-ready time | Time from handover to the user confirming they can work | Captures the real productivity impact |
| Post-deployment incidents | Tickets raised within the hypercare window, by category | Reveals build, data or peripheral issues |
| Old-device recovery rate | Share of old devices recovered against the deployment list | Directly tied to data-security and asset risk |
| Sanitisation records received | Share of recovered devices with a per-serial disposal or wipe record | Proves the data risk is closed |
| POD completeness | Share of swaps closed with every required evidence item | Makes everything else auditable |
| User satisfaction | Post-visit rating | Captures professionalism and communication |
Review these after the pilot and at the end of each wave. A good programme changes its runbook or its readiness checklist between waves in response to what the numbers show.
Worked example: sizing a 1,200-laptop refresh across 30 sites
The following is our own illustrative calculation to show the method; the inputs are assumptions you should replace with your own.
Suppose an organisation must replace 1,200 laptops across 30 offices. It uses cloud provisioning for most users and deskside white-glove for 60 executives. In the pilot, it measures that an engineer can complete about 12 standard swaps per day including recovery and evidence, and about 4 white-glove swaps per day.
- Standard swaps: 1,140 devices ÷ 12 per engineer-day = 95 engineer-days.
- White-glove swaps: 60 devices ÷ 4 per engineer-day = 15 engineer-days.
- Subtotal: 110 engineer-days.
- Buffer of 15% for no-shows, failed swaps and rescheduling (our assumption): about 17 engineer-days.
- Total: roughly 127 engineer-days of deskside effort, before travel between sites and before the pilot itself.
If the organisation runs six waves of five sites each and wants each wave completed in two working weeks, it can work out how many engineers each wave needs and where they should be located. This is where a dispersed footprint changes the economics: flying a central team to 30 sites adds travel days and costs to every wave, while dispatching qualified local engineers to each site under a common runbook keeps the effort close to the calculated figure.
What are the most common device deployment mistakes?
The most common mistakes are trusting the inventory, skipping the pilot, booking engineers before sites are ready, and treating old-device recovery as optional. All of them are avoidable with planning.
- Trusting the asset register. Reconcile against directory and HR data before ordering devices or scheduling users.
- Treating the pilot as a formality. If the pilot finds nothing, it was probably too small or too easy.
- Shipping devices before the site is ready. Devices waiting in an unsecured room are a loss and data risk.
- One provisioning model for everyone. Bandwidth-poor sites and specialist users need a different route.
- No appointment discipline. Unbooked users lead to idle engineers in the morning and overtime in the afternoon.
- Letting old devices accumulate. Every unrecovered laptop is an open security and asset question.
- No evidence standard. Without proof of delivery, disputes about what was done, where and when cannot be resolved.
Should you run the rollout in-house, with a partner, or through a platform?
Run deskside deployment in-house where most devices sit in a few large sites with capable local IT staff; use a single partner for a compact regional footprint; and use a field services platform when many dispersed sites across several countries need one runbook, one SLA and one evidence standard.
Internal teams bring knowledge of users and systems, but a refresh is a temporary peak, and staffing for it permanently is rarely efficient. Single partners can deliver well within their core market, though multi-country coverage often relies on subcontractors with different standards. A platform model, such as Centoffer’s global IT field services, dispatches vetted local engineers against a common runbook, with every swap tracked against the SLA and closed with proof of delivery — the operating pattern described throughout this guide. Centoffer’s geo-tagged dispatch explains how engineers are matched to the right site.
The bottom line
A deskside laptop refresh across many sites is a logistics and governance exercise wearing a technology costume. The provisioning tools have improved dramatically, but the outcomes users notice — a working device on the agreed day, their data intact, the old machine gone — still depend on wave planning, site readiness, a consistent deskside runbook, proof of delivery, and disciplined recovery and disposal.
If you are planning a device deployment across multiple sites or countries, start with an honest inventory and a measured pilot, then talk to Centoffer about running deskside swaps under one SLA with proof of delivery on every device.
Frequently Asked Questions
What is end-user device deployment?
End-user device deployment is the process of putting new laptops, desktops and peripherals into employees' hands ready to work. It covers procurement and staging, provisioning the operating system, apps and policies, scheduling and delivering the handover, migrating data and settings, and collecting and retiring the old device, including data sanitisation and asset write-off.
How long does a multi-site laptop refresh take?
It depends on device volume, the number of sites, engineer capacity per day and how much provisioning is automated. Rather than relying on a rule of thumb, calculate it: divide total devices by realistic swaps per engineer per day, add pilot time, buffer for site readiness and public holidays, and plan waves around business calendars such as month-end.
Do we still need deskside engineers if we use Windows Autopilot?
Often, yes. Autopilot reduces or removes imaging, and Microsoft says the end user only needs to connect to a network and verify credentials. But someone still has to deliver the device, help users migrate data and peripherals, collect and secure the old device, and capture proof of delivery. Deskside support remains valuable for executives, shared devices and sites with poor connectivity.
What happens to old laptops after a refresh?
Each returned device should be logged by serial number, kept in a secured chain of custody, and either redeployed after a reset or sanitised and passed to a certified recycler. The organisation should receive a per-device sanitisation and disposal record and write the asset off in its register. Any device that cannot be accounted for should be treated as a security incident.
Which KPIs should we track during a device deployment?
Track devices deployed against plan per wave, first-visit completion, user-ready time after handover, post-deployment incidents within a set window, old-device recovery rate, proof-of-delivery completeness, and user satisfaction. Review them after the pilot and after each wave so that problems are fixed before they repeat across later sites.