System Center 2016 Ends January 11, 2027: Options for VMM and SCOM
System Center 2016 support ends Jan 11, 2027. Inventory what you run, plan VMM's stepped upgrade path, and decide what to keep, replace or retire.

System Center 2016 reaches end of support on January 11, 2027. That covers Virtual Machine Manager, Operations Manager, Data Protection Manager, Orchestrator and Service Manager 2016. Windows Server 2016 follows a day later, on January 12. After those dates Microsoft stops shipping security updates and fixes for these products, so the tools that run and watch your servers become the next thing that needs a plan.
For most teams this is a scheduling problem rather than an emergency. The work is knowing what you run, choosing a path for each component, and leaving enough time for an upgrade that can't skip versions.
What is ending on January 11, 2027
Microsoft's lifecycle list for 2027 shows these System Center 2016 components ending support on January 11, 2027:
- System Center 2016 Virtual Machine Manager (VMM)
- System Center 2016 Operations Manager
- System Center 2016 Data Protection Manager
- System Center 2016 Orchestrator
- System Center 2016 Service Manager
The same list puts Windows Server 2016, Hyper-V Server 2016 and Windows Server Update Services for Windows Server 2016 at January 12, 2027. If your management servers also run Windows Server 2016, you have two deadlines landing in the same week. Our Windows Server 2016 end of support guide covers the operating system side, and our post on Windows Server 2016 Extended Security Updates through Azure Arc explains the paid bridge if a server can't move in time.
Start with an inventory
Before you pick a path, write down what you actually run:
- Which System Center components and versions are installed, and on which servers
- The operating system and SQL Server version under each one
- What depends on them, such as Hyper-V hosts and clusters managed by VMM, Operations Manager management packs and alerting, backup jobs in Data Protection Manager, and runbooks in Orchestrator
- Integrations, for example Azure Site Recovery connected to VMM
This list tells you how big the job is, and it often turns up components nobody uses anymore.
Upgrading VMM means stepping through versions
Virtual Machine Manager can't jump from 2016 straight to a current release. Microsoft's upgrade guidance supports VMM 2019 from VMM 2016 (Update Rollup 6, 1801 or 1807), VMM 2022 from VMM 2019, and VMM 2025 from VMM 2022. Upgrading from 2016 directly to 2022 or 2025 isn't supported.
Each step follows the same pattern: back up and retain the VMM database, uninstall VMM while keeping the database, upgrade the management server's operating system, then install the new VMM version against the retained database. A few details are worth planning for:
- Job history is deleted during the upgrade.
- VMM agents on Hyper-V hosts and library servers need updating afterwards. On clustered hosts, Microsoft recommends maintenance mode first, because the agent update can restart the Hyper-V management service.
- Azure Site Recovery settings can't be upgraded and need to be redeployed after the upgrade.
- The VMM connection to Operations Manager is disconnected before the upgrade and reconnected after it.
- Your SQL Server version has to be supported by the target VMM version.
Three hops in about nine weeks is possible, but it's tight. Depending on your environment, building a new, current environment and moving hosts across can be simpler than upgrading in place three times.
If you're upgrading, plan to land on System Center 2025. System Center 2022 moves to extended support on April 13, 2027.
Operations Manager: in-place hops or side by side
Operations Manager 2016 can't jump straight to Operations Manager 2025. Microsoft's upgrade guidance supports an in-place upgrade one step at a time: 2016 to 2019, 2019 to 2022, and 2022 to 2025. There is no supported in-place path from 2016 directly to 2022 or 2025.
If you want to keep the existing management group, plan those hops in order. For a distributed group, Microsoft upgrades management servers first, then gateways, consoles and agents, then the web console, reporting and Audit Collection Services. Back up the operational and data warehouse databases before you start, and confirm free space on the operational database.
The other supported option is a side-by-side (parallel) deployment. Keep the 2016 management group running, stand up a new management group on a supported version, upgrade agents, and multi-home them so they report to both groups until you finish migration and retire the old one. That path costs more hardware and setup, but it leaves the original environment intact while you prove the new one.
Pick the path from how much downtime you can accept and how many hops you can staff before January 11, 2027. Either way, land on a current release rather than stopping on an older hop that is already close to its own support cliff.
Sources: Microsoft Learn, "Upgrade System Center Operations Manager" (in-place targets and parallel/multi-home option); Microsoft Learn, "Upgrade agents in a parallel deployment". Checked November 9, 2026.
Upgrade the components in order
If you run more than one System Center component, Microsoft lists an upgrade sequence: Service Management Automation, Orchestrator, Service Manager, Data Protection Manager, Operations Manager, Configuration Manager, then Virtual Machine Manager. Following it avoids breaking the connections between components partway through.
Or decide what you no longer need
End of support is a good moment to ask whether each component still earns its place. Some common outcomes:
- Keep and upgrade. If VMM runs your Hyper-V fabric day to day, upgrade it on a planned path.
- Replace with Azure services. Monitoring, backup or disaster recovery can also move to Azure services instead of upgrading the 2016 tools. If backup and recovery are the question, see Azure Backup or Azure Site Recovery.
- Retire. Components with no active users or dependencies can be decommissioned once you've confirmed nothing relies on them.
Watch the SQL Server underneath
System Center databases often sit on SQL Server instances that are just as old. SQL Server 2016 reached end of support on July 14, 2026. Only paid Extended Security Updates keep it patched now, so check those instances as part of the same plan. Our SQL Server 2016 guide walks through the options.
A simple plan for the next nine weeks
- Inventory components, versions, servers and dependencies this week.
- Decide keep, replace or retire for each component.
- Back up databases and confirm restores before any change.
- Run the upgrade or new build in the order Microsoft lists, starting with a test or lower-risk environment.
- Update agents, reconnect integrations and confirm monitoring, backups and runbooks work before January 11.
If you'd like a second pair of eyes on your System Center estate, or help planning the upgrade path, our team can help.
Sources: Microsoft Lifecycle, "Ending support in 2027"; Microsoft Learn, "Upgrade information for Virtual Machine Manager"; Microsoft Lifecycle, "SQL Server 2016". All checked November 9, 2026.
Subscribe for the field notes
Join our community of 100+ IT professionals and get tech tips and BITSUMMIT updates once a month.


