Users Guide

6
Preparing the script les
This chapter describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment on a
target system in the Microsoft Windows PE and embedded Linux environment.
There are four main tasks:
Using The Sample DTK Scripts To Run A Full Deployment
Editing The Sample Batch Files To Perform A Complete System Deployment
Using DTK Sample Scripts To Capture Conguration Information
Preparing The Operating System Installation Scripts
Using the sample DTK scripts to run a full deployment
A scripted DTK deployment relies on the master deployment le to integrate all the applicable DTK task scripts and utilities and
perform preoperating system conguration tasks before launching the operating system installation les. The master deployment
le, along with the TKENVSET.BAT (for Windows) or tkenvset.sh (for Linux) scripts, makes up the master set of instructions that
drives the deployment process. This le is not provided with the sample scripts.
A sample DEPLOY.BAT is given below:
::
*****************************************************
::Call TKENVSET.BAT to discover platform information
::as well as set paths and environment variables for
::Deployment Toolkit Tools and Scripts.
*****************************************************
*****************************************************
:: call RAIDCFG.BAT to configure RAID.
::
*****************************************************
*****************************************************
:: Replicate the system settings to the current SUT!.
CALL SYSREP.BAT or DTKRUNALL.BAT.
::
*****************************************************
*****************************************************
::Partitioning the system hard disk. call PARTCFG.BAT.
*****************************************************
*****************************************************
:: Put hdd as first in boot sequence (1-removable, 2-
cdrom, 3-hdd)
:: If the system configuration has changed (i.e. a
::boot device was added, removed, or enabled in BIOS)
::the following line should be modified to reflect the
::new hdd device number.
:: This is calling Windows installer scripts.
*****************************************************
::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0
::call WIN2K12.BAT
35