Overview
The Microsoft Management Console (MMC) hosts administrative snap-ins that can target a remote computer — letting you manage services, event logs, and more from your own desk. This guide covers the prerequisites and the steps to connect, configured only for machines you’re authorized to manage.
Use MMC to manage a remote computer.
Note: Only configure remote management on computers you own or are explicitly authorized to administer.
Key Takeaways
- MMC snap-ins can connect to another computer over the network.
- The remote PC needs the right firewall rules and services enabled.
- Your account needs administrative rights on the remote PC.
- Many built-in snap-ins (Services, Event Viewer, Device Manager) support remote targets.
Prerequisites
- Both PCs on the same network/domain (or proper credentials for a workgroup).
- An administrator account on the remote computer.
- Network discovery and the relevant services running.
Allow Remote Management Through the Firewall
1. On the remote PC, open Windows Defender Firewall > Allow an app through firewall.
2. Enable "Windows Management Instrumentation (WMI)" and "Remote Event Log Management" for the appropriate network profile.
3. Apply the changes.
Start the Remote Management Services
1. On the remote PC, open services.msc.
2. Ensure "Windows Remote Management (WS-Management)" and "Remote Registry" are running (set to Automatic if needed).
3. Optionally run winrm quickconfig in an elevated prompt to configure WinRM.
Warning: Some guides suggest disabling UAC remote restrictions. Change this only if your environment specifically requires it, and revert it afterward — it lowers security.
Connect with an MMC Snap-in
1. On your PC, press Windows + R, type mmc, and press Enter.
2. Click File > Add/Remove Snap-in.
3. Choose a snap-in (e.g., Services or Computer Management) and click Add.
4. When prompted, select "Another computer" and enter the remote PC’s name or IP.
5. Click OK to connect and manage the remote machine.
Successfully accessing a remote computer.
Troubleshooting
Problem: "Access is denied" when connecting.
Solution: Confirm your account has admin rights on the remote PC and supply the correct credentials for that machine/domain.
Problem: "The RPC server is unavailable".
Solution: Enable the WMI/Remote firewall rules and ensure the Remote Registry and WinRM services are running.
Problem: Snap-in connects but shows no data.
Solution: Start the corresponding service on the remote PC (e.g., Remote Registry) and re-open the snap-in.
Problem: Works in a domain but not a workgroup.
Solution: Workgroups need matching local admin credentials and UAC/LocalAccountTokenFilterPolicy considerations — verify both PCs trust each other.
Conclusion
With the right firewall rules, services, and permissions in place, MMC snap-ins let you administer a remote computer as if you were sitting at it. Enable only what you need, manage only authorized machines, and revert any security relaxations when finished.
</w:pBdr><w:spacing w:before="220" w:after="40"/></w:pPr><w:r><w:rPr><w:b/><w:bCs/><w:color w:val="0B5394"/><w:sz w:val="21"/><w:szCs w:val="21"/><w:rFonts w:ascii="Calibri" w:cs="Calibri" w:eastAsia="Calibri" w:hAnsi="Calibri"/></w:rPr><w:t xml:space="preserve">About TechHub
This guide is part of the TechHub Knowledge Base. For more step-by-step IT guides and support, visit techhub.com.lk.
