Cannot Remotely Control a Disconnected Session
This article was previously published under Q281156 SYMPTOMS When you try to remotely control a session through Terminal
Services Manager, you may receive the following error message:
Terminal Services Manager If you clear the Require user's permission check
box on the Remote Control tab of a your user account, and then try to initiate Remote
Control through Terminal Services Manager, you receive the following error
message: Can't remote control Session (ID #) because it is disconnected with user's required permission enabled. (Error 0 - The operation completed successfully.) Terminal Services Manager When you attempt to remotely control a session with the shadow command, you may receive the following error message:
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. 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. CAUSE These error messages occur when you attempt to remotely
control a disconnected Terminal Services session. You cannot remotely control a
session that you have disconnected. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
