![]() ![]() Note, as it is a multi-file manifest, the path is the containing folder which is why it’s best to download each into their own folder. $templateFilePathversion = $path + "chrome.yaml" Now specify the filenames to use: #File Name Update 12/07/22 – Updated Winget.exe to replace old AppCLI oneįirst up, create a temp folder for the files to live in (I’ve opted for a random with the date): ![]() Update 12/11/21 – Thanks to the excellent work of Phil Jorgensen this can now run in the System Context which removes the admin rights requirement If we use Chrome as an example, most manifests will include 3 files, an installer, a locale and an app one, we need to get all 3 If you want to grab some manifests to test, the official repo is here: Therefore we’ll grab the file and store it locally ![]() The first thing to note is that a custom manifest has to be local, either on the machine itself, or on a network drive. This blog post will cover how to use a custom manifest stored online to deploy an application and then using a runbook With the release of Winget, we now have another app deployment method which works nicely with Intune.Īt the moment building a custom Winget repo is not an easy task, but you can deploy using a custom manifest. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |