Once you boot to the OSDCloud.iso, you will need to install the OSD Module first since it is not installed in the ISO by default. While you can add it, I recommend NOT so that you can always get the latest version

Once the OSD Module is installed, go ahead and change the Display Resolution (Virtual Machine) to your liking

Install-Module OSD -Force
Set-DisRes 1600


In the screenshot below, you can see I added the -Screenshot parameter. This will be covered at the end of this page. Once OSDCloud has started, you will go through a series of menus to select the OSBuild, OSEdition, and OSLanguage. These can be set by Start-OSDCloud parameters


After the Start-OSDCloud (preflight) is complete, the work shifts to Deploy-OSDCloud.ps1. I'll discuss this further in another page

AutoPilot Profiles

If you added AutoPilot Profiles to your OSDCloud.template, or in your OSDCloud.workspace, they should be in WinPE. You can select one, or skip this entirely


This is a new addition to OSDCloud where you can inject an Office or M365 ODT Configuration file. If you enabled this, make a selection or skip this step. In my example below I have mapped a drive with OSDCloud offline content, so it shows a different directory for the ODT files


Clear-Disk.fixed and New-OSDisk

You will be prompted to Clear any Fixed Disks and then a new OSDisk will be created

Feature Update

The next step is to download (or copy from USB) the Feature Update ESD and to expand the required Index to C:\

Final Steps

In these last few steps, Drivers are downloaded, as well as the required Unattend.xml Specialize content to expand and installed them. Office / M365 ODT Configuration and offline Content will be staged, and finally required PowerShell Modules will be applied to the Offline OS


They are saved on your Local Disk in C:\OSDCloud\ScreenPNG

Last updated