So.. I have questions..

Why are you setting AutoLogin via the sysinternals tool? If you are using MDT 
or SCCM/OSD, they will handle autologon themselves.

There is nothing about AutoLogon that could/should case a Blue Screen. Blue 
Screens are caused by OS/driver issues, not application issues. If your problem 
is the bluescreen, I would investigate the updates.

The Sysinternals autologon tool might not use the registry, it could use the 
protected LSA space instead, looking in the registry for the password does not 
prove failure of the autologon tool.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Denzik, Josh
Sent: Wednesday, May 3, 2017 4:47 AM
To: mdtosd@lists.myitforum.com
Subject: [MDT-OSD] Window 10 1703 Autologin Systinernal Tool

This message was sent securely by MUSC<http://www.musc.edu/>



I am using the sysinternal tool autologon. We copy the tool to 
C:\Windows\autologon. In the task sequence, I call that path with this command 
line step in the task sequence cmd.exe /c c:\windows\autologon\autologon.exe 
/accepteula username testdomain Password. I also delete this key if it is 
present because it causes autologon to fail with this command REG.exe DELETE 
"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v AutoLogonCount 
/f This was all working in Windows 1607. Now windows 1703 shows up and the reg 
keys that were being set by autologin are not there and it does this weird 
thing about looking for updates it's a blue screen I have never seen this 
screen before(new feature can it be turned off?), I am wondering if that is the 
issue and its wiping out the auto logon registry keys.



Good Set of Keys



[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"AutoRestartShell"=dword:00000001

"Background"="0 0 0"

"CachedLogonsCount"="10"

"DebugServerCommand"="no"

"DisableBackButton"=dword:00000001

"EnableSIHostIntegration"=dword:00000001

"ForceUnlockLogon"=dword:00000000

"LegalNoticeCaption"=""

"LegalNoticeText"=""

"PasswordExpiryWarning"=dword:0000000e

"PowerdownAfterShutdown"="0"

"PreCreateKnownFolders"="{A520A1A4-1780-4FF6-BD18-167343C5AF16}"

"ReportBootOk"="1"

"Shell"="explorer.exe"

"ShellCritical"=dword:00000000

"ShellInfrastructure"="sihost.exe"

"SiHostCritical"=dword:00000000

"SiHostReadyTimeOut"=dword:00000000

"SiHostRestartCountLimit"=dword:00000000

"SiHostRestartTimeGap"=dword:00000000

"Userinit"="C:\\windows\\system32\\userinit.exe,"

"VMApplet"="SystemPropertiesPerformance.exe /pagefile"

"WinStationsDisabled"="0"

"scremoveoption"="0"

"DisableCAD"=dword:00000001

"LastLogOffEndTimePerfCounter"=hex(b):f8,2f,8a,39,00,00,00,00

"ShutdownFlags"=dword:00000026

"EnableFirstLogonAnimation"=dword:00000001

"AutoLogonSID"="S-1-5-21-1310203998-2849947588-4241112151-500"

"LastUsedUsername"="username"

"DefaultUserName"="username"

"DefaultDomainName"="testdomain"

"AutoAdminLogon"="1"

"ScreenSaverGracePeriod"="5"

"allocatecdroms"="0"

"allocatedasd"="0"

"allocatefloppies"="0"





Bad Set of Keys



Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] 
"DefaultDomainName"=""

"DefaultUserName"=""

"EnableSIHostIntegration"=dword:00000001

"PreCreateKnownFolders"="{A520A1A4-1780-4FF6-BD18-167343C5AF16}"

"Shell"="explorer.exe"

"ShellCritical"=dword:00000000

"SiHostCritical"=dword:00000000

"SiHostReadyTimeOut"=dword:00000000

"SiHostRestartCountLimit"=dword:00000000

"SiHostRestartTimeGap"=dword:00000000

-----Original Message-----

From: Denzik, Josh

Sent: Friday, February 24, 2017 3:45 PM




-------------------------------------------------------------------------
This message was secured via TLS by MUSC<http://www.musc.edu>.

Reply via email to