Jun 16 2022 12:56 AM
i there
We exprience some weird problems.
Autopilot Windows 11 device and this with the option "user driven" that is no problem.
But when we want to add the device to our tenant with the option "self-Deployment" the device does not get the given name and you can not log in.
All of the above works like a charme with windows10.
Any ideas what could be wrong
regards
Eric
Jun 16 2022 08:43 AM
Jun 17 2022 12:11 AM
I will make a ticket indeed. But also here step by step explain what we do
just as clear, this works perfectly with windows 10
Step 1. We made autopilot deployment profiel.
settings:
Name
DP_FDCS
Description
Deployment profile Fons Vitae Desktop Company Shared inclusive Helllo
Convert all targeted devices to Autopilot
No
Device type
Windows PC
Out-of-box experience (OOBE)
Edit
Deployment mode Self-Deploying (preview)
Join to Azure AD as Azure AD joined
Language (Region) Operating system default
Automatically configure keyboard Yes
Microsoft Software License Terms Hide
Privacy settings Hide
Hide change account options Hide
User account type Standard
Allow pre-provisioned deployment No
Apply device name template Yes
Enter a name FDCS-%SERIAL%
Assignments
Included groups SCG_FDCS
Excluded groups
--
So after uploading the Windows 10 device hardware HASH (DELL Latitude 3420) to Autopilot and putting this in to the Group SCG_FDCS the deployment profile kicks in and all is good.
Same device but with Windows 11, device hangs on country selection page, or with luck login page that does not works.
Jun 20 2022 04:04 AM
Jun 21 2022 12:03 PM
Jun 22 2022 12:58 AM
Jun 22 2022 07:11 AM