01
What each component is for
Operations Manager is the monitoring engine — agent-based or agentless health checks across Windows, Linux, Unix, network devices and applications, with management packs for SQL Server, Exchange, IIS, SharePoint, Active Directory and hundreds of third-party products. Configuration Manager is the deployment workhorse — operating system imaging, application packaging and distribution, patch management, BitLocker management, and the on-prem twin of Microsoft Intune. Virtual Machine Manager orchestrates Hyper-V hosts, Azure Stack HCI clusters and (still) some legacy VMware vCenter scenarios. Data Protection Manager handles disk- and tape-based backup for Windows workloads with Azure Backup integration. Orchestrator runs IT runbooks via a visual designer for cross-product automation.
02
Per-core licensing — the same model as Windows Server
System Center is per-core, with the same 8-cores-per-processor / 16-cores-per-server minimum as Windows Server. Standard covers up to 2 OSEs per licence; Datacenter covers unlimited OSEs on the licensed host. The breakeven calculation is identical: above roughly six managed OSEs per host, Datacenter wins. The SCOM agent on a managed Windows or Linux OSE consumes that licence's OSE rights; SCCM clients consume the Client Management Licence (CML) — see below.
03
Client Management Licence (CML) — the part that catches everyone
Configuration Manager additionally requires a Client Management Licence (CML) per managed device. The CML is included with Intune Plan 1, with Microsoft 365 E3 / E5 / F3, with Enterprise Mobility + Security E3 / E5, or it can be bought standalone. Servers managed by SCCM consume a 'Server Management Licence' (SML) instead, which is included with the System Center per-core licence — but every workstation under SCCM management needs the CML, and this is the most common audit finding for organisations that bought System Center years ago and grew the SCCM-managed workstation count without revisiting CMLs.
04
Co-management with Intune
Modern Windows endpoints can be co-managed by SCCM and Intune simultaneously — both have authority over the device, with each workload (compliance, device configuration, endpoint protection, Windows Update, Office Click-to-Run, client apps, Office apps) explicitly assigned to one of the two managers. This is the supported migration path away from SCCM: gradually shift workloads to Intune as the cloud product matures in each area, while SCCM continues to handle the workloads where it remains stronger (deep application packaging, legacy operating systems, air-gapped sites). Full Intune-only management is the long-term target for most organisations; co-management is the bridge.
05
Where Azure Arc fits
Microsoft is consolidating on-prem management into Azure-anchored tools — Azure Arc-enabled servers, Azure Update Manager, Azure Monitor, Azure Policy. System Center 2025 continues to ship and is fully supported, but new deployments should evaluate the Arc + Intune path first; for many organisations, the combination of Arc-managed servers, Intune-managed endpoints and Azure Monitor for telemetry now covers what SCOM and SCCM used to do, at a per-server or per-device subscription cost rather than a perpetual licence. System Center remains the right answer for very large on-prem estates, air-gapped networks, and shops with deep packaging investment in SCCM.
06
SCOM, Linux and the cross-platform story
Operations Manager has supported Linux and Unix monitoring for over a decade via the OMI agent, and 2025 modernises the agent to the OpenTelemetry-aligned format. Management packs are available for Red Hat Enterprise Linux, SUSE, Ubuntu, AIX and Solaris (the older Unix support is in maintenance mode). The web console has been rebuilt on a modern stack, improving performance for large environments. SCOM remains one of the broader monitoring products on the market — for shops standardised on Microsoft, the management-pack ecosystem is the deciding factor versus open-source alternatives such as Prometheus + Grafana.
07
DPM, Azure Backup and modern data protection
Data Protection Manager handles disk- and tape-based backups for Windows, SQL Server, Exchange, SharePoint and Hyper-V. It integrates with Azure Backup to tier older recovery points to cloud storage, which is the supported pattern for long-term retention without keeping a tape library on site. For greenfield projects, Microsoft increasingly recommends Microsoft Azure Backup Server (MABS) — a free-to-license variant of DPM that requires only an Azure Backup vault subscription — for organisations whose backup needs are entirely or primarily Azure-tiered.