Deployment Guide

File Format
The -i and -o options use the .ini file format for system configuration (SYSCFG) options. All name/value entries that follow
the [syscfg] section header in the .ini file belong to the SYSCFG utility. For an example of the syscfg.ini file, see Sample
SYSCFG Utility .ini File Format.
SYSCFG Replication Rules
Not all BIOS and BMC options can be replicated using the .ini file. For example, boot sequence and device sequence are only
replicated if a device name list can be supplied. A numerical device list cannot be replicated since the index values can change
from system to system. In addition, because the service tag information is static, it is not commented out in the output file or
replicated. See the description of each option for further replication information.
The syscfg.ini file cannot be used across different systems. The file output operation places system identification information
at the beginning of the [syscfg] section. This information is used to determine if the file can be accepted as input for a
system. The following information is used for system identification:
● System ID Byte(s)
● System Name
● BIOS Version
If these values do not match the values found on the system, the file input operation fails.
The following is the SYSCFG behavior during replication:
● Options not available in SYSCFG are termed invalid options. If SYSCFG encounters an invalid option in the syscfg.ini file,
the SYSCFG utility terminates.
● Unsupported options are options available in SYSCFG but not applicable on certain systems. If SYSCFG encounters an
unsupported option, SYSCFG logs this option and continues to the next option.
● Unsupported arguments are arguments valid in SYSCFG but not applicable on certain systems. If SYSCFG encounters an
unsupported argument, SYSCFG terminates.
● SYSCFG logs a message in the log file for each option processed in the syscfg.ini file. To generate the log file, use the
logfile option.
RAID Replication
The RAID replication feature reads the RAID configuration information from the source system and creates a raid.ini file. This
raid.ini file can be applied to the RAID configurations of the target system. The RAID replication requires both, the source
system and the target system to have similar RAID controllers.
RACADM Replication
The RACREP.BAT sample script applies RAC configuration options to the target system based on the configuration information
that has been saved in a configuration file. User input is optional, depending on variables set in the RACREP.BAT sample
script. This script uses the RACADM.EXE utility to configure the RAC in the target system using the RAC configuration file,
raccfg.ini. The raccfg.ini configuration file is passed as the first parameter to the RACREP.BAT script. If this parameter is
not passed, the default variable values used in this script are set in the TKENVSET.BAT scripts. An optional second parameter
can be passed to this file, which specifies the IP address used in configuring the RAC. The raccfg.ini file is generated with the
RACCAP.BAT sample script.
Other Documents You May Need
In addition to this guide, you can access the following guides available at dell.com/support/manuals.
● The Dell OpenManage Deployment Toolkit Installation Guide provides information about installing and deploying DTK on
supported Dell systems. The guide is also available as part of the DTK download.
● The Dell OpenManage Deployment Toolkit User's Guide provides best practice procedures that focus on the basic tasks for
successful deployment of Dell systems.
● The Dell Systems Software Support Matrix provides information about the various Dell systems, the operating systems
supported by these systems, and the Dell OpenManage components that can be installed on these systems.
10
Introduction