The primary port used by SCCM Remote Control. TCP Port 2702: Used for the remote assistance feature. TCP Port 135: Used for initial RPC communication. How to Use the Standalone Remote Control Tool
The Windows 10 client must be able to receive traffic from the technician's machine. SCCM Remote Control uses . Ensure that your domain firewall policies allow inbound traffic over this port on all managed Windows 10 endpoints. Troubleshooting Common Connection Errors
To download SCCM Remote Control on Windows 10, follow these steps:
| Issue | Likely Cause | Solution | |-------|--------------|----------| | "Remote control failed to initialize" | Firewall blocking port 2701 | Validate inbound rule on Windows 10. Test with Test-NetConnection -Port 2701 | | Client not showing as "Yes" for Remote Control | Client settings not applied | Run ControlPanel > Configuration Manager > Actions > Machine Policy Retrieval & Cycle | | Cannot download client from SCCM server | Network Access Account or Distribution Point issue | Verify IIS on DP and proper permissions to SMS_DP_SMSPKG$ share | | Blank gray screen on remote view | Video driver or UAC limitation | Disable UAC remote restrictions via Group Policy or enable “Allow remote control of UAC prompts” | | Error: "Remote control is disabled by policy" | Client settings misconfiguration | Re-check “Enable remote control on clients” and redeploy policy | The primary port used by SCCM Remote Control
Remotely administer Windows computer - Configuration Manager
To successfully establish a remote session with a Windows 10 client, ensure the following configurations are in place:
One of the most critical aspects of SCCM remote control configuration involves defining which users and groups can initiate remote connections. Within the Permitted Viewers section, administrators specify the security principals authorized to establish remote control sessions. Common practice involves creating domain security groups such as "HelpDesk" or "SCCMAdmins" and adding these to the permitted viewers list. How to Use the Standalone Remote Control Tool
For organizations already using SCCM/Configuration Manager, Remote Control is a logical, centrally managed option that integrates well with inventory, deployment, and compliance workflows. For small orgs or users needing lightweight or internet-optimized sessions, consider Quick Assist or third-party tools.
To maintain security and compliance while using remote control:
If you encounter errors while trying to connect to a Windows 10 client, check the following common failure points: for a helpdesk tech)
On the admin machine, open a command prompt and run telnet Windows10PC 2701 . Fix: Create a Windows Firewall rule via Group Policy or SCCM CI to allow TCP 2701 inbound on all Windows 10 clients.
Navigate to the following directory on your SCCM Site Server or console machine: C:\Program Files (x86)\Microsoft Endpoint Manager\AdminConsole\bin\i386 (Note: On older versions, the path may be ...\Microsoft Configuration Manager\AdminConsole\bin\i386 ) Locate the following : CmRcViewer.exe (The actual Remote Control application) rdpcoreax.dll
If you need the remote control tool on a Windows 10 machine (e.g., for a helpdesk tech), you have two official options: