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\i386Copy 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.exerdpCoreSccm.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. Runningcmrcviewer.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
- Browse our General Tech Accessories picks on Amazon
- Samsung T7 1TB portable SSD
- Logitech MX Master 3S mouse
- Anker 8-in-1 USB-C docking station
- Samsung T7 1TB portable SSD
- Logitech MX Master 3S mouse
- Anker 8-in-1 USB-C docking station
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.