On a computer that is running Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1), unexpected alerts may be generated. Or, dependency monitors may indicate an incorrect state based on the Health Rollup policy and on the state of its contributing monitors.
This problem occurs because of a race condition during the monitor registration process.
This fix is contained within the Microsoft System Center Operations Manager 2007 Service Pack 1 update. To see a list of issues are fixed and how to obtain the cumulative rollup, refer to this article in the Microsoft Knowledge Base:
Description of System Center Operations Manager 2007 Service Pack 1
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note
If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note
The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must have System Center Operations Manager 2007 SP1 installed. Additionally, you must apply this hotfix must to each computer that meets one or more of the following conditions:
- Hosts a Microsoft Operations Manager root management server
- Hosts a Microsoft Operations Manager management server
- Hosts a Microsoft Operations Manager gateway server
- Hosts a Microsoft Operations Manager manually installed agent (discovery-based agent deployment was not used)
If you apply this hotfix package on a Windows Server 2008-based computer on which User Account Control (UAC) is enabled, you must run the hotfix package installer at a command prompt that you generate by using the Run as Administrator
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time
item in Control Panel.
System Center Operations Manager 2007 Service Pack 1, x86 version
|File name||File version||File size||Date||Time||Platform|
System Center Operations Manager 2007 Service Pack 1, x64 version
|File name||File version||File size||Date||Time||Platform|
To apply this hotfix, follow these steps:
- Copy the SystemCenterOperationsManager2007-SP1-KB958490-X86-X64-ENU.msi file to either a local folder or an available network shared folder.
- Run the SystemCenterOperationsManager2007-SP1-KB958490-X86-X64-ENU.msi file locally on each applicable computer that meets the predefined criteria.
- You can run the SystemCenterOperationsManager2007-SP1-KB958490-X86-X64-ENU.msi file from either Windows Explorer or at a command prompt.
- The Operations Manager services will be restarted while the hotfix is being applied.
By applying this hotfix, you will update both Operations Manager server role files and agent role files. After you apply this hotfix, agents that were previously deployed by using the Discovery Wizard will appear in the Pending Management node awaiting agent update approval. By approving agent updates, you will automatically apply the hotfix.Important note
By applying this hotfix, you will reset the Health Service configuration state on each management server or on each agent on which it is installed. Therefore, make sure that you review any unhealthy states that are listed on the Operations Manager console. Also make sure that you resolve all possible causes of these unhealthy states before you apply the hotfix. Failure to do this may cause event-based monitors to be incorrectly reset to a healthy state, and it may also cause related alerts to be incorrectly reset. In this situation, you may lose visibility into issues that affect the monitored environment. Finally, probe-based monitors in an unhealthy state may be reset, and therefore the correct health state of these monitors will not be indicated until the next state change occurs.
Before you apply this hotfix, you should consider its ramifications, its effect on company processes and procedures, on connected systems (connectors, ticketing applications, and SDK applications), and on communications with Network Operations Center (NOC) personnel. The whole Management Group state will be affected by this hotfix. We strongly advise that you plan ahead for this hotfix installation and that you test agent update approval in a controlled rollout. We recommend this approach because the overall monitored state within the management group may take time to stabilize and to provide a true picture of the management group on the Operations Manager console, on the Web console, or in Health Explorer State views.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft System Center Operations Manager 2007 R2.