I've never seen this before and its kind of hard to explain. So i thought i would attach a pic also.
Simply put, the domain prefix is missing. So upon entering a user creds for the 1st time after imaging. The error displays is "Incorrect username/password"
If select "Sign in options" and select the key image, i am able to then use my AD creds to logon.
Has anyone else seen this?
NOTE: The machine actually is domain joined, we just cant see the domain prefix.
Some background:
Win10 1803 Pro
Image captured using MDT
SCCM task sequence (SCCM CB 1802)
Thought it could possibly relate to my unattend.xml which contains:
I understand some of those above settings are deprecated, however It was the only way for me to get around "Just a moment" hang during OOBEsystem phase of the deployment.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi all,
I've never seen this before and its kind of hard to explain. So i thought i would attach a pic also.
Simply put, the domain prefix is missing. So upon entering a user creds for the 1st time after imaging. The error displays is "Incorrect username/password"
If select "Sign in options" and select the key image, i am able to then use my AD creds to logon.
Has anyone else seen this?
NOTE: The machine actually is domain joined, we just cant see the domain prefix.
Some background:
Win10 1803 Pro
Image captured using MDT
SCCM task sequence (SCCM CB 1802)
Thought it could possibly relate to my unattend.xml which contains:
SkipMachineOOBE = true
HideEULAPage=true
HideLocalAccountScreen=true
HideOEMRegistrationScreen=true
HideOnlineAccountScreens=true
HideWirelessSetupInOOBE=true
SkipeUserOOBE=true
I understand some of those above settings are deprecated, however It was the only way for me to get around "Just a moment" hang during OOBEsystem phase of the deployment.
Thanks all in advance.
Share this post
Link to post
Share on other sites