Deployment Guide
Table Of Contents
- Dell OpenManage Deployment Toolkit Version 5.5 User's Guide
- Introduction
- Pre-requisites and deployment
- Downloading DTK
- DTK Seamless package
- Setting up a directory structure for deployment
- Preparing the script files
- Using the sample DTK scripts to run a full deployment
- Editing the sample batch files to perform a complete system deployment
- Scripts for deployment on systems running windows
- Scripts for deployment on systems running Linux
- Replication scripts for deployment on systems running windows operating system
- Replication scripts for deployment on systems running Linux operating system
- Deployment scripts for systems running windows operating systems
- Deployment scripts for systems running Linux operating systems
- Other scripts for systems running Windows operating systems
- Other scripts for systems running Linux operating systems
- Editing example of TKENVSET and tkenvset
- Editing DTK task scripts
- Using DTK sample scripts to capture configuration information
- Preparing the operating system installation scripts
- Running the deployment scripts
- Deployment using removable boot media with a network connection (media-based) for systems running windows
- Media-based local deployment for systems running microsoft windows
- Media-Based local deployment with Networking enabled for systems running windows
- Deployment using removable boot media without a network (media-based) connection for systems running windows
- Network based deployment for systems running windows
- Using a third-party deployment solution framework for systems running windows
- Using Windows Pre-installation Environment driver CAB files for systems running Windows
- Deployment using Dell provided embedded Linux
- Deployment using customized embedded Linux
- Using a third-party deployment solution framework for systems running Linux
- Running Dell update packages on systems running embedded Linux
- Known issues and frequently asked questions
NOTE: You can use this script to create a new Dell utility partition only if there are no existing partitions on your hard disk.
Upgrades or downgrades can be made only to existing Dell utility partitions to capture BIOS and BMC settings using the
overwrite option.
CAUTION: The existing Dell utility partition must be the first primary partition on the hard disk. Also, the Dell
utility partition must be greater than or equal to 32 MB and less than 2 GB.
For details on the command line arguments to be used for UPINIT.BAT or upinit.sh, see the Dell Deployment Toolkit
Command Line Interface Reference Guide dell.com/openmanagemanuals.
Preparing the operating system installation scripts
The W2K8INST.BAT And W2K12INST.BAT script (on systems running supported Windows operating systems), the linux scripts
(on systems running supported Red Hat Enterprise Linux Server operating system), and suseinst.sh sample script (on systems
running supported SUSE Linux Enterprise Server operating system) are used to perform an installation. The variables and
paths must be specified before the operating system can be installed. For more information on installing Red Hat Enterprise
Linux and SUSE Linux Enterprise Server, see the Dell OpenManage Deployment Toolkit Installation Guide available at dell.com/
openmanagemanuals.
NOTE: It is recommended that you consult your Windows or Red Hat Enterprise Linux Server operating system
documentation and unattended deployment documentation to develop a thorough understanding of the unattended
installation process before attempting to perform a full scripted deployment.
NOTE: While installing Linux, ensure that you install grub in the boot partition. Otherwise, you cannot boot to the utility
partition by pressing the <F10> key during reboot.
W2K8INST.BAT, W2K12INST.BAT and W2K16INST.BAT
The W2K8INST.BAT, W2K12INST.BATand W2K16INST.BATsample scripts are used to perform an unattended installation of
the Windows Server 2008 , Windows Server 2012 and Windows Server 2016 operating systems respectively. The variables and
paths must be specified before the operating system can be installed.
NOTE:
It is recommended that you consult your Windows operating system documentation and unattended deployment
documentation to develop a thorough understanding of the Windows unattended installation process before attempting to
perform a full scripted deployment.
The syntax for W2K8INST.BAT,W2K12INST.BATand W2K16INST.BATare w2k8inst.bat,w2k12inst.batand
w2k16inst.bat respectively.
Utilities used
SETUP.EXE — Used to install the operating system in conjunction with the UNATTEND.XML and UNATTEND_UEFI.XML
answer files.
External dependencies
W2K8INST.BAT,W2K12INST.BATand W2K16INST.BATscripts uses two environment variables: DT_PLATFORM and
DT_DRIVE.
The DT_PLATFORM variable is set by TKENVSET.BAT using platform discovery.
The DT_DRIVE denotes the network drive letter to the network shared path containing the Windows Server 2008 or the
Windows Server 2012 operating system source and the UNATTEND.XML (in BIOS mode) or UNATTEND_UEFI.XML file (in UEFI
mode).
The W2K8INST.BAT script uses the UNATTEND.XML file (in BIOS mode) and UNATTEND_UEFI.XML file (in UEFI mode)
with SETUP.EXE utility to install the operating system files. The W2K12INST.BAT script uses the UNATTEND2K12.XML
file (in BIOS mode) and UNATTEND2K12_UEFI.XML file (in UEFI mode) with SETUP.EXE utility to install the operating
system files. The W2K16INST.BAT script uses the UNATTEND2K16.XML file (in BIOS mode) and UNATTEND2K16_UEFI.XML
Preparing the script files
49