This article takes a look at the MMC in broad terms and then describes the steps needed to create a custom management console. The examples in this article are based on Windows NT Workstation 5.0 Beta 2; please note that a Server setup will offer even more management possibilities.


MMC overview
The MMC itself is nothing more than an empty shell (Picture) that is capable of hosting snap-ins. Think of it as the window that surrounds the management tools you need. Typically, you will start the MMC by right-clicking My Computer and choosing "Manage," which will bring up the "Computer Management" console as preconfigured by Windows NT 5.0. There are also a group of other preconfigured consoles in the "Administrative Tools" group in the Programs menu. These tools equate to management tools and Control Panel applets you're used to in Windows NT 4.0.

The purpose of the MMC's snap-in architecture, of course, is to provide a way to manage one or more areas of Windows NT from a central location. Not only is an MMC console extensible, but each console can host a multitude of snap-ins if needed. Also, future Microsoft BackOffice server applications and third-party applications will use the MMC as their central management point as well. Users of SQL Server and Exchange Server, for example, are familiar with those tools' own "manager" programs (Enterprise Manager and Exchange Administrator), which in many ways are very similar to each other. Well, beginning with the next versions of each of these products (SQL Server 7.0 and Exchange 6.0), management will occur within the familiar MMC console. This means that administrators will only need to learn one tool for any kind of management and, if you think about it, it is this kind of knowledge leverage that makes a standardized Windows interface work so well.

A final note about the MMC: While many users will only use the MMC to manage their own, local, system, the MMC is also designed to facilitate remote administration across a network.