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 <[email protected]> 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 > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Britney Gibbs > *Sent:* Wednesday, September 13, 2017 10:41 AM > *To:* [email protected] > *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 <[email protected]> > 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...* > >
