One perfect PC, cloned to thirty desks, sounds like free IT. It can work — but only if you respect the three steps everyone wants to skip.
Because Reflect clones and images so well, offices naturally ask it to do one more job: prepare Windows once and deploy it everywhere. At small scale this is legitimate technician work, and Reflect's rescue media plus ReDeploy genuinely support it. But there is a line where imaging stops being deployment, the licensing has a catch most people never hear about, and Macrium itself sells different products for the real rollout job. Here is the whole picture, honestly.
A golden image is a reference installation: Windows installed on one machine, fully updated, with the office's standard software, settings and printers baked in — captured as an image before it ever becomes someone's computer. Deploying it means every new PC starts life identical, patched and ready, instead of spending its first day in Windows Update and software installs.
Before capture, the reference Windows must be generalised with Sysprep, Microsoft's built-in tool that strips machine-specific identity — the computer's security ID, name and driver state — so each deployed copy generates its own on first boot. Skip it and your fleet shares cloned identities: update services, domain trust and activation all misbehave in ways that surface weeks later. Reflect captures whatever you give it, faithfully — including a machine that was never prepared for copying.
For a handful of identical or near-identical PCs, the Reflect route is straightforward: capture the generalised image, boot each target from the rescue USB, restore the image, and run ReDeploy if the hardware differs so Windows gets bootable drivers for the new machine. Rename each PC, join the domain, and activate. An experienced hand does a desk in well under an hour, and for five or ten machines that is the whole story.
Neither Reflect nor Site Manager's backup console contains a deployment engine — no central rollout, no per-machine naming automation, no task sequences. Macrium knows this and sells the job separately: SiteDeploy for centralised deployment across a network, and the Deployment Kit, a portable USB-based kit for golden-image rollouts in the field. If you are imaging fifty machines a month, those are the honest products to evaluate; using a backup tool as a deployment system works until the volume makes the manual steps the bottleneck.
Separate from Macrium entirely: Windows itself restricts reimaging. Microsoft's imaging rights are tied to volume licensing — taking one installation and deploying it across many PCs is generally not something retail or OEM Windows licences permit, however easy the tooling makes it. Home users moving their own system between their own drives are in different territory, but an office planning a fleet rollout should confirm its Windows licensing position first. The tool will never warn you; the licence still applies.
See both tools working on real machines — Reflect on a single PC, Site Manager running an office full of computers.
▶️ Watch Full VideoOften yes, with ReDeploy run after each restore to inject the new machine's boot-critical drivers. Very different hardware — different storage controllers, or a jump across many hardware generations — raises the failure rate. Test the image on one example of each hardware type before committing the fleet.
No. Site Manager manages backups, not operating system rollouts. Macrium's deployment answers are SiteDeploy (centralised) and the Deployment Kit (portable). Buying the backup console to do deployment is the category mistake from the start of this guide series, in a second costume.
When the manual steps — boot media, restore, rename, join, activate — start consuming whole days each month, or when consistency slips because different hands do it differently. For most small IT teams that lands somewhere in the dozens of machines per rollout cycle.