First published on TECHNET on Feb 25, 2009
UPDATED QFE NOW AVAILABLE: 4/8/2009:
http://www.microsoft.com/downloads/details.aspx?FamilyID=f82ef6b3-a08e-4295-b9e3-fb78a74aefa8&di...
We have found a problem with the IIS Modules QFE and working on fixing it. In the meanwhile, the binaries for the QFE have been removed from the download site. The issue is in the setup code which causes the SDK and Configuration services on the RMS to be stopped and disabled. The setup code of the QFE may also modify the follow registry value on the RMS: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft Operations Manager3.0Server Management Groups<MG NAME>IsRootHealthService to 0.
If you installed the QFE on your RMS server and seeing the SDK service and Config service as disabled, you need to do the following to resolve the issue:
1 – If the registry key mentioned above was modified, set it back to 1
2 – Enable the SDK and Config services to their previous startup state (Automatic, except for the case of Clusters which should be Manual)
3 – Start the SDK and Config services.
*Update March 10th - Please note the following key may also be impacted on any Management Server (non-RMS). HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft Operations Manager3.0Server Management Groups<MG NAME>IsServer. This DWORD value should be set to 1 for any Managment Server (non-RMS). Thanks to Raphael Burri from the OpsMgr community for this additional information.
