Solution
Windows 11 refresh across many sites
Audit eligibility, stage devices, pilot at one site and deploy in waves with local engineers and acceptance records.
Quick answer
What is the answer?
Run a Windows 11 refresh across many sites in stages. Audit which devices can upgrade and which need replacing, stage new devices with your configuration, pilot at one varied site, then deploy in waves with local engineers. Record user acceptance at each site, retire old devices with proof, and close out with an updated asset register.
WHAT IT LOOKS LIKE
The situation.
Windows 10 reaches the end of mainstream support, and you manage devices in many offices. Some machines will upgrade in place. Others fail the requirements and need replacing. Your inventory is incomplete, and you have a small central team and no technicians in most locations.
Imaging the machine is the easy part. The hard part is coordination. Hardware must be ordered before you know how many machines need replacing. Each building has its own access rules. Users need their files, printers and apps on the first sign-in, and old drives hold data that needs to be wiped with proof.
A refresh across many sites works when it is run as a program. One schedule, one set of checks and one report format, with local engineers who know the building and follow the same brief everywhere.
What goes wrong when it is handled badly
- Hardware is ordered before the upgrade or replace split is known, so budgets and delivery dates are wrong.
- Every site is deployed at once, and a flaw in the configuration reaches all users.
- Engineers arrive without access approval or a delivery to unpack.
- Users lose files or settings because the profile move was not tested.
- Old devices leave the site without a recorded wipe or custody record.
- The asset register is not updated, so the next audit starts from zero.
HOW WE HANDLE IT
How we approach it.
STEP 01
Audit the estate and write the scope
We work from your inventory and check the gaps device by device. Each machine is sorted into upgrade, replace or unknown, and the written scope sets waves and dependencies.
STEP 02
Stage devices with your configuration
New devices are built to your standard, labeled and tested before they ship. Staging happens close to where they will be used.
STEP 03
Pilot at one varied site
The pilot includes a mix of laptops, desktops and awkward applications. Findings update the build and the runbook before more sites start.
STEP 04
Deploy in waves with local engineers
A named engineer at each site follows the brief, moves user data per your design and runs the acceptance checklist with each user.
STEP 05
Retire old devices and close out
Old devices are removed under a recorded custody trail and sanitized to your standard. You receive acceptance records, photos and an updated asset register.
What you receive
- A device-by-device eligibility list showing upgrade, replace or unknown
- A written rollout plan with a schedule for each site
- Pre-staged devices configured to your standard
- Signed acceptance records for each user or site
- Disposal and sanitization records for retired devices
- An updated asset register and closeout report
Services that apply
Related case studies
Case studies are representative scenarios, not client projects.
QUESTIONS
Common questions.
How do you plan a Windows 11 rollout across many offices?
How do we know which devices can upgrade?
Do we need local engineers at each site?
What about user data and settings?
What happens to the old devices?
Get started
Need engineers on site? Tell us where.
Tell us the sites, the scope and the timeline. We reply with a written plan.