![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 39%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBA%3C/text%3E%3C/svg%3E)
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
1,031 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
For SCCM version 2403, the supported SQL Server versions are SQL 2017, SQL 2019, and SQL 20221. Please ensure that you’re running a 64-bit version of SQL Server to host the site database2.
As for the Operating System, starting from SCCM version 2403, Windows Server 2012/2012 R2 operating system site system roles are not supported345. Therefore, it’s essential to upgrade your operating system to a newer version before attempting the SCCM upgrade5.
Here are the general steps for migrating SCCM:
Plan for Migration: Familiarize yourself with sites and hierarchies in Configuration Manager1. Install a Configuration Manager current branch hierarchy to be the destination hierarchy before you migrate data from a supported source hierarchy1.
Set Up Management Features: Set up the management features and functions that you want to use in your destination hierarchy before you start to migrate data1.
Plan for Overlap: Plan for overlap between the source hierarchy and your destination hierarchy1. Assign each new client in the destination hierarchy to a specific site in that hierarchy instead of using automatic site assignment1.
Migration Planning: Use the following articles to help you plan how to migrate a supported source hierarchy to a Configuration Manager destination hierarchy1:
- Prerequisites for migration
- Administrator checklists for migration planning
- Determine whether to migrate data to Configuration Manager current branch
- Plan a source hierarchy strategy
- Plan a client migration strategy
- Plan a content deployment migration strategy
- Plan a client migration strategy
- Plan a source hierarchy strategy
- Determine whether to migrate data to Configuration Manager current branch
- Administrator checklists for migration planning
Please note that these are general steps, and the exact process may vary based on your specific environment and needs.