OSD Community Tools

When i read what Update-OSDeployCore do. "Refreshes local OSDeploy Core content by invoking Update-OSDeployCoreCatalogOS first, Update-OSDeployCoreESD second, Update-OSDeployCoreRE third, and Update-OSDeployCoreDrivers last." First i cant find t...

Add so it: Install the OS. Autopilot Reg. Turn off the PC and make it ready for the user.

Add so i can set in that i only can use this device modules. And you can set a pre select like Microsoft Catalog.

I would like to submit a feature request regarding the handling of Provisioning Packages (.ppkg files). The Use Case (Why we need this): As an MSP/IT service provider, we use OSDCloud to provision laptops for multiple different clients. Each clien...

We currently use OSD PSModule integrated with ConfigMgr task sequence. The new OSDCloud PSmodule will definately need Command Line / Zero Touch support and easy way to customize the deployment in a similar way you can use $Global:MyOSDCloud variab...

It would be useful to be able to import a CA certificate to the Trusted Root Certificates store on both WinPE (for the driver downloads) and then have that also added to the deployed OS (for autopilot) for our transparent proxy web filter. (HTTPS ...

We use this functionality to add helpful scripts for our Desktop Techs to run if needed in OOBE if they encounter issues during Autopilot or Provisioning. Here is an example of that the installs the 'Autopilot Diagnostics Community' script. We typ...

I hope this switch manages to make its way into V2 once we can start calling via CLI again. Very useful to us thank you!

Having the default set to Windows Pro Retail probably covers 80-90% of deployments, but for the rest it would be great to see the OA3 data queried so that techs do not necessarily have to touch the OS Edition drop down menu and therefore reduce th...

I am trying to "validate" that Deploy-OSDCloud was "Successful". The problem is, i don't have anything to key off that tells you its ok to reboot. I thought looking for a string in the X:\windows\temp\osdcloud-logs\transcript.log would do it, but ...