Forum Discussion
Community ManagerRepost: Make quick assist run as admin
Mohammad_AlShaabi
You can do everything in the Nov 30 2023 05:18 AM post using Quick Assist. You do not need physical access to the machine to do any of those steps.
Note the runas /user:.\Administrator cmd, which you run inside quick assist. That gives you an elevated prompt without physical access to the machine or needing to have the user click anything, and you can proceed to make the registry changes in quickassist as well, by following the other steps.
Hi Glindauer, just wanting to be totally clear here -- in Quick Assist, the user receiving help still has to do the first step: "Allow Screen Sharing" to the incoming connection. No?
I prefer users I'm helping know that I am taking control of their machine, up front, so this seems to fill the bill for me.
I also like the idea of putting the 0x1 part of the command into a Startup batch file to reset back to secure. Haven't tried it yet,
My first paragraph should have read: "in Quick Assist, the user receiving help still has to do the first and 3rd steps of these: 1. Allow Screen Sharing" to the incoming connection, and, then, after the helper does a "Request Control," 3. Allow control.
Doesn't seem like this tool can be used as a standalone support tool without intervention from the user, in other words.
Yes, you are correct in both 1 and 3. The end user (being helped) has to Allow both screen sharing, and to Allow you (remote helper) control of their computer.
I think your idea of having a batch file to reset the UAC back to default (separate protected screen) is great, good thinking.
I also wanted to point out that in many cases you can be in a Microsoft Teams meeting, screen sharing, and allow a remote user to control the computer (again, one both has to share their own screen, and is prompted to Allow control).
This doesn't fix the UAC difficulty, that still needs to be handled as described in this thread (or some other way). The reason Teams might be a better solution than Quick Assist is that users may be more familiar with Teams. However, Teams teams currently has a drawback: screen sharing currently doesn't always show the Take Control GUI, and I'm not sure why. I see this more when end user is at home (not on Domain network).