How to enable Microsoft Operations Manager 2000 and Microsoft Operations Manager 2005 to resolve security GUIDs and SIDs (904740)
The information in this article applies to:
- Microsoft Operations Manager 2005
- Microsoft Operations Manager 2000
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows registry INTRODUCTIONYou find the Security Identifiers (SIDs) instead of the Globally Unique Identifiers (GUIDs) in
error messages that appear in Microsoft Operations Manager (MOM) 2000 and MOM
2005. MOM 2000 and MOM 2005 cannot resolve GUIDs from security events. This inability to resolve GUIDs from security events is described in the following Microsoft Knowledge Base article: 295859 You may not see the same event description in MOM 2000 that you see in Event Viewer
This article describes how to enable MOM 2000 and MOM 2005 to resolve
security GUIDs and SIDs. MORE INFORMATIONWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. How to enable MOM 2000 to
resolve security GUIDs and SIDsThe hotfix that is described in the following Microsoft Knowledge Base article makes it possible for MOM 2000
to convert an SID to a GUID: 295859 You may not see the same event description in MOM 2000 that you see in Event Viewer
In MOM 2005, a registry value is required
to make MOM 2005 convert an SID to a GUID. After you install
the hotfix that is described in Microsoft Knowledge Base article 295859, set a value for the following registry key to
enable MOM 2000 to resolve security GUIDs and SIDs: HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical
Software\Onepoint\Configurations\<Config
Group>\Operations\Agent To enable MOM 2000 to
resolve security GUIDs and SIDs, set the following value for this registry key: Value name: ResolveGUID
Value type: REG_DWORD
Value
data: 1 A value of 1 enables MOM 2000 to resolve security GUIDs and
SIDs. A value of 0 (zero) turns off this functionality. How to enable MOM 2005 to
resolve security GUIDs and SIDsSet a value for the following registry key to
enable MOM 2005 to resolve security GUIDs and SIDs: HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical
Software\Onepoint To enable MOM 2005 to
resolve security GUIDs and SIDs, set the following value for this registry key: Value name: ResolveGUID
Value type:
REG_DWORD
Value data: 1 A value of 1 enables MOM 2005 to resolve
security GUIDs and SIDs. A value of 0 (zero) turns off this
functionality. Note Those two ResolveGUID registry values are not in the same
location. Therefore, the upgrade process does not re-create the registry value
in the new location if you upgrade a MOM 2000 agent to a MOM 2005 agent. You
must manually create the new registry value. Additionally, you must change the
ResolveGUID registry value on each MOM 2000 agent or MOM 2005 agent if you want
to resolve security GUIDs and SIDs.
| Modification Type: | Major | Last Reviewed: | 8/1/2005 |
|---|
| Keywords: | kbtshoot kbhowto kbinfo KB904740 kbAudITPRO |
|---|
|