- Create builds using the naming conventions below
- After creation, re-sequence builds in the builds.xml file in <DistributionShare>\control\ using XML Notepad (or other XML editor).
- Use the task sequence editor to add any required custom options.
- NB: When adding applications to a Task Sequence, note that "command line" field cannot contain any path information. If using a "cmd" embedded command (i.e. mkdir, copy), you must prefix it with "cmd /c". If you executable name contains spaces, you must delimit it with quotes.
- The "Start In" field must contain a path that is valid for the stage of LiteTouch in which you use it. I.e., do not specify "X:\" as your root path if you are not in a WinPE section of the task sequencer. If you path contains spaces, do not delimit it with quotes (the Task Sequencer will add quotes via API... if you add them manually your custom task will fail!)
- Add a reboot action to the bottom of the "Custom Tasks" section to apply changes required by installers (must be performed before image capture).
Supplemental instructions for XP-based images:
- Beware the UBERBUG! To correct for an inability to boot XP after image application, you need to either apply a hotfix to your XP source (not available via Windows Update) or add a reg import command to the pre-install phase of your XP Build in the BDD workbench. (NOTE: This applies only for WIM-image based XP deployments)
- If you want your image to work across all HALs, you will need to switch your reference image HAL to an ACPI type, and then add the "ZTIHalSwitch.vbs" (from the Geek's Guide to Windows XP HAL Replacement) to your XP Build Task Sequence, in the post-install section, using BDD workbench.
- Builds that will use a captured XP image (WIM file) need to have additional storage drivers added to the "sysprep.inf" file associated with the build. The reference sysprep.inf content can be found in the "Staging" directory under "\DeployFiles" folder.
- Builds that will perform an unattended XP setup using the files from the XP Professional CD will need a custom content added to the "unattend.txt" file assiciated with the build. A reference file is stored in the "DeployFiles" subdirectory of the "Staging" directory. The unattend.txt file sections that require alteration are [MassStorageDrivers] and [OemBootFiles]
- Any new mass storage drivers added for XP systems will need to be added to the build's "\$OEM$\Textmode" directory, and the contents of their "txtsetup.oem" file will need to be merged into the master txtsetup.oem file in this directory.
Full description of each Build Name element, in sequence
|Vista Enterprise Edition, x86 platform, Service Pack 1, Patched September 2007, intended for use on Faculty/Staff system deployments.|