Rollout & Migrations · Deliverable
Pre-Staged and Pre-Imaged Devices.
Pre-staged and pre-imaged devices ready for deployment
Part of Rollout & Migrations. Last reviewed October 2026.
Quick answer
What is Pre-Staged and Pre-Imaged Devices?
A pre-staged device is hardware that has been unboxed, imaged or enrolled, patched, asset-tagged and tested before it reaches the user. Deploris receives your hardware at a staging point, applies your image or autopilot profile, records serial numbers, and ships site-ready kits so on-site time is spent on installation, not builds.
WHAT THE WORK COVERS
What Pre-Staged and Pre-Imaged Devices includes.
- 01Goods-in check of purchase order quantities, models, serial numbers and visible damage
- 02Imaging or enrollment using your tooling, such as Windows Autopilot, Intune, SCCM task sequences, Jamf or a vendor-supplied image
- 03BIOS and firmware baseline, driver verification and BitLocker or FileVault key escrow where your policy requires it
- 04Asset tagging, serial capture and upload to your asset register or CMDB
- 05Burn-in and functional testing covering boot, network, display, keyboard, camera and docking
- 06Kitting per user or per site with peripherals, cables, labels and a pick list
- 07Packaging and tracked shipment to each site with a manifest matched to the schedule
HOW WE DELIVER IT
How it is delivered.
- 1
Agree the build and the tooling
We confirm the image or enrollment profile, naming convention, driver packs and encryption settings with your endpoint team, and test the build on one unit of each model.
- 2
Receive and check hardware
Devices arrive at the staging point and are counted against the purchase order. Serial numbers are scanned and any short, wrong or damaged units are raised immediately.
- 3
Image, enroll and test
Each device is built or enrolled, patched to the agreed baseline, tagged and tested. Failures are quarantined and re-run, with the cause logged against the serial number.
- 4
Kit and ship to site
Devices are packed per site or per user with a manifest, then shipped on the dates in the rollout plan so stock lands before the engineers do.
INPUTS AND OUTPUTS
What you provide and what you receive.
You provide
- Approved image, Autopilot or Jamf profile, or build documentation we can reproduce
- Purchase order details and the delivery address for the staging point
- Naming convention, asset tag format and asset register or CMDB upload method
- User-to-device mapping where devices are assigned to named people
You receive
- Staged devices with serial number, asset tag and test result recorded per unit
- Goods-in report listing exceptions, shortages and damaged units
- Site-level manifests that match what is physically in each box
- Asset register update file ready to import into your CMDB
WHEN IT FITS
When this is the right deliverable.
You are issuing hundreds of laptops and cannot afford 45 minutes of imaging per device while an engineer waits on site.
Your sites have poor bandwidth, so downloading an image or large application set on location is not practical.
You want every device to arrive already tagged, enrolled and traceable, so the asset register is correct on day one of the rollout.
WHERE WE DELIVER
Delivered in 75+ metros across 11 countries.
Local, vetted engineers deliver this work on site across the United States and Western Europe, coordinated by one engagement manager.
QUESTIONS
Frequently asked questions.
What is the difference between pre-staged and pre-imaged devices?
Can you stage devices for Autopilot instead of using a custom image?
Where does the staging happen and who holds the hardware?
What happens when a staged device fails testing?
MORE DELIVERABLES
More from Rollout & Migrations.
QUOTE
Request a quote.
Share a few details and we will come back with the next steps.
Get started
Need engineers on site? Tell us where.
Tell us the sites, the scope and the timeline. We reply with a written plan.