Hi Sean – this is why you do not have a problem with reboots with Windows 10 1703:
AdminPassword=*** Remove that and I bet you have problems. I have never had to have it in the CS.ini file until now. I try to keep my CustomeSetting.ini file as lean as I can. My thinking is the more you put into it, the more chances something is going to change which would require upkeep. [Settings] Priority=Default Properties=MyCustomProperty [Default] _SMSTSOrgName=”CompanyName” SLShare=\\Server name\MDT\Logs\%Model%\%SERIALNUMBER% (this captures the logs of every build) SLShareDynamicLogging=\\Server name\MDT\Logs\%Model%\%SERIALNUMBER% (this captures the logs of every build) OSInstall=Y SkipCapture=Yes SkipUserData=YES SkipBitLocker=NO TpmOwnerPassword=password SkipAdminPassword=YES AdminPassword=Password SkipProductKey=YES WSUSServer=http://Server name OSDComputerName=Sitecode-%SerialNumber% JoinDomain= FQDN here DomainOUs1=OU=Laptops,OU=<site name>,OU=<site country>,DC=domain,DC= domain,DC=com DomainOUs2=OU=Desktops,OU=<site name>,OU=<site country>,DC= domain,DC= domain,DC=com DomainOUs3=OU=Laptops,OU=<site name>,OU=<site country>,DC= domain,DC= domain,DC=com DomainOUs4=OU=Desktops,OU=<site name>,,OU=<site country>,DC= domain,DC= domain,DC=com TimeZone=Timezone # TimeZoneName=Time zone name From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Sean Chapman Sent: Wednesday, September 13, 2017 12:48 PM To: mdtosd@lists.myitforum.com Subject: RE: [MDT-OSD] Windows 10 1703 breaking auto log on when updates are being applied I have no idea how to find what version of ADK/MDT im using but the date on the folder is 06/14/2016 Anyway… I have no problems with 1703 and autologon. Here is my CS [Settings] Priority=Default Properties=MyCustomProperty [Default] _SMSTSORGNAME=Coilcraft UserDataLocation=NONE DoCapture=YES OSInstall=Y AdminPassword=*** TimeZoneName=Central Standard Time JoinWorkgroup=WORKGROUP HideShell=NO FinishAction=RESTART DoNotCreateExtraPartition=YES ;WSUSServer=http://wsus01-vm:8530 ApplyGPOPack=NO SkipAdminPassword=YES SkipProductKey=YES SkipComputerName=NO SkipDomainMembership=YES SkipComputerBackup=NO SkipUserData=YES SkipLocaleSelection=YES SkipTaskSequence=NO SkipTimeZone=YES SkipApplications=YES SkipBitLocker=YES SkipSummary=YES SkipRoles=YES SkipCapture=NO SkipFinalSummary=YES ;JoinDomain=*** ;DomainAdmin=*** ;DomainAdminDomain=*** ;DomainAdminPassword=*** MachineObjectOU=OU=MDT,DC=***,DC=com SLSShare=\\WDS01-VM\W10dev$\Logs\ SLShareDynamicLogging=\\WDS01-VM\W10dev$\Logs\%OSDComputerName% From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Britney Gibbs Sent: Wednesday, September 13, 2017 11:16 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: Re: [MDT-OSD] Windows 10 1703 breaking auto log on when updates are being applied We are using Win10 Version 1703 on ADK/MDT Version 8443 on Server 2012 R2. Our CustomSettings.ini file is the original one that came with it other than a few modifications, but mostly pretty simple. We've tried the AdminPassword=Password and the SkipAdminPassword=YES. but I'm thinking that it never worked. Hard to tell. Thank you, Britney R. Gibbs On Wed, Sep 13, 2017 at 11:51 AM, Jimmy Martin <jimmy.mar...@bmhcc.org<mailto:jimmy.mar...@bmhcc.org>> wrote: Out of curiosity, what ver is your site? and are you using an old customsettings or is it a new one? Jimmy Martin (901) 227-8209<tel:(901)%20227-8209> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of Britney Gibbs Sent: Wednesday, September 13, 2017 10:41 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: Re: [MDT-OSD] Windows 10 1703 breaking auto log on when updates are being applied I'm having this same issue. Even though they said that the last Cumulative Security Update fixed it. Bad part about it for me is that if it doesn't AutoLogon, it won't finish the Task Sequence unless I go to C: and run the LiteTouch file there, then restart the PC, but it's not consistent. What happens if you move the "Apply Updates" portion to the State Restore part of the Task Sequence (if that's possible)? Thank you, Britney R. Gibbs On Tue, Sep 12, 2017 at 4:47 PM, David Landry <david.lan...@lairdtech.com<mailto:david.lan...@lairdtech.com>> wrote: Hi All, Anyone seen this? Windows 10 1703 64bit is no longer auto logging back in once it boots up to the desktop and starts installing apps. Where I really see this is when Windows updates runs. It can take up to 8 passes and it has always auto logged back in after each pass. We have no issues with Windows 7 or Windows 10 1607. I have a work around by adding AdminPassword= to the CustomSettings.ini file. I am hoping someone else has found the root cause with a fix? Thanks in advance.. Dave Landry 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... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The information contained in this communication and all accompanying documents from Coilcraft may be confidential and/or legally privileged, and is intended only for the use of the recipient(s) named above. If you are not the intended recipient you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance on the contents of this transmitted information is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and destroy the original message or accompanying materials and any copy thereof. If you have any questions concerning this message, please contact the sender.
