Make sure you use a Global Security Group in AD, not a local one! That's a common mistake when setting up which users are allowed with vWorkspace. Of course, if you provision a virtual desktop with vWorkspace, we take care of that for you!
Thats what i started with, but you still need to tell windows that users are allowed to do so as well.
Isn't what i described at the start setting delegation? Is there an other way?
Our customer rejected this solution because you get to view the entire console. Is there a way to present the console to a group of users with only the terminal servers node visable?
paulh21
33 Posts
1
November 24th, 2010 10:00
Found it!
on the terminal server, go to Administrative tools\Terminal Services\Terminal services configuration
right click RDP-TCP, choose properties
goto security tab
click add and add your remote control AD group
click Advanced, select the group en click edit
assuming this group also has memebership of remote desktop users only select (allow) Remote control
now to try and put this in a group policy...
Shame i cant award credits to myself
O no wait, i can
Michel Roth
173 Posts
0
November 24th, 2010 14:00
Thanks for sharing Paul. Do you know you can also delegate control to shadow on a vWorkspace level in the management console?
DELL-Jon Ro
1 Rookie
•
64 Posts
0
November 24th, 2010 21:00
Make sure you use a Global Security Group in AD, not a local one! That's a common mistake when setting up which users are allowed with vWorkspace. Of course, if you provision a virtual desktop with vWorkspace, we take care of that for you!
paulh21
33 Posts
0
November 25th, 2010 05:00
Thats what i started with, but you still need to tell windows that users are allowed to do so as well.
Isn't what i described at the start setting delegation? Is there an other way?
Our customer rejected this solution because you get to view the entire console. Is there a way to present the console to a group of users with only the terminal servers node visable?