Forum Discussion
Windows Autopilot deployment profiles Issue
PeterRising I havent created the machine sec group(assigned type)..I'm doing it now. I will autopilot reset again and try if it sees from the autopilot profile I created. and if it will work, I test too the dynamic group setup.
PeterRising It worked. fixed using Group Assigned and Dynamic Device.
Another 2 issues related to Autopilot Profiles are:
1. I have machine where I autopilot reset, and then when I logged in as standard user, the old user account(auto added as local administrator) still there.
2. Machine name conversion is not following the rule set DYD-%RAND:5% or DYD-%SERIAL%
is it related to microsoft announcement. any knowledge about it? https://techcommunity.microsoft.com/t5/intune-customer-success/known-issue-with-rename-device-setting-for-windows-10-devices-in/ba-p/390868
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;
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}}
