badtechs.blogg.se - Patchmypc alternatives

This Project does not provide Applications directly, Recipies provide the links to the Applications. Janik von Rots - Copy-CMDeploymentTypeRule Used and Modified code from the following, Thanks to all for their work: See also the list of contributors who participated in this project. Andrew Jimenez - Main Author - asjimene.If you have questions feel free to post an issue with the "Question" label here on GitHub, or ask me on Twitter (publicly is preferred, but I don't mind DMs).Run CMPackager as usual, the first run will create the recipes and place them in the recipes folder, future runs will update the recipes and download the drivers.įeel free to create your own Recipes, Contribute to the main code, or provide feedback!.Navigate to ".\ExtraFiles\Scripts" and open "MicrosoftDrivers.csv", Remove any Drivers that you want packaged, All models currently supported by the script should already be there.Add the "MicrosoftSurfaceDrivers.xml" Recipe to the "Recipes" folder.Enabling the Packaging of Microsoft Surface Device Drivers and Firmware

MEM ConfigMgr Console - Tested on SCCM 1906 - works best if the console has been opened at least once. Note that some packages require admin to be packaged (App is installed then uninstalled to grab version info)

Run CMPackager.ps1 - Recipes in the "Recipes" folder will be packaged if required.

Check out the Recipes in the "Disabled" Folder, Modify them to your needs, and copy them into the "Recipes" Folder.

Set up your SCCM Preferences in the CMPackager.prefs file (it is a standard XML file).The goal is to be able to package any frequently updating application with little to no work after creating the recipes. This Application is a PowerShell Script that can be used to create applications in SCCM, it takes care of downloading, packaging, distributing and deploying the applications described in XML "recipe" files.