In place Server 2012 to 2012 R2 upgrade - SCCM 1606

[wing5wong]

Hi,

anyone experienced with this upgrade?

We attempted it earlier today, but it was unsuccesful - WSUS appeared to fail, and generic troubleshooting, iuncluding recreating the SUSDB didnt look to get the software update point going again.

 

Technet showed this as a supported upgrade (2012 to 2012R2) but im wondering if i missed something.

 

We have just the one machine running SCCM alongside WSUS

 

Any advice on this process?

[anyweb]

have you seen this post from Paul ? it's for 1602 but it should be the same scenario

[wing5wong]

I hadnt seen that article, but had seen similar recommending removing WSUS 3.0 before an upgrade from 2k8 to 2012R2

As this was 2012 to R2, i assumed it didnt matter (WSUS 6).

 

Will attempt the same procedure anyway and post back with results.

[SCCMentor]

Feel free to post any comments on my blog as well. I'd like to collate any notes from the field to assist people when running this in PROD environments. Cheers Paul

[wing5wong]

Hi Paul, i will do that.

Need to get some organisation wide deployments out over this holiday period but will attempt the upgrade again after that.

[sumyun]

Hi wing5wong, I just went through an OS upgrade from 2012 to 2012 R2 this past weekend in production, primary site server. SUSDB is on this primary site server, however all the SCCM SUPs are on remote hosts (Server 2012 R2).

 

For my upgrade, we stopped and disabled all SCCM services, SQL services, and IIS services on primary site server before the upgrade. I also stopped all SCCM services and WSUS services on MPs / SUPs servers. The upgrade was smooth without much issue. Just a bit hiccup during patching the server itself at post upgrade.

 

My steps to turn those services up at post upgrade:

1) SQL services on Primary site server

2) IIS services on Primary site server

3) MPs and WSUS services on remote servers

4) SCCM services on Primary site server

 

*side note, couple weeks ago, we went from Server 2008 R2 to Server 2012, it was a mistake by service provider, suppose to be straight to Server 2012 R2! So we manage to get it up and running on Server 2012 for a few weeks.