ShaneO123
asked on
Microsoft, Terminal Server, Windows 2003, Remote control failed. Error code 5 Error [5]:Access is denied.
I have non-administrator User who needs access to the Remote Control feature of Terminal Server to provide other Users with software training. Starting Terminal Services Manager by using the "Run as..." option, and then logging-in as Administrator doesn't work.
Is there any way this can be done without giving this User full Administrative or Domain Admin rights?
Is there any way this can be done without giving this User full Administrative or Domain Admin rights?
Forgot to add this note
You need remote assistence to be enabled on the wworkstations.
I know it's a "duhhh" but still.. :)
You need remote assistence to be enabled on the wworkstations.
I know it's a "duhhh" but still.. :)
ASKER
This is not really an acceptable solution. The Remote Users are connecting from various workstations all over the county and to arrange remote control of their workstations, when everyone is already connected to the Server via Terminal Services, is not practical.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Firstly, I appologise for not responding sooner. My membership expired before you posted your reply, and I didn't renew my membership for several weeks.
Secondly, while your reply was detailed, it still DIDN'T work.
I still recieve the following error -
Session (ID 1) remote control failed
(Error 5 - Access is denied.)
Secondly, while your reply was detailed, it still DIDN'T work.
I still recieve the following error -
Session (ID 1) remote control failed
(Error 5 - Access is denied.)
I was having the same issue and came to find out that the permissions are actually applied on the session itself. This means not only does the user trying to do remote control have to log back in, but so does the user that needs to be controlled. I found this out through trial and error and found that once the end user logged back into the server i was able to remote their session with the permissions i put in place on the connection.
Use the save as file invitation detailed in the article bellow
http://technet.microsoft.com/en-us/library/bb457004(TechNet.10).aspx