I've noticed that when I attempt to use the new Help Desk baked into Horizon 7.4 that if I'm connecting to a user who's a Windows Standard User then I can't perform administrative tasks on the user's machine. This is very problematic. Is there a way to fix this? Something I'm missing?
When I request control the user has the ability to check a box that allows me to see UAC messages but they have to be an administrator in order to do that which kind of useless, unless VMware is advocating that I make all my end users admins (lol).
Any suggestions or thoughts?
HI,
I think we can change group policy to fix this issue.
Here is a blog User Account Control Allow UIAccess applications to prompt for elevation without using the secure de... talks about the UAC which related with the remote assistant problem.
I have tried this method and work fine for windows 7
Following steps need to apply:
1. open group policy edit.
2. go to windows Settings-> Security Settings->Local Policies->Security Options
3. find "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop", and enable it.
Then remote assistant works fine. And administrator can see the UAC message from his console.
HI,
I think we can change group policy to fix this issue.
Here is a blog User Account Control Allow UIAccess applications to prompt for elevation without using the secure de... talks about the UAC which related with the remote assistant problem.
I have tried this method and work fine for windows 7
Following steps need to apply:
1. open group policy edit.
2. go to windows Settings-> Security Settings->Local Policies->Security Options
3. find "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop", and enable it.
Then remote assistant works fine. And administrator can see the UAC message from his console.
Thank you! It worked! 🙂
I know this thread is a little old but could you please tell me where you made this change for testing purposes in 'local group policy editor?' I've made this change and it is not persistent. I'd like to test this using 'local group policy editor' first and verify that it is still a solution to this issue.
Thanks in advance.