OSDCloud Blog Series

Disclaimer: All information and content in this blog posts 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 David Segura, Microsoft, its author, or anyone else involved in the creation of these blog posts be held liable for any damage or data loss.

OSDCloud

In this blog series, I would like to introduce the shiniest OSD solution in the past years, which I was working a lot with and had so much fun. Most of you are already heard about OSDCloud from David Segura.

  • If you are new in this topic, you are at the best place.
  • If you are evaluating this solution, you are at a good place.
  • If you are using for costumers, stay here and trust me, I will show you some deep dive tricks in the later posts.

High level architecture from my point of view.

Each part of this OSDCloud flow will be described and I would be happy to discuss afterwards here in the comments or just reach me out in Twitter.

Short (management) summary

Pros:

  • No infrastructure needed
  • Able to deploy a fully customized image within minutes
  • Low maintenance
  • Easy to maintain images
  • Up to date drivers from vendor
  • Easily scales to worldwide deployment
  • Easily supports Autopilot via JSON

Cons:

  • Required to load into Windows PE (USB boot)
  • Internet required, if your scripts are stored in an online storage and want to update your OS and drivers during the process (otherwise check the comment from Gary below)
    • But WinRE supports Wireless

If you want to deep dive into the logic and source code, you can find the GitHub project link here and the PowerShell gallery link here

 

So, let’s jump into the new operating system deployment world with OSDCloud.

OSDCloud #1 – Basics

OSDCloud #2 – OS Installation with OSDCloud GUI

OSDCloud #3 – Zero Touch Deployment

OSDCloud #4 – OOBE customization

OSDCloud #5 – Azure integration

OSDCloud #6 – Notes from the field

OSDCloud #7 – Bonus

OSDCloud #8 – WDS Integration (under review)

OSDCloud #9 – OOBE Challenges

OSDCloud #10 – Full Automation Flow

4 Comments


  1. So you know if the solution will support WPA2 Enterprise any time soon?

    Reply

    1. Wireless support generally is a big effort for a relatively small gain. I always recommend using wired setup.

      Reply

  2. You note that Internet is required, I would disagree. I have everything synced to the flash drive. I can boot to the flash and get to OOBE login fully offline.

    Reply

    1. Thanks Gary for your comment and giving this idea to start an offline process.

      Reply

Leave a Reply

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