Identifying GUIDs in the Registry

Although in Windows 2000 resource and group names as well as GUIDs are logged directly to the cluster log, the following procedure can still be valuable. Note that Regedt32.exe is required for this procedure.

Caution

Do not use a registry editor to edit the registry directly unless you have no alternative. The registry editors bypass the standard safeguards provided by administrative tools. These safeguards prevent you from entering conflicting settings or settings that are likely to degrade performance or damage your system. Editing the registry directly can have serious, unexpected consequences that can prevent the system from starting and require that you reinstall Windows 2000. To configure or customize Windows 2000, use the programs in Control Panel or Microsoft Management Console (MMC) whenever possible.

To find a GUID in the cluster registry key

1. In a registry editor, do one of the following:
   • Click the HKEY_LOCAL_MACHINE subtree.

   – Or –

   • From the menu, choose HKEY_LOCAL_MACHINE.
2. Open the HKEY_LOCAL_MACHINE subtree.
   • If the Cluster key is present, go to step 5.
   • If the Cluster service has not started since the last reboot, load the Cluster registry key.
3. To load the Cluster hive (the Cluster key and its subkeys):
   • Click the HKEY_LOCAL_MACHINE subtree.
   • From the registry menu, select Load Hive.
   • Navigate to the cluster directory. (The cluster directory is probably %SystemRoot%\Cluster\).
   • Select CLUSDB (not Clusdb.log).

   The Load Hive dialog box appears and prompts you to supply a key name.

4. Type:

   Cluster

5. Open the Cluster key.

   GUIDs are located in the Groups, NetworkInterfaces, Networks, and Resources subkeys.

6. Open each of these subkeys to find the GUID of interest.
7. Open the GUID, and note the entry Name.

© 1985-2000 Microsoft Corporation. All rights reserved.