Collective term used to describe both the scope pane and the result pane of a console in which one or more snap-ins are loaded. A snap-in can add scope items and result items to its namespace— that is, it can add scope items in the scope pane and result items in the result pane of the console in which it is loaded.
A namespace extension snap-in can add scope items to the namespace of a primary snap-in— that is, it can add scope items as children of scope items inserted by the primary snap-in.
- namespace extension
A third type of node, called a built-in node, is implemented by MMC and does not interact with snap-ins. An example of a built-in node is the Console Root.
- Node Manager
Used interchangeably with the term "MMC" in the MMC SDK documentation. The Node Manager implements a number of MMC COM interfaces and exposes them to snap-ins for their use.
- node type
A scope or result item's most important property, represented by a node type GUID. An item's node type describes its overall type; for example, whether it is a user, a machine, or a domain entry in a Domain Name System (DNS) database. A node type is defined by the individual snap-in rather than by MMC. MMC uses an item's node type to determine whether it can be extended by extension snap-ins.
- node type GUID
GUID associated with a particular node type. Snap-ins must register the node type GUIDs of their extendible node types. GUIDs in this context have no COM significance, although they can be generated using Guidgen.exe.
- notification (or notification message)
How MMC informs a snap-in that it must perform an action, usually in response to a user action, such as selecting a scope item or a context menu item. MMC sends notification messages to the snap-in's IComponentData::Notify, IComponent::Notify, or IExtendControlbar::ControlbarNotify methods, depending on the notification.