JSI Tip 6943. You cannot remotely control a disconnected Terminal Services session?

When you user Terminal Services Manager to remotely control a session, you receive:

Terminal Services Manager

Can't remote control Session (ID #) because it is disconnected with user's required permission enabled.

(Error 0 - The operation completed successfully.)

If you clear the Require user's permission box, on the RemoteControl tab of the user account, and try again, Terminal Services Manager displays:

Terminal Services Manager

Session (ID #) remote control failed.

(Error 7050 - The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on. Also, you cannot control a session remotely from the system console and you cannot remote control your own current session.

If you use the shadow command, you receive:

Your session may appear frozen while the remote control approval is being negotiated.
Please wait...
Remote control failed. Error code 7050
Error \[7050\]:The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on. Also, you cannot control a session remotely from the system console and you cannot remote control your own current session.

You cannot remotely control a disconnected Terminal Services session. You cannot remotely control a session that you have disconnected.

Hopefully, this behavior will be corrected in a service pack.



TAGS: Windows 8
Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish