If one of your resolutions for 2020 is to save yourself more time, then Windows Autopilot and White Glove deployment might get you off to a flying start!
Windows Autopilot, (available from Version 1903), enables organisations to easily provision new devices by leveraging the preinstalled OEM image and drivers, with a simple process that can be performed by the end user to get their device business-ready. Autopilot can also be used to reset, repurpose and recover devices - great for those looking to reduce infrastructure management time and simplify processes.
Why you need Autopilot
If you are new to Autopilot, here’s a short re-cap of the benefits:
Autopilot replaces the need for you to pre-build or maintain custom images and drivers for every model of device being used, when initially deploying new Windows devices. Instead, we can leverage the OEM-optimised version of Windows 10 that is preinstalled on the device and initiate a “business-ready” state. As well as saving us huge amounts of time this feature also allows us to apply settings and policies, install apps and even change the edition of Windows 10 being used, (e.g. from Pro to Enterprise), to support advanced features.
It can also be used to re-purpose a device by leveraging Windows Autopilot Reset, to quickly prepare a device for a new user; or in break/fix scenarios, to enable a device to quickly be brought back to a business-ready state.
Once deployed, Windows 10 devices can be managed by tools such as Microsoft Intune, Windows Update for Business, Windows Endpoint Manager, and other similar tools.
Using Autopilot depends on specific capabilities available in Windows 10, Azure Active Directory, and MDM services such as Microsoft Intune. Check out the list of requirements that must be met.
White Glove Deployment with Intune
As you can’t deploy images from the cloud, those using Intune are set to gain the most. Windows Autopilot works with Intune to configure an OS already on a device by pushing settings, configuration and then deploying apps which are specifically targeted to the individual device.
With White Glove, the provisioning process is in fact, split. The time-consuming portions are performed by IT or partners and the end-user simply logs in for a few necessary settings and polices, before they begin using their device. These capabilities build on top of existing Windows Autopilot user-driven scenarios, supporting both the user-driven mode for Azure Active Directory Join; and user-driven mode for Hybrid Azure Active directory join scenarios.
Where to get started…
You may want to start by demonstrating an Autopilot deployment on a VM? I’ve found a great resource here on the Microsoft site, if you want to give it a go. You can also use a physical machine… just skip the instructions to install Hyper-V and create a VM.
As always, let me know if you have any questions or want to know more about Autopilot and Autopilot White Glove deployment.