+ Post New Thread
Results 1 to 11 of 11
O/S Deployment Thread, Unattend.xml issues in Technical; Can someone have a look at my unattend.xml and make sure I'm not being a totally n00b. Code: <?xml version="1.0" ...
  1. #1

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,303
    Thank Post
    226
    Thanked 412 Times in 305 Posts
    Rep Power
    163

    Unattend.xml issues

    Can someone have a look at my unattend.xml and make sure I'm not being a totally n00b.

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="specialize">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>0809:00000809</InputLocale>
                <SystemLocale>en-GB</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UserLocale>en-GB</UserLocale>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" 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>
                <TimeZone>GMT Standard Time</TimeZone>
            </component>
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <Credentials>
                        <Domain>PSL</Domain>
                        <Password>#############</Password>
                        <Username>administrator</Username>
                    </Credentials>
                    <JoinDomain>PSL</JoinDomain>
                    <MachineObjectOU>OU=devStaff,OU=Devices,DC=DOMAIN,DC=internal</MachineObjectOU>
                </Identification>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" 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>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                </OOBE>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>bwBuAGMAbwBtAGUANABjAHUAYgBpAGMAYQAhAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <DomainAccounts>
                        <DomainAccountList wcm:action="add">
                            <Domain>DOMAIN</Domain>
                            <DomainAccount wcm:action="add">
                                <Group>Administrators</Group>
                                <Name>Domain Admins</Name>
                            </DomainAccount>
                        </DomainAccountList>
                    </DomainAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>ZAByAHUAZwBDAGwAIQBuADEAYwBQAGEAcwBzAHcAbwByAGQA</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Name>prioryU</Name>
                            <DisplayName>PowerUser</DisplayName>
                            <Group>Administrators;Power users</Group>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
            </component>
        </settings>
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <UserData>
                    <ProductKey>
                        <Key>33PXH-7Y6KF-2VJC9-XBBR8-HVTHH</Key>
                        <WillShowUI>OnError</WillShowUI>
                    </ProductKey>
                    <AcceptEula>true</AcceptEula>
                    <FullName>System Manager</FullName>
                    <Organization>##########</Organization>
                </UserData>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog:c:/windows/system32/sysprep/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    I have been through about 14 of these, gradually adjusting, adding bits, taking away bits. Still everytime it boots it shows the language selection box. The selections given are right but I don't want that coming up at all.

    This is to be sysprepped into an image.

    Any ideas?

  2. #2

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,303
    Thank Post
    226
    Thanked 412 Times in 305 Posts
    Rep Power
    163
    The sysprep command I am using is:
    sysprep /generalize /oobe /shutdown /unattend:C:\Windows\system32\sysprep\unattend.xml

    Could the issue be that I am using the oobe switch and that actually forces that?

  3. #3


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,800
    Thank Post
    231
    Thanked 883 Times in 759 Posts
    Rep Power
    300
    i think it does that on purpose tbh btw

    <InputLocale>0809:00000809</InputLocale>
    <SystemLocale>en-GB</SystemLocale>
    <UILanguage>en-US</UILanguage>
    <UserLocale>en-GB</UserLocale>

    you have a contradictory en-us in there which may not help

  4. #4

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,303
    Thank Post
    226
    Thanked 412 Times in 305 Posts
    Rep Power
    163
    The UI is en-US as someone had said that there is no en-GB version of the windows interface. That was in one of my versions and still wouldn't work.

  5. #5

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,303
    Thank Post
    226
    Thanked 412 Times in 305 Posts
    Rep Power
    163
    Quote Originally Posted by sted View Post
    i think it does that on purpose tbh btw
    So there is no way to image a machine so that it appears at the login screen ready to use? I thought that was the whole point of imaging and deployment!

  6. #6


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,800
    Thank Post
    231
    Thanked 883 Times in 759 Posts
    Rep Power
    300
    Quote Originally Posted by TechMonkey View Post
    So there is no way to image a machine so that it appears at the login screen ready to use? I thought that was the whole point of imaging and deployment!
    mdt can

  7. #7


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    9,365
    Thank Post
    241
    Thanked 2,811 Times in 2,075 Posts
    Rep Power
    812
    You need to set the languages in the 'WindowsPE' pass.

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-International-Core-WinPE" 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">
                <SetupUILanguage>
                    <UILanguage>en-US</UILanguage>
                    <WillShowUI>OnError</WillShowUI>
                </SetupUILanguage>
                <InputLocale>en-GB</InputLocale>
                <SystemLocale>en-GB</SystemLocale>
                <UserLocale>en-GB</UserLocale>
                <UILanguage>en-US</UILanguage>
                <UILanguageFallback>en-US</UILanguageFallback>
            </component>
        </settings>
    </unattend>

  8. Thanks to Arthur from:

    TechMonkey (28th June 2012)

  9. #8

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,303
    Thank Post
    226
    Thanked 412 Times in 305 Posts
    Rep Power
    163
    Ta muchly. You will never guess what option is currently being tested on a build after I found a random table squirrelled away on someone's random blog about the minimum options they use with the keys clearly labelled. All this time I have assumed it was ok as I had the languages set!!

    Ta though, I'll report back. It's good that the official MS tool makes this so much easier to create!

  10. #9
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,483
    Thank Post
    10
    Thanked 502 Times in 442 Posts
    Rep Power
    114
    Quote Originally Posted by TechMonkey View Post
    The UI is en-US as someone had said that there is no en-GB version of the windows interface. That was in one of my versions and still wouldn't work.
    During the PE deployment it not present on the boot wim afaik and will error, for an unattended sysprep file after WDS has deployed the image then it is fine to use.

  11. #10

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,303
    Thank Post
    226
    Thanked 412 Times in 305 Posts
    Rep Power
    163
    Well in case anyone stumbles in here hoping for an answer I don't really have one. The one I created from the WAIK never worked. I cut the xml sheet right back to the bare minimum and still didn't work. In the end I took one from a thread on here that someone said worked for them, edited my details in and it worked. Makes a joke of producing an xml sheet with the approved tools that doesn't work! & having a tool that has so many options that are so similar with very little decent documentation.

    Grrr.

    Anyway, thanks for the hand all.

  12. #11

    Join Date
    Mar 2011
    Location
    Bournemouth
    Posts
    280
    Thank Post
    16
    Thanked 74 Times in 64 Posts
    Rep Power
    22
    Those passwords are easily decoded, in case theyre important, you may want to remove them

SHARE:
+ Post New Thread

Similar Threads

  1. [MDT] unattend.xml
    By garethedmondson in forum O/S Deployment
    Replies: 8
    Last Post: 28th November 2011, 02:38 PM
  2. Replies: 1
    Last Post: 19th August 2010, 12:24 PM
  3. unattend.xml not running on a custom syspreped image??
    By burgemaster in forum Windows 7
    Replies: 2
    Last Post: 25th March 2010, 10:21 AM
  4. [WDS] Win 7 unattend.xml help
    By Ste_Harve in forum O/S Deployment
    Replies: 5
    Last Post: 1st February 2010, 01:51 PM
  5. WDS - Unattended.xml has anyone got one?
    By Dos_Box in forum Windows Server 2008
    Replies: 2
    Last Post: 20th February 2008, 03:49 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •