Interesting.  I was basing my assumptions on the release notes:

And what I see when I try to establish remote control:

The account I am using is defined as an administrator in vWorkspace, with the right to remote control computers in this group.  I've also set the option to allow remote control as described above.  I will need to keep digging now that I know it is possible, even if unsupported.  Thanks

Steve, I just tested this and it worked fine.  See the screenshot below.  I opened a Session on 2008 R2 RD Session Host, opened the vWorkspace Management Console, right clicked on an active Windows 7 Ultimate Session -> Remote Control -> Switched to the Win7 desktop and accepted the request.

Steve,

Having the same problem, can't access the Remote Control item as its grayed out.

Running 7.1MR1 on Windows 7 VM's.

Currently use Altiris Remote to access the thin clients directly but the remote would be nice...

Peter

Peter, if Remote Control is greyed out the most common configuration setting is to "Enable RDP Remote Administration Control" in the properties of the Locations node.

The next things to check would be if you are running the vWorkspace Management Console from a Terminal Server Session (required for Remote Control), that the user being shadowed has an active session and that the Administrator has been properly delegated the Remote Control permission in vWorkspace.

Peter - My option is not grayed out.  I can attempt the connection, but get the error in the screenshot I posted when I do.

Patrick - Thanks for enumerating the pitfalls.  I've got all of those items covered, but the problems persist.  Maybe I will intall just the management console on another machine, RDP into it, and try a remote control session from there.  Maybe it's something to do with the broker I am attempting to remote control from.

Steve, do you have any GPOs that prevent remote control?  To see if it's vWorkspace related or not, try logging onto a server via mstsc, then try using the shadow.exe cmd line utility to remote control the session on another TS, virtual or physical desktop.

No GPOs preventing this, but trying shadow.exe led me to an error that I could research - Error [120]:This function is not supported on this system.

That in turn yielded this (both shadower and shadowee use multiple monitors):

http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2rds/thread/4d06278f-e0f4-4f8e-a8e1-3697ee967ef4

I have made some further research and discussions on the issue. It is currently confirmed that the Remote Control (Shadow) doesn’t support multi-monitor mode. In such a case, the “Access is denied” doesn’t mean permission insufficient, but inaccessible feature in the current mode.
In the same environment, when you use the command-line shadow 
  
    instead of UI, you will get the accurate error message as below:
  
Error [120]: This function is not supported on this system.
If there is any further update on this issue, I will follow up here and inform you.
Again, I very much appreciate your patience and cooperation. Good holiday!
·         Lionel Chen
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfd@microsoft.com

If Quest is getting the remote control done via the native Microsoft shadowing capability, that would explain my problem.  Thanks for pointing me in the right direction.

Steve