Macrium Site Manager Restore Test Recover One Full PC From the Console Before You Trust It
A backup you have never restored is a hope, not a backup. The cheapest day to discover a restore problem is a quiet afternoon with a spare PC — not the morning the accounts machine dies.
✍️ Technical Anshu🪟 Windows / Windows Server⏱️ 9 minute read
🎥 Watch the full Macrium Site Manager deployment in the video, step by step
Site Manager makes restores look easy from the console: pick the computer, pick the image, restore. And usually it is easy — if someone has walked the path before the emergency. Drivers for unfamiliar hardware, boot media that cannot find the server, a repository credential nobody wrote down: every one of these is a five minute fix during a test and a five hour crisis during a real failure. This guide runs the full test once, properly.
Restore Test — Pass Checklist
✅ Spare PC booted from Macrium rescue media
✅ Rescue environment reached the Site Manager server
✅ Image selected from the repository and restore started
✅ PC booted into Windows from the restored image
✅ User logged in, key apps opened, files present
⬜ Timed start to finish — written down for planning
The honest test only passes when every box is ticked on real hardware, not when the restore wizard merely completes
1
Choose the Test the Way a Real Failure Chooses It
Restore to a different, spare PC — not back onto the same machine the image came from. Real failures are rude: the original disk is dead, or the original PC is. A different target proves three things at once: your rescue media boots unfamiliar hardware, the image is complete and readable, and the restored Windows can start on hardware it did not grow up on. Pick an ordinary office image for the first test; add a server restore test later, in a maintenance window, with even more care.
2
Boot the Rescue Environment and Reach the Server
Boot the spare PC from Macrium rescue media — a USB stick built for Site Manager restores, so one stick can service any managed computer.
Where the platform's PXE server is set up, you can boot the recovery environment over the network instead — no hunting for the USB stick during a crisis.
In the rescue environment, connect to the Site Manager server when prompted and browse the repository.
Select the test computer and the image you want — a recent one, so the test reflects tonight's reality, not last month's.
If the rescue environment cannot see the network or the server, stop and fix that now. This exact failure, discovered during a real outage, is the one that turns a one hour restore into a lost day.
3
Restore, Boot, and Prove It Like a User
Run the restore to the spare PC's disk and let it complete without interruption.
Boot the machine and watch Windows start cleanly on the new hardware — allow it a few minutes for first-boot driver settling.
Log in with the real user's account type and open the applications that PC actually lives in — mail, the accounts package, the browser profile.
Open files from different dates, including one from the oldest chain you keep.
Check the agent: after the excitement, the restored PC should reconnect to the console so it rejoins the schedule instead of silently sitting outside it.
4
Write Down the Time and the Surprises
Record how long the restore took end to end — that number is your honest answer when a manager asks how long a dead PC takes to replace. Note anything that surprised you: a missing network driver in the rescue environment, a credential prompt nobody expected, a slow repository read. Fix each surprise, note the fix next to it, and put the whole page where the next admin will find it. Then repeat the test on a rhythm — quarterly is a sane office habit, and always after big changes to the server or repository.
🔴 Do not count image verification as a restore test. Verification checks that an image file is intact — valuable, and you should run it — but it never proves the restored PC boots, the user can log in, or the rescue media can find your server at 9 AM on the worst day of the year. Only a real restore proves those.
🎥 Watch the Complete Deployment in the Video
Server install, agent push, backup definitions and schedules — the whole Macrium Site Manager deployment, live and step by step.
Quarterly works for most offices, plus once after any major change: new Site Manager server, new repository, a platform upgrade, or a new PC model joining the fleet. Rotate which computer's image you restore so different hardware and different users get proven over the year.
Can I test a restore without spare hardware?
Partially. The platform's viBoot feature can boot an image as a virtual machine on Hyper-V or VirtualBox, which proves the image boots and the data opens — a genuinely useful check. It does not prove your rescue media boots a dead PC's replacement hardware, so treat viBoot as a bonus test, not a substitute for the real one.
The restored PC boots but Windows asks to be reactivated or apps complain. Is the test failed?
Not necessarily — hardware changes can trigger activation and licence checks in Windows and some applications, and that is a real-world fact of restoring to different hardware, not a backup failure. Note it in your test record so it is a known step in a real restore, and keep licence keys for key software with your restore notes.
This guide is based on the Technical Anshu Macrium Site Manager deployment video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏