System Center Licensing in SPLA

If Windows Server is the house, System Center is the facility management team—handling security, automation, monitoring, and backups.

For Service Providers, System Center is often the invisible layer that keeps the datacenter running. However, licensing it in SPLA requires you to split your thinking into two distinct worlds: managing Servers (the infrastructure) and managing Clients (end-user devices).

Below is your guide to the Core model for servers, the SAL model for clients, and how the Flexible Virtualization Benefit changes the game.

Managing Servers: The Core Licensing Model

When you use System Center to manage servers (virtual or physical), the licensing model mirrors Windows Server almost exactly. It is a Per Core model designed to match the Operating System layer.

The Editions: Standard vs. Datacenter

Just like Windows Server, the difference here is purely about virtualization density:

• System Center Datacenter: Designed for highly virtualized Private Clouds. It allows you to manage an unlimited number of Operating System Environments (OSEs) on the licensed host.
• System Center Standard: Designed for low density or non-virtualized servers. It generally covers the management of 1 OSE (plus the host if used solely for management).

The Hardware Math (The Rule of 8)

If you license the physical host (which is standard practice in SPLA), you must follow the same hardware minimums as Windows Server:

• Per Processor: You must license a minimum of 8 cores per physical processor.
• Per Server: Even if the hardware is small, you must license all physical cores on the server.
• Packaging: Licenses are sold in 2-core packs.

Pro Tip: The CIS Suite In SPLA, Microsoft offers the Core Infrastructure Server (CIS) Suite. This is a bundled SKU that includes both Windows Server and System Center for a single price. It is often significantly cheaper and administratively easier than licensing them separately if you are providing a fully managed IaaS offering.

Managing Clients: The SAL Licensing Model

If you are using System Center to manage end-user devices (e.g., PCs, laptops, or tablets), you cannot use the Core model. You must switch to the Subscriber Access License (SAL) model.

• System Center Client Management Suite: This is the specific SKU used for managing end-user devices.
• How it works: You report one SAL for every OSE (device) or User managed by the software.
• Components: This typically covers tools like Configuration Manager (SCCM) and Endpoint Protection when applied to client devices.

Common Compliance Pitfalls

1. The "Passive" Oversight: A common misconception is that you only need to license the "primary" monitoring server.

• The Rule: You must license the endpoints being managed. If you install a System Center agent on a customer's VM to monitor uptime or patch capabilities, that VM requires a System Center license (or the host must be licensed with Datacenter).

2. Mixing Core and SAL Auditors frequently find providers attempting to use "Core" licenses to cover client desktops or "SALs" to cover servers.

• The Rule: You must strictly separate Server OSEs (Core model) from Client OSEs (SAL model). You cannot mix and match these currencies for the same workload.

3. Counting Cores Incorrectly: As with Windows Server, a frequent error is counting total cores in a cluster and dividing them arbitrarily. You must license physical cores per physical processor, adhering to the 8-core minimum per processor.

Special Scenario: The Flexible Virtualization Benefit (FVB)

The Flexible Virtualization Benefit applies to System Center just as it does to Windows Server and SQL Server. This is ideal for customers who want to use their own System Center configuration to manage their specific VMs on your infrastructure.

The Scenario: The "Bring Your Own Management" Customer Your customer, ManageCo, has existing System Center Core licenses with active Software Assurance (SA) or subscriptions. They want to move their workloads to your datacenter and continue using their own System Center console to manage those VMs.

The New Rules (FVB):

1. Eligibility: You must be an Authorized Outsourcer (not a Listed Provider like AWS, Google, or Alibaba).

2. Deployment: ManageCo can deploy their System Center server components on your shared hardware.

3. Licensing:

• The customer uses their own System Center licenses to cover their VMs.
• Per VM Licensing: Instead of licensing the physical host, the customer licenses the Virtual Machine. They must assign licenses equal to the number of virtual cores (minimum 8 core licenses per VM).
• Disaster Recovery: The customer gains access to DR rights and other SA benefits for these licenses.

4. Reporting: You do not report System Center on your SPLA for these specific VMs.

Take Control of System Center Licensing with Octopus Cloud

Octopus Cloud helps service providers manage System Center licensing with confidence.

Whether you’re handling server infrastructure under the Core model, client devices via SALs, or leveraging the Flexible Virtualization Benefit for customer-owned licenses, Octopus Cloud ensures your SPLA reporting is accurate, audits run smoothly, and your managed services remain cost-effective and scalable.

To learn more on how Octopus Cloud can help you, reach out to our team.