Windows 10: Sysprep unattend first logon command error

Hello,


I am trying to create admin user that has "Password never expires" option with Unattend.xml. As I understand this can not be done while Sysprep, but rather on first log on. Therefore I wrote an Unattend.xml which looks like this:



<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<settings pass="oobeSystem">

<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>

<ProtectYourPC>1</ProtectYourPC>

<HideLocalAccountScreen>true</HideLocalAccountScreen>

<HideOnlineAccountScreens>true</HideOnlineAccountScreens>

<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>

</OOBE>

<UserAccounts>

<LocalAccounts>

<LocalAccount wcm:action="add">

<DisplayName>wsadmin</DisplayName>

<Name>wsadmin</Name>

<Password>

<Value>somepassword</Value>

<PlainText>false</PlainText>

</Password>

<Group>Administrators</Group>

</LocalAccount>

</LocalAccounts>

</UserAccounts>

</component>

<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">

<InputLocale>hr-HR</InputLocale>

<SystemLocale>hr-HR</SystemLocale>

<UserLocale>hr-HR</UserLocale>

</component>

</settings>

<settings pass="oobeSystem">

<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">

</component>

</settings>

<AutoLogon>

<Enabled>true</Enabled>

<LogonCount>1</LogonCount>

<Username>wsadmin</Username>

<Password>

<Value>somepassword</Value>

<PlainText>true</PlainText>

</Password>

</AutoLogon>

<FirstLogonCommands>

<SynchronousCommand wcm:action="add">

<CommandLine>cmd /C wmic useraccount where "name='wsadmin'" set PasswordExpires=FALSE</CommandLine>

<Description>Password never expires wsadmin</Description>

<RequiresUserInput>false</RequiresUserInput>

<Order>1</Order>

</SynchronousCommand>

</FirstLogonCommands>



</unattend>



I get error that <SynchronousCommand wcm:action="add"> is not valid. Any ideas?


Thanks in advance



Sven

:)

 

SysPrep Advice

Hi Joseph,

The topic that you raised is beyond the scope of support for this site which focuses more on home and personal end users. Here's what I found about SysPrep:

• What Is Sysprep?
• How To Sysprep – Sysprep is a Great And powerful tool And Easy
  Too If You Know How (Step-By-Step).

However these are old articles and the process may have been changed already. You may re-post this question in

TechNet Forums for further assistance.

All the best.

 

Customize Windows 10 Image in Audit Mode with Sysprep  

Just to add something, clarifying this.

There are two ways to sysprep with an answer file.

Method 1:

• Save the answer file in C:\Windows\System32\Sysprep folder as unattend.xml (you must use this name!)
• Run the sysprep command without /unattend switch, the answer file will be automatically read and used, machine is automatically shut down after the sysprep if /quit or /reboot switches are not used
• Example commands:
  • sysprep /generalize /oobe (sysprep with unattend.xml, shutdown when ready)
  • sysprep /generalize /oobe /quit (sysprep with unattend.xml,, quit to desktop when ready)
  • sysprep /generalize /oobe /reboot (sysprep with unattend.xml, reboot to OOBE when ready)

Method 2:

• Save the answer file anywhere you want to naming it as you wish with the extension .xml
• Run the sysprep command with /unattend switch giving the name and location of the answer file you want to be read and used
• Example command:
  • sysprep /generalize /oobe /shutdown /unattend:X:\MyAnswerFile.xml

 

Sysprep Error

hello i can`t sysprep windows 8.1 in vmware workstation here is error log

2019-05-16 05:19:18, Info [0x0f004d] SYSPRP The time is now 2019-05-16 05:19:18

2019-05-16 05:19:18, Info [0x0f004e] SYSPRP Initialized SysPrep log at c:\Windows\System32\Sysprep\Panther

2019-05-16 05:19:18, Info [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine

2019-05-16 05:19:18, Info [0x0f007e] SYSPRP FCreateTagFile:Tag file c:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything

2019-05-16 05:19:18, Warning SYSPRP WinMain: File operations pending

2019-05-16 05:19:18, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'

2019-05-16 05:19:18, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'

2019-05-16 05:19:18, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'SHUTDOWN'

2019-05-16 05:19:18, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'

2019-05-16 05:19:18, Info [0x0f00d7] SYSPRP WinMainre-validing 'cleanup' internal providers.

2019-05-16 05:19:18, Info SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3

2019-05-16 05:19:18, Error [0x0f00bb] SYSPRP SysprepSession::CreateSession: Action XML file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml does not exist[gle=0x00000002]

2019-05-16 05:19:18, Error SYSPRP RunPlatformActions:Could not create SysprepSession; dwRet = 0x2[gle=0x00000002]

2019-05-16 05:19:18, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x2[gle=0x00000002]

2019-05-16 05:19:18, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x80070002[gle=0x00000002]

2019-05-16 05:19:20, Info [0x0f0052] SYSPRP Shutting down SysPrep log

2019-05-16 05:19:20, Info [0x0f004d] SYSPRP The time is now 2019-05-16 05:19:20