I noticed that the scheduled backup of ConfigMgr can conflict with the installation of WSUS. When you have WSUS 3.0 SP1 installed on the same machine as your ConfigMgr Site you can, at random occassions, get problems with your WSUS installation. This is what happens: During the execution of the ConfigMgr Backup it does some kind of a healthcheck. When it then notices that the SUP/WSUS is not responding good it will try to do an repair action of WSUS. At this point the problem starts, bacause the installer of WSUS 3.0 SP1 doesn’t have a repair function, so WSUS will get uninstalled… After this has happened you can get errors like “Sync failed: WSUS server not configured. Source: CWSyncMgr::DoSync SMS_WSUS_SYNC_MANAGER” in the ConfigMgr Site Status.
There are two ways to workarround this:
- Disable the backup of ConfigMgr (not really an option).
- Make sure that the ConfigMgr Backup can’t find the WSUS 3.0 SP1 installer. You can do this by editting (just change the name or the location of the MSI) the following registrykey [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<Random number>\InstallProperties] “LocalPackage”=”C:\\WINDOWS\\Installer\\<Random number>.msi” “DisplayName”=”Microsoft Windows Server Update Services 3.0”
They say it is getting solved in WSUS 3.0 SP2. When your interested in that you can join the RC Program on: https://connect.microsoft.com/site/sitehome.aspx?SiteID=110.