Forum Discussion
Remote assistance with Quick Assist is changing
Hi Insiders! Russell Mosier and Bianca Taylor, from the Experiences + Devices team are excited to share an upcoming change to their remote assistance app, Quick Assist.
Remote assistance wi...
edd080 You're welcome. You may have to run this command first in an elevated PowerShell prompt before running the DISM command (change Path if you use a different location): Add-AppxPackage -Path "C:\Temp\MicrosoftCorporationII.QuickAssist_2022.509.2259.0_neutral___8wekyb3d8bbwe.AppxBundle"
Also, I was unable to run it as a GPO startup script, since the SYSTEM account is not allowed to run the Add-AppxPackage command. I guess I can use our Asset Management System, which can run scripts as different user, but it just doesn't work as well as GPO.
Do you have any suggestions on how to deploy on users systems as administrator?
I have created a package through SCCM which points to the powershell script, it runs as admin via sccm, tested on a few machines and it worked out fine so far; I will be deploying it to the other machines and see how it goes.
- Thanks for your update! We use a different product instead of SCCM which can do the same thing, I just find that it doesn't work as good as GPO. However, it looks like we don't have another option for deployment to our current computers. I will be creating our 21H2 image soon and I will make sure it will have the new QuickAssist pre-installed.
- Not sure if this might help you out then, what if you create a scheduled task via gpo that runs as user NTAUTHORITY , that way it runs with elevated privileges and you can include the power shell script from there. The scheduled task will not be visible to the user if they enter the scheduled task application from their machine; It will be visible if you use the run as option and authenticate with admin credentials. Hope it might help.
- Unfortunately I will run into the same problem as having it as start-up script. For whatever reason Microsoft decided that NTAUTHORITY\SYSTEM is not allowed to run Add-AppxPackage. I wasn't able to get it installed with just the DISM command, did you?