D
De Me
Guest
Hey everyone,
I've been using WDS to deploy Windows 10 to a small number of notebooks since version 1803. Updating the install.wim on the WDS server has always gone smoothly so far, with only minor caveats when adapting the existing Unattend XML answer file to the new images with the corresponding ADK's. I did install the 2004 ADK for this, of course.
So this time I went from 1903 to 2004 and the installation still goes through, but AutoLogOn does not work anymore as it did with version 1903. Usually, after deployment my clients would auto-login using a domain-user for 3 log-ons, soLenovo BIOS- and firmware updates could be installed without user interaction.
<settings pass="auditSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>{OUR-NON-PLAINTEXT-PASSWORD}</Value>
<PlainText>false</PlainText>
</Password>
<Domain>{OUR-DOMAIN}</Domain>
<Enabled>true</Enabled>
<LogonCount>3</LogonCount>
<Username>{OUR-USERNAME}</Username>
</AutoLogon>
</component>
</settings>
Unfortunately that doesn't work anymore with Windows 10 2004. After deployment, the client ends up on the login screen and I have to login manually. It's the same if I use a local account that is successfully created during installation.
Is this also due to Windows Hello, like the 2004 auto login issue discussed recently (I'm not allowed to post links)?
If so, can I deactivate Windows Hello during deployment, using Unattend XML?
Thanks in advance,
Danny Meyer
More...
I've been using WDS to deploy Windows 10 to a small number of notebooks since version 1803. Updating the install.wim on the WDS server has always gone smoothly so far, with only minor caveats when adapting the existing Unattend XML answer file to the new images with the corresponding ADK's. I did install the 2004 ADK for this, of course.
So this time I went from 1903 to 2004 and the installation still goes through, but AutoLogOn does not work anymore as it did with version 1903. Usually, after deployment my clients would auto-login using a domain-user for 3 log-ons, soLenovo BIOS- and firmware updates could be installed without user interaction.
<settings pass="auditSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>{OUR-NON-PLAINTEXT-PASSWORD}</Value>
<PlainText>false</PlainText>
</Password>
<Domain>{OUR-DOMAIN}</Domain>
<Enabled>true</Enabled>
<LogonCount>3</LogonCount>
<Username>{OUR-USERNAME}</Username>
</AutoLogon>
</component>
</settings>
Unfortunately that doesn't work anymore with Windows 10 2004. After deployment, the client ends up on the login screen and I have to login manually. It's the same if I use a local account that is successfully created during installation.
Is this also due to Windows Hello, like the 2004 auto login issue discussed recently (I'm not allowed to post links)?
If so, can I deactivate Windows Hello during deployment, using Unattend XML?
Thanks in advance,
Danny Meyer
More...