OSDCloud - Deploying Windows 10 to Surface devices with WinPE - Walkthrough with Intune & Autopilot

[@fbifido2]

I have now learn how to use OSDCloud, Thank you :) .

[@theCMC]

Happy to help!

[@HeyRadu]

Hi Dean, thank you for sharing with us the live walkthrough for the OSDCloud method. I believe it's an excellent & efficient way for quickly testing it into Hyper-V / VMware demo environments.

[@theCMC]

Glad you enjoyed it!

[@imranawan7908]

Great Video, When the surface joined via Autopilot, was it Azure AD or Hybrid? Can you remove unwanted apps? Can you rename the hostname as part of the enrollment ? But its a great video and thanks for sharing

[@theCMC]

Thanks! It was Azure AD Join Autopilot for this demo. You could remove unwanted apps via an App Uninstall Policy, but that’s not ideal I guess.

[@theCMC]

You wouldn’t be able to rename the device as part of the enrolment. It’d either be randomly named or assigned a name based on the autopilot profile device name setting (a prefix and then variable). You can rename the device once the device is built, either in MEM portal or in the Company Portal on the device itself.

[@pacmanh22]

is the USB needed to boot into WinPE?

[@theCMC]

Yes. It is built on an admin workstation as described here: osdcloud.osdeploy.com/get-started/requirements It essentially contains the scripts and components needed to get started building any device from the cloud.

[@fbifido2]

@@theCMC 0. Could all this be automated. 1. We build a admin workstation to create the WinPE boot image, ok. - After image is created do we still need the admin workstation? - Can we put Office, 7zip, VLC, AdobePDF, FoxitPDF, etc... in the core image, as to save time when installing windows. - Can't we just put the full install of windows on the usb at this point, so that we don't have to download it later? 2. We need to go to each user system to generate a json file to upload to Intune ? - Can't the WinPE image we created include a json file to tell windows that this pc/laptop should be enroll into Intune, so it should generate a JSON file and upload & register it into our azure account? - Can't we set the answers to the WnPE questions in the image, to make the deployment faster?

[@theCMC]

@CloudManagement.Community 0. Could all this be automated. 1. We build a admin workstation to create the WinPE boot image, ok. Q. After image is created do we still need the admin workstation? A. No, the admin workstation isn't really needed, but could be required to update the boot media next time there is a new version of OSDCloud. Q. Can we put Office, 7zip, VLC, AdobePDF, FoxitPDF, etc... in the core image, as to save time when installing windows. A. No, the "image" that's put onto USB is just the boot media, so it's not possible to add additional software to the image. I'll be doing a video of a new feature that will allow you to install software post-OS install, which may help! Q. Can't we just put the full install of windows on the usb at this point, so that we don't have to download it later? A. You could, but the idea of this is to allow you to pull any supported version of Windows, including all drivers, dynamically from the internet. If you just plan to use a full Windows image, you should continue with MDT, SCCM etc. 2. Q. We need to go to each user system to generate a json file to upload to Intune ? A. No. The JSON is specific to the Autopilot Profile. The JSON is generated from an admin workstation pointing at Azure AD/Intune. Q. Can't the WinPE image we created include a json file to tell windows that this pc/laptop should be enroll into Intune, so it should generate a JSON file and upload & register it into our azure account? A. Almost, yes. This is how it works, except it contains the JSON which tells the device which Autopilot profile / tenant to use in Azure AD. Q. Can't we set the answers to the WnPE questions in the image, to make the deployment faster? A. Yes - this is already released at osdcloud.osdeploy.com, but the video is not ready.

[@theCMC]

I'll correct myself: It is possible to use a custom image: osdcloud.osdeploy.com/get-started/start-osdcloud/customimage