OSDCloud: The ZTI Way
04-16-2021 8:38 PM
Last updated
04-16-2021 8:38 PM
Last updated
Disclaimer: All information and content in this blog post is provided without any warranty whatsoever. The entire risk of using this information or executing the provided content remains with you. Under no circumstances should mentioned persons or vendors, the author, or anyone else involved in creating these blog posts be held liable for any damage or data loss.
Knowledge: I assume that people who read this blog post have an general understanding of Windows ADK/PE, Windows 10 deployment, PowerShell and Windows Autopilot, so I won't be deep-diving into details about that in this post.
In this blog post I'll be using OSDCloud created by David Segura to create a Zero Touch (ZTI) Windows 10 deployment experience, if you are not familiar with OSDCloud then get started here or take a look at these great blog post Part 1 and Part 2 by Mattias Melkersen which should prepare you for this blog post.
You might know David Segura for his OSDBuilder project which is a awesome PowerShell module for Offline Servicing Windows Operating System Image.
WHAT DOES ZTI STAND FOR? Zero Touch Installation (ZTI) - is a fully automated deployment solution that require no user interaction.
OK, so if you have followed the walkthrough of OSDCloud creation provided in the above link(s), you should now have a workspace containing AutoPilot profile(s), Boot Media and maybe a wallpaper.
Now, let´s make the customizations that make it possible to automatically run OSDCloud with ZTI.
First we'll need to create a PowerShell configuration file and upload it to a online storage e.g. GitHub or a Webserver. This sample has been borrowed from David Segura
Copy the URL of the PowerShell file, we need it in a step further down below.
Run PowerShell as administrator.
So, in this elevated PowerShell session, we will now add support for WiFi and ZTI with the below command. Remember to replace the URL "some-online-cloud-storage.com" with your own.
If you need WinPE drivers just add manufacturer to the parameter -CloudDriver e.g. Dell or HP.
Do you need custom WinPE drivers? No problem! You can add them with this parameter -DriverPath <Path> e.g. C:\Temp\WinPE\Drivers
Note. The more you add to the boot media the bigger file you get - Just keep that in mind...
Now, create new ISO(s) with the below command.
Mount the "OSDCloud.iso" or "OSDCloud_NoPrompt.iso" image to a Hyper-V Virtual Machine.
A special thanks go once again to David Segura and his team of contributors for their awesome dedication to the OSD-community! If you want to learn a lot about OSD please visit his blog here
If you have any questions regarding this topic, feel free to reach out to me. I am most active on Twitter!
Start the Virtual Machine, lean back and watch the magic of ZTI