I am still "struggalang" with my Vista Unattend project. I found information that you can install additional drivers and programs by using DataImage, and a WIM on the server. The problem is that the WIM is neither copied nor extracted to the client during install. These components are necessary as the later Client Unattend updates the drivers and runs the programs that are supposed to be copied present. I have no validation errors in WSIM and there are no errors in the setupact or setuperr log files. I can't figure out what might be the problem, maybe I can get some help.

For anyone who notices there are some parts missing from the XML, its because this is only the WDSClientUnattend file. I can post the Setup Unattend file if needed.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
	<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">
			<WindowsDeploymentServices>
				<Login>
					<WillShowUI>OnError</WillShowUI>
					<Credentials>
						<Username>kdineen</Username>
						<Domain>shark</Domain>
						<Password>ZarleyZalapski33</Password>
					</Credentials>
				</Login>
				<ImageSelection>
					<WillShowUI>OnError</WillShowUI>
					<InstallImage>
						<ImageName>Windows Vista BUSINESS</ImageName>
						<ImageGroup>Vista</ImageGroup>
					</InstallImage>
					<InstallTo>
						<DiskID>0</DiskID>
						<PartitionID>1</PartitionID>
					</InstallTo>
				</ImageSelection>
			</WindowsDeploymentServices>
			<DiskConfiguration>
				<Disk wcm:action="add">
					<CreatePartitions>
						<CreatePartition wcm:action="add">
							<Order>1</Order>
							<Size>20480</Size>
							<Extend>false</Extend>
							<Type>Primary</Type>
						</CreatePartition>
					</CreatePartitions>
					<ModifyPartitions>
						<ModifyPartition wcm:action="add">
							<Active>true</Active>
							<Extend>true</Extend>
							<Format>NTFS</Format>
							<Label>system</Label>
							<Letter>C</Letter>
							<Order>1</Order>
							<PartitionID>1</PartitionID>
						</ModifyPartition>
					</ModifyPartitions>
					<DiskID>0</DiskID>
					<WillWipeDisk>true</WillWipeDisk>
				</Disk>
				<WillShowUI>OnError</WillShowUI>
			</DiskConfiguration>
			<ImageInstall>
				<DataImage wcm:action="add">
					<InstallTo>
						<DiskID>0</DiskID>
						<PartitionID>1</PartitionID>
					</InstallTo>
					<InstallFrom>
						<Credentials>
							<Domain>shark</Domain>
							<Password>ZarleyZalapski33</Password>
							<Username>kdineen</Username>
						</Credentials>
						<Path>\\unclesocks\RemInst\dataimage.wim</Path>
					</InstallFrom>
					<Order>1</Order>
				</DataImage>
			</ImageInstall>
		</component>
		<component name="Microsoft-Windows-International-Core-WinPE" 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">
			<SetupUILanguage>
				<UILanguage>en-us</UILanguage>
			</SetupUILanguage>
			<InputLocale>en-us</InputLocale>
			<SystemLocale>en-us</SystemLocale>
			<UILanguage>en-us</UILanguage>
			<UserLocale>en-us</UserLocale>
		</component>
	</settings>
	<cpi:offlineImage cpi:source="wim://unclesocks/seafood/distribution/installs/vista_business.wim#Windows Vista BUSINESS" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Answer found here, unfortunately...

So I need to find another way to dynamically add drivers and run a program during WDS Unattend. Any ideas? I didn't really want to have to put drivers into the INSTALL.WIM...

If you want to wait for 2008 R2 WDS, you will be able to dynamically inject drivers into a WIM as it loads. Late July or August for release

That sounds great. I'll put in a request for it now. So far my WDS testing is done on a 2003, but my 7server has 2008 R1. So when R2 comes out I'll upgrade it, so just have to do a migration.