ps1, and then upload to Microsoft Endpoint Manager > Devices > Scripts > + Add > Win 10 or later: If we want to do a script, all we need to do is save the command as a. This could either be as a script or Win32 app in MEM. Now, since we don’t want to run that command on every device manually to install apps from the Store, we’ll need to deploy that command. So if you do happen to run into a “No store account found” error when attempting to install, it may be because App Installer (winget) was not up to date. Before 1.3, installing Store apps from winget required a Microsoft Store/MSA account, but we can confirm on GitHub that was fixed. This does require winget 1.3 (which as of writing is in preview). Here’s what that command would look like for installing the Company Portal: winget install -id "9WZDNCRFJ3PZ" -exact -source msstore -accept-package-agreements -accept-source-agreementsĪnd then we have successfully installed the app!
If we want to script a solution using winget to install apps, we’ll need to automatically accept that agreement and make note of the Id of the app we want to install. But only after we agree to the terms of the Store. In the example above, we search for “company” and get a list of available apps from the Store.
0 kommentar(er)
