1. Support
  2. KBAs
  3. Cannot remote control a Windows XP SP2 or Server 2003 machine once it has been logged into with Microsoft Remote Desktop

Cannot remote control a Windows XP SP2 or Server 2003 machine once it has been logged into with Microsoft Remote Desktop

Goverlan fails to initiate a remote control session to a Windows XP SP2 or Server 2003 machine. The error returned is:

The remote machine is in an invalid state to start a remote control session.

This state occurs once a Remote Desktop connection has been established.

GoverLAN cannot reset the state of the remote machine because it failed to bind to its Terminal Services.

Error#1627: Function failed during execution.

Once a remote machine has been logged-in using Microsoft Remote Desktop, it is left in an invalid state to initiate a standard remote control session. Goverlan has been equipped with a mean to ‘reset’ this invalid state. However, with the introduction Windows XP Service Pack 2 and Server 2003, new security settings are preventing Goverlan from executing this reset action.

Resolution:

In order to allow Goverlan to reset a ‘remote desktop invalid state’, you need to authorize Terminal Services Remote Administration by setting the a specific registry key on the client machine. The following instructions describe this process:

  1. Open the Registry Editor on the Windows XP SP2 machine (the machine being remote controlled).
  2. Navigate to the registry key: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server
  3. Create and set the value: AllowRemoteRPC = DWORD:: 1
  4. Close the registry editor and reboot the machine.

Once a Windows XP SP2 or Server 2003 machine has been configured with this registry key and rebooted once, you will be able to use Microsoft Remote Desktop as well as Goverlan Remote Control.

Was this article helpful?

Related Articles