Most failed SEPM installs were lost before setup started, on a server that never qualified. Broadcom publishes the requirements; this page translates them into plain decisions.
The requirements for the manager are modest, but they are specific, and setup does not negotiate. A desktop Windows, the wrong server edition, or a disk that fills up in month two will each end the project in their own way. Here is the Broadcom list, what each line really means for a small office, and the free check that verifies your box before you commit an afternoon to it.
Broadcom's published minimums and recommendations, restated. Treat the minimums as the lab floor, not the office target.
SEPM runs on Windows Server. For the current 14.3 release line that means Server 2016, 2019 or 2022, with Server 2025 supported by the newest release update. Older servers like 2012 and 2012 R2 only work with older release updates, which is a polite way of saying do not build new on them. Two hard stops: desktop Windows (10 or 11) is not supported, no matter how powerful the PC, and Server Core is not supported either. The practical answer for a small office is a Windows Server VM. It does not need to be a big one, but it does need to be a server.
Broadcom lists 2 GB RAM available as the minimum and 8 GB or more as recommended, and adds the obvious but ignored note: if SQL Server also lives on this box, plan for more. Disk is where installs quietly die later. The published floor is about 40 GB free for the manager and a local database, with figures like 200 GB recommended for comfortable running. That gap between minimum and recommended is the database growing: client logs, events and content all accumulate. Build to the recommended side if this server will still matter in two years.
Broadcom supports SEPM in virtual environments, and most offices run it virtualised. The conditions are boring and real: reserve the resources so a busy host does not starve the manager during a definitions rush, and do not snapshot your way out of backups. A VM snapshot is not a SEPM backup; the supported story is the database backup plus the recovery file, covered in the backup case. Also keep the VM's clock honest. Time drift quietly breaks certificates, schedules and log timelines.
Broadcom's own Quick Start tells you to do something most installers skip: download SymDiag, Broadcom's free diagnostic tool, and run its preinstall check on the target server before installing. It tests the machine against the published requirements and flags the classic blockers while they are still cheap to fix. If SymDiag complains, believe it and fix the complaint. Setup failing halfway through the same issue costs you an uninstall, a cleanup and a worse mood.
Illustrative output. The pattern is the lesson: fix every FAIL, respect every WARN, then start setup.
The requirements above get a small office running. What they do not capture is how many clients report to this manager and how much history you keep. More clients mean more events, and longer log retention means a bigger database. The honest plan: if you are near the documented 500-client comfort zone of the default database, or you keep logs for months for compliance, size the server and choose the database (full SQL Server) for that reality now. Retrofitting either one later is possible and nobody enjoys it.
The video shows a real install on a real server. Use this page as the checklist you run before you press setup on yours.
▶️ Watch Full VideoOnly older SEPM release updates support it, and Broadcom moved on years ago. For a new install, use Windows Server 2016 or newer so you can run a current release.
It is above the published minimum and below the recommendation. For a tiny lab it will run. For a production office manager, especially with the database on the same box, plan on 8 GB or more.
It can, but every other role competes for the same RAM and disk and adds its own reboot and patching rhythm. A small dedicated VM is the setup admins do not regret.