remote control uac
We're using Teams for chat and video meetings, but would like to use the screen sharing and remote control for troubleshooting and suppport requests. However, Windows does not pass UAC prompts through the Teams screen sharing.
Regarding the comment on lowering the UAC level, when I used an Azure admin account this was the behavior:
In testing Teams, when I use an admin account for screen sharing, the user's screen view does not go black. I can see their desktop and the UAC prompt but the mouse and keyboard control becomes unavailable even when the user gives control.
Having the option to run Teams as a service with admin creds should be added to the functionality. With an increasing number of users working remotely the need for remote support is growing.
lower UAC so it won't dim display and it'll go through
It would be huge if UAC prompts were passed through Teams. IT managers would love to be able to support their team without using third party software.
Oliver Frye commented
This would be a great improvement to the Teams screen sharing functionality.
IT support staff will be able to use Teams instead of a third-party software package to provide remote support to users if they were able to get past the UAC prompt without the physical user's intervention.
Many third-party screen sharing applications already support this functionality (e.g. Teamviewer, Take Control, etc) and I know for certain in our case that providing this additional functionality would allow us to use Teams exclusively and no longer have to pay for an additional subscription just to remotely support users.
Please, this is a BASIC function in a Support Desk which is missing. Unfortunately Teams appears to have inherited this stupid limitation from Skype, which was already lame... :(
I'm also facing the same issue. Will this feature be allowed in future releases?
Also worth pointing out: UAC seems to break the remote control functionality entirely. I had the user acknowledge the UAC prompt and afterwards I could move my mouse, but clicking and using the keyboard did noting.
Ending and resuming control did not fix it. We didn't have time to troubleshoot the issue further, so I can't say if restarting the call or Teams would've fixed it.