Past a certain size, backups do not fail because the tool is weak. They fail because nobody saw the one red line in a list of two hundred. Site Manager exists to make that line impossible to miss.
In the video, Site Manager is what Anshu personally uses where it counts: daily backups across networks of 100 to 200 computers. At that scale the imaging itself is the easy part — Reflect-class agents handle it the same as always. The hard part is management: installing and updating the backup software everywhere, keeping schedules consistent, storing images sensibly, and above all knowing, every single morning, which machines are protected and which are not. That is the product Site Manager actually is.
Site Manager runs on one server (a modest VM is fine) and presents every protected workstation and server in a single list: last backup time, result, next scheduled run. Agents are installed remotely from the console — no desk visits, no USB sticks, no asking users to click through installers. When a new PC joins the office, it is added to the console, assigned a backup definition, and it simply starts appearing in the morning report.
Instead of configuring backup times machine by machine, you define them centrally: this group images nightly to the NAS repository, that group weekly, servers on their own window. A repository in Site Manager is a managed storage location with retention rules, so images are kept for the period you decided and old ones are cleared by policy — not by whichever drive happened to fill first. Change the policy once and it applies to the fleet, which is the difference between a backup strategy and two hundred private habits.
Ask administrators what actually saved them and most will name this unglamorous feature: Site Manager sends a daily summary of backup activity. Failures arrive in your inbox with the machine's name attached, while the problem is still last night's problem. Compare the standalone alternative at scale — two hundred individual result emails nobody reads, or two hundred PCs nobody opens. Central reporting converts backup from a hope into a checked fact, and the same logs provide the audit trail when a client or a compliance rule asks for proof.
The console itself is free to download and install; the money is in agent licences, one per managed computer, which Site Manager assigns and tracks for you. It can also manage PCs that already carry standalone Reflect licences, so a mixed estate is normal rather than a problem. Security logging records who changed schedules or restored what — in a multi-admin office, that accountability matters as much as the backups.
Site Manager manages machines it can reach. A laptop that spends its life on home Wi-Fi and never connects to the office network or VPN will miss its windows and show as stale in the dashboard — visible, at least, but not backed up. Roaming-heavy fleets need a plan for that (VPN-on-connect schedules, or a cloud backup tool for those specific machines). Also budget honestly: the console needs its server kept patched like any other, and repository storage for dozens of machines is a real capacity decision, not an afterthought.
See both tools working on real machines — Reflect on a single PC, Site Manager running an office full of computers.
▶️ Watch Full VideoThere is no official minimum — the console is free and licences are per machine. Practically, it starts paying off when checking individual PCs becomes a chore or a risk: typically somewhere past ten to twenty machines, or sooner if the machines are spread across sites or belong to clients who expect backup reporting.
No. It is built for local networks, and Macrium provides an offline activation route for the console and for Reflect, which suits air-gapped or restricted environments. Updates are then applied manually, which is the normal trade for working offline.
In repositories you define — typically a NAS, a file server share, or storage attached to the Site Manager server. The agents write images there over the network. Size that storage for your retention policy first; dozens of machines keeping weeks of images is a capacity plan, not a spare drive.