To register your Cluster Administrator extension DLL, call REGCLADM.EXE followed by the complete path to the DLL as follows:
regcladm path
Next, register DebugEx so that this extension is available to aid in debugging your resource DLL. To register DebugEx, enter:
regcladm debugex.dll
If DebugEx has already been registered, the Debug tab will appear as one of the tabs on the property sheet of Cluster Administrator.
There are two parts to the registration of a Cluster Administrator extension.
The first part is registering the extension with the cluster. The DllRegisterCluAdminExtension entry point accomplishes this registration. DllRegisterCluAdminExtension causes the AdminExtensions property to be stored in the cluster database and modified if necessary. The CLSID for the extension is placed in the AdminExtensions value if it is not already present.
The second part is registering the extension with COM. The DllRegisterServer entry point accomplishes this registration. This causes a key for the ProgId (for example, CLUADMEX.Standard) to be created below HKEY_CLASSES_ROOT and a key for the CLSID to be created below HKEY_CLASSES_ROOT\CLSID.
REGCLADM calls both DllRegisterCluAdminExtension and DllRegisterServer. Setup programs that install these extensions will also need to call these two entry points. If your setup program is run on a cluster node, call both entry points. If your setup program is run on a client (for example, a non-cluster node, such as where Cluster Administrator is installed), just call DllRegisterServer.