This is probably the page you need:

http://technet.microsoft.com/en-us/library/dd74454...

That will give you the information that you need in your sysprep file for doing a sysprep to prepare for an unattended installation.  Specifically, when you're sysprep a system that you're going to restart in WinPE to pull as an image, you use these tags for sysprep: sysprep /generalize /oobe /shutdown /unattend:"%YOURSYSPREPFILE.xml%"

Essentially, a sysprep file for a prepared system from which you're going to make an image for an unattended install needs certain things to be configured in passes 4 and 7, and will ignore settings in the other answer file passes.  To give you an idea, this is the file I use:

-----

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="%MYTOKEN%" 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>
            <UserLocale>en-us</UserLocale>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="%MYTOKEN%" 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>
                <ProtectYourPC>1</ProtectYourPC>
                <NetworkLocation>Work</NetworkLocation>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>%MYPASS%</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>%MYPASS%</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Name>Local Account</Name>
                        <Group>Administrators</Group>
                        <DisplayName>Local Account</DisplayName>
                        <Description>Local Account</Description>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <TimeZone>Mountain Standard Time</TimeZone>
            <RegisteredOrganization>%MYORGANIZATION%</RegisteredOrganization>
            <RegisteredOwner>%MYORGANIZATION%</RegisteredOwner>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="%MYTOKEN%" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ComputerName>*</ComputerName>
            <RegisteredOrganization>%MYORGANIZATION%</RegisteredOrganization>
            <RegisteredOwner>%MYORGANIZATION%</RegisteredOwner>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:c:/install.wim#Windows 7 ENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

-----

That should give you a better idea.  Good luck!

I'm a huge fan of this forum.  Long time lurker, first time poster.  Since the release of Windows 7, I have been scouring the forums looking for ideas and tips.  When DS 6.9 SP3 dropped, we started our effort to generate an image for Win 7 that was suitable for deployment.  I have been through the WAIK and generated my XML file the way I want it, but I have a few questions that need some clarification. 

1.  To enable DS to use the Win 7 sysprep files, where do I put it?  I've put the sysprep.exe found in the C:\Windows\System32\Sysprep directory just about everywhere I an think of, on the DS server, and I get no joy when I use the Sysprep option, in a Capture Image.

2.  Piggybacking on question 1, is is better to allow DS to sysprep the image or run the command on the computer, then capture the image? 

3.  I really like the idea of using a "tokenized" XML file, and I have that part working fine, but feeding the file to sysprep has been a challenge.  I tried to do it in Automation, but received an error that Sysprep was not a valid 32-bit application (the command I was running was a script that read:  C:\Windows\System32\Sysprep\Sysprep.exe /generalize /oobe /shutdown /unattend:F:\Images\%NAME%.xml).  Can the DS tokens be included in an unattend.xml file that is executed on the machine, pre-Captuer Image task, and pull the proper values upon deployment? 

4.  If I can get Win 7 sysprep working through DS, I will just feed that sysprep command via the Deploy Image job and life will be good.  Does anyone see any issues with it?

I've probably tried 25 permutations of the above scenarios, but have yet to have success.  When I try to sysprep with DS, the machine never gets the sysprep executed against it.  When I run sysprep on the actual computer, it doesn't get the proper variables, because it was executed in Production.

At this point, I'm banging my head against the wall, trying to figure it out.  I'm asking the collective wisdom of this forum for their assistance.  Thank you all, in advance.

How about grabbing a copy of the Windows Automated Installation Kit for Windows 7?
This Microsoft tool is all about creating an unattended installation for windows 7 deployment.