Modern OS Provisioning for Windows Autopilot using OSDCloud

Today I want to talk about modern OS Deployment for Windows Autopilot Enrollments using OSDCloud. Also, I will show you where we came from with regards of OS Provisioning and which customizations we made to OSDCloud to make it fit our needs even more.

OSD using a SCCM Task Sequence

When we started using Windows Autopilot back in 2018/19, we needed a solution to prepare existing devices for the enrollment with Autopilot and since we started using Pre-Provisioning (aka. WhiteGlove) as well, the official way for Autopilot for existing devices using the exported .json Profile was not an option. We started using a basic SCCM Task Sequence to install the base Windows Image and upload the Autopilot Hash as described here: and here:
The Task Sequence looked something like this, and contained basically three things besides the OSD itself, the Autopilot Upload, the “Tennant Lockdown” Feature using a script based on the solution of Michael Niehaus: and a part for handling drivers (not visible in the Screenshot).

While this solution worked pretty reliable, we had one issue with this solution, the driver management. Since we had to support more than 100 different hardware models from Dell, HP and Lenovo, we needed to provide drivers for all of these models for the inital installation. Additional to that, we wanted to have a way to allow installation of even more models in case something was not available in a specific region. All this created the need for a pretty large Task Sequence that needed to be maintained and also needed more than 100GB of storage on our around 30 Distribution Points all around the world.

Modern OS Provisioning using OSDCloud

Our Solution for this issue came with the wonderful Project OSDCloud, that supported nearly all of our hardware models out of the Box, by downloading drivers directly from the OEMs, eliminating the need of local repositories for these driver packs. Additionally with the support to download drivers from Windws Update, it even can support new / unknown models.

Since we already wanted to get rid of our SCCM Infrastructure and most of our newly bought devies are already uploaded by the OEM, we decided to go with an bootable USB Drive Solution, which in combination of the integrated Wi-Fi support allows us to worst case use an iPhone Hotspot to reprovision a client if needed.

While OSDCloud provides and integration for Autopilot, it is based on the .json file injection, makeing it unsuitable for Self-Deploying or Pre-Provisioning Scenarios. To mitigate this limitation and to further simplify the GUI to the point, where the admin does not have to choose the OS Version, we decided to build a small PowerShell Forms based GUI, that can be used to launch OSDCloud with a few parameters, Upload the device to Autopilot and set the Tenant Lockdown UEFI Variable. You can find the PowerShell Scripts for the launcher on my GitHub, so you can customize it to your needs:

The first Page of the Launcher will present you two options, the Autopilot Upload Button will unzip a password encrypted archive, containing the Autopilot Upload Script, described here, also i uploaded the script to extract the files to GitHub.

The Start-OSDCloud Button will show a new Page that allows you to select a driverpack and the OS Language.

The Windows Version (Win 10 vs. Win 11) will be automatically selected, based on Hardware support. Since the only devices, that we still want to be able to install Windows 10 have Intel Core CPUs form Generation 2 – 7, i only check for this and an enabled TPM 2.0 Security Chip here.

Once the Launcher checked the HW Compatibility, it fills a global Variable “StartOSDCloudGUI” and hand over the job to OSDCloud with an set ZTD Option, so it won’t ask for permission to wipe the SSD, so be careful during testing.

If you want to know more about this, let me know in the Comments and I will be happy to show you more details if wanted.





29 responses to “Modern OS Provisioning for Windows Autopilot using OSDCloud”

  1. Ahmed


    Very Informative, interested task sequence. could you please share this task sequence.


    1. Hi,

      sure i exported the TaskSequence for you and uploaded it to GitHub:

      You will have to customize it to your needs, the driver packages are 7z compressed folders containing the extracted driver files (.inf / .sys / etc.) The boot image and windows image is basically untouched, and the Hash Upload Package is created as described using the OA3Tool and and Azure Automation Runbook in the backend to upload the device to Autopilot.
      Best Regards

  2. […] Modern OS Provisioning for Windows Autopilot using OSDCloud. Link […]

  3. […] Modern OS Provisioning for Windows Autopilot using OSDCloud […]

  4. Thomas K


    can you explain

    “ it is based on the .json file injection, makeing it unsuitable for Self-Deploying or Pre-Provisioning Scenarios”

    self-deploying by the end user does not work with json injection?


    1. Hi, sure I mean the self-deploying mode that does not require the end-user to type in credentials:
      As described in the article Autopilot for existing devices, which is basically the json incjection, it does not support self-deploying or pre-provisioning (aka. WhiteGlove) scenarios:

  5. Mateusz

    It would be cool if you added support for autopilot tags 🙂

    1. What would you need for GroupTag support? Both the Upload script and the Automation Runbook are already ready for Autopilot GroupTags. The upload script from has a place to set a GroupTag in Line 27. We are using a Companion App as described here to set an individual GroupTag:

      1. Mateusz

        Well, yes indeed, but if we use this tool in many countries we have only one tag defined in the code without the possibility of choosing another.

        1. Would you like to have a free text input field for a GroupTag or would you prefer a Dropdown field with predefined values? I would need to check, but I think this should both be pretty easy to add.

          1. Mateusz

            It seems to me that a drop-down list would be better here to reduce the risk of user errors.

          2. I will have a look into this this evening

  6. Mateusz

    I understand that this script is called manually from a flash drive during OOBE or already on the desktop? Is it possible to create a bootable flash drive that will actomatically start the process u show the GUI?

    1. This solution is primarily targeting WinPE from USB or PXE, like it’s used in SCCM / MDT etc since this is not possible with the official script. During OOBE you can use the official Microsoft Script, which already contains a GroupTag field and an -online parameter to directly upload it to Autopilot, no need for any backend solution like here:
      Another solution during OOBE would be the Autopilot Manager from Oliver Kieslbach:

      1. Mateusz

        I am looking for a solution that has capabilities such as send Autopilot hash and download win 10 – 11 and install the system from scratch. With as little user interaction as possible.

        1. I quickly added a simple GroupTag selection UI to the Upload Script on

          Screenshot of Message

          You can enable it in line 11 and set the allowed GroupTags in line 13.

  7. Thomas K.

    Really great approach.

    Maybe I missed it, but how did you build the osdcloud image to include your launcher and script?


    1. Hi,
      I basically mounted the ready osdcloud image using DISM /Mount-image /imagefile: /MountDir:
      Once the image is mounted, i modified the File in Windows\System32\Startnet.cmd to instead of start the “Start-OSDCloudGUI” to run my modified launcher.
      Also I added a folder called “Autopilot” to Root of the mounted image, that contains the Files for the Autoilot Upload

      Best Regards

      1. Thomas K.

        Works fine.

        When the Mike MDMOSDCloud Gui comes up, by default nothing is selected for the DriverPack.

        Although its an Hyper-V virtual machine and the default OSDCloud GUI shows “Microsoft Update Catalog”.

        Anything I missed?
        Thanks in advance.

        1. I think this is normal and it should still download drivers from MS Windows Update, since the only the selection of the word “none” in line 515 in the script would disable driver download from WU.

          I think if we want to display “Microsoft Update Catalog” we could add an else statement to the if selection in line 452 to do a

          $formMainWindowControlDriverPackCombobox.Selectedindex = $formMainWindowControlDriverPackCombobox.FindString(“Microsoft Update Catalog”)

          But this should be only an optical change, it should not affect the result. Let me try this this evening…

          1. Thomas K.

            Great, thanks. And by the way, nice idea the 15x click on USB Version 0.3 🙂

          2. I just updated the file on GitHub, should now show “Microsoft Update Catalog” instead of empty.
            Yes I also like the “easteregg” to show the original OSDCloud UI in case we need something different 🙂

  8. Thomas K.


    the called Get-AutoPilotHashAndUpload.ps1 in Autopilot.ps1 is the same script as here?


    1. Hi, yes exactly you can use this script. If you don’t want to build the backend needed for the CollectHashandUpload.ps1 script, you can also use which uses DeviceCode Authentication instead, however I personally prefer the first variant, as it is easier for the technician.
      Best Regards,

  9. Thomas K.

    Is anyone getting the same cosmetic error as everything works, but

    powershell -NoL -C Install-Module -Name OSD -Force

    out of

    :: OSDCloud related commands
    powershell -NoL -C Initialize-OSDCloudStartnet
    powershell -NoL -C Initialize-OSDCloudStartnetUpdate
    powershell -NoL -C Install-Module -Name OSD -Force
    powershell -NoL -C Import-Module OSD -Force

    of the startnet.cmd errors out in:

    PackageManagement\Install-Package: The module ‘OSD’ cannot be installed or updates because the authenticode signature of the file ‘OSD.psd1’ is not valid.


    1. Hi, I had this on one of my boot drives, i modified the module Initialize-OSDCloudStartnet.ps1 from “X:\Program Files\WindowsPowerShell\Modules\OSD\\Public\Functions\OSDCloud\” to add “-SkipPublisherCheck” in line 33 that does the autoupdate.

  10. Once I initially commented I clicked the -Notify me when new feedback are added- checkbox and now every time a comment is added I get 4 emails with the same comment. Is there any method you possibly can remove me from that service? Thanks!

    1. Hi, you mean the notifications from GitHub? You can log in to GitHub, go to Settings -> Notifications -> under Subscriptions you can show your “watched repositories” and set if and how you want to notified on a per repo basis.

  11. Phillip

    We would like the ability to add the device to autopilot and your screenshot looks great. Do you have an easy guide on how we can add this to our current OSD cloud usb drive that uses winre? Your link to github has a lot of scripts and I’m not sure what to do. Has anyone written any step by step instructions for using your scripts? I see you’re posting screenshots but I’m really confused.

Leave a Reply

Your email address will not be published. Required fields are marked *