locked
Windows 7 AutoUnattend.xml - User & PC Name RRS feed

  • Question

  • So I've been asked to research Windows 7 images and the best way to create and deploy them. We don't have MDT 2010 up yet, so I'm stuck using a custom install.wim along w/ the unattend.xml file.

    Question #1

    How can you stop Windows 7 OOBE welcome screen from making you create a local user account? After Windows 7 finishes its text based setup, I want it to boot into Windows as Admin bypassing the welcome screen (create user/change PC name). This way desktop support can -

    1. Change the PC name
    2. Join the domain, reboot, and be done
    3. End user logs in, process complete

    There is no need for them to do a Audit mode w/ reboot. The domain accounts already exist. I don't want local users being created.

    In Win XP you could edit the sysprep.inf so that you had -

    [GuiUnattended]
    AutoLogon=Yes
    AutoLogonCount=1

    Which would allow you to log in as admin the first time after sysprep, join the domain, etc. How do you do this w/ Windows 7? I can only get it to log in as admin in systemAudit mode, I want to do it in OOBE.

    Hopefully I just missed something. Like I said, I'm new to automating Windows 7 setup.
    Wednesday, March 3, 2010 9:42 PM

Answers

  • Below is the oobe section from my unattend.xml
    WARNING: The text wraps.

    Here's how it works for us:
    1. Built in Administrator account is disabled by default. We leave it that way

    2. We set a password for Administrator account. The default is NULL password.

    3. We add a new local user account.
      a) We name it Admin
      b) We add it to local Administrators group
      c) We set a password for it

    4. We set OOBE values (Hide EULA etc).

    5. We set language and locale values.

    Before that, not shown in this slice of unattend.xml, we set:
    a) Product key (MAK).
    b) Time Zone.
    c) Registered Owner.
    d) Automatic generation of computer name.

    When the computer finishes applying image:
    a) The technician logs on with Admin account.
    b) Changes the name of the computer.
    c) Joins the computer to domain.
    d) Performs some limited data transfer between old and new computer.
    d) Does some paperwork (notes some inventory numbers, obtains end user's signatures etc).

    This workflow, which BTW we have well documented, works well for us.
    We could add some autologons, but we didn't find it's worth the effort.



        <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">
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Name>Admin</Name>
                            <Group>Administrators;Users</Group>
                            <Password>
                                <Value>Jwe5Mk2</Value>
                                <PlainText>true</PlainText>
                            </Password>
                        </LocalAccount>
                    </LocalAccounts>
                    <AdministratorPassword>
                        <Value>Jwe5Mk2</Value>
                        <PlainText>true</PlainText>
                    </AdministratorPassword>
                </UserAccounts>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
            </component>
            <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>0409:00000409</InputLocale>
                <SystemLocale>00000409</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UserLocale>00000409</UserLocale>
            </component>
        </settings>
    • Marked as answer by Dale Qiao Friday, March 5, 2010 2:23 AM
    Wednesday, March 3, 2010 10:36 PM

All replies

  • Below is the oobe section from my unattend.xml
    WARNING: The text wraps.

    Here's how it works for us:
    1. Built in Administrator account is disabled by default. We leave it that way

    2. We set a password for Administrator account. The default is NULL password.

    3. We add a new local user account.
      a) We name it Admin
      b) We add it to local Administrators group
      c) We set a password for it

    4. We set OOBE values (Hide EULA etc).

    5. We set language and locale values.

    Before that, not shown in this slice of unattend.xml, we set:
    a) Product key (MAK).
    b) Time Zone.
    c) Registered Owner.
    d) Automatic generation of computer name.

    When the computer finishes applying image:
    a) The technician logs on with Admin account.
    b) Changes the name of the computer.
    c) Joins the computer to domain.
    d) Performs some limited data transfer between old and new computer.
    d) Does some paperwork (notes some inventory numbers, obtains end user's signatures etc).

    This workflow, which BTW we have well documented, works well for us.
    We could add some autologons, but we didn't find it's worth the effort.



        <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">
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Name>Admin</Name>
                            <Group>Administrators;Users</Group>
                            <Password>
                                <Value>Jwe5Mk2</Value>
                                <PlainText>true</PlainText>
                            </Password>
                        </LocalAccount>
                    </LocalAccounts>
                    <AdministratorPassword>
                        <Value>Jwe5Mk2</Value>
                        <PlainText>true</PlainText>
                    </AdministratorPassword>
                </UserAccounts>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
            </component>
            <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>0409:00000409</InputLocale>
                <SystemLocale>00000409</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UserLocale>00000409</UserLocale>
            </component>
        </settings>
    • Marked as answer by Dale Qiao Friday, March 5, 2010 2:23 AM
    Wednesday, March 3, 2010 10:36 PM
  • Awesome thanks! I'll give it a shot and let you know.

    Edit: Works great, thanks again. I didn't think you could use SkipUserOOBE since the reference file said it was depreciated.

    Thursday, March 4, 2010 1:48 PM
  • Can anyone here help a novice. I having been trying to build an image that will allow my company to deploy the same image to multiple computers. The Image is built and after I use the unattend.xml file that I got online, the computer restarts and continue to restarts. Can someone give me a step by step dummy instruction on how to accomplish this task from installation to sysprep. thank you

    Monday, July 18, 2011 5:34 PM