WDS - W7 - Unattend.xml - Still Prompting For Language Despite Settings

[Sparky__H]

Hi Guys

I'm having a problem with the second answer file that WDS passes alone with install.wim. Basically despite setting language options to en-GB it STILL prompts with the language selection UI during the OOBE Pass.

Can anyone shed some light on 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>
                <NetworkLocation>Home</NetworkLocation>
                <ProtectYourPC>3</ProtectYourPC>
                <HideEULAPage>true</HideEULAPage>
            </OOBE>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>UABhAHMAcwB3AG8AcgBkAA==</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Description>Administrator Account</Description>
                        <DisplayName>Administrator</DisplayName>
                        <Group>Administrators</Group>
                        <Name>Admin</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <RegisteredOwner />
            <RegisteredOrganization />
            <TimeZone>GMT 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">
            <TimeZone>GMT Standard Time</TimeZone>
            <ComputerName>COMPUTERNAME</ComputerName>
            <RegisteredOrganization />
            <RegisteredOwner />
            <ProductKey>PRODUCTKEY</ProductKey>
            <AutoLogon>
                <Enabled>true</Enabled>
                <Domain>DOMAIN</Domain>
                <Username>USERNAME</Username>
                <Password>
                    <Value>PASSWORD</Value>
                    <PlainText>false</PlainText>
                </Password>
            </AutoLogon>
        </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">
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <InputLocale>en-GB</InputLocale>
            <SystemLocale>en-GB</SystemLocale>
            <UserLocale>en-GB</UserLocale>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:d:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

I can't see what is missing/wrong...


Cheers

 

[Sparky__H]

Cheers MrB I'll have a look at it tomorrow morning.

 

[Sparky__H]

Cheers MrB worked a treat

oddjob62 - Yeah that's a known issue

Seems it might be to do with the login information. Without it regardless the language option UI prompts.

 

[Sparky__H]

Oh great now I have another problem.

The Hyper-v clients I'm using WDS to deploy are finding the server, authenticating properly, and applying the correct images. They are being added to AD and the GUID is being stored. The first time...

Delete the computer from the Computer group and the VM just hangs at DHCP stage when trying it for a second time.

Joy happy fun time.

IGNORE!! - Right it's late and I'm tired. Seems that even though I deleted them using the MMC snap-in that wasn't enough. Had to delete them from the approved auto-add device list via CMD.

*sigh*