none
“Windows could not parse or process the unattend answer file for pass [specialize] The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft Shell Setup]” RRS feed

  • Question

  • Hello everyone,

    So I'm currently using MDT 2013 to successfully push my images to all of my machines. However I have a big desktop upgrade coming up and need to prepare 100 machines (all same model, same configuration). I would like to image one machine and sysprep it so that I can duplicate the hdd on our duplicator machine.

    I'm having a problem with the unattend file for this master hdd. I created a new unattend file using SIM for a few basic setup items and applied it during the sysprep.

    After sysprepping when the machine boots up I got stuck at "setup is installing devices" screen, even though I know that the only drivers on the image are from MDT and specific to this model of PC. I modified the generalize phase of my unattend file to leave the drivers in place during the sysprep process.

    However, I seem to still be getting errors in my file during the specialize phase and I cant figure it out. I will be posting my error logs and unattend file here shortly. 

    Wednesday, March 11, 2015 3:42 PM

All replies

  • Ok, here is my unattend file. I couldnt post a link so I'm pasting the file here.

    Going a little crazy trying to figure out what is breaking the sysprep. I dont want to do anything special, no auto naming, no adding to domain.

    Just copyprofile=true and activate windows.

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="specialize">
            <component name="Microsoft-Windows-IE-InternetExplorer" 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">
                <Home_Page>http:\\xxxlink</Home_Page>
                <SearchScopes>
                    <Scope wcm:action="add">
                        <ScopeDefault>true</ScopeDefault>
                        <ScopeDisplayName>Google</ScopeDisplayName>
                        <ScopeKey>Google</ScopeKey>
                        <ScopeUrl>http://www.google.com/search?q={searchTerms}</ScopeUrl>
                    </Scope>
                </SearchScopes>
                <DisableFirstRunWizard>true</DisableFirstRunWizard>
            </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>0409:00000409</InputLocale>
                <SystemLocale>en-US</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UserLocale>en-US</UserLocale>
            </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">
                <ComputerName></ComputerName>
                <ProductKey></ProductKey>
                <RegisteredOrganization>xxx</RegisteredOrganization>
                <RegisteredOwner>Windows User</RegisteredOwner>
                <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
                <TimeZone>Eastern Standard Time</TimeZone>
                <OEMInformation>
                    <Model></Model>
                    <Logo></Logo>
                </OEMInformation>
                <CopyProfile>true</CopyProfile>
                <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
            </component>
            <component name="Microsoft-Windows-SystemRestore-Main" 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">
                <DisableSR>1</DisableSR>
            </component>
            <component name="Microsoft-Windows-TapiSetup" 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">
                <TapiConfigured>0</TapiConfigured>
                <TapiUnattendLocation>
                    <AreaCode>""</AreaCode>
                    <CountryOrRegion>1</CountryOrRegion>
                    <LongDistanceAccess>9</LongDistanceAccess>
                    <OutsideAccess>9</OutsideAccess>
                    <PulseOrToneDialing>1</PulseOrToneDialing>
                    <DisableCallWaiting>""</DisableCallWaiting>
                    <InternationalCarrierCode>""</InternationalCarrierCode>
                    <LongDistanceCarrierCode>""</LongDistanceCarrierCode>
                    <Name>Default</Name>
                </TapiUnattendLocation>
            </component>
        </settings>
        <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">
                <InputLocale>0409:00000409</InputLocale>
                <SystemLocale>en-US</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UserLocale>en-US</UserLocale>
            </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">
                <AutoLogon>
                    <Enabled>true</Enabled>
                    <Username>admin-win</Username>
                    <Domain>.</Domain>
                    <Password>
                        <Value>xxxx==</Value>
                        <PlainText>false</PlainText>
                    </Password>
                    <LogonCount>999</LogonCount>
                </AutoLogon>
                <Display>
                    <ColorDepth>32</ColorDepth>
                    <HorizontalResolution>1024</HorizontalResolution>
                    <RefreshRate>60</RefreshRate>
                    <VerticalResolution>768</VerticalResolution>
                </Display>
                <FirstLogonCommands>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine>cscript c:\windows\system32\slmgr.vbs /skms xxx.root</CommandLine>
                        <Order>1</Order>
                        <Description>Set KMS Server</Description>
                    </SynchronousCommand>
                    <SynchronousCommand wcm:action="add">
                        <Order>2</Order>
                        <CommandLine>cscript c:\windows\system32\slmgr.vbs /ato</CommandLine>
                        <Description>Activate Windows</Description>
                    </SynchronousCommand>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine>REG ADD “HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff”</CommandLine>
                        <Description>Disable Set Network Location Prompt</Description>
                        <Order>3</Order>
                        <RequiresUserInput>true</RequiresUserInput>
                    </SynchronousCommand>
                </FirstLogonCommands>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                </OOBE>
                <RegisteredOrganization>xxx</RegisteredOrganization>
                <RegisteredOwner>Windows User</RegisteredOwner>
                <TimeZone></TimeZone>
            </component>
        </settings>
        <settings pass="generalize">
            <component name="Microsoft-Windows-PnpSysprep" 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">
                <DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="xxx.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>


    Thanks for any help you can provide.

    Wednesday, March 11, 2015 7:27 PM
  • Please check the setuperr and setupact.log which you can find on the machine that has just failed in the following directory: C:\Windows\Panther, open up a command prompt by pressing SHITF+F10 together. Then browse to the location, copy the logfiles to your deploymentshare and view them with CMtrace.exe the error will reveal itself, since it's in those two log's

    Cheers! Rens


    If this post is helpful please click &quot;Mark for answer&quot;, thanks! Kind regards

    Thursday, March 12, 2015 10:21 AM
  • I had the same problem, I was using the OSDComputerName = %Assettag% . Some computers did not have assettag in the bios. therfore computer name was set to "No Asset Tag". All worked well till the oobe, where the deployment errored out because computername are not allowed with spaces. 

    May be you have a property computer name or something else that is not valid. 

    Thursday, March 12, 2015 10:27 AM
  • Hello, azuberi80.

    This article should help you. 

    Thursday, March 12, 2015 1:48 PM
  •    <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" ... >
                <ComputerName></ComputerName>
                <ProductKey></ProductKey>
                <RegisteredOrganization>xxx</RegisteredOrganization>
                <RegisteredOwner>Windows User</RegisteredOwner>
                <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
                <TimeZone>Eastern Standard Time</TimeZone>
                <OEMInformation>
                    <Model></Model>
                    <Logo></Logo>
                </OEMInformation>
                <CopyProfile>true</CopyProfile>
                <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
            </component>

    OK, to start off with your ComputerName, PRoductKey, and OEMInformation fields are empty, they can't be empty.

    I know it's tempting to navigate through the SIM, and add stuff that looks cool... but please don't, the more stuff you add the more you will need to manually determine how to fix the stuff you added by parsing the Panther Logs.

    Instead, please start off with a known good unattend.xml file and run from there.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, March 13, 2015 6:17 AM
    Moderator
  • Thanks, I'll try filling those in. 

    I have been using MDT to deploy so I didnt know if I can just reuse the same xml file to re-sysprep the OS. 

    Friday, March 13, 2015 2:16 PM