This page will go through the steps of enrolling a device into Endpoint Manager and Autopilot.
...
Adding a Device record to Group Membership in Azure Active Directory
To access Azure Active Directory you can chose the Admin Tile within Office 365 or follow this LINK. After clicking on the link you will need to select Azure Active Directory.
To get to the main options for Azure AD click the Azure Active Directory on the left panel
First, let’s make sure that the device is in Azure AD after being bound to the on prem AD domain
Under the Manage selections chose “Devices”
Search for the computer name of the device we want to enroll
Click on “Azure Active Directory” on the left to go back to the original set of options
Select “Groups” from the panel to the right.
Search for the ManualAutoPilot group
Click on the ManualAutoPilot group to open up the options for that group
We want to add the device that is enrolling to this group so you will select “Members”
After selecting “Members” you should click the “+ Add Members”
Search for the computer name or Azure ID of the device you want to add to the group
Click on the device and then click on the blue “Select” button
You are ready to reset the device.
...
Changing the Name of the Device
You will be working within Endpoint Manager. You can access Endpoint Manager through the Admin Tile in Office 365 or through this LINK.
Once you’re in Endpoint Manager you will select “Devices”
Select “Windows” as the platform
Search for the device by its serial number. In most cases (as of July 2021) it’ll show up as Desktop-RANDOMSTUFF
Select the device you’re working on. You should see a screen with the following information
To change the name select the three “…”'s to find a “Rename Device” selection
A new pane will open and you can type in SSD-SERIALNUMBER
Select “Yes” for restart after if you are with the system otherwise leave this option as “no”
If everything worked correctly you should see a Restart and Rename “Complete” Status in the device record
...
Only add the Device record when the name change has completed and Azure Active Directory and Endpoint Manager displays the correct name. If either name is wrong then sync has not completed between the two and the Autopilot profile will not work correctly
Checking accuracy in Endpoint Manager - Under Devices → Windows you can search for the serial number of the device and see if the name is SSD-SERIALNUMBER
Checking accuracy in Azure Active Directory - Under Devices you can search for SSD-SERIALNUMBER. Because we are a Hybrid AD setup you should see two records that match.
If you see more than two you will need to stop and figure out where the rogue records came from.
If you only see one record then the device’s name update has not sync’d with Azure.
You will want to add the Endpoint Manager system to the ManualAutopilot groupuse Azure Active Directory to put the device record into ManualAutoPilot group.
Select “Azure Active Directory” then “Groups” from the panel to the right.
Search for the ManualAutoPilot group
Click on the ManualAutoPilot group to open up the options for that group
You will select “Members” then the “+ Add Members”
When searching for a device you will see both devices. You can add both devices without it duplicating anything as it will only keep one entry.
After the device record is added to ManualAutoPilot group you will have to wait between 10 minutes to 36 hours for the next step to complete. (Yes I’m serious and so is Microsoft)
You will want to use Endpoint Manager for verifying that Autopilot profile is assigned and working
When you’re in Endpoint Manager you’ll select “Devices”
Select “Enroll Devices”
Select the “Devices” option under Windows Autopilot Deployment Program
Search by serial number to see the device you’re working with
This is an example of what you should see:
When clicking the checkbox next to the device you can change the settings of the device when its imaged/Autopilot Restored.
You can set the name as SSD-SERIAL
You can set the primary user
The record may have one of the following Autopilot Profile Statuses
“Not assigned” - Typical of a device first exchanging data between itself and Autopilot/Azure
“Pending” or “Downloaded” or “Installing” - The profile exchange is complete but one or both entities have not confirmed a working profile yet.
“Assigned” - The exchange is complete and an Autopilot profile is on the system and ready for use