After you upgrade to Microsoft Operations Manager (MOM) 2005 or install MOM 2005, the following symptoms occur:

• In the State view of the Operators Console, the MOM 2005 server's Last Heartbeat time is empty, and the server State is Unknown.
• If you run a Management Pack script, Event ID 9122 is logged many times in the Application log.
• MOM 2005 agents do not correctly receive configuration information from the MOM 2005 server. Therefore, agents might not receive heartbeat requests.
• MOM 2005 agents are not added to computer groups.
• Attributes are not collected from MOM 2005 agents.
• You cannot use a domain name that contains a period as a NetBIOS domain name on the Mailbox Access Account page in the Exchange Management Pack Configuration Wizard. For example, example.com is a NetBIOS domain name that contains a period.
• Event 21289 "Package failed to pass server security verification" is logged in the Application event log.

This problem occurs if you use a NetBIOS domain name that contains a period. For example, example.com is a NetBIOS domain name that contains a period. You might experience this problem when you upgrade a Microsoft Windows NT 3.51 or a Microsoft Windows NT 4.0 domain that has a period in the domain name to a Microsoft Windows 2000 Server or a Microsoft Windows Server 2003 Active Directory domain. MOM 2005 assumes that a domain name with a period is a Fully Qualified Domain Name (FQDN) in an Active Directory domain.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Operations Manager 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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 this specific problem. 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.

Prerequisites

You must apply this hotfix to each computer that meets the following criteria:

• The computer hosts a MOM 2005 management server.
• You manually installed the MOM 2005 agent on the computer.

Restart requirement

The MOM Service is restarted when you install this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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 tool in Control Panel.After you install this hotfix, the following files have the listed attributes or later:

Hotfix installation information

You must manually install this hotfix on all MOM 2005 management servers and all agents where the control level is set to none. To find agents where the control level is set to none, follow these steps:

1. Start the MOM 2005 Administrator Console.
2. Expand the Microsoft Operations Manager\Administration\Computers container.
3. Click Agent-managed Computers. You can sort the agents by clicking the Control Level column.

To install this hotfix, follow these steps:

1. Copy the Mom2005-rtm-kb889187-x86-ia64-enu.exe file to a local folder or a shared network folder that the MOM 2005 management computers can access.
2. Run Mom2005-rtm-kb889187-x86-ia64-enu.exe locally on each computer that meets the prerequisites for this hotfix. You can run Mom2005-rtm-kb889187-x86-ia64-enu.exe by using Windows Explorer or at a command prompt.

After you install this hotfix on the MOM 2005 management server, the Pending Actions container in the MOM 2005 Administrator Console contains update actions for agent computers. To update the agents that are listed in the Pending Actions container with a control level of full, follow these steps:

1. In the MOM 2005 Administrator Console, click the Microsoft Operations Manager\Administration\Computers\Pending Actions container.
2. In the results pane, right-click an agent computer where the control level is full, and then click Apply Patches Now.
3. If you do not want to use the management server action account, click Other, type the user name and password that you want to use, and then click OK.

To work around this problem, you can use the MOM 2000 original release version. The MOM 2000 original release version supports the period character in a NetBIOS domain name.

For more information about other problems that are resolved by Microsoft Operations Manager 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base: For more information about a related topic, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:

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 Operations Manager 2005 Service Pack 1.