Link to home
Start Free TrialLog in
Avatar of Edward Crist
Edward CristFlag for United States of America

asked on

Windows 7 sysprep answer file

I'm in a bind and looking for help.  I've having no luck creating a viable unattend.xml answer file for my Windows 7 Enterprise image creation.  I have 500+ laptops to image and I just need a file that will do the following.....

create a local admin user account
add the laptop to my domain
set the display to 1024x768
set time zone to eastern time

Does anyone have a simple xml file that I can modify to accomplish this?  This was a LOT easier in XP Pro!!

Thanks, folks.
ASKER CERTIFIED SOLUTION
Avatar of Hayes Jupe
Hayes Jupe
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
To add to Hayes answer, you get the System Image Manager tool from the Windows Automated Installation Kit (WAIK), which is a free download from MS (For Windows 7 you either need the Windows 7 RC waik, or the RTM WAIK, which is now available to technet/msdn subscribers.)
Avatar of Edward Crist

ASKER

I'm trying to use the Win7 SIM from the AIK.  The attached answer file is what I've got so far....but it's not entering the product key and not joinning the domain.  I'm confused about AUDIT vs OOBE vs PE!!

Any help is greatly appreciated!
sysprep.txt
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks!  Got it working now!
Also dont forget that when binding to the domain it will bind with a random name, if thats ok for you then great, we have had to create a VB script to bind to the domain after we have provided the correct name.

If you bind to the domain using the answer file, depending on how your AD is setup and you do the rename you may have AD trust issues when it comes time to login.

The code snippet should give you what you need, but without the domain bind, if you want me to give you the VBScript i created for binding to the domain after you have assigned the correct machine name let me know.
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Deployment" 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">
            <Reseal>
                <Mode>OOBE</Mode>
            </Reseal>
        </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">
            <OOBE>
                <ProtectYourPC>1</ProtectYourPC>
                <NetworkLocation>Work</NetworkLocation>
                <HideEULAPage>true</HideEULAPage>
            </OOBE>
            <TimeZone>W. Australia Standard Time</TimeZone>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>PASSWORD GOES HERE</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Description>ADMIN USER</Description>
                        <DisplayName>Administrator</DisplayName>
                        <Group>Administrators</Group>
                        <Name>Administrator</Name>
                    </LocalAccount>
                </LocalAccounts>
                <AdministratorPassword>
                    <Value>Password goes here</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
            </UserAccounts>
            <OEMInformation>
                <Manufacturer>CHANGE</Manufacturer>
                <HelpCustomized>false</HelpCustomized>
                <SupportHours>08:00 - 17:00</SupportHours>
                <SupportPhone>PHONE NUMBER</SupportPhone>
                <SupportURL>SUPPORT URL</SupportURL>
            </OEMInformation>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Description>KMS Authentication</Description>
                    <CommandLine>c:\windows\system32\slmgr.vbs -skms KMS.SERVER.HERE</CommandLine>
                    <Order>1</Order>
                </SynchronousCommand>
            </FirstLogonCommands>
        </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>en-us</InputLocale>
            <SystemLocale>en-us</SystemLocale>
            <UILanguage>en-us</UILanguage>
            <UILanguageFallback>en-us</UILanguageFallback>
            <UserLocale>en-us</UserLocale>
        </component>
    </settings>
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-LUA-Settings" 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">
            <EnableLUA>false</EnableLUA>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim://SERVER1/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Open in new window

@pnorris99 Could you post the code for binding to the domain after you have assigned the correct machine name?  Thanks!
Avatar of John Smith
John Smith

null
If you don't have a KMS server you can still use an MAK key.  You would have to go to the Volume License Site and request one, and once you have, it will give you one automatically.  You can use that to activate windows instead of a KMS key.