Using custom consoles
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Using custom consoles
After you create and save an MMC console, you can use it on your local computer, send it to other users in e-mail, post it on your network or the Web, or copy it to a floppy disk and install it on other computers. You can also use MMC and the Active Directory directory service to publish consoles or assign consoles to users. For more information about distributing software, see Active Directory.
Requirements to use a console
To use a console, you must have access to the services and administrative tools included in the console, either installed on the local computer or available on the network. You must also have administrative permissions for the components on the system that is administered by the console.
Opening a saved console
If you save a console to the per-user Administrative Tools folder (located at systemdrive\Documents and Settings\user\Start Menu\programs\Administrative Tools), it is then available to that user in the Administrative Tools folder on the programs menu.
If you know the name and location of a console file, you can open it as you would any other document:
By double-clicking the .msc file
By right-clicking the .msc file, and then clicking Open
From a command prompt
On computers running Windows 2000, Windows XP Professional, or an operating system in the Windows Server 2003 family, you can log on to your computer with user rights and perform routine tasks. However, you must use the Run As command to open console files and perform administrative tasks that require Administrator rights. You can use this command by typing runas at the command prompt or by right-clicking an .msc file, and then clicking Run As.
For more information about opening consoles, see Open a saved MMC console for local and remote computers, and Open MMC.