In this Blogpost I will show you how easy it is now (with the 8.6 RU2/RU3 release) to consume things like OSDCloud without modifying the boot.wim File.
If you are running 8.6 RU2 or higher, do not use my old Blogpost on OSDCloud because here is a very simple and supported method to leverage the same as in my old Blogpost without manually modifying the boot.wim File. The other steps are still valid..
First you have to include the „correct“ packages when creating your Preboot Environment. Make sure all needed packages are added and bring them in the „correct“ order, otherwise this will not work.
Recreate your Preboot Environment and wait until it is finished.
The second step is to create a new Job and add the following Tasks into the Job
The third step is to create a Task using the following command:
This will install and enable Powershell Gallery support and in addition it will install the HP Client Management Script Library (HPCMSL) into WinPE which is very useful if you are managing HP Devices. I highly recommend taking a look at HPCMSL.
The next step is to create a Task to start OSDCloud or OSDCloudGUI
Instead of using Start-OSDCloud you might also use Start-OSDCloudGUI which launches a GUI in WinPE to select OS language and other things.
If you want to use your own ESD/WIM File without downloading the Operating System ISO/ESD Files from Microsoft you could also map a Networkdrive or put the File on a USB Drive.
Here you can find a Blogpost with some examples to securely map a Drive in WinPE Part 1 and Part 2.
Make sure your file resides in a folder called OSDCLoud\OS. The files are automatically mounted… You have to use the -FindImageFile parameter when starting OSDCloud.
Wait for the Job to finish… – Thats it.
Reference:
Endpoint Management 