-
Title
Error attempting to remote control Virtual Machine "Session 0 on Computer [computername] could no -
Description
When attempting to use the "Remote Control Session" feature from within the vWorkspace Management Console the following error is received.
"Session 0 on Computer [computername] could not be remote-controlled. (result=0)"
The user can connect via Remote Desktop to the target Virtual Machine (VM). But they are unable to remote control the session.
-
Cause
Insufficient permissions on the VM.
-
Resolution
In a true Terminal Server environment a user can be granted "Remote Control" permission on the RDP Connector using Terminal Services Configuration (TSADMIN.EXE) in 2003 or Remote Desktop Session Host Configuration in 2008.
In client based operating systems (I.E. Windows XP, Windows Vista, etc.) there is no way to set such permissions on the RDP Connector so you must be a local Administrator on the client system in order to use this feature. -
Additional Information
The "Remote Control Session" feature actually utilizes Microsoft's 'shadow.exe' which is part of the Terminal Services tools. Per Microsoft in order to remote control sessions using Shadow.exe you must hvae Full Control access permission.
http://technet.microsoft.com/en-us/library/cc776289(WS.10).aspx