Configuration Manager Remote Control Tool – Standalone Version

First-line support techs often need to remote-control end-user machines without being handed access to the full ConfigMgr console — and the good news is you don’t have to give them the whole console to do it. If a machine already has the Configuration Manager client installed, you can extract just the remote control viewer and […]

Configuration Manager Remote Control Tool Standalone Version
First-line support techs often need to remote-control end-user machines without being handed access to the full ConfigMgr console — and the good news is you don’t have to give them the whole console to do it. If a machine already has the Configuration Manager client installed, you can extract just the remote control viewer and hand that out on its own.

Step 1: Grant permissions

Before extracting anything, add the accounts of the techs who need remote control access to the Remote Tools Operators role-based security group, in the Administration workspace of the ConfigMgr console. Without this, the standalone viewer will connect but be refused a session.

Step 2: Extract the required files

On a machine that has the ConfigMgr Console installed (or the primary site server itself), go to the console install location — by default:
%programfiles%\Microsoft Configuration Manager\AdminConsole\bin\i386
Copy the following into a new folder:
  • 00000409 — a folder; copy it in its entirety (it holds the localized resource files the tool needs to run).
  • cmrcviewer.exe
  • rdpCoreSccm.dll

Step 3: Deploy and use it

Name the new folder something sensible (e.g. “ConfigMgr Remote Tool”), then copy it to a USB drive or push it out to first-line tech machines. Running cmrcviewer.exe from that folder launches the standalone remote control tool — no console install required, and no console access granted beyond the specific remote-tools permission.

Still Works on Current Configuration Manager (Updated for 2026)

This extraction technique remains valid on current Configuration Manager (2603) — the same three items (cmrcviewer.exe, rdpCoreSccm.dll, and the 00000409 localized-resources folder) still live under the AdminConsole’s bin\i386 path, and the Remote Tools Operators role-based security group name is unchanged. If the console has been installed to a non-default location, adjust the path accordingly — the file names and folder structure underneath it stay the same regardless of where the console itself was installed.

Resources

Files extracted from the ConfigMgr console install location for the standalone Remote Control Tool

Discover more from TechyGeeksHome

Subscribe to get the latest posts sent to your email.

Andrew Armstrong

Andrew Armstrong is a UK-based IT professional with 26+ years of hands-on experience in Windows, Windows Server, SCCM/ConfigMgr, Active Directory, PowerShell, and enterprise infrastructure.

He founded TechyGeeksHome in 2010 and has published over 1,500 practical guides covering real-world IT problems and solutions. When not solving IT problems,

Andrew develops free Windows utilities including Ultimate Settings Panel, which has been downloaded over 850,000 times.