This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. An event contains certain fields that are formatted as an ObjectGUID. The ObjectGUID requires a lookup to Active Directory to obtain the distinguished name of the object. A new event is generated when the Audit Collection Service (ACS) forwarder obtains the event. However, immediately after the new event is generated, the lookup value in Active Directory may not be available. In this scenario, a lookup failure occurs, and the forwarder forwards the event that contains the ObjectGUID instead of the distinguished name to the collector.
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:
971541 Description of System Center Operations Manager 2007 Service Pack 1
This hotfix provides a registry key that can configure the forwarder to wait for a specified time period and performs a lookup retry before forwarding the event to the collector. 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.
You must have System Center Operations Manager 2007 Service Pack 1 installed. Additionally, this hotfix must be applied to each computer that meets one of the following criteria:
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 Manually Installed Agent (Discover-based agent deployment not used)
You do not have to restart the computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix does not replace a previously released hotfix.
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 SP1 X86
System Center Operations Manager 2007 SP1 X64
To extract the hotfix files that are contained in this hotfix, follow these steps:
Copy the SystemCenterOperationsManager2007-SP1-KB954329-X86-X64-ENU.MSI file to either a local folder or to an available network shared folder.
Run the SystemCenterOperationsManager2007-SP1-KB954329-X86-X64-ENU.MSI file locally on each computer that meets the predefined criteria.
Note You can run the SystemCenterOperationsManager2007-SP1-KB954329-X86-X64-ENU.MSI file from either Windows Explorer or at a command prompt.
On a computer that has the Operations Manager console feature installed, click Start, point to All Programs, point to System Center Operations Manager 2007, and then click Operations Console.
Select the Administration view, expand Administration, expand Device Management, and then click Pending Administration.
In the Pending Administration folder, approve agents that are the Agent Requires Update type.
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.
How to create a required registry key on affected agents
This hotfix lets you create a new registry key on affected ACS Forwarders. This registry key allows for a retry on any ObjectGUID that cannot have its distinguished name resolved on the first attempt. This registry key must be created on all affected ACS Forwarder roles because it does not exist by default. A suggested initial retry value in milliseconds is provided. The retry value may have to be tuned, depending on the environment.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To create the required registry key on affected ACS Forwarder roles, follow these steps:
On an ACS Forwarder role, use Registry Editor to locate the following registry subkey:
Stop and then restart the Operations Manager Audit Forwarding Service from the Services MMC snap-in so that the value can take effect.
Note The RetryDelay value is the number of milliseconds (ms) that the forwarder will wait before the operation is retried. An initial value of 100 ms is suggested. If the initial value is unsuccessful, increase the value 20 ms at a time, restarting the Operations Manager Audit Forwarding Service every time for the new value to take effect. If the RetryDelay value is too large, unwanted ACS Forwarder performance issues may occur. Keep the value as low as possible for successful distinguished name resolution.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For a list of issues that are fixed in Microsoft System Center Operations Manager 2007 R2, refer to the following article in the Microsoft Knowledge base:
971410 List of issues that are fixed in System Center Operations Manager 2007 R2