Forum Discussion
Nathan_Pfeifer
Apr 27, 2022Former Employee
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...
GreatToHearFromYou
May 30, 2022Brass Contributor
Thanks! That would be much appreciated! 👍
edd080
May 31, 2022Brass Contributor
Hi there again so this is the command line from SCCM that calls the Powershell script :
"%Windir%\system32\WindowsPowerShell\v1.0\powershell.exe" -ExecutionPolicy Bypass -Command \\server-name\Applications\QuickAssist\quickassist.ps1
sccm will call the powershell script (ps1) which has the following command:
DISM /online /add-provisionedappxpackage /packagepath:"\\Server-name\Applications\QuickAssist\MicrosoftCorporationII.QuickAssist_2022.509.2259.0_neutral___8wekyb3d8bbwe.AppxBundle" /skiplicense
Hope the above might help you out.
- edd080May 31, 2022Brass ContributorYep i totally agree.
- GreatToHearFromYouMay 31, 2022Brass ContributorAbsolutely, I 100% agree.
I guess they try to push the Microsoft Store down everyone's throat, because otherwise hardly anyone would be using it. It is also a way to push businesses from Pro to Enterprise, since the latter can create a customized store with only approved apps. Also, the fact that they will include QuickAssist by default in future Windows 11 images, but not in future Windows 10 images, makes it pretty clear what agenda Microsoft is following. - edd080May 31, 2022Brass ContributorThat is good news! Glad it worked out for you.
Honestly though I think Microsoft should have implemented this as a normal update or at most give us admins something to work on such as deploying it as an msi application; but I suppose, nothing is straight forward after all. - GreatToHearFromYouMay 31, 2022Brass ContributorThank you Sir!!! I don't know what did it, either the -ExecutionPolicy Bypass part or the fact that you run it in a separate PS1 script (I ran it inline from a batch script calling PowerShell to execute), but it doesn't really matter, because of your help I was able to deploy it just using the DISM command now through GPO at startup. 👍