System Center 2022 Licenses Managed Cores. Standard Gets Two OSEs.
You opened a 2022 licensing URL. Keep it. System Center 2022 is still what a lot of estates run. It is not what Microsoft lists as the current commercial product.
The Product Terms for System Center Server (EA/EAS/SCE) now list System Center 2025 Standard and Datacenter as 2-packs and 16-packs of Core Licenses, date available 11/24. The prior-version line on that entry currently names System Center 2019 (3/19). New version rights still sit on Software Assurance or a subscription. This page is the 2022 metric. Microsoft’s server virtualization guidance still names System Center 2022 Standard and Datacenter as the Management Servers examples. The model did not flip. You license the managed host. You do not license the management server a second time.
The 2025 spoke stays at the System Center 2025 licensing guide. Version-to-version comparison stays at System Center 2022 vs 2025. This URL is the 2022 metric.
That’s the problem.
A console list of SCOM agents is not a position. Server ML versus client ML, Standard versus Datacenter, physical cores versus vCores, whether Software Assurance or a subscription sits on the paper, and whether the OSE is a server or a client are different objects. Mix them and you either stack Standard until it costs more than Datacenter, or you brief unlimited managed VMs you do not have, or you license the SCOM box and leave the Hyper-V hosts naked.
Do not invent a list price. Your number is the quote, the MLS, or the CSP subscription in front of you. Microsoft’s how-to-buy page still prints an MSRP for a 16-core two-processor server. Do not paste it.
You license the managed host, not the SCOM box
Microsoft’s System Center licensing resources page and the System Center 2025 product FAQ (same Management Servers model): licenses are required only for the endpoints being managed. No additional licenses are needed for management servers or for SQL Server technology used in System Center. Server virtualization guidance: separate licenses are not required to run the management console on the server used to manage your licensed servers.
The live 2022 page said “managing server” and “server being managed” in the same article. Use the second one. Server Management Licenses attach to the host you manage.
Server ML versus client ML
System Center has two license families. They are not interchangeable.
Server MLs cover devices running server operating system environments, including virtual machines, Hyper-V isolated containers, and Windows Server containers. They are core-based. Two editions: Standard and Datacenter. Microsoft’s licensing resources page: the editions are differentiated by virtualization rights only. All server MLs include the same components and the ability to manage any supported workload.
Client MLs cover devices running non-server OSEs. Three types on Microsoft’s current table:
| Type | What it permits |
|---|---|
| Per User ML | Manage any OSE accessed by one user. |
| Per OSE ML | Manage one OSE accessed by any user. |
| Device ML (Core CAL or Enterprise CAL Suite) | Manage any OSE on one device. |
Server virtualization guidance: if the device has multiple VMs and you license by OSE, you need an OSE client ML for each VM and the host OSE. A user client ML covers that user’s VMs across devices. A device ML from a CAL suite covers the host and all VMs on that device.
Microsoft’s client feature table splits three columns. Configuration Manager (and Virtual Machine Manager on the client side) uses a per-user or per-OSE client ML and is listed as included in Core CAL Suite and Enterprise CAL Suite. Endpoint Protection is a per-user or per-device subscription, also listed in both suites. Other management products (Service Manager, Operations Manager, Data Protection Manager, Orchestrator) use their own per-user or per-OSE client MLs. Do not invent suite coverage Microsoft’s table does not show. Read the current product-licensing page against the paper in front of you.
Standard and Datacenter: same components, different OSE rights
Microsoft’s System Center licensing resources and the 2025 product FAQ split two editions. The 2022 metric is the same split.
| Edition | How you license it | OSEs when you license physical cores | What it is for |
|---|---|---|---|
| Datacenter | Management Servers, per core | Unlimited OSEs and Hyper-V isolated containers on that licensed managed server | Highly virtualized hosts |
| Standard | Management Servers, per core | Two OSEs or two Hyper-V isolated containers. Unlimited Windows Server containers without Hyper-V isolation. | Lightly virtualized or physical hosts. Stack more Standard licenses for more OSEs, or license extra VMs if you have SA or a subscription. |
Product Terms and the licensing-resources footnote: Standard also permits management of the physical OSE on the licensed server, in addition to two virtual OSEs, if that physical OSE is used solely to host and manage virtual OSEs.
Windows Server containers without Hyper-V isolation: unlimited on both editions. Core-based licensing models and the product-licensing table.
Do not brief Datacenter as “more components.” The 2025 FAQ: System Center Server Management components are an integrated offering. They are not sold separately. Microsoft’s how-to-buy page lists Configuration Manager, Data Protection Manager, Operations Manager, Orchestrator, Service Manager, and Virtual Machine Manager in both editions. The April 2022 GA blog named SCOM, VMM, Orchestrator, Service Manager, and DPM as the 2022 release. Configuration Manager has its own current-branch cadence. The server ML still includes the listed component right. Evaluation Center still serves 2022 bits for SCOM, Orchestrator, VMM, Service Manager, and DPM.
SQL technology is included as a supporting runtime. Product-licensing table: right to run management server software and supporting SQL Server Runtime (SQL Server Standard edition). Product Terms: you may run any number of instances of the included SQL Server database software in one OSE on a server for the limited purpose of supporting that product. That is not a free SQL Server license for production databases sitting next to SCOM.
Physical cores: eight per processor, sixteen per server
When you license the physical box, you license all physical cores on the managed server. Product Terms and the licensing resources footnote:
- Minimum 8 core licenses per physical processor
- Minimum 16 core licenses per server
That 16-core floor is the Management Servers model, aligned with Windows Server. It is not a SQL Server rule. Do not import SQL’s four-core-per-processor floor onto a System Center true-up.
Core-based licensing models: System Center Server core licenses (Server MLs) are sold in 2-core packs. Eight 2-core packs is the documented minimum to license a physical server. Current Product Terms list 2025 as 2-packs and 16-packs. Do not invent a 2022 16-pack SKU on this URL.
Worked shapes from Microsoft’s own System Center table on that page:
- 1 processor, 2 cores: 16 core licenses for Standard covering 2 OSEs (the 16-core floor binds)
- 2 processors, 6 cores each: 16 core licenses for Standard covering 2 OSEs, or for Datacenter covering any number of OSEs on that host. Standard covering 4 OSEs: 32 core licenses.
- 4 processors, 10 cores each: 40 core licenses for Standard covering 2 OSEs or for Datacenter. Standard covering 4 OSEs: 80 core licenses.
A one-socket box still needs 16 core licenses. The 2025 product FAQ states the same 16-core floor for single-processor servers. Count cores Microsoft will count, not sockets on a purchase order.
Standard is two OSEs, not “license the host and manage whatever”
Product Terms, Standard, physical cores: manage up to two OSEs on the licensed server. Need more VMs? Stack. Assign another full set of Standard core licenses equal to the physical-core requirement, manage two more OSEs.
Server virtualization guidance: Standard examples are the physical OSE plus one VM, or two VMs. If the physical OSE is used only to support VM workloads, the same licenses permit management of two VMs plus the host.
Datacenter on a fully licensed physical server: unlimited OSEs on that managed server. That grant is the edition. It is not a folklore crossover from list-price ratios. Compare your quote, not a blog heuristic.
Peak capacity matters. If you move VMs between hosts, each host must be licensed for the peak you actually manage. Physical-core licenses stay on the server. They do not follow the VM on a short-term basis. Server virtualization guidance: the exception is licensing by VM, where subscription licenses or licenses with Software Assurance may move to another server in the same server farm as needed. License Mobility through SA is listed for all System Center Server editions in Product Terms. Flexible Virtualization Benefit (October 2022) is the path onto Authorized Outsourcers that are not Listed Providers, with SA or a subscription. Flexible Virtualization Benefit guidance applies to software products broadly, including this model. Server virtualization guidance states it for System Center management of workloads on those outsourcer servers.
Licensing by VM needs SA or a subscription
Core-based licensing models: beginning in October 2022, the Management Servers model can be licensed two ways. Physical cores on the managed server, or by virtual machine. The VM path is subscription licenses or licenses with active Software Assurance only. Product Terms repeat that gate.
When you license by virtual OSE:
- License all virtual cores in the managed virtual OSE
- Minimum 8 licenses per virtual machine
- Minimum 16 licenses per customer
Server virtualization guidance: that customer minimum means you must have at least 16 subscription licenses or licenses with active Software Assurance before you use the VM path. One VM: 8 cores. Two VMs in the estate: the 16-per-customer floor binds. The number of processors on the host does not change those VM minimums.
Without SA or a subscription, you do not have this option. You license the physical cores on the managed host.
What you do not need an ML for
Product Terms carve out cases that do not take a Management License, including network infrastructure devices that only transmit network data and do not run Windows Server software, and devices monitored solely for hardware status (temperature, fan speed, power, reset, CPU availability). Do not treat a hardware ping as a managed OSE. Do not treat an empty conversion of physical to virtual as a second managed OSE without reading the clause on the paper in front of you.
Endpoint Protection has a narrow extra path. Product Terms: you may use System Center Endpoint Protection to manage OSEs you are already protecting with the Standard tier of Azure Security Center or Microsoft Defender for Endpoint, without assigning System Center MLs for that limited use. That is not a free SCOM grant.
What 2025 changed that this URL must not steal
Keep these on the 2025 guide, not as if they were 2022 rules:
- System Center 2025 is current in Product Terms (date available 11/24).
- 16-packs of Core Licenses appear on the 2025 availability table. This 2022 page stays with the documented 2-core pack.
- Feature, security, and Azure-integration work belongs at the System Center 2025 licensing guide.
- Version-to-version comparison, including any price table, stays at System Center 2022 vs 2025. Do not paste MSRP from either Microsoft page or from that comparison URL.
This URL stays 2022 because that is the query and the slug. Evaluation Center still serving 2022 bits does not make 2022 the current commercial SKU.
What to have this week
Do this before the next true-up, EA amendment, or CSP quote. Produce a System Center pack, not a pasted Microsoft FAQ.
- Every managed OSE. Server versus client. Physical, VM, Hyper-V isolated container, or Windows Server container. The management server itself called out, not mixed into the managed-host count.
- Cores the way Microsoft counts them. Physical cores by processor with the 8/16 floors, or vCores per VM with the 8-per-VM and 16-per-customer floors. One owner of the number. Infrastructure Mapper is the topology file.
- Whether SA or a subscription sits on those licenses. That single bit decides VM licensing, License Mobility, Flexible Virtualization, and a 2025 upgrade right.
- Client ML population. Per user, per OSE, or CAL-suite device ML. ConfigMgr versus Endpoint Protection versus the other management products.
- What you own versus what you manage. Microsoft Entitlements Manager is the MLS / entitlement side. Microsoft Deployment Manager is the Windows Server and SQL deployment file for the hosts sitting under those agents.
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is “we licensed the SCOM servers” or “Standard includes the host so the VMs are free”, you do not have a System Center position.
Picture your procurement director, sixty days out. Finance has this 2022 URL bookmarked. The quote walking in may already say 2025. Neither document is the estate. The number is cores after the 8/16 floors on the managed host, edition actually assigned, OSE count, and whether SA is on the paper.
The decision layer, not another SCOM inventory
You already have SCOM, VMM, ConfigMgr, or a CMDB full of managed computers. The gap is not another discovery export. The gap is turning that estate into a metric: server ML versus client ML, edition, OSE type, cores Microsoft will count, SA yes or no. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. IFMP is the topology file. MEM is the entitlement file. LCM is the renewal file.
If you are heading into a System Center true-up or a 2022-to-2025 conversation and your current tools still need three weeks to separate Standard hosts that need stacking from Datacenter hosts that do not, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
Do not let the vendor frame this as “just buy Datacenter, unlimited virt is included” without counting the cores on the managed host. Do not let your own side frame the management server as the licensed object, or treat a 2022 ML without SA as a VM-licensed 2025 right. The right question is: which edition, how many cores after the 8-per-processor and 16-per-server floors, how many OSEs, is this a VM that needs SA, and what does the paper actually grant. That is a data question, not a sales question.
The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
Sources
- System Center licensing resources (server ML vs client ML, 8/16 floors, edition table, client ML types, components): https://www.microsoft.com/en-us/licensing/product-licensing/system-center
- Product Terms, System Center Server, EA/EAS/SCE (2025 availability 11/24; prior version line 2019 3/19; Management Servers per core; VM licensing with SA/subscription; SQL technology; SA License Mobility): https://www.microsoft.com/licensing/terms/productoffering/SystemCenterServer/EAEAS
- Core-based licensing models (Management Servers; 2-core packs; 8/16 physical floors; VM path 8 per VM and 16 per customer; stacking table): https://www.microsoft.com/licensing/guidance/Core-based-licensing-models
- Server virtualization licensing guidance (names System Center 2022 Standard and Datacenter; managed-host assignment; no extra console license; client OSE/user/device MLs; VM move with SA): https://www.microsoft.com/licensing/guidance/Server_Virtualization
- System Center 2025 product page (same model FAQ: endpoints only; no extra management-server or SQL license; editions differ by virtualization rights only; components not sold separately; 2-core packs; do not paste MSRP): https://www.microsoft.com/en-us/system-center/system-center-2025
- How to buy / pricing overview (component list both editions; 2022 datasheet link; do not paste MSRP): https://www.microsoft.com/en/system-center/pricing
- System Center 2022 generally available (1 April 2022; SCOM, VMM, Orchestrator, Service Manager, DPM): https://www.microsoft.com/en-us/windows-server/blog/2022/04/01/system-center-2022-is-now-generally-available/
- Evaluation Center, System Center 2022 downloads: https://www.microsoft.com/en-us/evalcenter/download-system-center-2022
- System Center documentation hub: https://learn.microsoft.com/en-us/system-center/
- Flexible Virtualization Benefit (October 2022; Authorized Outsourcers, not Listed Providers; SA or subscription): https://www.microsoft.com/licensing/guidance/Flexible-Virtualization-Benefit
