Dell OpenManage Deployment Toolkit Version 5.2.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction........................................................................................................... 6 What is new in this release....................................................................................................................6 Other Documents You May Need.........................................................................................................7 Other supporting documents you may need............................................................
Sample deployment configuration files for Windows................................................................. 29 Sample deployment configuration files for Linux........................................................................30 Sample scripts for deployment on Windows system................................................................... 31 Sample scripts for deployment on Linux system......................................................................... 32 RPMs............................
6 Running the deployment scripts .................................................................... 55 Deployment using removable boot media with a network connection (media-based) for systems running windows.................................................................................................................. 55 Media-based local deployment for systems running microsoft windows ...................................... 56 Creating and customizing images for Windows PE 3.0.........................
Introduction 1 The Dell OpenManage Deployment Toolkit (DTK) includes a set of utilities, sample scripts, and sample configuration files that you can use to deploy and configure the Dell systems. You can use DTK to build script-based and RPM-based installation for deploying large number of systems on a pre-operating system environment in a reliable way, without changing their current deployment processes.
– Red Hat Enterprise Linux 6.7 (64-bit) • Added support for the following Dell PowerEdge servers: – R230 – R330 – T130 – T330 NOTE: For the list of supported operating systems and Dell servers, see the Dell Systems Software Support Matrix at dell.com/openmanagemanuals. NOTE: Use both DTK and the Server Administrator from the same release version to get complete supported features of Server Administrator.
• Operating system documentation to prepare for and execute the unattended installation process. In addition, you should consult the available web-based resources such as: – The Microsoft Tech Net database at microsoft.com/technet – The Red Hat Enterprise Linux support pages at redhat.com – The SUSE Linux Enterprise Server support pages at novell.com • Windows PE 3.0 - Windows Automated Installation Kit (Windows AIK), Windows PE 4.0, Windows PE 5.
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Go to Dell.com/support. 2. Select your support category. 3. Verify your country or region in the Choose a Country/Region drop-down list at the bottom of the page. 4. Select the appropriate service or support link based on your need.
Prerequisites and deployment 2 The Deployment ToolKit (DTK) is a collection of Windows PE and Linux-based utilities and scripts that assist in performing operating system tasks and deployment on Dell systems. An advanced knowledge of Windows PE and Linux is required for users who want to use the DTK utilities to perform pre-operating system and post-operating system configuration tasks or to run a scripted deployment in the respective environments.
• Microsoft Windows Server 2012 R2 Foundation, Essentials, Standard, and Datacenter editions • Dell’s Precision R7910 Supported operating systems – Microsoft Windows 7 (32-bit and 64-bit) – Windows 8.1 (64-bit) For Linux, the DTK utilities support deploying the following operating systems in BIOS and UEFI mode: • SUSE Linux Enterprise Server 12 (64-bit) • SUSE Linux Enterprise Server 11 SP4 (64-bit) • Red Hat Enterprise Linux 7.1 (64-bit) • Red Hat Enterprise Linux 7.
Deployment prerequisites Before beginning the deployment process for Windows PE, ensure that you have all of the following tools, software, and information ready to use or consult: • Windows Automated Installation Kit (AIK) for Windows Server 2008 R2, Windows Server 2008 and Microsoft Windows 7 (32-bit and 64-bit) to build Windows PE 3.0 ISO image. • Windows Assessment and Deployment Kit (ADK) for Windows Server 2012 to build Windows PE 4.0 ISO image.
• Dell Systems Management Tools and Documentation DVD. • Your operating system software and documentation. • An optimally configured source system with network access. NOTE: You can download the latest drivers from www.dell.com/support. Drivers The following table describes the essential and optional drivers required for Dell‑supported hardware to build your Windows PE environment. NOTE: The drivers provided have been tested successfully in the Windows PE environment. Table 1.
Additional Tools Purpose Source Windows ADK for Windows Server 2012 R2 and Windows 8.1 (64-bit) Create a bootable media for Windows PE 5.1. microsoft.com The following table is a matrix of Linux system files and other tools to use with DTK utilities and its sample scripts. Table 3. Supporting Tools and System Files for Linux Additional Tools Purpose Source Save in DTK location mkfs.* Formats hard-drive partitions. Any system running the Linux operating system. In the PATH variable.
Additional Tools Purpose Source Save in DTK location NOTE: For legacy operating systems, you may need to use the driver disk. At the end of the Red Hat Enterprise Linux Server installation, you may need to install the drivers available on the Systems Build and Update Utility. Deploying operating systems After the system hardware is versioned and configured, an operating system can be installed using unattended setup files, samples of which are provided as part of DTK.
DTK is flexible enough to fit into almost any deployment plan. DTK components can be used in many different ways to assist IT staff in deploying Dell systems in large numbers. Because all the tools and scripts are task-oriented, many of them can be used separately to perform a specific task on many systems or collectively to perform many tasks on many systems at once. For information on the deployment methods, see Running The Deployment Scripts.
Compute sled to PowerEdge FD332 setup Operating system installation support SYSCFG/RAIDCFG Description configuration support Compute sled with PERC + 1 Yes PowerEdge FD332 with a dual PERC mapped to the compute sled (split mode) + single boot VD Yes PERC controller with boot VD must be the first in the boot order list of the compute sled BIOS Compute sled without PERC + multiple PowerEdge FD332 with a dual PERC mapped to the compute sled (joint mode) + single boot VD Yes Yes PERC controller with bo
Compute sled to PowerEdge FD332 setup Operating system installation support SYSCFG/RAIDCFG Description configuration support No Yes sleds (split mode) + multiple boot VD Compute sled with PERC + PowerEdge FD332 (single/ multiple) with a single PERC mapped to the compute sled + multiple boot VD No scenario to install operating system with multiple boot VD Deployment matrix Depending on the scope, current business needs, network setup, and process, you can select any of the suggested methods of deploym
Deployment Methods Complexity Deployment solution framework from a third‑party vendor Mixed Advantages • Can install supported Windows or Linux operating systems. • DTK can be used in context of third-party deployment solution framework. Third-party deployment solution framework is used as the deployment transport mechanism. Tasks and scripts can be pushed to the target systems. Must either acquire and learn to use or have an existing third-party deployment solution framework.
NOTE: You can also download the latest drivers from www.dell.com/support. 4. Generate a system BIOS, BMC (Baseboard Management Controller), RAID, and/or RAC configuration profile from the optimally configured source system. Copy the generated configuration files to a read/write share onto the workstation. NOTE: You can obtain the system BIOS, BMC, RAID, and/or RAC configuration files from DTK Windows PE ISO image and running the SYSCAP.BAT, RAIDCAP.BAT, and RACCAP.
the deployment in the system directory for the target system. Copy all necessary files in the \Toolkit \Systems\ directory (Windows) or /opt/dell/toolkit/systems/
Downloading DTK 3 This section describes some of the procedures necessary to begin the deployment process, including: • Downloading and unzipping the Deployment Toolkit (DTK) components, including a comprehensive matrix of DTK components. • Setting up a directory structure to facilitate a successful deployment, including a list of the supporting components that are not included with DTK, but are needed to use DTK. • Setting up an optimally configured source system.
DTK utilities for 32-bit systems are located in the following directories: • Utilities: \Dell\x32\Toolkit\Tools • Sample scripts: \Dell\x32\Toolkit\Template\Scripts • Sample configuration files:\Dell\x32\Toolkit\Template\Configs DTK utilities for 64-bit systems are located in the following directories: • Utilities: \Dell\x64\Toolkit\Tools • Sample scripts: \Dell\x64\Toolkit\Template\Scripts • Sample configuration files: \Dell\x64\Toolkit\Template\Configs The directory \Dell\x32\Toolkit\Systems o
Directory structure on the target system The following table describes the contents of the directory structure on the target system. Table 7. Target System Directory Structure Contents Contents Details /lib The libraries and drivers required for embedded Linux to function. /bin Basic utilities (ls, chmod, and so on). /sbin Utilities that are required by the system superuser to perform administrative tasks. /opt The libraries, binaries, and scripts required for the toolkit to function.
Toolkit Components Purpose syscfg.exe • Reports and configures • • – BIOS settings and options – BMC settings and options – RAC 5 settings and options – IDRAC settings and options Maintains system state between reboots. Reports hardware devices and other system-related information. sysdrmk.exe Used by UPINIT.BAT to patch the boot sector and Master Boot Record (MBR). config.ini Configuration file used by raidcfg.exe. CAUTION: Do not edit this file. Incorrect edits might cause raidcfg.exe to fail.
Toolkit Components Purpose windows_scripts.lst Displays the list of input SYSCFG sample scripts available to be converted to RACADM scripts. For example in the prompt type dtktoracadm.exe windows_scripts.lst, converts the list of sample .BAT files present from the input file. racscripts The racscripts folder is empty before running the utility. Once the .exe script is run, the converted SYSCFG scripts to equivalent RACADM scripts are present in this folder. changed_tokens.
Toolkit Components Purpose sys.ini A .ini file used with syscfg. UpinitErrorCodes.txt Lists the error codes and messages for upinit.sh. Converter Has the sample utility using python script. Type in the terminal python dtktoracadm.py to convert the SYSCFG scripts to equivalent RACADM scripts. linux_scripts.lst Displays the list of input SYSCFG sample scripts available to be converted to RACADM scripts. For example in the prompt type python dtktoracadm.py linux_scripts.
Group SYSCFG Commands Equivalent RACADM Commands --BootSeqRetry BIOS.BiosBootSettings.BootSeqRetry --HddFailover BIOS.BiosBootSettings.HddFailover --SetBootOrderFqddn BIOS.BiosBootSettings.SetBootOrderFqddn -BIOS.BiosBootSettings.SetLegacyHddOrderFqdd SetLegacyHddOrderFqddn n Integrated Devices Memory Settings Miscellaneous Settings Processor Settings SATA Settings 28 --EmbVideo BIOS.IntegratedDevices.EmbVideo --IoatEngine BIOS.IntegratedDevices.IoatEngine --IntegratedNetwork1 BIOS.
Group SYSCFG Commands Equivalent RACADM Commands --SecurityFreezeLock BIOS.SataSettings.SecurityFreezeLock --ConTerrmType BIOS.SerialCommSettings.ConTermType --ExtSerialConnector BIOS.SerialCommSettings.ExtSerialConnector --FailSafeBaud BIOS.SerialCommSettings.FailSafeBaud --RedirAfterBoot BIOS.SerialCommSettings.RedirAfterBoot Slot Disablement --Slotn BIOS.SlotDisablement.Slotn System Information --svctag BIOS.SysInformation.SystemServiceTag System Security --AcPwrRcvryDelay BIOS.
Sample deployment configuration files for Linux The following table describes examples of Linux configuration files used to perform a scripted deployment. The Linux files are located at opt/dell/toolkit/template/configs. NOTE: All configuration files are provided as examples only. The sample configuration files must be edited before they can be used in any deployment tasks. Table 11. Sample Configuration Files for Linux Toolkit Components Purpose autoinst.
Sample scripts for deployment on Windows system The following table lists Windows sample scripts necessary to perform a scripted deployment. The sample scripts for Windows are located at Toolkit\Template\Scripts. NOTE: All DTK scripts are provided as examples only. The batch scripts and configuration files must be modified to reflect the unique information for each deployed system. Table 12. Sample Scripts For Deployment on Windows System Toolkit Components Purpose createup.
Toolkit Components Purpose SYSREP.BAT Applies (replicates) BIOS and BMC configuration settings and configures the target system. TKENVSET.BAT Sets the path of DTK installation and variables for the specific system being deployed. UPINIT.BAT Creates and populates the Dell utility partition. Sample scripts for deployment on Linux system The following table lists Linux sample scripts necessary to perform a scripted deployment. NOTE: All DTK scripts are provided as examples only.
RPMs The following table describes all DTK RPMs at mnt/cdrom/RPMs. The syscfg and raidcfg RPMs are also available in Dell Systems Management Tools and Documentation DVD. Table 14. RPMs RPMs Purpose syscfg Configures server BIOS, BMC/DRAC settings, DTK state settings, PCI device detection, and so on. raidcfg Configures all supported RAID controllers. racadm Configures RAC. NOTE: Besides the listed RPMs, a set of dependency RPMs are also available at this location.
Setting up a directory structure for deployment 4 To perform a Deployment ToolKit (DTK)-enabled deployment, you must create a deployment directory structure on either a network share or your local workstation hard drive. The deployment directory structure is a central repository for all deployment files that can be used for network deployment and to build a bootable deployment media. It can also be used successively as a testing space.
information. On systems running Linux, the /systems folder acts as a repository for the common files required for the systems. On systems running Windows, you can store all profile configuration files for an optimally configured Dell PowerEdge server in the directory Toolkit\Systems\. These files can then be accessed from this directory when deploying multiple similar PowerEdge servers.
Preparing the script files 5 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.
::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0 ::call WIN2K8.BAT Editing the sample batch files to perform a complete system deployment The sample scripts utilize DTK utilities, the additional supporting utilities, the source system configuration files, the target system hardware drivers, and the operating system installation files to perform a full deployment on the target system.
Table 17. Capture Scripts for Linux Script Name Description Associated Files raccap.sh Captures RAC settings to a file for DRAC 4. • tkenvset.sh — Used by raccap.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. racadm — Used by raccap.sh to retrieve RAC information and to configure settings. The wrapper script, racadm, invokes racadm4, racadm5, or racadm6 depending on the system configuration. syscfg— Used by raccap.sh to configure DRAC. • • raidcap.
Table 19. Replication Scripts for Linux Script Name Description Associated Files racrep.sh Applies the RAC configuration settings saved in a file to the current system. • tkenvset.sh — Used by racrep.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files. racadm — Used by racrep.sh to replicate the RAC information and to configure settings. The wrapper script, racadm invokes racadm4 , racadm5 , or racadm6 depending on the system configuration.
Deployment scripts for systems running Linux operating systems The following table lists the deployment scripts for systems running Linux. Table 21. Deployment Scripts For Linux Script Name Description Associated Files lininst.sh and lininst7.sh Performs an unattended installation of a supported Red Hat Enterprise Linux operating system in BIOS and UEFI mode. • • • • • • • • • suseinst.sh Performs an unattended installation of a supported SUSE Linux Enterprise Server operating system.
Script Name Description Associated Files • • • • • NOTE: Both grub and grub2 uses the following images in conjunction with the unattended answer file to perform unattended operations: – initial ramdisk — Available on the SUSE Linux Enterprise Server operating system media – kernel image — Available on the SUSE Linux Enterprise Server operating system media autoinst.xml — Used by suseinst.sh in conjunction with grub to install the operating system files. autoinst-sles11.xml — Used by suseinst.
Script Name Description Associated Files – UPINIT.BAT— Used by PARTCFG.BAT to create and populate the Dell utility partition. – FORMAT.EXE— Provided by Windows to format the partition. Other scripts for systems running Linux operating systems The following table lists the other scripts for Linux. Table 23. Other Scripts for Linux Script Name Description Associated Files tkenvset.sh Sets the path for DTK installation and variables for the system to be deployed and configured.
Script Name Description Associated Files • • • unzip — Used by upinit.sh to populate the Dell utility partition. mke2fs — Used to create a ext2 file system. upimg.bin — Contains the zipped contents of the Dell utility partition. Editing example of TKENVSET and tkenvset The majority of editing required for DTK sample scripts involves the TKENVSET.BAT (for Windows) or tkenvset.sh (for Linux) script. As a result, the scripting discussion focuses on this script.
4. Set the variable that defines the directory containing the configuration files for your Dell systems (DT_SYSTEMS). This variable is set to %DT_PATH%\Systems (Windows) or $dt_path/systems (Linux) by default in the sample script. Edit this path to add a subdirectory for the Dell system you plan to deploy. For example, $dt_path/systems/. 5. Set the variable that defines the directory containing DTK deployment scripts (DT_SCRIPTS). This variable is set to %DT_PATH%\Template\Scripts (Windows)
In raccap.sh: DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.ini To edit the RAC configuration variables, locate the following lines: In RACREP.BAT: :: RAC section set DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE=%DT_SYSTEMS%\%DT_PLATFORM%\raccfg.ini In racrep.sh: # RAC section DT_NICCFG=10.98.8.121 set DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.
# RAIDCFG section DT_VD_SIZE=10480 # default size for virtual disk CAUTION: DT_MOUNT specifies the mount point of the Dell utility partition. If your RAMDRIVE, hard drive, or other device already owns this designation, mount does not override the setting and the utility partition is not created. In partcfg.
• RAIDCFG.BAT or raidcfg.sh • SYSREP.BAT or sysrep.sh • PARTCFG.BAT or partcfg.sh RACREP.BAT or racrep.sh The RACREP.BAT or racrep.sh sample script applies RAC options to the target system based on configuration information that has been saved in the configuration file. User input is optional, depending on the variables set in the RACREP.BAT or racrep.sh sample script. On systems running Windows, RACREP.BAT script uses RACADM.EXE to configure RAC in the target system.
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. PARTCFG.BAT or partcfg.sh In BIOS mode, the PARTCFG.BAT or partcfg.sh sample script creates and populates the Dell utility partition using UPINIT.BAT or upinit.sh and creates the deployment partition on a specified disk. In UEFI mode, the partcfg.sh sample script creates the deployment partition on a specified disk. For more information about using the UPINIT.
On systems running Windows: call Z:\Dell\Toolkit\Template\Scripts\SYSCAP.BAT On systems running Linux: /opt/dell/toolkit/template/scripts /syscap.sh 2. Boot the source system into Windows PE or embedded Linux. The script runs and saves the configuration information in the \Toolkit\Systems\ directory in Windows and /opt/dell/toolkit/systems/ directory in Linux. 3. Edit the startnet.
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.
W2K8INST.BAT and W2K12INST.BAT The W2K8INST.BAT and W2K12INST.BAT sample scripts are used to perform an unattended installation of the Windows Server 2008 and Windows Server 2012 operating systems respectively. The variables and paths must be specified before the operating system can be installed.
NOTE: On systems running Windows Server 2012 operating system, save the default answer files as UNATTEND2K12.XML or UNATTEND2K12_UEFI.XML. NOTE: See your operating system documentation for instructions on modifying the options in the operating system unattended installation file to customize the scripted installation of your operating system. On systems running Windows Server 2008 or Windows Server 2012 operating system, save the completed file in the \Toolkit\os_deploy\ directory after you h
NOTE: The sample file provided to install Red Hat Enterprise Linux Server (version 5) in BIOS mode is named ks-rhel5.cfg. To use the sample ks-rhel5.cfg file to install Red Hat Enterprise Linux Server (version 5) using lininst.sh, ensure that you rename the file to ks.cfg. NOTE: The sample files provided to install Red Hat Enterprise Linux Server (version 6) are ksrhel6.cfg (in BIOS mode), and ks_rhel6_uefi.cfg (in UEFI mode). To use the sample ks-rhel6.
The suseinst.sh script uses the unattended answer file in conjunction with the grub utility and kernel image and initial ramdisk files to install the operating system files. autoinst.xml or autoinst_uefi.xml for SUSE Linux Enterprise server The autoinst.xml and autoinst_uefi.xml file is the default name of the answer file that you use to automate an unattended SUSE Linux Enterprise Server installation in BIOS and UEFI modes respectively. A sample copy of the autoinst.xml/autoinst_uefi.
Running the deployment scripts 6 This chapter provides best practices, procedures, and scenarios for using the Deployment Toolkit (DTK) to perform pre‑operating system configuration tasks and to install supported operating systems on supported Dell systems. After you have populated the deployment directory structure with all necessary files and carefully edited the deployment scripts and configurations files, you are ready to begin the final stage of the deployment process.
• The operating system is installed from a network share. This installation may happen after your system reboots. Media-based local deployment for systems running microsoft windows This deployment method is easy to assemble, but is the least flexible. Any change to the system configuration, for example, requires the creation of a new bootable media. This method does not provide a writable media, making it necessary to use predefined and tested configuration files.
NOTE: The destination folder (C:\winpe_51) is created as part of the process, and must not be an existing directory. The destination path and the path to the Dell drivers must not contain any blank space. Creating a bootable media for Windows PE 3.0 To create a bootable media: 1. Click Start and navigate to All Programs → Microsoft Windows AIK. 2. Click Windows PE Tools Command Prompt to open a command prompt window. 3. Navigate to C:\program files\Windows AIK\Tools\x32 or C:\program files\Windows AIK
This deployment method is easy to assemble and provides great flexibility in changing the scripts and configuration files. Any change to the system configuration, for example, does not require re‑creation of the bootable media. This method also provides access to the remote share as writable media. Hence, the configuration files captured during the deployment automation process can be saved to the remote share.
• Configuration information is read from the media. • The operating system is installed from the media. Network based deployment for systems running windows For Windows PE environments, deployment using Remote Installation Services (RIS) is recommended. For details, see the Microsoft RIS documentation. You can also use any other deployment tool such as Automated Deployment Services (ADS).
PXE-Based deployment The procedure enables you to boot DTK over network and pass parameters (startup script location and name) during boot using the Preboot eXecution Environment (PXE) configuration file. This automatically launches the start-up script off the network share, when DTK is booted. 1. Obtain the ISO image of the embedded Linux available at www.dell.com/support. 2.
Your ISO image is ready for booting. Media-based deployment The different media-based deployments are as follows: • Deployment Using Custom Scripts • Deployment Using RPMs • Deployment Using USB Deployment using custom scripts 1. Obtain the ISO image of the embedded Linux at www.dell.com/support. 2. Extract the contents of the ISO image to a folder (for example, isoimage) on your hard drive. 3. Copy the custom scripts into the same folder.
Installing DTK RPMs using YUM To install DTK RPMs using YUM: 1. Install YUM and the dependency RPMs. 2. Mount the DTK iso to /mnt/cdrom. 3. Create a repository file (for example, dtk.repo) for the required operating system in a writable location. The corresponding RPMs for the operating system are located at /mnt/cdrom/RPMs/, where OS can be the supported Linux operating system. For example, to deploy DTK RPMs on RHEL 6.x, you can use the following content in dtk.
4. Select the downloaded ISO image, and select the option to convert the image to a bootable USB format. Deployment using customized embedded Linux Make sure that you have the following basic libraries, Dell toolkit libraries, tools, and utilities required for DTK and integrate them to your embedded Linux deployment environment to proceed with the deployment: • Drivers for all hardware installed in the embedded Linux. These drivers are available at www.dell.com/ support.
7 Running Dell update packages on systems running embedded Linux You can run the Dell Update Packages in embedded Linux environments on supported Dell systems. The common scenarios for running update packages are: • Running Update Packages In Dell-Provided Embedded Linux • Running Update Packages In Customized Embedded Linux Running update packages in Dell-provided embedded Linux 1. Obtain the required update packages from the Dell Server Updates DVD or from www.dell.com/ support. 2.
Update Packages Dependency Dependencies Available On iDRAC Instrumentation drivers /mnt/cdrom/tools Dell PowerVault 220S SCSI drivers Kernel SAS SAS drivers Kernel Any Update Package RPMs Linux media or any open source website sysvinit grep sed awk less fmt tar.gz compat-libstdc proc-mail libxml2 After you have met all the dependencies, run the update packages in your customized embedded Linux environment. For more information, see Running Update Packages In Dell-Provided Embedded Linux.
Known issues and frequently asked questions 8 This section describes known issues with the Deployment Toolkit (DTK) utilities and scripts, including answers to some frequently asked questions. Known issues The following issues are organized by DTK utility or other function. General issues • Virtual disk creation and/or deletion takes a long time on Microsoft Windows PE.
Q: When I use the sample DTK scripts to deploy multiple systems, do I edit the configuration files to reflect unique information (such as unique system names, IP address, and BIOS asset tags) for each system? A: The sample scripts are provided as examples for users who want to develop their own deployment process. The scripts may work perfectly in your environment. If not, you may need to develop your own scripts entirely from scratch.
When dealing with SAS devices, the array disk location is displayed as channel:target:enclosure. It is possible to have the enclosure value as non-zero. If the enclosure has a non-zero value, then all three numbers (channel, target, and enclosure) have to be included on the command line. Q: Do I need to specify RAID type and size when creating virtual disks? A: No. The default RAID type is RAID 0. If RAID size is not provided, the maximum size allowed for virtual disk is created.
A: Ensure that the RAID controllers can be seen in the BIOS during POST. If the BIOS does not detect the controller, then RAIDCFG does not detect it. Also ensure that the controller is set to RAID mode and not any other mode in the controller BIOS. Q: What is span length? A: Span length enables you to select the number of array disks in a span for the nested RAID levels (RAID-10, RAID-50, and RAID-60). The default (minimum permissible) span length value is 2 for RAID-10, 3 for RAID-50, and 4 for RAID-60.
Q: In --solcfgparams, when I set the Serial Over LAN (SOL) character send threshold using solcharsendthreshold to be 225, I get a Hardware subsystem error. Invalid data field in request. What are the valid values? A: The range of valid values for --solcfgparams and --solcharsendthreshold are from 1 to 220. Q: How do I enable console redirection on a modular system? A: Set the --serialcomm option value to enableconred. For example, syscfg -serialcomm=enableconred.
2. Delete the entry: Run efibootmgr -b XYZ –B Windows PE questions Q: My system gets the error Illegal or Missing File Types Specified in Section Files.SCSI.Name during an unattended installation of a supported Windows operating system on supported Dell systems. A: This behavior can occur when the line in the Txtsetup.oem file under the [Files.SCSI. name] heading is not a supported file type. To resolve this behavior, you must remove the line in the Txtsetup.oem file.
