Building a Common Image - Developing a common software image for the HP dc7900, Elite 8000 and 6000 Pro desktop models

Note:
For complete copies of the SYSPREP.inf files used by HP,
please see Appendix A: Sample Answer Files on p. 22.
cmdlines.txt
In addition to the SYSPREP directory and .inf file, you will need to create the
directory ―c:\i386\$oem$‖. Within this directory, you will need to place a file
named ―cmdlines.txt‖ containing at least the following lines:
[Commands]
"c:\SYSPREP\SYSPREP -clean"
This will ensure that all services related to non-used mass storage devices will be
removed from the system.
oobeinfo.ini (Windows XP)
In addition to SYSPREP.inf, Windows XP relies heavily on the oobeinfo.ini file. This
file resides in the directory: ―C:\windows\system32\oobe‖. If you are using HP
preinstalled or restored images, then this file should be intact and all settings should
be correct.
Note:
This file will be different for Windows XP Home Edition
and Windows XP Professional.
Running SYSPREP (Windows XP)
After the previous steps have been completed, you will be ready to run sysprep.exe
to prepare the system for imaging. Please see the documentation included in
deploy.chm for Sysprep.exe command-line options. After running Sysprep.exe, you
will be ready to capture then deploy your image.
Note:
Windows XP may present a warning that the reseal limit
has been reached, and your WPA grace period will not
be reset. If you are using the HP-provided image, i386
folder contents, sysprep.inf and have not altered the file
―C:\windows\system32\oobe\oobeinfo.ini‖, then you
can disregard this message. Your image will not rely on
Windows Product Activation. Otherwise, end-users will be
required to ―Activate‖ their product with Microsoft during
OOBE.