none
MDT 2013 Update 1 Windows 10 Deployment Not Automatically Logging On After Windows Updates

    Pregunta

  • I created a new Windows 10 standard deployment task and clicked the check boxes to enable the Windows Updates tasks in the TS.  It logged in automatically after each reboot during the deployment until it rebooted for updates.  Then it stops at the Administrator login screen waiting for manual user login after each reboot.  After manually logging in for each round of updates, the deployment task completes successfully.

    Does something have to be manually configured for autologin to work or should it work by default?

     
    lunes, 21 de septiembre de 2015 3:31

Respuestas

  • If found that the cause of the issue is because the deployments are being run through Hyper-V Manager using the enhanced session mode.  

    When enhanced session mode is not enabled, I can still see the progress on the task sequences after reboots.

    That's why when a log in manually, I can see that the deployment was still continuing in the background.  The task sequences do not stop, but they are hidden behind the login screen.

    miércoles, 30 de septiembre de 2015 2:48

Todas las respuestas

  • I created a new task sequence for Server 2012 R2 and it has the same problem of not automatically logging in after reboots.  So, it is not a problem specific to Windows 10 deployments.

    This is a brand new deployment share and all brand new task sequences.

    The password I specified works, but it just doesn't logon automatically. 


    • Editado MyGposts lunes, 21 de septiembre de 2015 14:05
    lunes, 21 de septiembre de 2015 14:04
  • I checked the unattend.xml of all the task sequences and they are all set to autologon true 999 times.  Some show password as plain text and some show an encrypted password, but they all do not automatically login during the task sequence.

    Is there someplace else you have to configure the automatic login after each reboot in the task sequence?  The administrator password I specified during the creation of the task sequence is being successfully being set, but it stops at the login screen waiting for the password to be typed in manually after each reboot that happens during the task sequence.


    • Editado MyGposts lunes, 21 de septiembre de 2015 16:36
    lunes, 21 de septiembre de 2015 16:30
  • Is the image applied a sysprep and captured image?

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    lunes, 21 de septiembre de 2015 22:55
    Moderador
  • These are not sysprepped images.  These are deployments created directly from the ISO install files.

    I plan to create the first image from the ISO, install Windows Updates and then sysprep and capture the new image after the  updates are installed.

    martes, 22 de septiembre de 2015 0:11
  • Very strange.  Can you post a OneDrive (or something similar) link to your bdd.log and setupact.log?

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    martes, 22 de septiembre de 2015 0:17
    Moderador
  • Here is a link to the logs bdd.log

    Setuptact

    martes, 22 de septiembre de 2015 2:04
  • The BDD.log is only a few lines.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    martes, 22 de septiembre de 2015 17:53
    Moderador
  • I am having a similar issue with my Win10 Upgrade task sequence. The administrator account was disabled. I thought the entries in the Configuration phase of the Unattend.xml file enabled the administrator account and configured it for AutoLogon?
    martes, 22 de septiembre de 2015 20:14
  • I am having a similar issue with my Win10 Upgrade task sequence. The administrator account was disabled. I thought the entries in the Configuration phase of the Unattend.xml file enabled the administrator account and configured it for AutoLogon?

    Autologin is never configured.  There is a bug right now that at the end you would have to log in to see the summary screen (unless you have summary disabled).

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    martes, 22 de septiembre de 2015 20:57
    Moderador
  • I am having a similar issue with my Win10 Upgrade task sequence. The administrator account was disabled. I thought the entries in the Configuration phase of the Unattend.xml file enabled the administrator account and configured it for AutoLogon?


    Autologin is never configured.  There is a bug right now that at the end you would have to log in to see the summary screen (unless you have summary disabled).

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    Can you elaborate on that? Why is autologin never configured? If this behavior is a bug, what is SUPPOSED to happen during the Upgrade task sequence? How are the post upgrade task sequence steps supposed to be executed?
    martes, 22 de septiembre de 2015 21:48
  • They run before login (or at least they are supposed to).

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/


    martes, 22 de septiembre de 2015 21:58
    Moderador
  • They run before login (or at least they are supposed to).

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/


    After looking at my monitoring for an Upgrade deployment, I see that the "Post Upgrade" steps are indeed running, even without me logging in. These include the steps in the Post Processing folder. But, until I login the task sequence is not properly "finishing." My reporting still shows the deployment as in progress, and I don't get the "LTI deployment completed successfully" message until I login with an account that has admin rights.
    martes, 22 de septiembre de 2015 22:26
  • The summary screen part is a bug.  I haven't tested it yet but, you might be able to disable the screen and get past that.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    martes, 22 de septiembre de 2015 22:37
    Moderador
  • This seems like a totally different issue that needs its own thread.

    I'm still having the original problem.

    martes, 22 de septiembre de 2015 22:47
  • Your BDD.log didn't help because it only had a few lines.  I need a more complete log.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    martes, 22 de septiembre de 2015 23:09
    Moderador
  • How do I get more complete logs?  I posted the logs that were generated.
    martes, 22 de septiembre de 2015 23:23
  • Keith's video in my signature should point you to the logs.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    miércoles, 23 de septiembre de 2015 0:29
    Moderador
  • Have you tried this with a normal SKU?  Something not EVAL?

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    miércoles, 23 de septiembre de 2015 17:42
    Moderador
  • Yes.  I tried Server 2012 R2 using Technet subscription software and it does the same thing.

    Only the Windows 10 install is 90 day evaluation.

    miércoles, 23 de septiembre de 2015 18:48
  • jueves, 24 de septiembre de 2015 2:48
  • Are you using the 8298 build of Update 1? 

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    viernes, 25 de septiembre de 2015 23:01
    Moderador
  • Yes.
    sábado, 26 de septiembre de 2015 2:08
  • Looked at the Bdd.log file,

    Try removing the ZTIApplyGPOPack and/or skip the domain join step to see if it's a Group Policy object blocking autologin


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    domingo, 27 de septiembre de 2015 23:02
    Moderador
  • Removing domain join did not help.  As soon as it reboots in the State Restore section of the task sequence, it stops logging in to the Administrator account automatically.  Earlier in the task sequence, it shows logging in as "Other User."

    At first, it stopped logging in after rebooting for windows updates, so I inserted an extra reboot in front of Windows Updates and now it stops at the login screen after that reboot instead.


    • Editado MyGposts lunes, 28 de septiembre de 2015 0:19
    lunes, 28 de septiembre de 2015 0:17
  • It appears that the task sequence continues on in the background even though it stops logging on.  I just logged into the Administrator account and it's now displaying the deployment summary "Success" screen.  

    You just cannot view the progress and see when it completes because it's hidden behind the Administrator login prompt.

    lunes, 28 de septiembre de 2015 1:02
  • I'm confused by the last two posts.

    Are you saying that the OS won't autologon after Windows Setup? or that the OS won't autologon sometime after starting State Restore? 

    IF you are still having problems please post your bdd.log file to a public site like one drive and post the share. Additionally post the time index of when you were forced to manually logon.

    Additionally, it would be good to see the contents of
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    lunes, 28 de septiembre de 2015 4:05
    Moderador
  •  The bdd.log link should posted earlier should still be working. https://onedrive.live.com/redir?resid=529f3393ff6e2282!677&authkey=!ACHJ2GJK4PTDWP0&ithint=file%2clog

    The point where it stops logging on is in the State Restore section.  The screen shot  posted above shows the reboot I added. After that reboot, it stops logging on automatically for the rest of the task sequence.

    If I don't add the extra restart, then it stops logging on when it restarts for the Windows Updates tasks.  I added the extra reboot today so that I can see if it will login automatically without having to wait for it to download and install the Windows updates.

    So, any reboot that happens starting from the State Restore section of the deployment results in the UI stopping at the login screen.  However, it appears that the deployment is still continuing in the background.  


    • Editado MyGposts lunes, 28 de septiembre de 2015 4:18
    lunes, 28 de septiembre de 2015 4:16
  • Again, I am confused by the problem here.

    You say that you added a reboot between the Tatoo and the WindowsUpdate commands above, however in the bdd.log file, I see no delay in processing:

    Event 41001 sent: ZTITatoo processing completed successfully. ZTITatoo 9/21/2015 8:25:55 AM 0 (0x0000) Microsoft Deployment Toolkit version: 6.3.8298.1000 ZTIWindowsUpdate 9/21/2015 8:25:55 AM 0 (0x0000)

    We should see a delay between the ZTITatoo and the ZTIWindowsUpdate, but the change is instant.

    Additionally, I asked some other questions above, but did not receive an answer.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    lunes, 28 de septiembre de 2015 15:02
    Moderador
  • Here is the link to the registry key:

    https://onedrive.live.com/redir?resid=529F3393FF6E2282!680&authkey=!AMcJQrcHnesg2MM&ithint=file%2creg

    The bdd.log is from 9/21/2015 before adding the extra reboot.  I only inserted the extra reboot last night as a test to see if the problem remained even without installing Windows Updates and to save the time of waiting for Windows Updates to download and install before seeing if the issue was resolved. 

    Other than that, it didn't add anything to troubleshooting and the original bdd.log posted last week still has all the information. The autologin problem is the same whether or not  that additional restart is added.

    lunes, 28 de septiembre de 2015 16:04
  • I tried creating a new deployment share and it has not solved the issue.

    I made a new standard client task sequence and specified an administrator password in the configuration of the task sequence and I have the exact same issue as before.  It keeps showing the login screen after each reboot instead of showing the desktop.

    I created a second new standard client task sequence and did NOT specify an administrator password and it has a different error.  It says Remote Desktop Services is busy.  If I click OK, then it goes to the desktop without typing a password.

    martes, 29 de septiembre de 2015 4:18
  • We still haven't narrowed down what the problem is here, Thanks for posting the reg file, I can see that the relevant entries have been turned off, so of course it won't auto logon

    "AutoAdminLogon"="0"
    Now you need to figure out *who* is resetting the autoadminlogon during your scripts, be prepared to insert pauses into your task sequence so you can test.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    martes, 29 de septiembre de 2015 15:29
    Moderador
  • If found that the cause of the issue is because the deployments are being run through Hyper-V Manager using the enhanced session mode.  

    When enhanced session mode is not enabled, I can still see the progress on the task sequences after reboots.

    That's why when a log in manually, I can see that the deployment was still continuing in the background.  The task sequences do not stop, but they are hidden behind the login screen.

    miércoles, 30 de septiembre de 2015 2:48
  • i have the same problem.

    But..

    1.I created a w7 vms. in domain, activated, etc.

    2. take a snapshot

    3. launch task sequence and it works fine.

    If i launch the ts again after apply the snapshot, the auto login does not work.


    Miguel H. (Marquemos como utiles los mensajes que lo son).

    domingo, 11 de octubre de 2015 9:56
  • I think the problem is related with that : http://blogs.technet.com/b/mniehaus/archive/2015/08/24/windows-10-mdt-2013-update-1-and-hideshell.aspx

    i am researching.

     

    Miguel H. (Marquemos como utiles los mensajes que lo son).

    domingo, 11 de octubre de 2015 15:21
  • Finally, you should add hideshell=yes in you customsettings.ini.

    I fixed the problem with this.


    Miguel H. (Marquemos como utiles los mensajes que lo son).

    lunes, 12 de octubre de 2015 9:13
  • This doesn't fix the issue.

    The problem occurs, for us, on mobile devices such as laptops and Surface Pros.

    During the task sequence, after the Install OS phase, the laptop (for example) will reboot, enter Windows, and instead of auto logging into the defined local administrator account, it sits at the Login Screen with the "Other User" prompt on top.  The task sequence does NOT run in the background so the deployment is in a stand still until someone manually logs in.  At that point, the task sequence picks back up automatically.
    martes, 17 de noviembre de 2015 18:33
  • If you are having this issue in any way differently than MyGPosts you have a different issue.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    miércoles, 18 de noviembre de 2015 19:35
    Moderador
  • If you are having this issue in any way differently than MyGPosts you have a different issue.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    No, because we experience the same exact issue, but the fixes offered here do not work...and many other people are having the same problem.
    jueves, 19 de noviembre de 2015 17:41
  • It is a different issue.  His was because he was using enhanced sessions on Hyper-V.  Start a new thread.  I am not saying it to be snotty but, if you want help with what is a different issue then a new thread is the way to go.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.


    jueves, 19 de noviembre de 2015 18:40
    Moderador
  • I'm testing MDT 2013 update 1 right now and am having the exact same issue.  On a vanilla win10 VM, I mapped a drive to the deployment share, kicked off litetouch, ran a windows update TS and it bombs out after reboot (no finished/error screen, no indication that the TS is still running, etc).

    I had this issue with the last version of MDT and the problem was with the LTI cleanup script - there was a line in there that would set filteradministratortoken to a value of 1.  So basically, you could run a full deployment TS fine, but once LTI cleanup ran it would change that regkey to a value of 1; any post OS task sequences would then bomb out after reboot.

    Here is the code from LtiCleanup.wsf after update1:

    		'//  Re-enable UAC for Administrator account (Windows 8 and above)
    		'//----------------------------------------------------------------------------
    
    		If oEnvironment.Item("OSCurrentVersion") <> "" then
    			oUtility.GetMajorMinorVersion(oEnvironment.Item("OSCurrentVersion"))
    			If ((oUtility.VersionMajor = 6 and oUtility.VersionMinor >= 2) or oUtility.VersionMajor >= 10 ) then
    				oLogging.CreateEntry "Re-enabling UAC for built-in Administrator account", LogTypeInfo
    				oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken", 1, "REG_DWORD"
    			End if		
    		End if

    I think Keith had pointed out that it should be enabled for security reasons, but if we can't run post OS deployments out of box, then maybe this shouldn't be enabled in LtiCleanup.wsf.

    My original finding:

    https://social.technet.microsoft.com/Forums/en-US/e282edea-f2ab-49d2-8966-ac2fdd1d9eb9/ts-wont-resume-after-first-reboot-disable-uac-the-only-workaround?forum=mdt



    • Editado resident1155 viernes, 18 de diciembre de 2015 17:55
    viernes, 18 de diciembre de 2015 17:12