mdt - Microsoft Deployment Toolkit setting SystemAutoLogon registry key when deploying upgraded OS -


i'm trying deploy images via mdt have been upgraded via mdt "standard client upgrade" task sequence. images started win10 v1607 images , updated v1703 , captured.

when go deploy captured images, i'll popup on first login c:\ltibootstrap.vbs can't found. digging, discovered after os installed , pc restarts, mdt task sequence continues running the system account . bizarre typically runs built-in administrator account.

for reason, though unattend.xml file contains usual autoadminlogon entries, registry key at

hklm\software\microsoft\windows nt\currentversion\winlogon\systemautologon 

is being created , set 1 during deployment. (i discovered comparing registries @ end of deployment.) key not present in captured image. this key not created if deploy image manually updated v1703 (via windows update instead of mdt).

any ideas on why unattend.xml ignored or cause systemautologon created , set?

i figured out going on.

the mdt upgrade task sequence invokes upgrade command line /postoobe option pointing setupcomplete.cmd. causes file copied c:\windows\setup\scripts\setupcomplete.cmd. when windows install complete, if file present @ location, run under system account.

the problem file remains after upgrade task sequence totally complete. if capture image , deploy real machine, see setupcomplete.cmd , run after deploy, instead of using usual default administrator account.

i imagine presence of file @ c:\windows... causes registry changes mentioned above. setupcomplete.cmd built bootstrap upgrade mdt task sequence, , needs removed c:\windows... when task sequence done running.

knowing post-upgrade portion of upgrade task-sequence runs system instead of administrator via different mechanism standard deployment important, there limits can do. default sequence lets install applications.. need apps ok being installed system.

for i've updated local setupcomplete.cmd in scripts directory delete when done changing last loop (there typo in loop before preventing exit echo):

for %%d in (c d e f g h j k l m n o p q r s t u v w x y z) if exist %%d:\windows\setup\scripts\setupcomplete.cmd (  del /q /f %%d:\windows\setup\scripts\setupcomplete.cmd echo %date%-%time% exiting setupcomplete.cmd >> %windir%\temp\setupcomplete.log) 

Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -