Tuesday, November 25, 2008 2:44 AM
I have a Primary Site server in mixed mode with WSUS. WSUS is configured at port 8530. Everything works normally, until the server is rebooted. When that happens it "appears" as if WSUS is uninstalled. The IIS site, the Admin console and the interfaces SCCM is using all disapper. SCCM throws a 6600 error on the WSUS Config Mgr.
I've had this happen twice now. There is a discussion on this over at MyITForum, but there doesn't appear to be any resolution.
Tuesday, November 25, 2008 3:29 AMHello,
You could have added the link to the MyITForum discussion so that we do not go over the same ideas here too, but offer something new with other perspectives.
It is not clear if what is uninstalled in your environment is the role in SCCM, the configuration properties of WSUS or the application itself.
However, if it is the application, WSUS is installed as an MSI, you should be able to check the MSIInstaller events in your event viewer, probably see what triggers the deinstall and when it happened.
That might give clues to why it is removed, but it sounds like irregular Windows Installer behaviour, if the installation was completely successful, missing components should trigger a self-repair otherwise there should be a rollback if Windows Installer cannot ensure all components have the integrity for the consistent availability of the application.
Hope this sheds more light on your situation.
Tuesday, November 25, 2008 7:46 AMThis issue has already been discussed here in the forums (unfortunately you don't see anything on the server that gives you a hint why it's uninstalling). The product group is aware of this issue and working on a hotfix as far as I know. Stay tuned.
Tuesday, November 25, 2008 12:39 PM
Thursday, November 27, 2008 7:07 AMDont you worry Bob, there are many who are sailing in the same boat, just keep any eye on your servers specially during critical patch release.Cheers,Hemant
Wednesday, December 03, 2008 10:57 AMCode Snippet
Lets first try and understand what is happening:
1. WSUS was installed as a SUP for SCCM and randomly being removed;
2. The WSUS seems to be uninstalled by MSI, which is called when SCCM is unable to find the WSUSApiFeature component.
3. The call to MSI is an attempt to fix the missing WSUS component.
4. Unfortunately, WSUS has a known issue with MSI repair that will always fail if a repair is call which results in some of the WSUS web directories being removed which requires WSUS to be reinstalled to restore functionality.
When Windows Installer trying to “repair” WSUS, it calls WSUS MSI file. To avoid WSUS being removed by “hiding” the WSUS MSI file.
The WSUS installer file information is saved at:
"DisplayName"="Microsoft Windows Server Update Services 3.0"
We may find the file, e.g. C:\WINDOWS\Installer\9c9a4.msi and rename it. When MSI could not find the C:\WINDOWS\Installer\9c9a4.msi, it is supposed to stop repairing WSUS and not remove it.
Hope this helps you guys!
Wednesday, December 10, 2008 8:08 PM
Will this posting be updated when Microsoft has a hotfix for this issue? I just installed WSUS for the third time on one of our sites, after it disappears. The only good thing is that I learn to look before we deploy our patches, so it is getting easier. Would definitely like to know when a hotfix exists.