0

I have a task sequence to deploy a sysprep'd Windows 10 image.

The TS works fully automatically after the wizard, EXCEPT for the last reboot.

After 'Restart computer' shown in the screenshot, it does not auto login again. If I manually login to the Administrator account, it will quickly finish the last couple steps then reboot to a fully deployed state.

enter image description here

I checked the unattended.xml file for the task sequence, and I see the auto login count for Administrator IS set to 999, so it should be working.

Why does it not auto login for the final few steps?

Improve this question
9
  • Checking the logs will give you more information than the unattend.xml content. Have a look in SMSTS.log and maybe BDD.log. Depending on the deployment phase, they are located in different locations but for your case, they should be in %WINDIR%\TEMP\DeploymentLogs
    – ZivkoK
    Commented Jan 20, 2022 at 20:16
  • @ZivkoKozarov nothing shows up in the logs that seems out of the ordinary/related to this.
    – cclloyd
    Commented Jan 21, 2022 at 16:34
  • Is the computer already joined to the domain when the autologon stops working? (when you have to logon manually for the task sequence to continue)
    – ZivkoK
    Commented Jan 21, 2022 at 19:47
  • @ZivkoK no. It runs that after it logs in (it immdiately does EnableLoginAnimation and the rest of the TS)
    – cclloyd
    Commented Jan 21, 2022 at 21:00
  • I was suspecting a problem with GPOs applied to the computer before the end of the task sequence, that's the most common issue with autologon not working till the end. By default, the computer is joined to the domain during Windows Setup but If you did perform the necessary modifications to your unattend.xml (remove the joindom node) to ensure that it is only done during "Recover from Domain" step, then it must be something else...
    – ZivkoK
    Commented Jan 21, 2022 at 22:03

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .