Are you waiting for network? Does the autologon account already have a profile on all the devices? I have seen cached logon be more forgiving I noticed your autologon command does not include the /accepteula switch. This could yield the spotty results you note…
Jimmy Martin (901) 227-8209 From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Monday, September 22, 2014 6:18 AM To: [email protected] Subject: RE: [MDT-OSD] AutoLogon With Domain Account in Task Sequence for Windows 7 SP1 x64 No, what David suggested was to use a GPPE to set the Registry keys for the autologon instead of using your scripts. Mike From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Denzik, Josh Sent: Sunday, September 21, 2014 7:37 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] AutoLogon With Domain Account in Task Sequence for Windows 7 SP1 x64 This is not a GP policy issue for the machine, I had the machine join an OU that has no GPO’s applied to it. Any other ideas? -Thanks in Advance Josh From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David van Beek Sent: Friday, September 19, 2014 5:27 PM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] AutoLogon With Domain Account in Task Sequence for Windows 7 SP1 x64 Maybe group policy preference is an option for autologon to set the regkeys. Add the computer account to an AD group and use a filter for the gpo preferences. Sent from my iPhone Met vriendelijke groet / With kind regards, David van Beek On 19 sep. 2014, at 22:30, Denzik, Josh <[email protected]<mailto:[email protected]>> wrote: You accomplished on a win7 x64 during an SCCM OSD Task sequence? The latest: I have created a PowerShell script that creates and sets the values for the reg keys and used the SMSTSPostAction variable to run the script at the very end of the task sequence. After all reboots have been completed during the ts. powershell -File "c:\Program Files\Scripts\Powershell\AutoLogonx64.ps1" -ExecutionPolicy ByPass PowerShell Script Set-Location -Path hklm: New-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' -Name "AutoAdminLogon" New-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' -Name "DefaultUserName" New-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' -Name "DefaultDomainName" New-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' -Name "DefaultPassword" Set-Location -path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' Set-ItemProperty -Path Winlogon AutoAdminLogon -Value 1 Set-ItemProperty -Path Winlogon DefaultUserName -Value user Set-ItemProperty -Path Winlogon DefaultDomainName -Value domain Set-ItemProperty -Path Winlogon DefaultPassword -Value Password Restart-Computer So now at the end it still comes up to the ctrl alt delete does not login and the password key is not even there. And the autoadminlogon is set to 0. Any more suggestions? To accomplish this in a task sequence? Please Help! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Saraceno, Rob Sent: Friday, September 19, 2014 10:24 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] AutoLogon With Domain Account in Task Sequence for Windows 7 SP1 x64 I’ve found the registry method to work better if you don’t have a default domain and you put the domain into the user name (either as below or using the UPN) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "AutoAdminLogon"="1" "DefaultUserName"="mydomain\domain account" -"DefaultDomainName" "DefaultPassword"="MyPassword" From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Denzik, Josh Sent: Thursday, September 18, 2014 9:02 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] AutoLogon With Domain Account in Task Sequence for Windows 7 SP1 x64 All, I am having some trouble getting my machines to autologon with Windows 7 SP1 x64. 1st Method: The AutoLogon 3.01 Utility(Sysinternals Tool) is copied to a folder and referenced via command line to set the parameters in the task sequence: cmd.exe /c c:\windows\autologon\autologon.exe user domain password Result: It comes up to the logon screen and never tries to logon. The AutoAdminLogon is set to 0. (This method works on x86 flawlessly.) 2nd Method I import this RegKey Via Command Line in the Task sequence: cmd.exe /c REG IMPORT AutoLogonx64.reg See Below: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "AutoAdminLogon"="1" "DefaultUserName"="domain account" "DefaultDomainName"="mydomain" "DefaultPassword"="MyPassword" Result: Again comes up to the logon screen and does not automatically login. Once again the AutoAdminLogon is set to 0. If I log into windows and set AutoAdminLogon and then reboot the machine it automatically logs in. It appears that something is not getting set correctly in the registry. Is this because of it being x64 or is SCCM setting something and overriding my task? Does anyone have any suggestions to accomplish this? It must be done with a domain account. Thanks in Advance: Josh Denzik ---------------------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Bain Capital, LLC Boston, MA USA +1 (617) 516 2000 ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
