Tag Archives: console

SCCM – Server OS upgrade from 2008R2 to 2012R2

I recently completed an OS upgrade of my environment from 2008R2 to 2012R2 on a CAS>Primary Hierarchy. I found the documentation a bit limiting especially post install as without a doubt there are some issues you are bound to run into. So what is a good way going about the process? I broke this up into 3 main steps

  1.  Prepare the OS Drive by cleaning up data (a Windows.Old Directory is stored post upgrade that consumes a lot of space)
  2. The OS upgrade itself. (If using a VM, Snapshot!)
  3. Post upgrade Tasks and remediation

1. Preparation

  • Check Disk space of OS Drive
  • Delete old log files in inetpub.
  • Install desktop experience so that you get the Disk cleanup utility to use post upgrade.
  • If using a static IP, take note of these details as the upgrade will change to DHCP
  • Uninstall WSUS 3.0 SP2
  • Remove the Software Update Point Role from SCCM
  • Stop the SCCM site using Presinst.exe /StopSite (Stopping the CAS server will stop the whole hierarchy)
  • Create a snapshot here if you have a VM

2. OS Upgrade

Just like any OS upgrade, however you are doing it. In this case with a VM the ISO was mounted the the in place upgrade was kicked off.

 

3. Post upgrade:

  • Ensure the Windows Deployment Service is started and running for the following site system roles (this service is stopped during upgrade):
    • Site server
    • Management point
    • Application Catalog web service point
    • Application Catalog website point
    • Ensure the Windows Process Activationand WWW/W3svc services are enabled, set for automatic start, and running for the following site system roles (these services are disabled during upgrade):
  • Site server
  • Management point
  • Application Catalog web service point
  • Application Catalog website point

Ensure each server that hosts a site system role continues to meet all of perquisites for site system roles that run on that server. For example, you might need to reinstall BITS, WSUS, or configure specific settings for IIS.

Below are the common issues I came across and the fix for each.

Application Catalog does not connect

http://blogs.microsoft.co.il/u-btech/2016/05/25/sccm-1602-application-catalog-is-broken-after-windows-server-inplace-upgrade/

After upgrading SCCM OS the application server config point stopped working. This is due to .Net 4.5

Cannot connect to the application server error message below.

When looking in the Site Component node, I could see that the SMS_AWEBSVC_CONTROL_MANAGER possess a warning sign which was in fact a several error notifications with the following description:

After installing .Net framework 4.5.2,  rebooting the server I still had that same error message.

Again, browsing to  http://localhost/CMApplicationCatalogSvc/applicationofferService.svc resulted in providing me a lead to an error in a line (which can be a result of one of my troubleshooting steps before writing these words) fixing a line in the file: “C:\Program Files\SMS_CCM\CMApplicationCatalogSvc\Web.config”

from:

<serviceHostingEnvironment>
<baseAddressPrefixFilters>
<add prefix=”HTTP://SCCM.U-BTech.COM:80“/></baseAddressPrefixFilters>
</serviceHostingEnvironment>

To:

<serviceHostingEnvironment>
<baseAddressPrefixFilters><add prefix=”HTTP://SCCM.U-BTech.COM:80″/></baseAddressPrefixFilters>
</serviceHostingEnvironment>

And performing IISReset was the last piece in that puzzle that fortunatly solved the problem.

Console not working Remotely

Post upgrade the WMI permissions get overwritten thus the console does not work remotely any longer.

On the site server launch wmimgmt.msc console.

Then browse to root / SMS and root / SMS / site_[site name]. Add the SMS Admins local group back to both of these, and make sure they have Execute Methods, Provider Write, Enable Account, and Remote Enable allowed.

 

WSUS High CPU/Memory Usage

I also had multiple issues with WSUS 4.0 post upgrade. Most importantly was to patch the OS so that it is current. Also had to apply the steps in my post below to resolve the issue.

IIS w3wp.exe 100% CPU, WSUS and SCCM

Happy Upgrading!!