Dell OpenManage Deployment Toolkit Version 5.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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. © 2016 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 DTKTORACADM................................................................................................................................................................
Sample scripts for deployment on Linux system......................................................................................................... 31 RPMs............................................................................................................................................................................... 32 Documentation.................................................................................................................................................................
Creating and customizing images for Windows PE 4.0 and 5.1.................................................................................. 55 Integrating DTK directory structure .......................................................................................................................... 55 Creating a bootable media for Windows PE 3.0......................................................................................................... 55 Running the image....................................
1 Introduction 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.
DTKTORACADM The DTK SYSCFG deployment scripts are converted to equivalent RACADM scripts, that helps in migration to utilize RACADM in the deployment solution. The utility has the conversion tool for converting the SYSCFG scripts in both environments: Microsoft Windows and Linux operating systems. Starting 12th generation of PowerEdge servers and later, selected set of SYSCFG commands are a part of the DTK sample scripts. The list of DTK sample scripts are present in \Toolkit\Tools\CONVERTER \windows_script
Group SYSCFG Commands Equivalent RACADM Commands --gatewayv6 iDRAC.IPv6.Gateway --ipv6address1 iDRAC.IPv6.Address1 --ipv6address2 iDRAC.IPv6.Address2 --linklocaladdrv6 iDRAC.IPv6.LinkLocalAddress --prefixlengthv6 iDRAC.IPv6.PrefixLength --connectionmode iDRAC.IPMISerial.ConnectionMode --msgcommbitrate iDRAC.IPMISerial.BaudRat --msgcommflowctrl iDRAC.IPMISerial.FlowControl --tmcfghandshakectrl iDRAC.IPMISerial.HandshakeControl --tmcfglineediting iDRAC.IPMISerial.
Group SYSCFG Commands Equivalent RACADM Commands --ErrPrompt BIOS.MiscSettings.ErrPrompt --NumLock BIOS.MiscSettings.NumLock --ForceInt10 BIOS.MiscSettings.ForceInt10 --DcuIpPrefetcher BIOS.ProcSettings.DcuIpPrefetcher --DcuStreamerPrefetcher BIOS.ProcSettings.DcuStreamerPrefetcher --LogicalProc BIOS.ProcSettings.LogicalProc --ProcExecuteDisable BIOS.ProcSettings.ProcExecuteDisable --ProcHwPrefetcher BIOS.ProcSettings.ProcHwPrefetcher --ProcVirtualization BIOS.ProcSettings.
• The Dell Systems Software Support Matrix provides information about the various Dell systems and the operating systems supported by these systems. • The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy.
– Enterprise Systems Management – Remote Enterprise Systems Management – Serviceability Tools – Dell Client Command Suite – Connections Client Systems Management d. • To view a document, click the required product version. Using search engines: – Type the name and version of the document in the search box. Contacting Dell NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog.
2 Pre-requisites and deployment The Deployment Toolkit (DTK) is a collection of Windows PE and Linux-based utilities and scripts that help 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 preoperating system and postoperating system configuration tasks or to run a scripted deployment in the respective environments.
For Linux, the DTK utilities support deploying the following operating systems in BIOS and UEFI mode: • SUSE Linux Enterprise Server 12 SP1 (64-bit) • SUSE Linux Enterprise Server 11 SP4 (64–bit) • Red Hat Enterprise Linux 7.2 (64-bit) • Red Hat Enterprise Linux 6.8 (64-bit) • CentOS 7.0 (64-bit) • CentOS 7.2 (64-bit) NOTE: CentOS deployment is supported only on DSS1510, DSS1500, DSS2500 platforms.
• Windows Assessment and Deployment Kit (ADK) for Windows Server 2012 R2 and Windows 8.1 (64-bit) to build Windows PE 5.1 ISO image. • Windows Assessment and Deployment Kit (ADK) for Windows Server 2016 and Windows 10.0 (64-bit) to build Windows PE 10.0 ISO image. • Working knowledge to build Windows PE 3.0, Windows PE 4.0, Windows PE 5.1, and Windows PE 10.0 (see the Microsoft documentation to customize Windows PE).
Table 4. Drivers Required to Build Your Windows PE Environment Drivers Purpose common\hapi Essential files for DTK tools to work. common\raidcfg Essential files for raidcfg to work. winpe3.x\WINPE3.0_driverinst.bat Used to install Dell-provided drivers, from \Dell\x32\Drivers or \Dell\x64\Drivers, into the customized Windows PE 3.0 image. winpe4.x\WINPE4.0_driverinst.bat Used to install Dell-provided drivers, from \Dell\x64\Drivers, into the customized Windows PE 4.0 image. winpe5.x\WINPE5.
Additional Tools Purpose Source Save in DTK location parted To create GUID Partition Table (GPT) in UEFI mode. Any system running the Linux operating system. In the PATH variable. unzip To unzip files in Linux. Any system running the Linux operating system. In the PATH variable. upimg Contains system-specific Dell utility partition files. /opt/dell/toolkit/systems, or the Dell Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD.
Deployment DTK offers a complete set of utilities, sample scripts, and RPM packages that can be used to automate deployment on large numbers of Dell systems. This guide is designed to help you through some of the most basic planning considerations, logistical preparations, and deployment procedures to get you started using DTK to deploy Dell systems.
Compute sled to PowerEdge FD332 setup SYSCFG/RAIDCFG configuration support Description Compute sled with PERC + 1 PowerEdge Yes FD332 with a dual PERC mapped to the compute sled (joint 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 with PERC + 1 PowerEdge Yes 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
Deployment matrix Depending on the scope, current business needs, network setup, and process, you can select any of the suggested methods of deployment. Table 8. Deployment Method Matrix Deployment Methods Complexity Local deployment (bootable Relatively simple media) Advantages • • • Disadvantages Necessary if a network • connection is not available or is too slow. Can install supported • Windows operating systems. Can install to support for the Linux operating systems.
After you have determined which deployment method best suits the needs of your organization, you are ready to begin building the DTK deployment directory structure on a network volume. For instructions on installing the DTK components and populating the deployment directory structure, see Preparing The Script Files. DTK deployment overview The deployment process can be separated into two main tasks: preparation and the actual deployment. For more details, see Preparing For Deployment and Deploying.
• Operating system and hypervisor deployments • Hardware updates • Hardware diagnostics • Easy maintenance of PowerEdge servers iDRAC and Lifecycle Controller functionality can also be accessed through remote interface tools such as, iDRAC Web UI, RACADM Command Line interface, and Web Service Management (WS-MAN) interface. After you have installed the operating system and all applicable device drivers using Dell Lifecycle Controller, check www.dell.com/ support for the latest drivers.
3 Downloading DTK 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.
• Sample configuration files: \Dell\x64\Toolkit\Template\Configs The directory \Dell\x32\Toolkit\Systems or \Dell\x64\Toolkit\Systems is a placeholder that can be used for all system information that is captured using sample scripts and tools (for example, the system specific BIOS) and Baseboard Management Controller (BMC) configuration files used by the DTK utilities for configuring a system). For more information on the deployment directory structure, see Setting Up A Directory Structure For Deployment.
Contents Details /var Any run-time variable data that might be required for embedded Linux and tools to function. /tmp The only safe, writable area. However, all the data in this folder is lost every time you reboot. /usr Miscellaneous tools and libraries for embedded Linux to function.
Toolkit Components Purpose IDRAC7 Configures iDRAC7. NOTE: This feature may not be supported on all systems. RAC 4 Configures Dell Remote Access Controller (DRAC) 4/P and DRAC 4/I. RAC 5 Configures DRAC 5/iDRAC. pci.ids Reports PCI devices when used with syscfg.exe. disclaimer.txt Displays the disclaimer for the tools. RaidcfgErrorCodes.txt Lists the error codes and messages for the raidcfg.exe tool. SyscfgErrorCodes.txt Lists the error codes and messages for the syscfg.exe tool.
Toolkit Components Purpose NOTE: This feature may not be supported on all systems. racadm7 Configures iDRAC7. raidcfg Creates and reports RAID information. RaidcfgErrorCodes.txt Lists the error codes and messages for the raidcfg tool. stsvc.ini Configuration file used by raidcfg. syscfg • • • SyscfgErrorCodes.txt Lists the error codes and messages for the syscfg tool. sys.ini An .ini file used with syscfg. UpinitErrorCodes.txt Lists the error codes and messages for upinit.sh.
Table 13. SYSCFG equivalent RACADM commands Group SYSCFG Commands Equivalent RACADM Commands iDRAC Settings lcp --dnsdhcp iDRAC.IPv4.DNSFromDHCP lcp --domainname iDRAC.NIC.DNSDomainName lcp --dnsracname iDRAC.NIC.DNSRacName lcp --dnsregisterrac iDRAC.NIC.DNSRegister --idractype iDRAC.Info.Type -z legacy --autoneg iDRAC.NIC.Autoneg --gateway iDRAC.IPv4.Gateway --ipaddress iDRAC.IPv4.Address --macaddress iDRAC.NIC.MACAddres --nicselectionfailover iDRAC.NIC.
Group Integrated Devices Memory Settings Miscellaneous Settings Processor Settings SATA Settings Serial Communication 28 SYSCFG Commands Equivalent RACADM Commands --HddFailover BIOS.BiosBootSettings.HddFailover --SetBootOrderFqddn BIOS.BiosBootSettings.SetBootOrderFqddn --SetLegacyHddOrderFqddn BIOS.BiosBootSettings.SetLegacyHddOrderFqddn --EmbVideo BIOS.IntegratedDevices.EmbVideo --IoatEngine BIOS.IntegratedDevices.IoatEngine --IntegratedNetwork1 BIOS.IntegratedDevices.
Group SYSCFG Commands Equivalent RACADM Commands Slot Disablement --Slotn BIOS.SlotDisablement.Slotn System Information --svctag BIOS.SysInformation.SystemServiceTag System Security --AcPwrRcvryDelay BIOS.SysSecurity.AcPwrRcvryDelay --PwrButton BIOS.SysSecurity.PwrButton --SetupPassword BIOS.SysSecurity.SetupPassword --SysPassword BIOS.SysSecurity.SysPassword --maxpowercap System.Power.Cap.MaxThreshold --minpowercap System.Power.Cap.MinThreshold --capenable System.Power.Cap.
Table 15. Sample Configuration Files for Linux Toolkit Components Purpose autoinst.xml Sample file used during an unattended installation of SUSE Linux Enterprise Server operating systems in BIOS mode. autoinst-sles12.xml Sample file used with unattended installation of SUSE Linux Enterprise Server (version 12) operating system in BIOS mode. autoinst_sles12_uefi.xm Sample file used with unattended installation of SUSE Linux Enterprise Server (version 12) operating system in UEFI mode.
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 16. Sample Scripts For Deployment on Windows System Toolkit Components Purpose createup.cfg This file is used by UPINIT.BAT. diskpartclr.cfg Used by PARTCFG.BAT to clear the partitions on the selected disks. diskpartos.cfg Used by PARTCFG.BAT to create deployment partition to install the operating system. LISTUP.
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 17. Sample Scripts For Deployment on Linux system Toolkit Components Purpose errhndl.sh Handles errors returned in DTK scripts. lininst.sh Performs an unattended installation of a supported Red Hat Enterprise Linux Server (version 5 and 6) operating system. lininst7.
Documentation The following table describes documents containing reference information for each DTK utility and instructions for using DTK utilities and sample scripts. On systems running the Windows operating system, documentation can be found at \Dell\Docs. On systems running the Linux operating system, documentation can be found at mnt/cdrom/docs. Table 19.
4 DTK Seamless package The DTK Seamless package is a single installer package that carries Linux DTK RPMs (RHEL, SLES) and its dependency. Seamless package — Downloading and Installing This section describes the downloading and installing of DTK seamless package. The seamless package auto recognizes the OS type and its respective dependency during the installation and installs SYSCFG, RAIDCFG, and RACADM tools on post Linux operating system.
Non-interactive mode: In the non-interactive mode, all the available tools are installed by default. Any other option is ignored. Type the following command: ./DTKTOOLS__Linux64_.Bin [—f/--force] Once the DTK tools installation is complete, success message is displayed on the screen. To uninstall the DTK tools, run the command ./DTKTOOLS__Linux64_.Bin [-d/--delete] To view the available options, run the following command in the command line: .
5 Setting up a directory structure for deployment 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.
Operating system installation files For more details on installing Windows Server and Linux operating system using DTK, see the Dell OpenManage Deployment Toolkit Installation Guide available at dell.com/openmanagemanuals.
6 Preparing the script files 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.
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. The sample scripts provided with DTK can be edited and customized using any ASCII text editor that conforms to the hardware available on the target systems.
Script Name raidcap.sh Description Captures the RAID settings and saves them to a file. Associated Files • syscfg— Used by raccap.sh to configure DRAC. • tkenvset.sh — Used by raidcap.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. raidcfg — Used by raidcap.sh to retrieve RAID information and to configure settings. • syscap.sh Captures BIOS, DRAC, and BMC configuration settings and saves them to a file. • tkenvset.sh — Used by syscap.
Table 24. Deployment Scripts For Windows Script Name Description Associated Files W2K8INST.BAT Performs an unattended installation of • supported Windows Server 2008 operating systems. • • • W2K12INST.BAT Performs an unattended installation of • supported Windows Server 2012 operating systems. • NOTE: From Windows Server 2012 onwards, Server Core is • the default deployment configuration setting. However, • you can modify the xml files to change the setting. TKENVSET.BAT — Used by W2K8INST.
Script Name suseinst.sh Description Performs an unattended installation of a supported SUSE Linux Enterprise Server operating system. Associated Files • ks_rhel7_uefi.cfg — Used by lininst.sh with grub2 to install the Red Hat Enterprise Linux Server (versions 7) operating system files in UEFI mode. • tkenvset.sh — Used by suseinst.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.
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 27. 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.
and scripts and sets the variables for the system to be deployed and configured. The variables and paths specified in this file before other supporting scripts are used. Specifying DTK installation paths The TKENVSET.BAT or tkenvset.sh sample script is provided with the following default values. These values must be confirmed in some cases, and modified in other cases, before a deployment.
In SYSCAP.BAT on systems running Windows: set DT_SYS_CAPFILE=%DT_SYSTEMS%\%DT_PLATFORM%\syscfg.ini In syscap.sh on systems running Linux: set DT_SYS_CAPFILE=$dt_systems/$dt_platform/syscfg.ini To edit the SYSCFG replication variables, locate the following lines: In SYSREP.BAT on systems running Windows: set DT_SYS_REPFILE=%DT_SYSTEMS%\%DT_PLATFORM%\syscfg.ini In syscap.sh on systems running Linux: DT_SYS_REPFILE=$dt_systems/$dt_platform/syscfg.
set DT_HD=0 :: PARTCFG section set DT_OS_SIZE=4000 set DT_OS_FSTYPE=FAT32 if not "%DT_PARTN_UP%"=="ON" goto ospart :: DELLUP section set DT_UP_SIZE=32 set DT_UP_IMAGE=%DT_SYSTEMS%\UPIMG.BIN :: RAIDCFG section:: default size for virtual disk set DT_VD_SIZE=10480 :: default size for virtual disk In partcfg.sh in BIOS mode: DT_PARTN_UP=on # Default Hard Drive DT_HD=/dev/sda # deployment section set DT_DP_SIZE=64 # DELL UP section set DT_UP_SIZE=32 set DT_UP_IMAGE=$dt_systems/upimg.
6. If the DT_PARTN_UP variable is set to ON, edit the default variable value for the utility partition installation package location (DT_UP_IMAGE=%DT_SYSTEMS%\UPIMG.BIN for Windows and DT_UP_IMAGE=$dt_systems/upimg.bin for Linux), if applicable. NOTE: Edit the UPIMG_BIN variable only if you have changed the name or path of the utility partition installation package.
settings, see SYSCAP.BAT Or syscap.sh. The second parameter is a name or path to a log file. This parameter is not set to any value by default, and no log file is generated. NOTE: If the replication requires a change in the memory redundancy mode, reboot the target server and run the script again to complete the replication. NOTE: The racrep.sh and sysrep.sh have duplicate functions. If you run racrep.sh after the command sysrep.sh, the latter overwrites the former settings. PARTCFG.BAT or partcfg.
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.cmd file (Windows PE image) or start-up script file (embedded Linux image) to remove the text you added in step 1. 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.
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.
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 file (in UEFI mode) with SETUP.
• DT_HD — Sets the required disk to be configured for partition. External dependencies of lininst.sh The DT_PLATFORM variable is set during deployment by tkenvset.sh using platform discovery. The lininst.sh script uses the unattended answer file with the grub utility and kernel image and initial ramdisk files to install the operating system files. For more information about preparing the unattended answer file, see Answer Files.
suseinst The suseinst.sh sample script is used to perform an unattended installation of a supported SUSE Linux Enterprise Server operating system. The variables and paths must be specified before the operating system can be installed.
7 Running the deployment scripts 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.
• Creating And Customizing Images For Windows PE 3.0 • Creating and Customizing Images For WinPE 4.0 and 5.1 • Integrating The DTK Directory Structure • Creating A Bootable Media For WIN PE 3.0 • Running The Image Creating and customizing images for Windows PE 3.0 If you are using Windows PE 3.0, download Windows Automated Installation Kit (Windows AIK) from microsoft.com. By default, Windows AIK is copied to the C:\Program Files\Windows AIK directory.
NOTE: The destination folder (C:\winpe_30) 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. 5. NOTE: The execution script contains the following step, you can skip running the command. Run the following command: oscdimg -n -bc:\winpe_30\etfsboot.com c:\winpe_30\ISO c: \winpe_30\WinPE3.0.iso WinPE3.0 iso, a media bootable ISO image is created.
1. Boot the target system with the bootable deployment media. 2. Execute the master batch file, which calls individual task scripts and utilities from the network share to complete the deployment process. Deployment using removable boot media without a network (mediabased) connection for systems running windows For media-based deployment without a network connection: 1. Create a deployment media containing a bootable image with the appropriate drivers.
• PXE-Based Deployment • Network File System or SMBFS File System Based Deployment 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.
• 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. NOTE: Your scripts must also take care of copying miscellaneous items to unlock the media, so that the media can be mounted and ejected as per the operating system’s installation process. 4. In /mnt/cdrom/isolinux/isolinux.
NOTE: For both installations, the raidcfg and syscfg binaries and libraries are installed at /opt/dell/toolkit/bin. The racadm binaries are installed at /opt/dell/srvadmin/bin and /opt/dell/srvadmin/sbin. Installing DTK RPMs using DTK tools To install DTK RPMs using DTK tools: 1. Mount the DTK media at /mnt/cdrom. 2. Navigate to the /mnt/cdrom/SYSMGMT/dtktools/ directory. NOTE: The /mnt/cdrom/SYSMGMT/dtktools directory contains all DTK RPMs and the dependency RPMs. 3.
Using a third-party deployment solution framework for systems running Linux You can use DTK with any existing third-party deployment solution framework that provides a PXE booting infrastructure that can be used as transport mechanism for the DTK utilities. Because each third-party deployment framework is unique, these solutions are beyond the scope of this document.
8 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 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.
9 Known issues and frequently asked questions 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.
A: A hot spare is an extra and unused disk drive that is part of an array disk subsystem. A hot spare is always in standby mode. If a disk failure occurs, the hot spare replaces the failed drive without interrupting the system. Q: What is mr2kserv.exe? A: The mr2kserv.exe is a service needed to configure all LSI RAID controllers in Windows PE. It provides Plug and Play support.
Q: What is the minimum configuration needed to support BMC Platform Event Filtering? A: You must enable LAN-channel access pefalerting and ensure that you set the BMC IP address and Gateway values for alerting. Q: I installed the factory defaults for the BMC of my system. Then, I enabled BMC user ID 3. What is the username for this user ID? A: The default username for user IDs 3 to 10 is NULL. Q: Can I use this NULL username to remotely log in to a BMC of a system? A: No.
A: On a Dell server running in UEFI mode, DTK supports only 64–bit ELI. Q:How to delete the Unavailable: RHEL_DTK_UEFI and Unavailable: SLES_DTK_UEFI entries displayed on the F11 UEFI boot manager? A: Do the following to delete the entries: 1. Identify the boot entry number (for example, BootXYZ) of the entry to be deleted: Run efibootmgr from the command line. 2.
