Office 365 Mobile MDM – Modern Device Management with Microsoft 365 Business Premium–Part 1
Intune MDM – Modern Device Management with Microsoft 365 Business Premium – Part 2
Intune MAM – Modern Device Management with Microsoft 365 Business premium – Part 3
Endpoint Manager – Modern Device Management with Microsoft 365 Business Premium – Part 4
Baselines – Modern Device Management with Microsoft 365 Business Premium – Part 5
Deployment – Modern Device Management with Microsoft 365 Business Premium – Part 6
Autopilot admin – Modern Dev Management with Microsoft 365 Business Premium – Part 7
In the previous post I detailed Windows Autopilot from the administrator’s point of view. What does it look on the device side?
Just before the Autopilot Reset is selected in the EndPoint Manager portal as shown above, let me show you one quick configuration I’ve also done in Windows Hello for Business to make life that little bit easier.
In Devices | Enroll Devices | Windows enrollment select Windows Hello for Business as shown above.
I have set the Configure Windows Hello for Business to be Disabled. Because I’m using a machine WITHOUT a TPM chip here (i.e. a Virtual Machine), it means that if Windows Hello for Business is enabled I’m going to need to go through the process of registering a device PIN. For now, to keep it as simple as possible, I want that Disabled.
Of course, I have also completed the Autopilot enrolment process and created an Autopilot device policy as detailed in the previous part in the series. Note, that a user has also already been assigned to this device. This means that the machine will be joined to Azure AD using this assigned user. That means they will not need to input their credentials during the process.
After selecting Autopilot Reset in Endpoint Manager I am asked to confirm the process as shown above. Take careful note here of what Autopilot does to that machine.
Select Yes to continue.
Once I select Autopilot Reset in Endpoint Manager, any active user will receive the above message that they have 45 minutes before the targeted machine is forcibly rebooted. I will fast track that process by manually rebooting the workstation to commence the Autopilot reset process.
If the devices is at the lock screen you will see the above message when the Autopilot process commences.
The workstation will then reboot and commence a Windows ‘refresh’ of the device, effectively doing a clean installation of Windows 10.
It will then complete the Autopilot configuration as seen above. You will note here that no user input is required. The reason for this is in Endpoint Manager a user has already been assigned to the device.
Not long after, you’ll will then end up with the ability to login to the workstation, as shown above.
When you do, you’ll be taken through the normal first run Windows experience as shown above.
The standard desktop should appears and all the device policies, Intune, Endpoint Security, etc will commence application to the device. Thus, it is just like you did a manual device join to Azure AD but you DIDN’T! Autopilot did all the hard work for you!
This is an example of how easy modern device management cam make your life once you set it up. If there is a problem with a machine, don’t waste long hours troubleshooting! Do an Autopilot reset to get a fresh version with everything deployed and accessible from the cloud. Easy! Need to reprovision an existing machine for a new user? Autopilot Reset again. Easy! the list goes on and on for the benefits of Windows Autopilot.
Although not yet available, what would you say if the same Autopilot concept was coming to both iOS and Android? Roll on modern device management is what I would say.
Modern Device Management with Microsoft 365 Business Premium – Part 9
3 thoughts on “Modern Device Management with Microsoft 365 Business Premium–Part 8”