A systems administrator needs to create a customized management interface for tier-1 help desk technicians that consolidates the Event Viewer, Services, and Device Manager snap-ins into a single window. To maintain administrative control, the administrator must ensure technicians can use the tools but cannot add or remove snap-ins or modify the console layout. Which of the following approaches best satisfies these requirements?
- Launch Microsoft Management Console (mmc.exe) in Author Mode, add the required snap-ins, and save the console file in User Mode - Limited Access.Answer
- BOpen Computer Management (compmgmt.msc), customize the System Tools branch, and export the configuration as an Administrative Template (.adm) file.
- CConfigure the Local Security Policy (secpol.msc) snap-in under User Rights Assignment to restrict MMC customization permissions for non-administrators.
- DOpen System Properties (sysdm.cpl), select the Advanced tab, and adjust User Profiles settings to lock administrative tool window layouts.
Answer
The administrator should launch Microsoft Management Console (mmc.exe) in Author Mode, add the necessary snap-ins, and save the console file in User Mode - Limited Access.
Building a custom management console using Microsoft Management Console (mmc.exe) allows administrators to select specific snap-ins (Event Viewer, Services, Device Manager) and combine them into a single file (.msc). By saving the file in User Mode (specifically Limited Access, Single Window or Multiple Window), technicians can execute the management tools within the console but are strictly prevented from adding/removing snap-ins or altering the interface design.
Step-by-Step Solution
Key Concept
Microsoft Management Console (MMC) Customization and Console Modes