IT Consultant Everyday Notes

Just some problems/solutions storage

Category Archives: WSUS

SCCM: Secondary SUP broke the primary one.

Recently I helped my Customer with a CMG configuration. The Clients are not hybrid joined, so we needed to use PKI infrastructure. For the Pilot the Customer decided to bring a new 2016 Server and configure it for SSL-enabled MP and SUP in the current HTTP environment (SCCM is installed on Windows Server 2012 R2).

Everything looked ok until the second SUP was prepared. We used as a guide and pointed the new WSUS to the primary database. That was a mistake – the secondary WSUS was installed ok, but the primary went down and could not start anymore. I tried to run wsusutil postinstall  with specified content folder and database, but WSUS was not happy anyway. wsusutil log revealed that the new 2016 WSUS actually updated WSUS DB schema and the old 2012 R2 WSUS could not access it anymore Smile. The error message suggested to upgrade WSUS to the same version…

Hopefully we had a backup of the DB, so I deleted the new WSUS, restored the DB with the old schema and re-run wsusutil postinstall content_dir=*MYFOLDER*  SQL_Instance_Name=*MySQLNAME*. After that the primary WSUS started and with some time SUP connected to it correctly.

After that I install a new WSUS on the 2016 server again, but this time I used a local folder for content and WID for the WSUS database. Next, I moved database from WID to my SQL server with a different name (since SUSDB already existed there) and tweaked registry settings in WSUS Server configuration to point it to the new location. step-by-step is here:

registry settings for SQL name and DB name (if the name was changed):


Lesson learned: it is always better to use the same OS version for site systems in your SCCM infrastructure.

SCCM: SUP is not working due to WSUS crash

Interesting case – WSUS built for SCCM SUP crashed regularly. It started from once in a month, after that more and more often and finally WSUS application pool could not stay and hour. Recommended solution was to recycle WSUS application pool. But that was not really a solution since permanent monitoring is required.

It turned out to be a known issue for SCCM 2012 (looks like SCCM CB is affected too) and Microsoft recommends to enlarge App Pool private memory to 4 (or in some cases to 8!) GB. Sounds a bit crazy for me but at least WSUS is up and running now.

More technical details in the following article:

SCCM: WSUS re-installation

I recently found a badly broken 2012 R2 WSUS in one of my Clients environment. After some troubleshooting I decided to re-install WSUS to save time.

Here are several points to remember during re-installation.

1. Not everything will be uninstall with WSUS

– Windows Internal Database (should be unchecked in Feature List during uninstallation or uninstalled using directions:

– Content of C:\Windows|WID should be cleared before the new install (otherwise you may have an error message “Synchronization in progress. Please cancel synchronization and rerun postinstall again.”  after the new WSUS will be installed

– you may decide to clean \WSUS folder created for the old WSUS

2. If you will use PowerShell for WSUS installation and wsusutill won’t be able to configure WSUSContent folder for you you may have an error saying Content folder cannot be accessed. In this case you may decide to add the content folder location to XML configuration script, the process is described here:

Unfortunately in my case postinstall failed regardless giving me weird: “System.InvalidOperationException — Client found response content type of ‘text/html; charset=utf-8’, but expected ‘text/xml’”. I tried to unistall MMC cache for WSUS, uninstall WID and WSUS, nothing helped.

Finally I uninstalled WSUS, WID, IIS, cleaned abovementioned directories, reboot the server and installed the WSUS back (enabled HTTP Activation under WCF for .Net 4.5 and  patched the server with the latest WSUS Updates). This time it successfully started.

SCCM: The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance

SCCM: Updates cannot be deployed due to WSUS improvements

Recently Microsoft published a WSUS update to support Windows 8 and Server 2012.  A lot of updates must be re-downloaded after that, otherwise they cannot be deployed.

Here is the way to fix it:

SCCM 2007: Apply hotfix described in