Question

Difficulty: MediumWindows Administrative and System Management Tools

A systems administrator needs to create a restricted, customized administration tool for a junior technician that contains only the Event Viewer and Device Manager snap-ins. The technician should be able to view these utilities but prevented from modifying the console layout. Sequence the administrative steps required to configure and deploy this custom Microsoft Management Console (MMC).

  1. 1Open the Run dialog box and execute mmc.exe to open a blank management console.
  2. 2Navigate to File > Add/Remove Snap-in and select the required management snap-ins.
  3. 3Access File > Options and switch the Console mode to User mode - limited access.
  4. 4Save the file with an .msc extension and distribute it to the technician's workstation.

Answer

The correct sequence starts by opening a blank console using mmc.exe, adding Event Viewer and Device Manager via Add/Remove Snap-in, changing the Console mode to User mode - limited access under Options, and saving the result as an .msc file.
Building a restricted MMC custom console requires initializing the blank MMC executable (mmc.exe), adding the target snap-ins (Event Viewer and Device Manager), configuring the Console mode under Options to User mode (limited access) to lock the layout, and finally saving the customized workspace as an .msc file.

Step-by-Step Solution

1
Launch the Microsoft Management Console shell.
An empty MMC shell opens in Author mode by default.
Custom snap-in consoles must be constructed from an unconfigured MMC root.
2
Add Event Viewer and Device Manager snap-ins.
The specified administrative utilities are populated in the console tree.
Administrative utilities must be added before locking down the user interface.
3
Configure the console security and mode settings.
The Console mode is changed from Author mode to User mode - limited access.
This mode prevents users from adding/removing snap-ins or saving layout modifications.
4
Save and deploy the customized console file.
A standalone .msc file is created for distribution.
Saving finalizing the configuration so the junior technician can launch the pre-configured environment directly.

Key Concept

Microsoft Management Console (MMC) Author vs. User Mode configuration and .msc file creation.
Rate this question