Deployment Guide

NOTE: Do not replicate the RAC IP address when creating a .cfg file. Replicating the RAC IP address can leave the
system inaccessible because multiple systems are configured with the same IP address.
NOTE: The racrep.sh and sysrep.sh have duplicate functions. If you run racrep.sh followed by sysrep.sh,
the latter overwrites the former settings.
RACCAP.BAT or raccap.sh
The RACCAP.BAT or raccap.sh sample script captures RAC configuration settings and saves them to a specified location. An optional
user input can be passed as a parameter. You can provide the path or file name as an input to this script. The default variable values used
in this script are set to the correct default values to perform a scripted deployment. On systems running Windows, the RACCAP.BAT
uses the RACADM.EXE utility to retrieve RAC configuration settings from the source system and to save it in raccfg.ini file at
\Toolkit\Systems\<target system>. On systems running Linux, the raccap.sh script uses the racadm wrapper script or the
syscfg utility (depending on the RAC version on your system) to retrieve RAC configuration settings from the source system and to
save it in raccfg.ini at /opt/dell/toolkit/systems/<target system>.
NOTE: Ensure that you run RACCAP.BAT in a writable environment. If you run RACCAP.BAT in a read-only environment,
DTK displays the message <filename.ini> has been generated.
UPINIT.BAT or upinit.sh
The UPINIT.BAT or upinit.sh is a tool used to create and populate a new Dell utility partition and to upgrade or downgrade an
existing utility partition.
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.
Preparing the script files
47