How to Configure MMC Snap-ins on Windows Server 2012 R2

Microsoft Management Console (MMC) is the host application for virtually all Windows Server 2012 R2 administrative tools. Individual management capabilities are delivered as MMC snap-ins — Active Directory Users and Computers, DNS Manager, DHCP Manager, Group Policy Management, Certificate Manager, Computer Management, and dozens of others are all MMC snap-ins hosted within the same console framework. Understanding how to create custom MMC consoles that combine multiple snap-ins into a single management window can significantly reduce administrative overhead, particularly for administrators who routinely need to work with multiple tools simultaneously.

Windows Server 2012 R2 includes over 50 built-in MMC snap-ins plus additional ones installed with RSAT and server roles. Custom MMC consoles can be saved as .msc files and shared with other administrators, deployed via Group Policy to standardize administrative tooling, or placed on the desktop/taskbar for quick access to frequently used management tools. This guide covers creating custom MMC consoles, configuring snap-in options, using Author mode vs. User mode, and distributing custom consoles.

Prerequisites

– Windows Server 2012 R2 with appropriate roles and features installed
– Administrative credentials
– RSAT tools installed for remote server management snap-ins
– Active Directory domain membership (for domain-related snap-ins)

Step 1: Open the MMC Host Application

Open an empty MMC console:

# Open an empty MMC
mmc.exe

# Open a specific saved console
mmc.exe "C:AdminToolsServerAdmin.msc"

# Open MMC for a specific remote computer (Computer Management example)
compmgmt.msc /computer:\Server01

An empty MMC console opens with just the Console Root node in the left pane. The console operates in Author mode by default when opened as mmc.exe, allowing you to add snap-ins and customize the layout.

Step 2: Add Snap-ins to the Console

Add snap-ins via File > Add/Remove Snap-in (Ctrl+M):

The Add/Remove Snap-ins dialog shows all available snap-ins on the left. For building a comprehensive server administration console, add these frequently used snap-ins:

# Key MMC snap-ins and their standalone .msc shortcuts for reference:
# compmgmt.msc       - Computer Management (composite: Event Viewer, Services, Device Manager, etc.)
# devmgmt.msc        - Device Manager
# diskmgmt.msc       - Disk Management
# eventvwr.msc       - Event Viewer
# perfmon.msc        - Performance Monitor
# services.msc       - Services
# taskschd.msc       - Task Scheduler
# gpedit.msc         - Local Group Policy Editor
# secpol.msc         - Local Security Policy
# certmgr.msc        - Certificates (current user)
# certlm.msc         - Certificates (local machine)
# comexp.msc         - Component Services (COM+)
# wf.msc             - Windows Firewall with Advanced Security
# dsa.msc            - AD Users and Computers (requires RSAT)
# dssite.msc         - AD Sites and Services (requires RSAT)
# dnsmgmt.msc        - DNS Manager (requires RSAT-DNS-Server)
# dhcpmgmt.msc       - DHCP Manager (requires RSAT-DHCP)
# gpmc.msc           - Group Policy Management (requires GPMC)

Step 3: Build a Custom Server Administration Console

Create a comprehensive custom console combining the most frequently used snap-ins:

1. Open MMC: press Win+R, type mmc, press Enter
2. Press Ctrl+M to open Add/Remove Snap-ins
3. Add the following snap-ins in order:

# When adding these snap-ins in the GUI, choose "Local Computer" 
# for the standalone target or connect to remote servers as needed:

# Snap-ins to add to a Server Administration console:
# 1. Event Viewer          → Add → "Another computer" → enter server name
# 2. Services              → Add → select computer
# 3. Disk Management       → Add → "Another computer"  
# 4. Performance Monitor   → Add
# 5. Task Scheduler        → Add
# 6. Certificates          → Add → "Computer account" → "Another computer"
# 7. Windows Firewall      → Add
# 8. Device Manager        → Add → "Another computer"

After adding snap-ins, rename the Console Root node for clarity:

– Right-click “Console Root” in the left pane
– Select “Rename”
– Type “Server01 Administration Console”

Step 4: Organize Snap-ins with Folder Nodes

Add folder nodes to organize many snap-ins into logical groups:

1. In Add/Remove Snap-ins, add the “Folder” snap-in (listed as “Folder” in the snap-in list)
2. After adding the folder, right-click it in the console tree and rename it
3. Drag and drop other snap-ins to nest them under folder nodes

# Suggested folder organization for a comprehensive admin console:
# Console Root
# ├── Server Infrastructure
# │   ├── Services
# │   ├── Task Scheduler
# │   └── Device Manager
# ├── Storage
# │   └── Disk Management
# ├── Security
# │   ├── Certificates (Local Machine)
# │   └── Windows Firewall with Advanced Security
# ├── Monitoring
# │   ├── Event Viewer
# │   └── Performance Monitor
# └── Active Directory (if applicable)
#     ├── AD Users and Computers
#     └── DNS Manager

Step 5: Configure Console Mode (Author vs. User)

Before saving a console, configure its mode to control how other users can interact with it:

Click File > Options to set the console mode:

– Author mode: Full access to all MMC features — users can add/remove snap-ins, create taskpad views. Appropriate for personal admin consoles.
– User mode – Full Access: Users can navigate the full console but cannot add or remove snap-ins. Appropriate for shared admin consoles where the configuration should remain fixed.
– User mode – Limited Access, Multiple Windows: Users can open multiple windows but cannot change the window layout or navigate outside designated sections.
– User mode – Limited Access, Single Window: Most restrictive — users see only a single predefined view.

For a console shared with a junior administrator who should only be able to view but not modify the configuration, choose “User mode – Full Access.”

Step 6: Save and Deploy Custom Consoles

# Save the console from MMC: File > Save As
# Use .msc extension
# Example: C:AdminToolsServerAdmin.msc

# Deploy to multiple administrators via file share
Copy-Item "C:AdminToolsServerAdmin.msc" "\FileServer01AdminToolsServerAdmin.msc"

# Create a desktop shortcut to the console
$WshShell = New-Object -comObject WScript.Shell
$Shortcut = $WshShell.CreateShortcut("$env:PublicDesktopServer Admin Console.lnk")
$Shortcut.TargetPath = "mmc.exe"
$Shortcut.Arguments = "`"C:AdminToolsServerAdmin.msc`""
$Shortcut.IconLocation = "C:WindowsSystem32mmc.exe,0"
$Shortcut.Description = "Server Administration Console"
$Shortcut.Save()

Deploy via Group Policy for consistent administrative tooling across admin workstations:

# Copy the MSC file to SYSVOL for easy access
Copy-Item "C:AdminToolsServerAdmin.msc" "\domain.comSYSVOLdomain.comAdminToolsServerAdmin.msc"

# Create a Group Policy Preference to copy the file to admin workstations
# (Configure via GPMC > Computer Configuration > Preferences > Windows Settings > Files)

# Alternatively, deploy the shortcut via Group Policy Preferences > Shortcuts

Step 7: Create Taskpad Views for Common Operations

Taskpad views in MMC provide button-based shortcuts for frequently performed actions:

1. Right-click a node in the console tree and select “New Taskpad View”
2. The Taskpad View Wizard configures the taskpad appearance
3. After creating the taskpad, add tasks using the “New Task Wizard”
4. Tasks can run shell commands, scripts, or MMC menu commands

Example taskpad tasks for a Services snap-in node:

– “Restart IIS” — runs iisreset.exe
– “Check Failed Services” — runs a PowerShell script
– “View Event Log” — opens the Event Viewer node

Step 8: Restrict Access to MMC Snap-ins via Group Policy

Use Group Policy to restrict which snap-ins standard users can access:

# Group Policy path:
# User Configuration > Administrative Templates > Windows Components > Microsoft Management Console

# "Restrict the user from entering author mode": Enabled
# "Restrict users to the explicitly permitted list of snap-ins": Enabled
# Then individually enable only the snap-ins you want users to access

# To configure via PowerShell (add to Group Policy Object):
Import-Module GroupPolicy

$gpo = Get-GPO -Name "Admin Workstation Policy"
Set-GPRegistryValue -Name "Admin Workstation Policy" `
    -Key "HKCUSOFTWAREPoliciesMicrosoftMMC" `
    -ValueName "RestrictToPermittedSnapins" `
    -Type DWord -Value 1

Step 9: Connect Snap-ins to Remote Computers

Many snap-ins can be pointed at remote computers for remote management. The method varies by snap-in:

# Open Computer Management connected to a remote computer
compmgmt.msc /computer:\Server01

# Open Services focused on a remote computer
# In MMC > Add/Remove Snap-in > Services > "Another computer" > type server name

# Open Event Viewer for a remote computer
# In MMC > Add/Remove Snap-in > Event Viewer > "Another computer" > type server name

# Computer Management with remote computer from command line
Start-Process mmc.exe -ArgumentList "compmgmt.msc /computer:\Server01"

Step 10: Automate Common MMC-Based Tasks with PowerShell

For tasks performed via MMC snap-ins, PowerShell often provides a faster, scriptable alternative:

# Instead of using Disk Management GUI, use PowerShell
Get-Disk | Select-Object Number, FriendlyName, OperationalStatus, Size
Get-Partition | Select-Object DiskNumber, PartitionNumber, DriveLetter, Size

# Instead of using Services GUI, use PowerShell
Get-Service | Where-Object { $_.StartType -eq "Automatic" -and $_.Status -eq "Stopped" }

# Instead of using Event Viewer GUI, use PowerShell
Get-WinEvent -FilterHashtable @{ LogName = "System"; Level = 2; StartTime = (Get-Date).AddHours(-24) }

# Instead of using Certificate Manager GUI, use PowerShell
Get-ChildItem cert:LocalMachineMy | Where-Object NotAfter -lt (Get-Date).AddDays(30)

# Instead of using Device Manager GUI, use PowerShell
Get-PnpDevice | Where-Object Status -ne "OK" | Select-Object Class, FriendlyName, Status

Summary

MMC custom consoles on Windows Server 2012 R2 provide an efficient way to consolidate frequently used administrative tools into a single, organized workspace. By combining relevant snap-ins, organizing them with folder nodes, configuring appropriate console modes for different user levels, and saving the result as shareable .msc files, administrators can standardize their tooling across teams and eliminate the time lost switching between multiple separate administrative consoles. While PowerShell increasingly replaces GUI-based administration for scripted and repeatable tasks, custom MMC consoles remain valuable for interactive, exploratory administration where the visual interface aids in diagnosis and configuration work.