This documentation is archived and is not being maintained.

Using Custom MMC Snap-in Extensions

Exchange Server 2003

Using Custom MMC Snap-in Extensions

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.To add your own MMC snap-in extension to an existing node in the Exchange System Manager

  1. Identify the snap-in GUID of the extension that you will add to extend the node.
  2. Identify the node type GUID of the MMC node to be extended.
  3. Add the extension GUID to the node type GUID.

The details of performing these steps are described below:

To identify the snap-in GUID of the extension
  1. Open the Microsoft® Visual Basic® Snap-in project for the new extension.
  2. Select the Designers container and identify the DSR project name. This is not always the same as the DSR file name.
  3. Open the Microsoft Visual Studio® tool, OLE View.
  4. On the File menu, click View Type Lib. In the Open dialog box, select the compiled OCX for the extension and click OK.
  5. In the ITypelib Viewer, click the coclass <DSR project name> object. The proper GUID will appear in the right pane.

To identify the node type GUID of the MMC node to be extended
  1. Identify the snap-in GUID for the extension as described above.
  2. Open the Registry.
  3. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\MMC\<snap-in GUID>\NodeTypes.
  4. Note the GUID of the node type that you want to extend.

To add an extension to a node type GUID
  1. Identify the node type GUID as described in the previous section.
  2. Open the Registry.
  3. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\MMC\NodeTypes\<node type GUID>.
  4. Create a new subkey named Extensions. To do this, right-click the GUID, click New, and then click Key.
  5. Click the new key and create a new subkey with the appropriate extension type. Valid subkeys are Namespace, Property Sheet, Context Menu, Task, and Toolbar.
  6. Add a value to the subkey using the following model: < snap-in GUID> = <snap-in name>

To avoid creating new GUIDS each time a project is compiled using Visual Basic
  1. Open your Visual Basic project.
  2. Under the Project menu, click Project Properties, then click the Components tab.
  3. Select Binary Compatibility for the Version Compatibility.
Note  If compatibility is broken during a new compile, Visual Basic creates new GUIDs.

Note  Both Visual Basic and Visual C++ perform a full unregister/register after a new compile for ATL components. This makes it necessary to add the registry settings described above each time before you debug. To avoid this requirement, write REG files for the Registry changes. You can then use a batch file for debugging. In the batch file, first import the Registry files, and then start MMC.
Show: