Remote Control of Session Refused

[dcipher]

Hi

When I use the Session Management tool to Remote Control a Session it reports that the user refused the connection. However, I have set the group policy to allow interaction without permission and I have also set the property on the user to allow remote control without permission. So the session manager should not be reporting that the user refused the connection because they should never have been asked. I am using 8.3.7.18 on Windows 2012 Standard Edition.

Simon

[admin]

Hello,

Is your server also a domain controller or not ? If not, you may need to set up this group policy also on every client computers. The default user able to do remote control is the administrator account of the server, any other user even if member of the administrator group may not be able to do so.

[dcipher]

None of my servers are domain controllers. I am logged in as the Administrator and I am the one being refused remote control of other users. I never experienced this problem when I was running Windows Terminal Server. It only started after I switched all our servers to TSPlus. The way I overcome this issue is to use a cmd file:

Code: Select all

@echo off
set /p session="Enter the Session ID to shadow:"
mstsc.exe /shadow:%session% /control /noConsentPrompt

However it would be nice just to be able to use everything from the Session Manager.

Thanks,
Simon

[dave]

Simon:
I don't think you can use the TS Plus remote session control tools. Microsoft changed the way that session shadowing connections work in Server 2012 and I suspect that the tools that TS Plus uses to connect relies on the old shadow method. The code you have in your last reply is very similar code to what we're using to connect and as far as I know is the only solution for Server 2012 and 2012 R2. Conversely, that same method will not work in 2008 R2 or earlier. I definitely agree that having a GUI would be superior to the command line method for this particular function.

Best,
Dave