Event details
I also think there is still a need for some On-prem infrastructure for OSD. Autopilot solves a lot, but you are still going to find use cases for imaging a system where you have replaced a hard drive or the OS is beyond repair so you will need a MDT server or ConfigMan for that purpose.
"imaging a system where you have replaced a hard drive " Amen; I'd love to know what the recommendation is here.
I feel like this is a huge gap with AutoPilot that was completely forgotten about.
- A lot of vendors OEM’s have cloud solutions to organize the OSD management with bios boot to cloud solution…
- They do but most of those services have a cost not to mention some sort of login that end users would not really have. Heck my techs don't even want those either.
- I recommend using the manufacturer's recovery media. I am familiar with Dell, which will give you an up-to-date Windows image, and Lenovo, which will give you the exact version of Windows that came on the device when it was purchased (which is admittedly not great if that version is no longer supported by Intune). With this method, you need to keep some USB flash drives around with the recovery media, but you don't have to run an OSD environment.
>I feel like this is a huge gap with AutoPilot that was completely forgotten about.
A gap; for sure. Is it _huge_ though? On a day-to-day basis how much bare-metal imaging are you forced to do because of hardware failures? The general expectation is that this is a very, very small percentage. If that's not true, I'd love to hear why it's not. So the question is, how much effort do you want to put into a bare-metal imaging solution? You have options ranging from just installing from ISOs, to MDT, all the way to some cloud OSD solutions.
- For this I am pushing my techs to my build from https://osd.osdeploy.com/ Works great and I do not have to maintain drivers :). It puts the unit essentially back to OOB state and then autopilot takes over once the os has been laid down.
