Introduction to Remote Control in Configuration Manager


Updated: May 14, 2015

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1

Use remote control in System Center 2012 Configuration Manager to remotely administer, provide assistance, or view any client computer in the hierarchy. You can use remote control to troubleshoot hardware and software configuration problems on client computers and to provide help desk support when access to the user’s computer is required. Configuration Manager supports the remote control of workgroup computers and computers that are joined to an Active Directory domain.

In addition, Configuration Manager lets you configure client settings to run Windows Remote Desktop and Remote Assistance from the Configuration Manager console.


You cannot establish a Remote Assistance session from the Configuration Manager console to a client computer in the following scenarios:

  • The client computer is in a workgroup.

  • The computer running the Configuration Manager console is running Windows XP Service Pack 3, but the host computer is not running Windows XP Service Pack 3. For more information, see your Windows Remote Assistance documentation.

You can start a remote control session from any device collection in the Configuration Manager console, from the Windows Command Prompt window, or from the Windows Start menu.

What’s New in Configuration Manager


The information in this section also appears in the Getting Started with System Center 2012 Configuration Manager guide.

The following items are new or have changed for remote control since Configuration Manager 2007:

  • Remote control now supports sending the CTRL+ALT+DEL command to computers.

  • You can apply different remote control settings to collections of computers by using client settings.

  • You can lock the keyboard and mouse of the computer that is being administered during a remote control session.

  • The copy and paste functionality between the host computer and the computer that is being administered has been improved.

  • If the remote control network connection is disconnected, the desktop of the computer that is being administered will be locked.

  • You can start the remote control viewer from the Windows Start menu.

  • Remote control client settings can automatically configure the Windows Firewall on client computers to allow remote control to operate.

  • Remote control supports connecting to computers with multiple monitors.

  • A high visibility notification bar is visible on client computers to inform the user that a remote control session is active.

  • By default, members of the local Administrators group are granted the Remote Control permission as a client setting.

  • The account name of the administrative user who starts the remote control session is automatically displayed to users during the remote control session. This display helps users to verify who is connecting to their computer.

  • If Kerberos authentication fails when you make a remote control connection to a computer, you are prompted to confirm that you want to continue before Configuration Manager falls back to using the less secure authentication method of NTLM.

  • Only TCP port 2701 is required for remote control packets; ports TCP 2702 and TCP 135 are no longer used.

  • Responsiveness for low-bandwidth connections supports the following improvements:

    • Elimination of mouse trails by using single mouse cursor design.

    • Full support for Windows Aero.

    • Elimination of mirror driver.