[This is preliminary documentation and subject to change.]
As noted elsewhere, the snap-in's nodetype is identified by a GUID that describes the node's overall type such as whether it's a user, a machine, a domain entry in a DNS database, or something else. The following example shows a sample entry for the NodeTypes key, and the subkey entries associated with extensions that may be required beneath it.
Incidentally, do not use these GUIDs for your own applications. They are examples only.
HKEY_LOCAL_MACHINE\Software\Microsoft\MMC\NodeTypes
{12345601-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Log object"
Extensions
NameSpace
{19876201-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Alert SnapIn"
{34346202-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Viewer Snap-In"
ContextMenu
{19876202-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Alert Snap-In"
{34346202-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Viewer Snap-In"
ToolBar
{19876202-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Alert Snap-In"
{45091ca8-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Crystal Report"
PropertySheet
{19876202-EA27-11CF-ADCF-00AA00A80033}
= REG_SZ "Alert Snap-In"
If a snap-in is designed only to extend another snap-in, it must also register itself under the particular NodeTypes subkey that it extends and must indicate the type of extension it has. Following are explanations of subkey uses:
For general information about the registry, see Installing Applications and related sections of the Microsoft Platform SDK.