Windows

Customize Microsoft Management Console (MMC) consoles in Windows 2000 Professional

Microsoft Management Console (MMC) snap-ins are a handy part of a fully-functioning Windows 2000 Professional system. Learn how you can create your own customized set of snap-ins to get the most out of your experience.

Most of the administrative functions you perform in Windows 2000 Professional happen through various Microsoft Management Console (MMC) snap-ins. A useful advantage to this modular design is the fact that you can customize the consoles to suit your needs. For example, you can add a selection of consoles to your own custom console for the administrative functions you perform most often.

To create your own custom console with a selection of snap-ins, follow these steps:

  1. Go to Start | Run, and enter MMC.EXE in the Run dialog box.
  2. In the console window, choose Console | Add/Remove Snap-in.
  3. Click Add, select the desired snap-in, and then click Add again.
  4. Insert any other consoles you want to include and then click Close.
  5. Save the console so you can use it any time you need it. To do so, go to Console | Save As.
  6. Specify a location and filename, and the MMC will save the console with an .msc file extension.

Miss a column?

Check out the Windows 2000 Professional archive, and catch up on all the Windows 2000 Professional columns.

Want more Windows 2000 Professional tips and tricks? Automatically sign up for our free Windows 2000 Professional newsletter, delivered each Tuesday!

For quick access to the console, create a shortcut to it in your Start menu or on your desktop.

2 comments
yogivkbg
yogivkbg

How about the author and user mode permissions for MMC

Tony K
Tony K

If you have a custom MMC that you want to use as a "template" for others, MSC files are just XML and can easily be edited in a text editor. Why would you do this instead of using author mode? One word: scripting. We've just recently given our hub operators the option to manage the AD accounts for their clients for our external-facing systems. I wanted to limit them to their client OU only, so I simply created an MMC with the view I wanted, and replaced all instances of the OU name with a tag which I then ran a script against. I created 60 locked-down, single-view MMCs with less than an hour's actual work (the script also published them all via Citrix so I didn't have to deal with that, too).

Editor's Picks