Hi, I was wondering if someone would be able to shed some light on a issue I am seeing with a cached credential scenario. We are testing the deployment of Intune Autopilot with AAD. The issue we are having goes as follows:
Environment:
Windows 10 Ent 1709\1803
Autpilot
AAD Joined
AAD Connect Syncing users and devices
Steps to recreate the problem:
1. Autopilot begins and we are presented with the basic OOBE questions (Region, Keyboard...)
2. We then need to enroll with the users UPN (test.user@company.com. which is also the users AD credentials)
3. We are then directed to to enter the username
4. after the above username and password are entered, OOBE eventually completes, automatically logs in the user to the desktop with the above credentials provided.
This is all good. Though, the issue is if the user shuts down or get disconnected from internet (at autologn), the credentials that OOBE automatically logged in with (the username and password from Step 2 &3), do not get cached. Which leads to the user NOT be able to physically hit ctrl-ALt-Del to login for the first time. The problem seems to lie in the first Post OOBE autologon, that is does not cache credentials. The only way to cache credentials, is the user has to be internet connected, then logout and log back in. Then the credentials will become cached, other then the above steps, the credentials will not get cache, and if the user is NOT connected to internet, at first physical logon, they will NOT be able to login, as the credentials we not stored.
I hope I was able to paint a proper picture in describing the issue. Please let me know if anything I left out.
Thank you!