Recently I made an attempt to upgrade the Operating System of a SCOM 2012 Management Server from Windows Server 2008 R2 to Windows Server 2012 Release Preview.
While I was on it I thought: let’s do the same thing with an SCCM 2012 Primary Site Server.
Common practice trying these scenarios is using a lab environment (using Hyper-V), mine is configured like this:
- The Site server database is hosted on a separate SQL 2008 R2 server running Windows Server 2008 R2, this machine remains untouched. The Site server database runs on a separate named instance;
- One SCCM 2012 Primary Site server, unrestricted internet access is available
The SCCM Primary has the following site roles installed:
- Application Catalog web service point
- Application Catalog website point
- Distribution point
- Management point
- Endpoint Protection point
- Software Update point
MDT 2012 Update 1 is installed as well.
For the Software Update point, WSUS is running locally on the SCCM 2012 Site server.
Setup is started in Windows after mounting the Windows Server 2012 Release Preview installation media.
During setup, I immediately received an error message which states that WSUS should be uninstalled before setup can continue. This message surprised me a little bit and made me think what impact this upgrade scenario might have in production environments. So I removed the Software Update point, uninstalled WSUS and restarted the server.
After restarting the server I was able to successfully do an in-place upgrade to Windows Server 2012 Release Preview.
Since WSUS was uninstalled I added the role manually afterwards, then I added the Software Update Point once more.
Before synchronizing for the first time after upgrading I noticed that all updates were expired so I had to run my initial synchronization again.
This is something that might have a great impact when organizations want to upgrade the OS on their SCCM infrastructures because it basically means the update repository might need to be rebuilt completely.
Conclusion is that upgrading the OS on SCCM 2012 Site servers will work but upgrading WSUS in the process in not possible. This is most unfortunate and I expect this feature to have a great impact on production environments.
Keep in mind though that this test was conducted in a lab environment. I don’t recommend doing this in a production environment at all until the RTM version of Windows Server 2012 is released and Microsoft considers running SCCM 2012 on Windows Server 2012 a supported configuration. Once Windows Server 2012 is added as a supported configuration on Technet upgrade scenarios become available.
At this time I’m not sure how other SCCM roles are affected by the upgrade. This requires some additional testing…