Hi, how are you trying to test this? On new devices shipped from your OEM, or by reformatting an existing Windows 10 machine or upgrading a Windows 7? If the latter, have you created a csv file for the machine and imported into Windows Autopilot devices as shown in the below image?
Glad to hear it worked for you. To answer your questions;
1). The Admin user issue is highlight from this known issues page - https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/known-issues and shown below;
.png){kind=link}
2). Machine name conversion issue, What machine name is being generated in the autopilot setup? A random name? I do know that this doesn't work / work well with Hybrid Azure AD join, but you are using just Azure AD join right?
1). this is purely Intune & AAD. The machine was AAD joined(automatically added as local admin), and then repurposed to a standard user(autopilot reset). I can still see the previous user(local admin) after autopilot reset. My solution might be:
- Use the "wipe action" to totally remove the prev AAD local administrator owner because it already offers the wipe action to keep the enrollment record on my tenant. I hope will completely remove the prev. user.
2) The naming conversation reflected in intune/aad is the same as the device name. No changes at all.
I found the solution, instead of using MyCompany-%RAND:5% or %SERIAL%, use this format MyCompany-{{serialnumber}} or MyCompany-{{RAND:5}}
