Autopilot - Manually register devices with automatic upload

 

This can be very useful for everyone that have a test lab where you want to register your virtual machine in Intune.

Here's the quick step on how to register your machine from the OOBE:

1. When you get to OOBE, press "Shift + F10" to open a command-prompt:
   
   
2. Now, all you need to do is run this commands:


3. After running the commands, you'll be prompt for valid credentials for adding the device to Intune.
   
   

And...you're done! The device information (hardware hash, etc.) gets registered and if you boot up your device again, you'll enter the autopilot process.

PS Scripts - Set Windows Registered User and Organization

Here's a quick and easy PowerShell script to set Windows registered owner and organization. The script will automatically set the owner as the logged user.

Tip: Use it during Autopilot deployment so you can have this information automatically added after the assigned user sign-in.

Windows Autopilot Ultimate Guide by Robin Hobo

 

If you're looking for the most comprehensive step-by-step guide for Windows Autopilot, I strongly recommend you to take a look to Robin Hobo's "Windows Autopilot – The ultimate step-by-step deployment guide".

It's just so simple, accessible and straight forward that you will start using Autopilot in a couple of hours.

So, go ahead and take a look to Robin Hobo's post:
Robin Hobo - Windows Autopilot – The ultimate step-by-step deployment guide

Microsoft Windows Autopilot – Introduction Video

Here’s a quick but well designed video quickly explaining what’s Microsoft Autopilot and how it works!

Microsoft Autopilot Explained

M365 Series - Windows Autopilot White Glove – What is it?

The world of Windows deployment is radically changing in the last couple of years with Windows 10.

With the introduction of Windows as a Service, Windows Autopilot and the Microsoft 365 ecosystem, the need to create a golden image and deploying it massively is no more the “only good scenario” available for enterprises.

Specifically the Windows Autopilot was a very nice way to give the user a machine where he only needed to login with it’s corporate device and the machine get all the corporate configurations.

But…in a lot of scenarios this was a poor experience for the end user that needed to wait a lot of time before he really could use the machine, specially in a poor network environment.

Thinking on this issue, Microsoft developed Windows Autopilot White Glove.
This basically allows IT Administrator to do all the initial work of pre-provisioning all “non-user specific” data. For example, corporate wide software.

After this pre-provisioning, when the user receives the machine, the Autopilot process just resumes the process for the “user-specific” configuration.

Take a look at Windows Autopilot White Glove in action:

A day in a life of an OSD Guru

Here’s one excellent presentation during Microsoft Ignite 2018 with Johan and Ami Arwidmark.
Although not a in-depth presentation, it really touch's all different themes about Windows 10 deployment, from the traditional scenarios to the new one’s, like AutoPilot.

Take a look here: