SCCM Upgrade is blocked on Windows Server 2012/2012 R2

If you still have ConfigMgr Site Servers running on Server OS 2012/2012 R2, plan for a server upgrade before SCCM 2403 blocks the upgrade.


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.

https://forum.goddesszex.dev/showthread.php?tid=10013

http://www.xcosmic.net/rsf/showthread.php?tid=179

https://forum.l2endless.com/showthread.php?tid=10359

https://foro.muelendhir.com/showthread.php?tid=28649

https://forum.mbprinteddroids.com/showthread.php?tid=1044

https://forum.21up.co.uk/showthread.php?tid=556&pid=565

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.


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.

https://dev-forum.vmssoftware.com/viewtopic.php?t=356701

https://www.thewbs.net/pages/forums/showthread.php?tid=3503&pid=3679#pid3679

https://sportsreptile.site/thread-6146.html

https://hondaikmciledug.co.id/HRIS/showthread.php?tid=5842

https://hawkinsmotorcoach.com/forums/thread-1846.html

https://angelelite.de/showthread.php?tid=2704

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.

https://forum.technologyrobone.com/Thread-fkbobw-hfinfajej

https://www.mircalemi.net/showthread.php?tid=4131&pid=13698#pid13698

https://rokforall.altervista.org/showthread.php?tid=15181

https://themastergames.com/mybb/thread-odwgao-hseozxned

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.

Comments

Post a Comment

Popular posts from this blog

8 Ways to Fix Windows Update Error 0x80070643

 Windows update error 0x80070643 stops you from installing the latest Windows updates. Learn why this error occurs and how can you resolve it with multiple solutions. In this post, I will show you how to fix the Windows Update error 0x80070643 that occurs when you attempt to install the latest updates on Windows 11/10 devices. The error 0x80070643 can be resolved using different methods, which will be covered in this guide. I ran across issue 0x80070643 on my Windows 11 PC when I was downloading the most recent updates. The update was stuck installing for a few minutes and finally resulted in error 0x80070643. https://stock.talktaiwan.org/index.php?topic=478832.0 https://stock.talktaiwan.org/index.php?topic=407059.0 https://stock.talktaiwan.org/index.php?topic=427920.0 http://forum.analysisclub.ru/index.php?topic=128627.0 http://forum.analysisclub.ru/index.php?topic=142620.0 http://forum.infinite-soul.org/viewtopic.php?f=64&t=9756 https://rostovbike.ru/thread-1012.html https://foru
Read more

8 Ways to Fix Windows 11 Upgrade Error 0x800F0830-0x20003

Multiple solutions to resolve 0x800F0830-0x20003 error that occurs during Windows 11 installation or upgrade in the SAFE_OS phase during INSTALL_UPDATES operation. If you are encountering the error 0x800f0830-0x20003 when upgrading to Windows 11, this tutorial covers the solutions to resolve this error. An error 0x800F0830-0x20003 prevents the upgrade process on Windows 10/11. This error occurs during the SAFE_OS phase during the INSTALL_UPDATES operation. If you don’t resolve this error, you’ll never be able to upgrade your Windows to the next version. Installing Windows 11 or upgrading it from Windows 10 is a smooth process, and you can use multiple methods to upgrade to Windows 11. However, you may encounter several errors during the upgrade, either due to hardware being incompatible, incompatible apps, or other reasons. We recommend referring to the Microsoft article on Windows 11 upgrade and installation error codes. https://forum.goddesszex.dev/showthread.php?tid=17913 https://fo
Read more

Enable/Disable End Task in Taskbar on Windows 11

You can now close all your apps from the taskbar on Windows 11 without having to use Task Manager. Learn how to enable or disable End Task in the taskbar on Windows 11 using multiple methods. The End Task in Taskbar feature on Windows 11 allows you to quickly terminate apps directly from the taskbar without having to use Task Manager. In this article, I will demonstrate multiple methods to enable or disable the taskbar end task option on Windows 11. Starting with Windows 11 version 23H2, you can enable and use the End Task option to terminate unresponsive applications directly from the Taskbar. You don’t need to open the task manager on Windows 11 to end the processes any more. Unfortunately, not many users are aware of this extremely helpful feature because it is hidden under the “For Developers” section. There are situations when you have no choice but to use Task Manager to forcefully end your unresponsive apps. In some cases, I noticed that even my task manager was frozen and faile
Read more