BDD 2007 for Server OS Deployment - Trial 2
Posted
Wednesday, January 31, 2007 1:10 PM
by
jhuston
Okay, last time I discussed how to get plug and play enumeration to fully discover all resources. That's just fine. One of those resources, however, is a serial-attached-SCSI (SAS) RAID card that has the boot disk attached to it.
The Out-of-box drivers works just fine for getting WinPE 2.0 to see that RAID card, partition it, format it, etc. However, when the Windows 2003 setup runs, it needs the same RAID drivers available for the textmode portion of the installation. BDD 2007 does not place the SCSIAdapter drivers into a $OEM$\textmode directory for you - you need to do this yourself.
So, where do I put them? You will notice a $OEM$ directory at the top of the d:\Distribution folder. Should you place the files here? Not necessarily. Turns out that the task sequence calls a script called LTIApply.wsf when it comes time to install the OS. For non-Vista operating systems, it will first copy the source files down to the MININT directory on the boot drive and then copy the $OEM$ directory and proceed with installation.
The LTIApply.wsf script will look in several locations for the $OEM$ directory and, once it is found, use that directory for the build. It will not merge directories, so plan ahead. This is the order in which it looks for the directory:
- d:\Distribution\Control\build_name\$OEM$
- d:\Distribution\Operating Systems\OS_Name\$OEM$
- d:\Distribution\architecture\$OEM$
- d:\Distribution\$OEM$
In my test case, I used the first option and placed the $OEM$ in the same directory as the build control files. This makes sense since you also must update the UNATTEND.TXT file to indicate which drivers to load via the OEM files and what files to include in the temporary boot directory used by textmode.
Once that is taken care of, you should be good to go for installation.