New
#170
Thank you, I think the possible mistake I have made is the switch to OOBE in the first place when in Audit mode.
Thank you, I think the possible mistake I have made is the switch to OOBE in the first place when in Audit mode.
First off all, thanks for this massive tutorial. I've been checking it last few weeks and trying my own unattended installation. I've ran into 1 problem. I want 1 user account created without any prompt for a password. So that windows logs in automatically and proceeds with the installation. I keep getting a prompt for setting a new pw. Can i get some help fixing this?
Yes!
Code:<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" 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"> <UILanguage>nl-NL</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>nl-NL</UserLocale> <InputLocale>0413:00020409</InputLocale> <SystemLocale>nl-NL</SystemLocale> </component> <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"> <OOBE> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <ProtectYourPC>1</ProtectYourPC> <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideLocalAccountScreen>true</HideLocalAccountScreen> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <DisplayName>Gebruiker</DisplayName> <Group>Administrators</Group> <Name>Gebruiker</Name> <Password> <Value>KgBQAGEAcwBzAHcAbwByAGQA</Value> <PlainText>false</PlainText> </Password> </LocalAccount> </LocalAccounts> </UserAccounts> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> <TimeZone>W. Europe Standard Time</TimeZone> </component> </settings> <settings pass="specialize"> <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"> <OEMInformation> <Logo>c:\windows\system32\oemlogo.bmp</Logo> <Manufacturer>SOMCOM </Manufacturer> <Model>Maatwerk</Model> <SupportHours>Maandag t/m vrijdag: 9-18 uur en zaterdag: 10-17 uur</SupportHours> <SupportPhone>0592-308260</SupportPhone> <SupportURL>http://www.somcom.nl</SupportURL> </OEMInformation> <CopyProfile>true</CopyProfile> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> <TimeZone>W. Europe Standard Time</TimeZone> </component> </settings> <cpi:offlineImage cpi:source="wim://desktop-ltlppfd/iso_files/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
You are missing the autologon part in the unattend.xml. I have my work laptop not here, but I think it should be in the Shell_Setup for oobeSystems. Without you only create the account with that password, but you do not login automatically
AutoLogon | Microsoft Docs
In OobeSystem > User Accounts, create a local admin account with password:
Add component Shell-Setup > Autologon to answer file in configuration pass 7 OobeSystem:
Enable Autologon, use same user account as the admin user and password you have already set up, set LogonCount to 2:
Important is that Autologon account exists, and that it has a password.
In answer file, that looks like this:
This user will be set in netplwiz as autologon user.
Kari
Last edited by Kari; 21 Feb 2019 at 14:08. Reason: Replaced bad screenshots
Ah, thanks. Im trying it right now. Will let you know! thanks!
7.12) When reference machine has booted to desktop, sign in to your administrator account using password you set in answer file in step 4.8
At the above step, I am unable to sign in as administrator as its not accepting my password. I can try few workarounds but I am not sure how it is going to affect the image creation process.
Please advise. Thanks
That's quite straight forward: if the password does not work, it is wrong.
If you follow the instructions exactly as written, you create a local admin account in step 4.8, giving it a password. In step 7.12, you then sign in to reference machine using this local admin account with its password.
If password is not accepted, you do not enter it correctly.
WarningYou must be careful in step 4.8 when creating password! For security reasons, when you save an answer file containing password, it will be encrypted by default and cannot be recovered. Opening answer file will show the encrypted password, as shown in this extract from my standard unattend.xml answer file:
The smallest typo invalidates the password. If you thought that in step 4.8 you set password for your local admin account as MyPassword, but accidentally typed it in System Image Manager as Mypassword (lowercase p instead of uppercase), it will not work when you enter password as MyPassword.
Although it is a security risk not to encrypt the password, if you want to you can disable encrypting by setting <PlainText> value to TRUE:
Kari
Last edited by Kari; 25 Feb 2019 at 20:54. Reason: A few typos fixed