Do you accept the request? If the user of the console session on the server clicks YES , you are automatically connected to the console session on the remote Windows Server based server. If the user on the server's console clicks NO or does not respond, you receive the following error message at the command prompt on the remote computer:.
Remote control failed. Error code Error []:The request to control another session remotely was denied. If you are logged on to the console of the server that is running Terminal Services, if you try to shadow another user's session from the console of the computer, you receive the following error message:. Remote Control Failed. Error Code Error []:The requested session cannot be controlled remotely. This may be because the session is disconnected or does not 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. Sounds like what you want is a RAT. A remote administration tool. I see this alot with the "script kiddies". However, I do NOT recommend this. If you are willing to pay, you can use Teamviewer. It will do this very easily. Teamviewer does have a free version, but it is for personal use only. I believe the Commercial version of Teamviewer allows you to disable the pop up on the bottom of the screen.
Glad to hear you found a solution. Just get used to starting your session in windowed mode not full screen and keep your cursor out of the window to avoid taking control. You can use the built-in Microsoft Remote Assistance utility to remote control rdp sessions on pc's. Create a shortcut on YOUR desktop with the following fields Active Oldest Votes. Improve this answer. Juha Juha 3 3 silver badges 6 6 bronze badges. Also interesting: forums. Just wanted to follow up and let you know that I did indeed get it working.
After sifting through all the posts in that Green Button thread you linked to, I found that all I needed was the tip in the very last post: "In the future, if you don't want to use the shadow command, you can just go into the "users" tab of the task manager. Then, right click a user's name and select shadow session or shadow user I forget exactly what it says. But if you haven't changed the other settings, the other use will be prompted to allow you to take control first.
Minus that last bit about the other user getting prompted I didn't have that obstacle, fortunately. Maybe some settings did get changed, I'm not sure. In any case, I wanted to make sure I thanked you properly for pointing me in the right direction.
Thanks a million! Juha, Your link is broken. There doesn't seem to be a way to directly remote-connect to a shadow session. There are several unique stack traces of the processes that access the fDenyTSConnections key value.
Two of them are the following:. In the first stack the interesting thing is that there is the CPolicyMonitor class in the lsm. As you can see the key is monitored by the same functions we have seen in the first stack trace above, so there are some validation checks related to this key in lsm. I examined each of these registry keys and found out that both of them work as expected. No matter how the Remote Desktop Services TermService service is started, it cannot be stopped while one of the following is true:.
The bad thing is that the Remote Desktop Configuration SessionEnv service can be stopped and if so, you will receive the following error while trying to shadow a session:. On the other hand, once the host restarts, the Remote Desktop Configuration SessionEnv service starts again under the condition that one of the keys is set to an appropriate value as mentioned above.
Of course, it can be started manually at any time if you have privileged access. The services are:. Here are several screenshots demonstrating this. After that I disconnected and established a shadowing connection the last screenshot.
0コメント