Receive notification right in your inbox whenever new content like this is released & sign up for our email list!
We’ll send you the latest updates, how-to’s, and solutions to empower you at every endpoint.
OSD Cloud is created and maintained by David Segura @SeguraOSD.
OSDCloud is a solution for deploying Windows 10/11 x64 over the internet using the OSD PowerShell Module. This works by booting to WinPE where the OSDisk is wiped and partitioned. Once this is complete, the Windows Operating System is downloaded from Microsoft Update (using CuRL), before finally being staged (expanded) on the OSDisk. Driver Packs from Dell, Lenovo, and HP are downloaded directly from each of the manufacturers where they are installed in WinPE or in the Windows Specialize Phase. For computers that do not have a Driver Pack, hardware drivers are downloaded from Microsoft Update, so this should work on just about any computer model out there
On this page, I’m going to give a very simple overview and demo, of the basic functionality. Once you know the basics, you can start to go much further, implementing your own unattended file, enabling or disabling capabilities, removing Appx packages, and more. See Functions
OSDCloud requires that you boot from WinPE which has PowerShell and a few other items enabled and has Internet Access. Rest of the hard work of adding Modules to WinPE, David has simplified it down to a couple of commands. The content is hosted on GitHub, so you can always go behind the scenes and take a look, nothing is a black box.
What I appreciate about OSDBuilder is the logging. Everything you could want is logged. Using this method, then posting the logs to your internal doc site provides complete transparency for what is going into your OS Media.
I’m leveraging a ConfigMgr Task Sequence since ConfigMgr already had WinPE with PowerShell and other items integrated into it. I also have BGInfo integrated into my WinPE, which is slick.
However, if you want, you can create your own completely custom WinPE, which David talks about in his docs.
My Task Sequence is very simple for the demo, just to show how David has done all the work for you. I’ve added an “Eject CD” step for when I’m running it on VMs, just to ensure it doesn’t reboot into WinPE on accident.
Run Command Line Step
cmd.exe /c start /wait %SYSTEMROOT%System32WindowsPowershellv1.0powershell.exe -ep bypass -command (new-object -ComObject Microsoft.SMS.TsProgressUI).CloseProgressDialog() ; Start-OSDCloudGUI
And that’s it, it will launch OSD Cloud’s GUI and allow you to continue.
Using the ConfigMgr Custom Boot Image, WinPE loads and presents the Task Sequences:
The Pre-Req Step runs the command to load the requirements into WinPE. You can see exactly what it is doing in the logs, as well as see items downloaded into the temp folder.
The next step launches OSDCloudGUI, with all of its options.
Once you’ve chosen your options, it will continue in PowerShell Console, formatting the drive properly, then downloading the required Windows content.
Similar to “Apply Operating Step”, OSDCloud extracts the Windows Image to the Drive, as shown in the command window.
After the reboot, you’ll see it running OOBE, and eventually get to the point you’re asked questions. (Unless you leverage a custom unattended file)
After going through the rest of the dialogs and adding a user, you’ll be able to log on and use the computer.
About Recast Software
1 in 3 organizations using Microsoft Configuration Manager relies on Right Click Tools to surface vulnerabilities and remediate quicker than ever before.
Download Free Tools