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.
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.
What is never told to us is that before we do any of this, we need to:
- make sure a CLEAN copy of windows 10 is installed on the device – which it never is.
- Capture the hardware hash of the device and upload it to Intune.
- Finally, if the device is already past the OOBE, re-image the device and hand it over to the staff member..
Hardly the autonomous, streamlined sales pitch we’ve been sold – is it?
Well, I’m here to say I want to make it a little less painful with my first published PowerShell module – Intune.USB.Creator!
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…
Let’s get into how we use it!
First things first, we need to make sure the device you are going to use to build the Autopilot device has a few pre-requisites:
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. Below is probably the easiest of the lot..
Some of the helper functions rely on other modules – so let’s install those (using PowerShell 7 of course..)
The module uses Windows 10 installation media to create the bootable media. 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.
Finally, let’s install the Intune.USB.Creator module..
How to use
Once all the pre-requirements are installed, plug a USB into our device and let’s create an Autopilot provisioning device.
Open up PowerShell 7 as an administrator and we will type in the following command:
Hitting enter will kick off the device provisioning code..
A few things to note on each parameter:
- 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. So grab a copy now and store it locally. Consider this fair warning.
- WindowsIsoPath (Not required) – as mentioned in the pre-requirements section, you need to source your own copy of Windows 10. This shouldn’t be difficult. Try and get a copy of the “multi-edition” so you can build different variants if required. If you don’t provide a path to a copy of Windows 10, the device will still be provisioned, but there will be nothing added to the solution except for WinPE.
- GetAutopilotCfg (Not required) – this is a simple switch to allow you to log in to an Azure tenant and capture the Autopilot configuration files. If you omit this, you will end up with a provisioning device that installs windows 10 and does nothing else.
Once our USB has been created, all that is required to do is plug it into our target device and boot from it.
WinPE will load and trigger the built in provisioning script which will load the operating system onto the device and inject the Autopilot configuration file.
Once the device has been provisioned – remove the USB and reboot. We should now be greeted with the standard Out of Box Experience, ending with the ability to log in to the tenant we captured the Autopilot configuration from!
Pretty cool, if I do say so myself.
Using this solution should provide you with a bootable USB that will get you from “out of box” to “ready to enrol” in less than 5 minutes.