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: https://technet.microsoft.com/library/hh852345.aspx 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
-SUP
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 https://support.microsoft.com/en-us/kb/3095113
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.
Installing multiple sccm client hotfixes
Error handling in TS without MDT using OSDBackground
SCCM 2007 Report: Windows 7 computers without SP1
About Author
Jörgen Nilsson
Add a Comment
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Great post! Anxiously waiting for the additional steps for local SQL and SUP as I’m in this exact situation.
Any chance you could post the missing steps for local SQL with local SUP? I’m looking to go from 2008R2 to 2012R2.
Thanks!
Yoour BCP will include RTOs (Restoration Time Goals)
that outline the crucial time interval during which enterprise capabilities should be restored.
Just to clarify, we need to be at SCCM CB 1602 on 2008R2 before we run the upgrade to get us to 2012 R2 correct?
Correct!
/Jörgen
Great post, updated same as you and all worked a treat.
“Any chance you could post the missing steps for local SQL with local SUP? I’m looking to go from 2008R2 to 2012R2.
Thanks!”
ME TOO! ! !
Hi Jörgen,
so you we’re running SCCM 1602 on an Windows 2008 R2 server?
I’m currently at SCCM 2012 R2 SP1 CU3 on Windows 2008 R2 and I’m planning an in-place upgrade to 1511. Do I need to do an in-place upgrade of my OS first or do I need to do the SCCM in-place upgrade prior?
thx
HI,
You must upgrade to ConfigMgr 1602 before you can upgrade the server OS on the site server. It is not tested and not supported to do so before 1602.
/JÖrgen
Thanks for your response Jörgen.
This was my approach:
– in place upgrade Server2008R2 to Server2012R2
– download&install all WUpdates
– install WADK10 (was already installed)
– install KB3095113 (gives Error, found out I needed 2 other KB’s first, but also Error, so skipped this)
– in place upgrade SCCM 2012 R2 SP1 CU3 to 1511 (8325)
– upgrade through new servicing channel to 1602 (8355) -> first pre production collection
Cheers,
Harm
Hi
I just completed the in-place OS upgrade (CM on 1602) according to your directions, and now PXE boot is no longer working.
I redistributed content, reinstalled roles of one DP to see if that would help, no luck. Any advice?
Here is part of my smspxe.log:
Failed to get information for MP: XXXXXXX. 80004005. SMSPXE 5/25/2016 9:06:03 AM 2160 (0x0870)
reply has no message header marker SMSPXE 5/25/2016 9:06:03 AM 2160 (0x0870)
Failed to send status message (80004005) SMSPXE 5/25/2016 9:06:03 AM 2160 (0x0870)
Failed to send the status message SMSPXE 5/25/2016 9:06:03 AM 2160 (0x0870)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 5/25/2016 9:06:03 AM 2160 (0x0870)
PXE Provider failed to process message.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 5/25/2016 9:06:03 AM 2160 (0x0870)
Hi Jörgen,
If we have 2 servers, a Primary server and dedicated SQL server, do we need to upgrade both to win2012 R2 or only the primary site?
Has this been tested with Server 2016? I realize it is not RTM but this will be H U G E ! ! I had heard that this was going to be an option to get to 2016 so I was stoked to see this post!!!
Hi,
Not yet, but I think the intention is to support it.
/Jörgen
Hi
We have SQL on the same box upgraded to 2014 all good .1602 is already done .
What abt any SQL instance do i need to disable that when i am doing inplace Windows OS upgrade .
Hi,
No need to stop it, I didn’t
/Jörgen
Hi,
I am in the process of getting primary site server upgrade to Server 2012 R2. Only server not running 2012 R2. Do you still have to uninstall WSUS if it’s not installed on primary site? WSUS role is installed on Server 2012 R2 and is the SUP in ConfigMgr 1602. Here is a quick break down:
Primary Site: 2008 R2
Site System
Service Connection point
Site Server
Component server
DP
Site System: 2012 R2
SUP
Site System
Component
SQL-Server: 2012 R2/SQL 2012
Site System
Reporting services
site db
component
Plus a few more acting as DP’s
Hi,
The WSUS admin console is, so yes I would uninstall it.
/Jörgen
Sorry, got confused with the two replies. In the case of SUP on separate server already running 2012 R2 and primary server 2008 r2 not having WSUS role installed, do I have to remove WSUS from 2012 R2 server? Thanks.
Hi,
You still have the WSUS admin console on the Primary site server at least, so yes uninstall it.
/Jörgen
Hi All.
We’ve inherited someone else’s SCCM setup as they left our company a few years back. We brought in someone else since then however he has since left after being here a few years. This was just one of his responsibilities. Now I’m trying to get us up to date…and I’ve not been a SCCM admin guy… more on the lines of a SUP and App deployment person.
I’ve run across some issues since upgrading from Server 2008R2 to 2012R2. I upgraded a few months ago from SCCM 2012 R2 –> 1511 –> 1602 –> 1606. No real issues there.
Yesterday, I upgraded SCCM01 and SCCM02 (below) to Server 2012 R2. I removed WSUS from 01 and 02, disabled and stopped the SCCM services on both, made sure no AntiVirus was installed, rebooted both, then upgraded the OS.
After the upgrade was complete, I installed full WSUS on 02 and the console on 01 and have had trouble with WSUS and the Enrollment point ever since. I’m waiting for my sync again for WSUS which will not be done until tomorrow so I figured I would ask about the Enrollment Point problem. Please see below for the error.
Guide used:
https://ccmexec.com/2016/03/configmgr-cb-1602-server-2008-r2-in-place-upgrade-to-2012-r2/
SCCM01 – Primary Site: 2012R2
-Component Svr
-Distribution Point
-Enrollment Point
-Management Point
-Service Connection Point
-Site Server
-Site System
SCCM02 – Site System Server: 2012R2
-Asset Intelligence
-Component Server
-Endpoint Protection Point
-Reporting Svcs Point
-Site System
-SUP
SCCM03 – Site System Server: 2008R2
-Component Server
-Distribution Point
-Enrollment Proxy Point
-Management Point
-Site System
———————————————————
ERROR IN COMPONENT STATUS–>SMS_ENROLL_SERVER COMPONENT
———————————————————
Enrollment Point Control Manager detected that the Enrollment Point is not responding to HTTP/HTTPS requests. The http status code and text is 500, Internal Server Error.
Possible cause: Internet Information Services (IIS) isn’t configured to listen on the ports over which Enroll Service is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which ENROLLSRV is configured to use.
Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
I’m not clear on this as I don’t deal with IIS.
Any guidance would be greatly appreciated.
Hi we used the same steps as above and no major issues on our Primary Site Server. However our SQL server is still running on
-Server 2008 R2
-SQL Server 2008 R2
Is there an upgrade path for this? Thanks
I am already at 1606 with Windows Server 2012. I would like to upgrade to Windows Server 2012 R2. Do I need to uninstall WSUS since I am already on Windows Server 2012? I can’t seem to find any good info related to upgrading from 2012 to 2012R2.
Thanks,
Mike
I upgraded a 2008 R2 server to 2012 R2 and had the following issues. Lost WMI permissions for the console, app catalog stopped working and had issues with wsus syncing. Website links to fixes for these issues are
https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure
https://forums.iis.net/t/1149768.aspx
https://blogs.technet.microsoft.com/configurationmgr/2015/03/23/configmgr-2012-support-tip-wsus-sync-fails-with-http-503-errors/
I hope this information helps someone else.
I upgraded my Primary server on 2012R2 to 1702. I have DP’s that are just running the DP roll that are on OS 2008 R2. Can I in-place upgrade those OS’s for the DP’s from 2008R2 to 2012 R2? I’ve read mixed answers.