ConfigMgr CB 1602 Server 2008 R2 in-place upgrade to 2012 R2

One of the new features in the newly released version of Configuration Manager CB 1602 is that in-place upgrade of the Server OS from 2008 R2 -> 2012 R2 is now supported. This will save a lot of time and money for many customers out there, great that it is finally supported!

I upgraded my old Server 2008 R2 test environment to Configuration Manager CB 1511 which has been with me since Configuration Manager 2012 RTM was released. The upgrade of the OS was pretty straight forward, IMPORTANT!! WSUS MUST be uninstalled before the upgrade, more information can be found here: failure to do this will have serious results according to the documentation.

My setup looks like this, I actually cheated and configured a new server running server 2012 R2 with WSUS and the Windows 10 hotfix and changed to that as the active WSUS server before the upgrade, and Yes I know it is not supported 😉 Will see if I can document the steps for a setup with a local SQL and SUP as well.

Primary Site Server:
-Server 2008 R2
-MP, DP and so on… no SUP

Site System:
-Server 2012 R2

SQL Server:
-Server 2012 R2
-SQL Server 2012

Here is how I did it, If the SUP/WSUS and SQL is installed on the same server there are a few additional steps which is not included here.

1. Backup, Backup, Backup.. make sure you have a WORKING backup in case anything goes wrong.

2. Uninstall antivirus from the server if not System Center Endpoint Protection is used then there is no need, this is just to be on the safe side for the upgrade itself.

3. Restart Server

4. Uninstall WSUS, in my case the admin console only otherwise the full product !Important must uninstall WSUS! Read the article above.

5. Disable Configuration Manager services that are set to start automatically, to be able to sort out any issues after the upgrade with drivers e.t.c before ConfigMgr is started.


6. Restart Server

7. Upgrade Server OS using in-place upgrade, make sure to use the updated Server 2012 R2 media and make sure to review any warnings that you are prompted with.

8. Verify that the upgrade was successful, review event logs and start IIS Manager and review the IIS settings, my IIS was disabled, see note below.

9. Install WSUS Admin console (or full WSUS depending on local or remote SUP)

10. Install Hotfix KB 3095113, that adds Windows 10 Upgrade support

11. Start Configuration Manager Services and change startup to Automatic for the services that we changed above.

12. Verify that everything is working, System Status, Component status…

13. Install Anti-virus

14. Install all Software Updates for Server 2012 R2, I was struggling when to do this but I decided to do it after I verified that Configuration Manager was working to make potential troubleshooting easier.

That is how I did it and it seems to be working just fine. I ran into a couple of things with the OS upgrade itself, no big deal at all.

1. IIS and WAS was disabled during upgrade due to “incompatibility with the current setup”, I have a lot of test websites, webservices and stuff so I assume that was why, I cleaned up the IIS from old websites. I had to change the startup type of the services to automatic and then start them, then everything worked fine.


2. .NET Optimization ran for about 15 minutes consuming a lot of CPU, check that before you freak out that the system is slower 😉

3. CCMRepair was also launched automatically which also consumed some CPU.

That is how I did it.


Add a Comment

Your email address will not be published. Required fields are marked *