Bootable iso image of windows 10
WindowsIsoPath (Not required) - as mentioned in the pre-requirements section, you need to source your own copy of Windows 10.WinPEPath (Required) - I’ve put a copy of WinPE up on my own storage account - feel free to use it, but if the cost of storage ends up too much, I will take this down.Hitting enter will kick off the device provisioning code. Open up PowerShell 7 as an administrator and we will type in the following command: Publish-ImageToUSB -winPEPath "" -windowsIsoPath "C:\path\to\win10.iso" -getAutopilotCfg Once all the pre-requirements are installed, plug a USB into our device and let’s create an Autopilot provisioning device. Install-Module -Scope CurrentUser -Force
#BOOTABLE ISO IMAGE OF WINDOWS 10 INSTALL#
This can be procured from many locations - if you do not have access to this, someone you work with will - just make sure you have a copy of the latest *.iso on your device.įinally, let’s install the module.
#BOOTABLE ISO IMAGE OF WINDOWS 10 WINDOWS 10#
The module uses Windows 10 installation media to create the bootable media. Some of the helper functions rely on other modules - so let’s install those (using PowerShell 7 of course.) Install-Module WindowsAutoPilotIntune -Scope CurrentUser -Force Below is probably the easiest of the lot. The module was written primarily for PowerShell 7 - if you don’t have it yet, there’s a bunch of ways to get it on your machine. Let’s get into how we use it! Pre-Requirementsįirst things first, we need to make sure the device you are going to use to build the Autopilot device has a few pre-requisites: This is a solution developed over the last few years and road-tested with multiple clients and environments - something that is reliable enough that I’m happy enough to share it as a complete solution - something I rarely do due to being an obsessive perfectionist… Well, I’m here to say I want to make it a little less painful with my first published PowerShell module - ! Hardly the autonomous, streamlined sales pitch we’ve been sold - is it? Finally, if the device is already past the OOBE, re-image the device and hand it over to the staff member.Capture the hardware hash of the device and upload it to Intune.make sure a CLEAN copy of windows 10 is installed on the device - which it never is.What is never told to us is that before we do any of this, we need to: I totally agree - the sales pitch we are all given is that your staff can go out to a big-box store, buy a laptop and in minutes be greeted with a “welcome to mega-corp” login screen. The most common complaint that I’ve received from people over the last few years around Intune / Autopilot / Modern Management is that people find it frustrating how much effort is involved in getting a device prepared to handover to a client for Autopilot enrollment. Published: File under: Azure, Intune, PowerShell