KACE Product Support : Unattend answer file for pass [oobe system] . The answer file is invalid

Unattend answer file for pass [oobe system] . The answer file is invalid

Hi All,

I am using this to sysprep a Win10 1809 version via VM on hyper-v.

This the error I get

And when i click OK, this is what i get

and if i click the above, the OOBE error appears and loops to the second screenshot.

I have gone through both Microsoft Technet support and Dell Support and they have asked me to get in contact with you guys over here.

Any help on this is greatly appreciated.

6 Comments [ + ] Show comments

You will need to post the answer file so we can see what the problem might be. Be sure to remove any passwords, even if they are hashed. - chucksteel 5 years ago
- agreed, also please let us know if the answer file was built with Sysprep Creator or any other tool - Channeler 5 years ago
This is the answer file.

--------------

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

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

-<settings wasPassProcessed="true" pass="generalize">

-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Security-SPP">

<SkipRearm>1</SkipRearm>

</component>

+<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-PnpSysprep">

</settings>

-<settings wasPassProcessed="true" pass="specialize">

-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Deployment">

-<RunSynchronous>

-<RunSynchronousCommand wcm:action="add">

<Order>1</Order>

<Path>net user administrator /active:No</Path>

<WillReboot>Never</WillReboot>

</RunSynchronousCommand>

</RunSynchronous>

</component>

-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Security-SPP-UX">

<SkipAutoActivation>true</SkipAutoActivation>

</component>

-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Shell-Setup">

<ComputerName>*</ComputerName>

<CopyProfile>true</CopyProfile>

<TimeZone>TIMEZONE</TimeZone>

</component>

-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-UnattendedJoin">

-<Identification>

-<Credentials>

<Domain>DOMAIN_FQDN</Domain>

<Password>*SENSITIVE*DATA*DELETED*</Password>

<Username>SAMACCOUNTNAMEADMIN</Username>

</Credentials>

<JoinDomain>DOMAIN_FQDN</JoinDomain>

<MachineObjectOU>OU_INTEGRATION</MachineObjectOU>

<JoinWorkgroup/>

</Identification>

</component>

</settings>

-<settings pass="oobeSystem">

-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-International-Core">

<InputLocale>KEYBOARD_LAYOUT</InputLocale>

<SystemLocale>DEFAULT_SYSTEM_LAYOUT</SystemLocale>

<UILanguage>en-US</UILanguage>

<UILanguageFallback>en-US</UILanguageFallback>

<UserLocale>USER_LOCALISATION</UserLocale>

</component>

-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Shell-Setup">

-<AutoLogon>

-<Password>

<Value>PASSWORD_LOCAL_ADMINISTRATOR</Value>

<PlainText>true</PlainText>

</Password>

<LogonCount>2</LogonCount>

<Enabled>true</Enabled>

<Username>LOGIN_LOCAL_ADMINISTRATOR</Username>

</AutoLogon>

-<FirstLogonCommands>

-<SynchronousCommand wcm:action="add">

<CommandLine>cscript c:\windows\system32\slmgr.vbs /ipk BHXQD-CNMKV-VMWBT-2YM2B-HT9R4</CommandLine>

<Description>Windows License Key</Description>

<Order>1</Order>

<RequiresUserInput>false</RequiresUserInput>

</SynchronousCommand>

-<SynchronousCommand wcm:action="add">

<RequiresUserInput>false</RequiresUserInput>

<Order>2</Order>

<Description>Active Windows</Description>

<CommandLine>cscript c:\windows\system32\slmgr.vbs /ato</CommandLine>

</SynchronousCommand>

-<SynchronousCommand wcm:action="add">

<CommandLine/>

<Description>Disable UAC</Description>

<Order>3</Order>

<RequiresUserInput>false</RequiresUserInput>

</SynchronousCommand>

</FirstLogonCommands>

-<OOBE>

<HideEULAPage>true</HideEULAPage>

<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>

<NetworkLocation>Work</NetworkLocation>

<ProtectYourPC>3</ProtectYourPC>

<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>

<HideOnlineAccountScreens>true</HideOnlineAccountScreens>

<HideLocalAccountScreen>true</HideLocalAccountScreen>

</OOBE>

-<UserAccounts>

-<LocalAccounts>

-<LocalAccount wcm:action="add">

-<Password>

<Value>PASSWORD_LOCAL_ADMINISTRATOR</Value>

<PlainText>true</PlainText>

</Password>

<Description>Local Administrator</Description>

<DisplayName>LOGIN_LOCAL_ADMINISTRATOR</DisplayName>

<Group>Administrators</Group>

<Name>LOGIN_LOCAL_ADMINISTRATOR</Name>

</LocalAccount>

</LocalAccounts>

-<DomainAccounts>

-<DomainAccountList wcm:action="add">

-<DomainAccount wcm:action="add">

<Group>Administrators</Group>

<Name>USERNAME</Name>

</DomainAccount>

<Domain>DOMAIN_FQDN</Domain>

</DomainAccountList>

</DomainAccounts>

</UserAccounts>

<RegisteredOrganization>InfoVista SAS</RegisteredOrganization>

<RegisteredOwner>InfoVista SAS</RegisteredOwner>

</component>

</settings>

</unattend> - lgoh 5 years ago
- This looks like a diff file, based on the minus and plus signs. Is this the actual file from the broken system? When the error is on the screen you can press Shift-F10 to open a command prompt and the file should be in c:\windows\system32\sysprep\unattend.xml
  
  If you are deploying the image using the K2000, run the net use command to see which drive letter is mapped to the petemp share and copy the file there. You can then mount the share on another computer to get the file. Note that the petemp share is hidden, so you won't see it, but you can map a drive letter to it using the SAMBA password. - chucksteel 5 years ago
  - apologies. i had taken from the panther folder and not the system32 folder.
    
    this is the unattend.xml from the system32 folder
    
    --------------
    
    <?xml version="1.0" encoding="UTF-8"?>
    
    -<unattend xmlns="urn:schemas-microsoft-com:unattend">
    
    -<settings pass="generalize">
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Security-SPP">
    
    <SkipRearm>1</SkipRearm>
    
    </component>
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-PnpSysprep">
    
    <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
    
    <DoNotCleanUpNonPresentDevices>false</DoNotCleanUpNonPresentDevices>
    
    </component>
    
    </settings>
    
    -<settings pass="specialize">
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Deployment">
    
    -<RunSynchronous>
    
    +<RunSynchronousCommand wcm:action="add">
    
    </RunSynchronous>
    
    </component>
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Security-SPP-UX">
    
    <SkipAutoActivation>true</SkipAutoActivation>
    
    </component>
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Shell-Setup">
    
    <ComputerName>*</ComputerName>
    
    <CopyProfile>true</CopyProfile>
    
    <TimeZone>TIMEZONE</TimeZone>
    
    </component>
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-UnattendedJoin">
    
    -<Identification>
    
    -<Credentials>
    
    <Domain>DOMAIN_FQDN</Domain>
    
    <Password>PASSWORD_ADMIN</Password>
    
    <Username>SAMACCOUNTNAMEADMIN</Username>
    
    </Credentials>
    
    <JoinDomain>DOMAIN_FQDN</JoinDomain>
    
    <MachineObjectOU>OU_INTEGRATION</MachineObjectOU>
    
    <JoinWorkgroup/>
    
    </Identification>
    
    </component>
    
    </settings>
    
    -<settings pass="oobeSystem">
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-International-Core">
    
    <InputLocale>KEYBOARD_LAYOUT</InputLocale>
    
    <SystemLocale>DEFAULT_SYSTEM_LAYOUT</SystemLocale>
    
    <UILanguage>en-US</UILanguage>
    
    <UILanguageFallback>en-US</UILanguageFallback>
    
    <UserLocale>USER_LOCALISATION</UserLocale>
    
    </component>
    
    -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Shell-Setup">
    
    -<AutoLogon>
    
    -<Password>
    
    <Value>PASSWORD_LOCAL_ADMINISTRATOR</Value>
    
    <PlainText>true</PlainText>
    
    </Password>
    
    <LogonCount>2</LogonCount>
    
    <Enabled>true</Enabled>
    
    <Username>LOGIN_LOCAL_ADMINISTRATOR</Username>
    
    </AutoLogon>
    
    -<FirstLogonCommands>
    
    -<SynchronousCommand wcm:action="add">
    
    <CommandLine>cscript c:\windows\system32\slmgr.vbs /ipk BHXQD-CNMKV-VMWBT-2YM2B-HT9R4</CommandLine>
    
    <Description>Windows License Key</Description>
    
    <Order>1</Order>
    
    <RequiresUserInput>false</RequiresUserInput>
    
    </SynchronousCommand>
    
    -<SynchronousCommand wcm:action="add">
    
    <RequiresUserInput>false</RequiresUserInput>
    
    <Order>2</Order>
    
    <Description>Active Windows</Description>
    
    <CommandLine>cscript c:\windows\system32\slmgr.vbs /ato</CommandLine>
    
    </SynchronousCommand>
    
    -<SynchronousCommand wcm:action="add">
    
    <CommandLine/>
    
    <Description>Disable UAC</Description>
    
    <Order>3</Order>
    
    <RequiresUserInput>false</RequiresUserInput>
    
    </SynchronousCommand>
    
    </FirstLogonCommands>
    
    -<OOBE>
    
    <HideEULAPage>true</HideEULAPage>
    
    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    
    <NetworkLocation>Work</NetworkLocation>
    
    <ProtectYourPC>3</ProtectYourPC>
    
    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
    
    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
    
    <HideLocalAccountScreen>true</HideLocalAccountScreen>
    
    </OOBE>
    
    -<UserAccounts>
    
    -<LocalAccounts>
    
    -<LocalAccount wcm:action="add">
    
    -<Password>
    
    <Value>PASSWORD_LOCAL_ADMINISTRATOR</Value>
    
    <PlainText>true</PlainText>
    
    </Password>
    
    <Description>Local Administrator</Description>
    
    <DisplayName>LOGIN_LOCAL_ADMINISTRATOR</DisplayName>
    
    <Group>Administrators</Group>
    
    <Name>LOGIN_LOCAL_ADMINISTRATOR</Name>
    
    </LocalAccount>
    
    </LocalAccounts>
    
    -<DomainAccounts>
    
    -<DomainAccountList wcm:action="add">
    
    -<DomainAccount wcm:action="add">
    
    <Group>Administrators</Group>
    
    <Name>USERNAME</Name>
    
    </DomainAccount>
    
    <Domain>DOMAIN_FQDN</Domain>
    
    </DomainAccountList>
    
    </DomainAccounts>
    
    </UserAccounts>
    
    <RegisteredOrganization>InfoVista SAS</RegisteredOrganization>
    
    <RegisteredOwner>InfoVista SAS</RegisteredOwner>
    
    </component>
    
    </settings>
    
    </unattend> - lgoh 5 years ago
Running sysprep on a machine that is joined to the domain is not recommended. That could be the cause of the problem, regardless of the error message you received. - chucksteel 5 years ago
- ah crikey, i forgot to mention that the screenshot is just an example. when i do the sysprep all of it is a green checkmark - lgoh 5 years ago
The last time I ran in to this issue with a Win 10 x64 image, the problem was somehow related to the CopyProfile setting in specialize pass.

Removing the <CopyProfile>true</CopyProfile> (or set to false) resolved the issue in my environment. - styler 5 years ago
- thanks for the suggestion, will let you know if it works. - lgoh 5 years ago
Based on your screen shots you are using a very old version of sysprep creator/executor. I would try to update that first and then see what happens. You can always validate the sysprep unattend.xml file before you run it using System Image Manger in the ADK.

https://www.itninja.com/blog/view/validating-unattend-xml-files-with-system-image-manager - jamie_kace 5 years ago
- where do i find this ADK that has the System Image Manager ? - lgoh 5 years ago
  - Well you should have the ADK installed since you cannot create a KBE without it.
    
    https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
    
    The System Image Manager Tool is part of the Deployment tools when you install the ADK. - jamie_kace 5 years ago
Hi All,

apologies on the late replies. So this is what i did.

Reinstall Win 10 v1803 , deactivated Windows Defender. Use the Kace K2000 sysprep executor (all green) and edited the unattend.xml file by removing the <copyprofile>.

Still getting the same error as what i mentioned above. There is no unattend.xml file in the panther folder . - lgoh 5 years ago
- there's a setuperr file and the error show's the following..
  
  2018-09-19 15:47:26, Error SYSPRP ClipCleanUpState resetting WNF_OLIC_OS_LICENSE_TERMS_ACCEPTED failed with NTSTATUS=c0000022[gle=0x00000002] - lgoh 5 years ago
  - It appears you are using an OEM Windows, see these links:
    
    https://www.dell.com/community/ImageAssist/Windows-10-Creator-Update/td-p/5111969
    
    https://social.technet.microsoft.com/Forums/en-US/87e7ce72-0907-46d0-b042-6dafc633e53d/wnfolicoslicensetermsaccepted?forum=win10itprosetup
    
    OEM media is not supported by Quest:
    https://support.quest.com/kace-systems-deployment-appliance/kb/135252/using-oem-source-media-and-images
    
    Here is how to validate the Media BEFORE running sysprep, it shoud return as Volume Licensed:
    
    https://www.tenforums.com/tutorials/49586-determine-if-windows-license-type-oem-retail-volume.html - Channeler 5 years ago

Answers (1)

Posted by: rocky.perritt 5 years ago

Check your install media you uploaded. We had a similar issue and that fixed it. Remember you have to mount the .iso file and point to the mounted drive. You cannot point to the .iso file directly.

Answer this question

Posted by:

View more:

KACE Product Support Questions

question

Unattend answer file for pass [oobe system] . The answer file is invalid

Answers (1)

Posted by:

View more:

Related Questions

Related Links

Related Posts

KACE Product Support

Unattend answer file for pass [oobe system] . The answer file is invalid

Answers (1)

Posted by:

Don't be a Stranger!

View more:

Related Questions

Related Links

Related Posts

Share