SCCM Upgrade is blocked on Windows Server 2012/2012 R2

SCCM Upgrade is blocked on Windows Server 2012

Starting with version 2403, the SCCM upgrade is blocked in the hierarchy that is running site roles on Windows Server 2012/2012 R2. In simple words, Windows Server 2012 and 2012 R2 operating systems won’t be supported for installing SCCM roles anymore.

Recently, Microsoft released Configuration Manager current branch update 2403. One of the prerequisites for installing this update is that you should not have site servers and roles running on Windows Server 2012 or 2012 R2. If you have these unsupported server OS in your setup, the 2403/2409 upgrade will fail.

The site servers and roles commonly include distribution points, Management points, servers running SUP role, etc. Configuration Manager administrators should prepare to upgrade their Windows servers to the next supported version, which is 2016, 2019, 2022, or 2025. This allows them to upgrade to version 2403 as well as future CB releases without any issues.

Install and Update Third Party Applications with Patch My PC
Install and Update Third Party Applications with Patch My PC

Also Read: SCCM client version, build numbers, and console versions

Console Notification for Server 2012/2012 R2 Upgrade

When you launch the console, you will see a notification that the Configuration Manager upgrade will be blocked on hierarchy servers running Windows Server 2012/2012 R2.

This console notification appears for everyone, regardless of whether or not you’re running site servers and roles on Windows Server 2012/2012 R2. This notification is displayed to administrators so that they are aware of the change and can plan to upgrade their server OS to a supported version.

Starting in version 2403, Configuration Manager upgrade will be blocked on Configuration manager hierarchy which are running on Windows server 2012/ 2012 R2 operating system. Upgrade your operating system immediately.

Configuration Manager Console Notification
SCCM Upgrade is blocked on Server 2012 and 2012 R2
SCCM Upgrade is blocked on Server 2012 and 2012 R2

If this notification doesn’t apply for your organization, you can dismiss it in the console. If you aren’t running site roles on Server 2012 or 2012 R2 across your hierarchy, you shouldn’t face issues during the SCCM 2403 upgrade.

Why SCCM Upgrade is blocked on Windows Server 2012/2012 R2

On October 10th, 2023, Windows Server 2012 and Windows Server 2012 R2 will enter the Extended Support Updates phase. Microsoft will no longer provide support for Configuration Manager site servers and roles installed on these operating systems. In other words, Microsoft will no longer provide free updates, bug fixes, or technical support for these operating systems.

Windows Server 2012 was released on 4 September 2012 and 2012 R2 was released on October 18, 2013. It’s been almost 12 years and as per the Microsoft lifecycle, these products have reached their EOL (end of life). Whether or not you use ConfigMgr, updating the old Windows servers to a supported version is a recommended practice that all businesses ought to adhere to.

Many organizations have not upgraded Windows Server 2012/2012 R2 to higher versions, either due to licensing costs or application compatibility issues. You will not receive security updates if, for whatever reason, you choose not to subscribe to extended support (ESU) for the servers.

Performing an in-place upgrade of Windows Server

To conclude, performing an in-place upgrade to the supported version will fix your 2403 upgrade issue if your site roles are operating on Server 2012 or 2012 R2. That’s the only way to get to version 2403 or later.

For SCCM roles that are running on Windows Server 2012 R2, you can perform an in-place upgrade to either Windows Server 2016 or Windows Server 2019. That is the upgrade path that Microsoft suggests.

Check out this super useful guide that includes information on supported in-place upgrade paths for Windows Server. Additionally, review the Windows Server OS that SCCM is compatible with.

Need more help?

If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.