Contents

Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide PDF

1 of 72
1 of 72

Summary of Content for Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide PDF

Dell EMC OpenManage Deployment Toolkit Version 6.2 User's Guide

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.

2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

2018 - 12

Rev. A01

Contents

1 Introduction....................................................................................................................................................6 DTK Deprecation Message............................................................................................................................................... 6 What is new in this release................................................................................................................................................6 DTKTORACADM................................................................................................................................................................ 7 Other Documents You May Need...................................................................................................................................12 Other supporting documents you may need.................................................................................................................12 Accessing documents from the Dell EMC support site............................................................................................... 13 Contacting Dell..................................................................................................................................................................13

2 Pre-requisites and deployment..................................................................................................................... 14 Supported systems...........................................................................................................................................................14 Supported operating systems......................................................................................................................................... 14 Supported BIOS Firmware versions............................................................................................................................... 15 Prerequisites and requirements.......................................................................................................................................15

Installation prerequisites.............................................................................................................................................15 Deployment prerequisites.......................................................................................................................................... 15 Drivers.......................................................................................................................................................................... 16 Other supporting tools and system files.................................................................................................................. 17

Deploying operating systems...........................................................................................................................................18 Deployment....................................................................................................................................................................... 18 Deployment matrix........................................................................................................................................................... 19 DTK deployment overview..............................................................................................................................................20

Preparing for deployment......................................................................................................................................... 20 Deployment.................................................................................................................................................................20

Configuring a source system ......................................................................................................................................... 20 RAC and BIOS configuration..................................................................................................................................... 21 How to obtain Dell utility partition files.................................................................................................................... 21

3 Downloading DTK........................................................................................................................................ 22 Extracting DTK components on systems running windows....................................................................................... 22

DTK components on systems running windows.................................................................................................... 22 Extracting DTK components on systems running Linux............................................................................................. 23

DTK components on the mounted media............................................................................................................... 23 Directory structure on the target system............................................................................................................... 23

DTK contents....................................................................................................................................................................24 System utilities and supported files for windows...................................................................................................24 System utilities and supported files For Linux........................................................................................................ 25 SYSCFG equivalent RACADM commands..............................................................................................................27

Sample scripts for deployment....................................................................................................................................... 31 Sample deployment configuration files for Windows............................................................................................. 31 Sample deployment configuration files for Linux.................................................................................................... 31 Sample scripts for deployment on Windows system.............................................................................................32

Contents 3

Sample scripts for deployment on Linux system....................................................................................................33 RPMs.................................................................................................................................................................................34 Documentation.................................................................................................................................................................34 Drivers and Dell real mode kernel ..................................................................................................................................35

4 DTK Seamless package................................................................................................................................36 Seamless package Downloading and Installing.......................................................................................................36

5 Setting up a directory structure for deployment.......................................................................................... 38 DTK utilities and files....................................................................................................................................................... 38 System-specific files........................................................................................................................................................38 Operating system installation files..................................................................................................................................39

6 Preparing the script files .............................................................................................................................40 Using the sample DTK scripts to run a full deployment.............................................................................................. 40 Editing the sample batch files to perform a complete system deployment.............................................................. 41

Scripts for deployment on systems running windows........................................................................................... 41 Scripts for deployment on systems running Linux..................................................................................................41 Replication scripts for deployment on systems running windows operating system........................................ 42 Replication scripts for deployment on systems running Linux operating system...............................................42 Deployment scripts for systems running windows operating systems................................................................43 Deployment scripts for systems running Linux operating systems .....................................................................43 Other scripts for systems running Windows operating systems......................................................................... 44 Other scripts for systems running Linux operating systems................................................................................ 45

Editing example of TKENVSET and tkenvset ............................................................................................................. 46 Specifying DTK installation paths.............................................................................................................................46 Confirming or editing DTK installation path variables............................................................................................46

Editing DTK task scripts..................................................................................................................................................49 RACREP.BAT or racrep.sh........................................................................................................................................ 49 RAIDCFG.BAT or raidcfg.sh......................................................................................................................................50 SYSREP.BAT or sysrep.sh.........................................................................................................................................50 PARTCFG.BAT or partcfg.sh....................................................................................................................................50

Using DTK sample scripts to capture configuration information............................................................................... 50 Capturing the system BIOS and BMC configuration with the SYSCAP or syscap.sh sample script............... 51 Capturing the RAC configuration with the RACCAP or raccap.sh sample script...............................................51 UPINIT.BAT or upinit.sh.............................................................................................................................................52

Preparing the operating system installation scripts.....................................................................................................53 W2K12INST.BAT and W2K16INST.BAT................................................................................................................... 53 UNATTEND.XML aND UNATTEND_UEFI.XML.....................................................................................................54 Linux scripts................................................................................................................................................................54 suseinst....................................................................................................................................................................... 56

7 Running the deployment scripts ..................................................................................................................58 Deployment using removable boot media with a network connection media-based for systems running windows............................................................................................................................................................................ 58 Media-based local deployment for systems running Microsoft Windows ............................................................... 59

4 Contents

Creating and customizing images for Windows PE 5.1......................................................................................... 59 Integrating DTK directory structure ........................................................................................................................59 Creating a bootable media for Windows PE 5.1..................................................................................................... 59 Running the image.....................................................................................................................................................60

Media-Based local deployment with Networking enabled for systems running windows......................................60 Bootable Windows PE media with Networking enabled.......................................................................................60 Preparing and populating the network share.......................................................................................................... 61

Deployment using removable boot media without a network media-based connection for systems running windows.............................................................................................................................................................................61 Network based deployment for systems running windows........................................................................................ 61 Using a third-party deployment solution framework for systems running windows................................................61 Using Windows Pre-installation Environment driver CAB files for systems running Windows.............................. 62 Deployment using Dell provided embedded Linux....................................................................................................... 62

Network-based deployment..................................................................................................................................... 62 Media-based deployment......................................................................................................................................... 63

Deployment using customized embedded Linux..........................................................................................................65 Using a third-party deployment solution framework for systems running Linux..................................................... 65

8 Running Dell update packages on systems running embedded Linux............................................................66 Running update packages in Dell-provided embedded Linux.....................................................................................66 Running update packages in customized embedded Linux........................................................................................66

9 Known issues and frequently asked questions..............................................................................................68 Known issues....................................................................................................................................................................68

General issues.............................................................................................................................................................68 RAIDCFG issues......................................................................................................................................................... 68 SYSCFG issues...........................................................................................................................................................68 Windows PE installation issues................................................................................................................................ 68 Embedded Linux installation issues..........................................................................................................................68

Frequently asked questions............................................................................................................................................ 69 General deployment questions.................................................................................................................................69 RAIDCFG questions...................................................................................................................................................69 SYSCFG questions.....................................................................................................................................................70 Embedded Linux questions........................................................................................................................................71 Windows PE questions..............................................................................................................................................72

Contents 5

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. Using DTK you can install operating systems on Dell systems in BIOS or Unified Extensible Firmware Interface (UEFI) mode.

In addition to the command line utilities used to configure various system features, DTK also provides sample scripts and configuration files to perform common deployment tasks and documentation. These files and scripts describe the use of the DTK in Microsoft Windows Pre- installation Environment (Windows PE) and Linux environments.

Topics:

DTK Deprecation Message

What is new in this release

DTKTORACADM

Other Documents You May Need

Other supporting documents you may need

Accessing documents from the Dell EMC support site

Contacting Dell

DTK Deprecation Message The OpenManage Deployment Toolkit (DTK) along with the associated tools and capabilities will be deprecated for version 6.1 and later:

Redundant Array of Independent Disks Configuration (RAIDCFG) Utility

System Configuration (SYSCFG) Utility

ELI tool

Utility Partition (UPINIT)

It is recommended to use the RACADM Command Line (CLI) as a replacement for the RAIDCFG and SYSCFG utilities. For more information on downloading RACADM, see www.dell.com/Support/Home.

NOTE: DTK will continue to support any new hardware or operating system for the 14th generation of PowerEdge servers. However, support for later generations of PowerEdge servers will be deprecated. For more information about features supported by DTK, see the latest User's Guide available at www.dell.com/OpenManageManuals .

What is new in this release The new features for this release include:

Added support for the following operating systems:

Red Hat Enterprise Linux 7.5 (64-bit)

Red Hat Enterprise Linux 6.10 (64-bit)

SUSE Linux Enterprise Server 15 (64-bit)

Added support for below Network Cards:

QLogic 10GE 4P QL41164HxRJ-DE Adapter

1

6 Introduction

QLogic 10GE 4P QL41164HxRJ-DE Adapter

QL41262HMKR-DE 25 Gigabit Ethernet

QLogic FastLinQ 41262 Dual Port 25GbE SFP28 rNDC

QLogic 2x25GE QL41262HMCU CAN

Intel(R) Ethernet 25G 2P XXV710 Adapter

Intel(R) Ethernet 10G 2P X550-t Adapter

Intel(R) Gigabit 4P I350-t Adapter

Intel(R) 10GbE 4P X710-t Adapter

Intel(R) 4P X550 rNDC

ConnectX-5 Dual Port 100 GbE QSFP Network Adapter

ConnectX-4 Dual Port 100 GbE QSFP Network Adapter

ConnectX-5 Single Port VPI EDR QSFP28 Adapter

Added support for the following Dell PowerEdge servers:

PowerEdge R240

PowerEdge R340

PowerEdge T140

PowerEdge T340

PowerEdge R740xd2

Support Matrix for the controller card:

Table 1. Support Matrix for the controller

Controller type OSD Support with PowerEdge MX740c and PowerEdge MX840c

OSD support with MX5016s

Virtual Disk, Physical Disk support with Compute Backplanes

Virtual Disk, Physical Disk support using Mx5016s HDDs

H745P MX Yes No Yes Yes

H730P MX Yes NA Yes NA

HBA330 MX No NA PD = YES ; VD = NO NA

HBA330MMZ No No PD = YES ; VD = NO PD = YES ; VD = NO

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.

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_scripts.lst for Microsoft Windows operating systems and toolkit/Converter/ linux_scripts.lst for Linux operating system. The converted scripts are available in the folder racscripts.

Introduction 7

Table 2. DTKTORACADM Command on Windows Operating System

Valid Arguments dtktoracadm.exe or dtktoracadm.exe windows_scripts.lst debug Description On systems running Windows operating system, run the command, where windows_scripts.lst is the

input file which contains the list of path to run the RACADM scripts and debug is an option which list the file status.

Applicable Systems All PowerEdge 12 and later systems.

Table 3. DTKTORACADM Command on Linux Operating System

Valid Arguments python dtktoracadm.py or python dtktoracadm.py linux_scripts.lst debug Description On the system running Linux operating system, in the prompt type the command, where

linux_scripts.lst is the input which contains the list of path to run the RACADM scripts and debug is an option which list the file status.

Applicable Systems All PowerEdge 12 and later systems.

The set of converted commands are available in dtktoracadm_dict.map. For more information see, Dell EMC OpenManage Deployment Toolkit User's Guide or Dell EMC OpenManage Deployment Toolkit Installation Guide. The following table lists the set of commands available:

Table 4. 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.Failover

--subnetmask iDRAC.IPv4.Netmask

--vlanid iDRAC.NIC.VLanID

--dnsserver1v6 get iDRAC.IPv6.DNS1

--dnsserver2v6 get iDRAC.IPv6.DNS2

--gatewayv6 iDRAC.IPv6.Gateway

--ipv6address1 iDRAC.IPv6.Address1

--ipv6address2 iDRAC.IPv6.Address2

--linklocaladdrv6 iDRAC.IPv6.LinkLocalAddress

--prefixlengthv6 iDRAC.IPv6.PrefixLength

8 Introduction

Group SYSCFG Commands Equivalent RACADM Commands

--connectionmode iDRAC.IPMISerial.ConnectionMode

--msgcommbitrate iDRAC.IPMISerial.BaudRat

--msgcommflowctrl iDRAC.IPMISerial.FlowControl

--tmcfghandshakectrl iDRAC.IPMISerial.HandshakeControl

--tmcfglineediting iDRAC.IPMISerial.LineEdit

--tmcfgnewlineseq iDRAC.IPMISerial.NewLineSeq

--solcharaccuminterval iDRAC.IPMISOL.AccumulateInterval

--solbitrate iDRAC.IPMISOL.BaudRate

--solprivlevel iDRAC.IPMISOL.MinPrivilege

--solcharsendthreshold iDRAC.IPMISOL.SendThreshold

BIOS Option Settings --HddSeq BIOS.BiosBootSettings.HddSeq

Boot Settings --BootMode BIOS.BiosBootSettings.BootMode

--BootSeqRetry BIOS.BiosBootSettings.BootSeqRetry

--HddFailover BIOS.BiosBootSettings.HddFailover

--SetBootOrderFqddn BIOS.BiosBootSettings.SetBootOrderFqddn

--SetLegacyHddOrderFqddn BIOS.BiosBootSettings.SetLegacyHddOrderFqddn

Integrated Devices --EmbVideo BIOS.IntegratedDevices.EmbVideo

--IoatEngine BIOS.IntegratedDevices.IoatEngine

--IntegratedNetwork1 BIOS.IntegratedDevices.IntegratedNetwork1

--IntegratedNetwork2 BIOS.IntegratedDevices.IntegratedNetwork2

--IntegratedRaid BIOS.IntegratedDevices.IntegratedRaid

--InternalUsb BIOS.IntegratedDevices.InternalUsb

--OsWatchdogTimer BIOS.IntegratedDevices.OsWatchdogTimer

--SriovGlobalEnable BIOS.IntegratedDevices.SriovGlobalEnable

--Usb3Setting BIOS.IntegratedDevices.Usb3Setting

Memory Settings --DynamicCoreAllocation BIOS.ProcSettings.DynamicCoreAllocation

--CorrEccSmi BIOS.MemSettings.CorrEccSmi

--MemTest BIOS.MemSettings.MemTest

--NodeInterleave BIOS.MemSettings.NodeInterleave

--memopmode BIOS.memsettings.MemOpMode

--videomem BIOS.memsettings.VideoMem

--sysmemvolt BIOS.MemSettings.SysMemVolt

--sysmemtype BIOS.MemSettings.SysMemType

--sysmemspeed BIOS.MemSettings.SysMemSpeed

--sysmemsize BIOS.memsettings.SysMemSize

Introduction 9

Group SYSCFG Commands Equivalent RACADM Commands

--memoperatingmode BIOS.memsettings.MemOpMode

Miscellaneous Settings --AssetTag BIOS.MiscSettings.AssetTag

--ErrPrompt BIOS.MiscSettings.ErrPrompt

--NumLock BIOS.MiscSettings.NumLock

--ForceInt10 BIOS.MiscSettings.ForceInt10

--insystemcharacterization BIOS.MiscSettings.InSystemCharacterization

Processor Settings --DcuIpPrefetcher BIOS.ProcSettings.DcuIpPrefetcher

--DcuStreamerPrefetcher BIOS.ProcSettings.DcuStreamerPrefetcher

--LogicalProc BIOS.ProcSettings.LogicalProc

--ProcExecuteDisable BIOS.ProcSettings.ProcExecuteDisable

--ProcHwPrefetcher BIOS.ProcSettings.ProcHwPrefetcher

--ProcVirtualization BIOS.ProcSettings.ProcVirtualization

--RtidSetting BIOS.ProcSettings.RtidSetting

--ProcX2Apic BIOS.ProcSettings.ProcX2Apic

--cpucore BIOS.ProcSettings.ProcCores

--cpuspeed BIOS.ProcSettings.ProcCoreSpeed

--logicproc BIOS.procsettings.LogicalProc

--proc1brand BIOS.procsettings.Proc1Brand

--proc1id BIOS.procsettings.Proc1Id

--proc1l2cache BIOS.procsettings.Proc1L2Cache

--proc1l3cache BIOS.procsettings.Proc1L3Cache

--proc1numcores BIOS.procsettings.Proc1NumCores

--proc2brand BIOS.procsettings.Proc2Brand

--proc2id BIOS.procsettings.Proc2Id

--proc2l2cache BIOS.procsettings.Proc2L2Cache

--proc2l3cache BIOS.procsettings.Proc2L3Cache

--proc2numcores BIOS.procsettings.Proc2NumCores

--proc64bit BIOS.procsettings.Proc64bit

--procadjcacheline BIOS.procsettings.ProcAdjCacheLine

--procbusspeed BIOS.procsettings.ProcBusSpeed

--proccorespeed BIOS.procsettings.ProcCoreSpeed

--qpispeed BIOS.procsettings.QpiSpeed

--procconfigtdp BIOS.procsettings.ProcConfigTdp

SATA Settings --WriteCache BIOS.SataSettings.WriteCache

--SecurityFreezeLock BIOS.SataSettings.SecurityFreezeLock

--embsata BIOS.SataSettings.EmbSata

10 Introduction

Group SYSCFG Commands Equivalent RACADM Commands

--sata0 BIOS.SataSettings.SataPortA

--sata1 BIOS.SataSettings.SataPortB

--sata2 BIOS.SataSettings.SataPortC

--sata3 BIOS.SataSettings.SataPortD

--sata4 BIOS.SataSettings.SataPortE

--sata5 BIOS.SataSettings.SataPortF

--sata7 BIOS.SataSettings.SataPortH

--sataporta BIOS.SataSettings.SataPortA

--sataportb BIOS.SataSettings.SataPortB

--sataportc BIOS.SataSettings.SataPortC

--sataportd BIOS.SataSettings.SataPortD

--sataporte BIOS.SataSettings.SataPortE

--sataportf BIOS.SataSettings.SataPortF

--sataportg BIOS.SataSettings.SataPortG

--sataportgmodel BIOS.SataSettings.SataPortGModel

--sataportgdrivetype BIOS.SataSettings.SataPortGDriveType

--sataportgcapacity BIOS.SataSettings.SataPortGCapacity

--sataporth BIOS.SataSettings.SataPortH

--sataporthmodel BIOS.SataSettings.SataPortHModel

--sataporthdrivetype BIOS.SataSettings.SataPortHDriveType

--sataporthcapacity BIOS.SataSettings.SataPortHCapacity

--sataporti BIOS.SataSettings.SataPortI

--sataportimodel BIOS.SataSettings.SataPortIModel

--sataportidrivetype BIOS.SataSettings.SataPortIDriveType

--sataporticapacity BIOS.SataSettings.SataPortICapacity

--sataportj BIOS.SataSettings.SataPortJ

--sataportjmodel BIOS.SataSettings.SataPortJModel

--sataportjdrivetyp BIOS.SataSettings.SataPortJDriveType

--sataportjcapacity BIOS.SataSettings.SataPortJCapacity

Serial Communication --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.SysSecurity.AcPwrRcvryDelay

Introduction 11

Group SYSCFG Commands Equivalent RACADM Commands

--PwrButton BIOS.SysSecurity.PwrButton

--SetupPassword BIOS.SysSecurity.SetupPassword

--SysPassword BIOS.SysSecurity.SysPassword

System Power --maxpowercap System.Power.Cap.MaxThreshold

--minpowercap System.Power.Cap.MinThreshold

--capenable System.Power.Cap.Enable

--nmibutton BIOS.SysSecurity.NmiButton

--powerbutton BIOS.SysSecurity.PwrButton

Other Documents You May Need In addition to this guide, you can access the following guides available at dell.com/openmanage/manuals. See Accessing Documents From The Dell Support Site.

The Dell OpenManage Deployment Toolkit Installation Guide provides information about installing, deploying, and upgrading the DTK on supported Dell systems. The guide is also available as part of the DTK download.

The Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide provides information about configuring the BIOS, Baseboard Management Controller (BMC), Remote Access Controller (RAC), RAID controllers, and hard-drive partitions on supported Dell systems.

TheDell OpenManage Installation Guides provides additional information about performing an unattended installation of Server Administrator on systems running supported Windows, Red Hat Enterprise Linux Server, SUSE Linux Enterprise Server, and Citrix Xen Sever operating systems.

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.

The Integrated Dell Remote Access Controller 8 (iDRAC8) Command Line Interface Reference Guide provides information about the RACADM subcommands, supported interfaces, property database groups and object definitions for iDRAC8 and CMC.

The Integrated Dell Remote Access Controller 8 (iDRAC8) User's Guide provides information about configuring and using iDRAC8 for 13th generation rack, tower, and blade servers to remotely manage and monitor your system and its shared resources through a network.

The Dell Baseboard Management Controller Utilities User's Guide provides information about configuring a managed system to use the BMC Management Utility to manage your system through its BMC. The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy.

The Glossary provides information about the terms used in this document.

The Deployment Toolkit release notes (for Windows PE and embedded Linux) which is also available as part of the DTK download, provides the latest available information about the installation and operation of the DTK components and the list of PowerEdge systems supported for this version of DTK.

Other supporting documents you may need Besides the Dell-provided documentation, there are numerous other resources to aid you in planning and executing a DTK - assisted deployment.

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

12 Introduction

The SUSE Linux Enterprise Server support pages at novell.com

Windows PE 5.1, Windows PE 10.x - Windows Assessment and Deployment Kit (ADK), and Windows Deployment Services (WDS) documentation.

Imaging software documentation, if you are creating a bootable media or are planning to deploy from an image (deploying from an image is not covered in this guide).

Accessing documents from the Dell EMC support site You can access the required documents using the following links:

For Dell EMC Enterprise Systems Management documents www.dell.com/esmmanuals

For Dell EMC OpenManage documents www.dell.com/openmanagemanuals

For Dell EMC Remote Enterprise Systems Management documents www.dell.com/esmmanuals

For iDRAC and Dell Lifecycle Controller documents www.dell.com/idracmanuals

For Dell EMC OpenManage Connections Enterprise Systems Management documents www.dell.com/esmmanuals

For Dell EMC Serviceability Tools documents www.dell.com/serviceabilitytools

a Go to www.dell.com/support.

b Click Browse all products.

c From All products page, click Software, and then click the required link from the following:

Analytics

Client Systems Management

Enterprise Applications

Enterprise Systems Management

Public Sector Solutions

Utilities

Mainframe

Serviceability Tools

Virtualization Solutions

Operating Systems

Support

d To view a document, click the required product and then click the required 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.

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.

Introduction 13

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.

A preoperating system environment is defined as the environment used to configure system hardware before a major operating system, such as Microsoft Windows or Linux, is installed. DTK utilities and scripts, for example, are run in a Windows PE or Linux environment for hardware configuration.

Because of the open nature of the utilities and scripts and the environment in which they can be used, it is recommended that DTK users have an advanced understanding of the Windows PE and Linux environment and scripting knowledge for the respective environments. DTK users with an advanced understanding of Windows PE and Linux can take full advantage of the utilities and exploit their capabilities preceding and beyond what the sample scripts can provide.

CAUTION: Some of the DTK utilities can destroy data if used incorrectly. To avoid the potential risk of data loss, take all necessary precautions to protect data so that mission-critical systems are not disrupted in the unlikely event of a failure. See the Dell EMC OpenManage Deployment Toolkit Command Line Interface Reference Guide available at dell.com/openmanagemanuals for complete information about the capabilities of each DTK utility.

NOTE: For Microsoft WinPE and OS deployment support limitations, see http://technet.microsoft.com/en-us/library/ hh824993.aspx

Topics:

Supported systems

Supported operating systems

Supported BIOS Firmware versions

Prerequisites and requirements

Deploying operating systems

Deployment

Deployment matrix

DTK deployment overview

Configuring a source system

Supported systems For a complete list of supported PowerEdge systems, see the Dell EMC Systems Software Support Matrix in the required version of OpenManage Software at dell.com/openmanagemanuals.

Supported operating systems DTK utilities support Windows PE 10.0 (64-bit) and Windows PE 5.1 (64-bit), to deploy the following operating systems in BIOS and UEFI mode:

Microsoft Windows Server 2012 R2 Foundation, Essentials, Standard, and Datacenter editions

Microsoft Windows Server 2016 Foundation, Essentials, and Standard editions

2

14 Pre-requisites and deployment

For Linux, the DTK utilities support deploying the following operating systems in BIOS and UEFI mode:

SUSE Linux Enterprise Server 15 (64-bit)

Red Hat Enterprise Linux 7.5 (64-bit)

Red Hat Enterprise Linux 6.10 (64-bit)

You can install the DTK Linux RPM utilities on the following operating systems in BIOS and UEFI mode:

SUSE Linux Enterprise Server 15 (64-bit)

Red Hat Enterprise Linux 7.5 (64-bit)

Red Hat Enterprise Linux 6.10 (64-bit)

NOTE: The RPMs are available in the RPMs folder of DTK ELI ISO at linux.dell.com/repo/hardware, and also in the Dell EMC Systems Management Tools and Documentation DVD.

Supported BIOS Firmware versions The latest (n) version or the n-1 version of BIOS firmware that is available at www.dell.com/support.

Prerequisites and requirements The prerequisites and requirements to run DTK utilities are listed in the following sections:

Installation Prerequisites

Deployment Prerequisites

Installation prerequisites Before installing the DTK components for Windows PE, ensure that you have the following:

The DTK self-extracting zip file (DTKX.X-WINPE-XX.exe), which contains the utilities, sample scripts, sample configuration files, and documentation to deploy your Dell system.

A Windows workstation or server that has 512 MB of RAM.

Before installing DTK components for embedded Linux, ensure that you have the following:

The DTK ISO image, which contains the utilities, sample scripts, sample configuration files, RPMs, and documentation to deploy your Dell system.

NOTE: The DTK ISO contains two bootloaders (isolinux for BIOS mode and grub2 for UEFI mode).

A Linux workstation that has at least 200 MB of free hard-drive space.

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 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 5.1, and Windows PE 10.0 (see the Microsoft documentation to customize Windows PE).

Working knowledge of Microsoft Remote Installation Services (RIS) and Automated Deployment Services (ADS) (including setting up of RIS and ADS environments) or any other third-party deployment system or tool for Windows PE.

Pre-requisites and deployment 15

Working knowledge of Windows Deployment Services (WDS) or any other third-party deployment system or tool for Windows PE.

A workstation with the following capabilities:

Writable media drive

Network access

A target system with a media drive, if performing a local deployment.

A target system with a media drive and network access, if performing a network deployment.

All DTK utilities, sample scripts, and sample configuration files.

Dell EMC 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.

For Linux, ensure that you have all of the following tools, software, and information ready to use or consult:

Advanced knowledge of Linux and Linux scripting (bash), Linux networking, installing and working with RPM Package Managers, and creating and modifying loop file systems.

A workstation with the following capabilities:

A writable media drive

Network access

A target system with a media drive, if performing a local deployment.

A target system with a media drive and network access, if performing a network deployment.

All DTK utilities, sample scripts, sample configuration files, and RPM packages.

All operating system RPM packages that DTK RPMs require.

NOTE: Tools such as Yellowdog Updater, Modified (YUM), Yet Another Setup Tool (YAST), and Advanced Packaging Tool (APT) can be used to manage RPM dependency issues.

All other utilities and files necessary to perform the deployment, including all required Linux drivers, operating system drivers, and the Dell utility partition file.

Dell EMC 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 Dellsupported hardware to build your Windows PE environment.

NOTE: The drivers provided have been tested successfully in the Windows PE environment.

Table 5. 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.

16 Pre-requisites and deployment

Drivers Purpose

winpe5.x\WINPE5.x_driverinst.bat Used to install Dell-provided drivers, from \Dell\x64\Drivers, into the customized Windows PE 5.1 image.

winpe10.x\WINPE10.x_driverinst.bat Used to install Dell-provided drivers, from \Dell\x64\Drivers, into the customized Windows PE 10.0 image.

Other supporting tools and system files While DTK provides all the necessary utilities and scripts for deploying Dell systems, there are more applications, utilities, and system files to create the preoperating system environment in which this toolkit is used.

The following table lists the Windows system files and other tools to use DTK utilities and its sample scripts.

Table 6. Supporting Tools and System Files for Windows

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

Windows ADK for Windows Server 2016 and Windows 10.0 (64-bit)

Create a bootable media for Windows PE 10.0. 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 7. 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.

fdisk To create Master Boot Record (MBR) partitions in BIOS mode.

Any system running the Linux operating system.

In the PATH variable.

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.

NOTE: In the previous releases, each Dell system required a unique upimg file. The upimg file is common for all Dell systems.

/opt/dell/toolkit/systems, or the Dell Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD.

/opt/dell /toolkit/ systems

kernel image Used during a Linux unattended installation.

Available on the Linux media. /opt/dell /toolkit /systems/linux

Pre-requisites and deployment 17

Additional Tools Purpose Source Save in DTK location

initial ramdisk Used during a Linux unattended installation.

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.

Available on the Linux operating system media or on the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD.

/opt/dell /toolkit /systems

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. The sample configuration files are operating system specific, and have been enhanced for Dell systems. For information on modifying the sample configuration files, see your operating system documentation.

DTK Utilities (SYSCFG and RAIDCFG) and scripts (sample) supports Windows PE 5.1, and Windows PE 10.0. For Microsoft WinPE and OS deployment limitations, see technet.microsoft.com/en-us/library/hh824993.aspx.

DTK helps to deploy the Microsoft Windows Server operating systems in BIOS and UEFI mode, for supported OS information refer Supported operating systems.

NOTE: For the latest supported operating systems, see the Windows PE documentation.

DTK helps to deploy the Linux operating systems in BIOS and UEFI mode, for supported OS information refer Supported operating systems. The sample configuration files contain examples to deploy the supported operating systems.

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.

A well-thought-out deployment plan is critical to the success of your deployment effort and includes the following considerations:

Assessing your existing IT environment

Selecting an operating system

Selecting the optimum Dell OpenManage systems management software configuration for your system

Choosing a deployment method

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.

18 Pre-requisites and deployment

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 Advantages Disadvantages

Local deployment (bootable media)

Relatively simple 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.

Any change requires the creation of a new bootable media.

Limited space on media for some operating system installation files.

Deployment tasks must be performed at the individual target system.

Media are read-only and requires the creation of a RAMDISK for temporary data storage.

Installation time is high.

Remote deployment over a network (bootable Windows PE or Linux media with network stack loaded)

Moderate Everything is in 1 place in a

network share.

Easy to manage changes can be made in a single location.

Data captured (profiles) can be stored in a network share.

Data can be replicated from a network share.

Can install supported Windows or Linux operating systems.

Must have network connection.

Deployment tasks must be performed at the individual target system.

Must locate the appropriate Windows PE or embedded Linux network drivers.

Not supported from a mapped NetWare system.

Deployment solution framework from a thirdparty vendor

Mixed 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.

PXE boot for Linux High Everything is in 1 place on a

network share.

Easy to manage changes can be made in only in 1 place.

High flexibility for remote deployment.

No media required.

Faster deployment.

Must have high-speed connectivity to network (LAN).

Set up time is longer.

Pre-requisites and deployment 19

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.

Preparing for deployment For using DTK utilities and scripts to deploy on a target system:

1 On systems running Windows, copy or extract DTK utilities, sample scripts, sample configuration files, and drivers provided (in the zip file) to the Windows PE image. On systems running Linux, obtain the DTK Linux ISO image, which is a self-contained bootable ISO image.

2 On systems running Windows, organize DTK utilities, scripts, and configuration files, the operating system installation files, and the requisite system files and drivers on a network share or local media. On systems running Linux, use and customize the sample scripts per your requirements.

3 Set up an optimally configured source system by using the Dell Systems Build and Update Utility on the Dell EMC Systems Management Tools and Documentation DVD (to install your operating system) and the Systems Service and Diagnostics Tools (to load drivers). This source system acts as the master server that is used to replicate settings to target servers.

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.BAT scripts or for Linux from DTK Linux ISO image and running the syscap.sh, raidcap.sh, and raccap.sh scripts.

NOTE: You can use a system BIOS configuration profile generated for all systems belonging to the same generation.

5 Create an operating system answer file that contains unattended operating system software installation information.

6 Edit the DTK sample script files that read the system configuration files to set up the system BIOS, BMC, RAID, and RAC and then install an operating system on a target system.

Deployment After you have prepared all scripts, files, and utilities, you are ready to proceed with the deployment process. While there are many ways to use DTK utilities to deploy Dell systems, this guide focuses on the two most common methods for Windows PE and Linux: mediabased deployment (local) and network-based deployment (remote).

Configuring a source system You need an optimally configured system, both for testing purposes and as the source for the SYSCFG and RAC configuration files, to be used in the deployment process. For instructions on using the sample DTK scripts, SYSCAP.BAT or syscap.sh and RACCAP.BAT or raccap.sh, to generate SYSCFG and RAC configuration files that are used to configure the target system, see Using DTK Sample Scripts To Capture Configuration Information.

20 Pre-requisites and deployment

SBUU is replaced with Lifecycle Controller on Dell 13G server onwards. iDRAC with Lifecycle Controller is an Embedded Systems Management application for operating system deployment and lifecycle management of PowerEdge servers. You can access Dell Lifecycle Controller by pressing during system boot up.

The local GUI of iDRAC9 with Lifecycle Controller allows you to do the following in a pre-OS environment:

Hardware configuration

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. Install all necessary drivers to be used in 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/

RAC and BIOS configuration Configure RAC on your source system using the RACADM.EXE (Windows) or racadm (Linux) utility, if applicable. BIOS options can be configured using racadm.

NOTE: For more information on configuring RAC and BIOS options on your source system, see the Integrated Dell Remote Access Controller 9 (iDRAC9) Version 3.00.00.00 or later version User's Guide.

After you have successfully prepared your directory structure for a deployment and fully configured your source system, you are ready to write, review, or edit the deployment sample scripts. For instructions on editing the sample scripts necessary to run a full deployment, see Preparing The Script Files.

How to obtain Dell utility partition files Obtain the Dell utility partition files from /opt/dell/toolkit/systems, or the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD.

Pre-requisites and deployment 21

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.

Configuring supported RAID controllers.

Topics:

Extracting DTK components on systems running windows

Extracting DTK components on systems running Linux

DTK contents

Sample scripts for deployment

RPMs

Documentation

Drivers and Dell real mode kernel

Extracting DTK components on systems running windows DTK components are provided in a self-extracting zip file at www.dell.com/support. The self-extracting file can be opened on any system running Microsoft Windows operating system. By default, DTKX.XWINPE- XX.exe files are extracted to the root directory of your local hard drive, C:\. You can change this location by giving a different path when extracting the files, but it is recommended that you keep the DTK default directory structure if you plan to use the sample deployment scripts provided with DTK.

1 Download the DTK file DTKX.X-WINPE-XX.exe from www.dell.com/support and save it on your system.

2 After the file downloads, double-click the file. The Dell OpenManage Deployment Toolkit for WindowsPE screen containing the product and download information appears.

3 Click OK.

4 Click Unzip.

By default, files are unzipped to C:\. You can unzip the DTK components to your local hard drive and then copy them later to a network volume, or you can change the installation path to an available network share. For example, you can unzip the files directly to the network share (for example, Z:\) that you plan to use in the deployment process.

DTK components on systems running windows Workstation is the system on which the DTK components are extracted.

Source system is an optimally configured system from which the system settings are captured.

Target system is the system on which the settings captured from the source system are replicated.

3

22 Downloading DTK

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\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.

Additionally, DTK contains a batch file, extract.bat, which can be used to extract the CAB files of winpe5.x, and winpe 10.x folders.

Extracting DTK components on systems running Linux DTK components are provided as an ISO image at www.dell.com/support. You can use a CD/DVD burning software to burn the ISO image on a bootable CD/DVD or loop mount the ISO image to access the image contents. To extract DTK components to a workstation running a Linux operating system perform the following steps.

1 Download the ISO image dtk_X.X_XXX_Linux.iso from www.dell.com/support and save it on your system (where X is the latest DTK version and XXX is the latest build for the DTK release).

2 After the image is downloaded, burn it on a CD/DVD.

DTK components on the mounted media The following table describes the files, components, and other contents of the mounted media.

Table 9. Mounted Media Contents

Contents Details Location

docs Contains Quick Installation Guide. /mnt/cdrom/docs

LICENSING Contains all the licenses for the open source components used in the media. /mnt/cdrom/LICENSING

README Provides the latest product information. /mnt/cdrom

sa.1 Contains the Linux kernel images. /mnt/cdrom/isolinux

sa.2 Initial RAM disk containing the embedded Linux component and DTK tools. /mnt/cdrom/isolinux

RPMs Contains DTK RPMs and dependency RPMs /mnt/cdrom/RPMs

Directory structure on the target system The following table describes the contents of the directory structure on the target system.

Downloading DTK 23

Table 10. 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 required by the system superuser to perform administrative tasks.

/opt The libraries, binaries, and scripts required for the toolkit to function.

NOTE: The /opt/dell/srvadmin directory must be writable.

/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.

DTK contents DTK contains Windows PE-based or Linux-based utilities, utility to convert SYSCFG to RACADM commands, sample scripts, sample configuration files, drivers, RPMs, and documentation for automating the deployment on Dell systems. For a more information on DTK utilities, see the Dell EMC OpenManage Deployment Toolkit Command Line Interface Reference Guide. For more information on sample configuration files and scripts, see Editing The Sample Batch Files To Perform A Complete System Deployment and Preparing The Script Files.

System utilities and supported files for windows The following table lists the files located in Toolkit\Tools on systems running the Windows operating system. These are the core tools (utilities) that perform preoperating system configuration and deployment tasks. See the Dell EMC OpenManage Deployment Toolkit Command Line Interface Reference Guide at dell.com/openmanagemanuals for complete information about the capabilities of each DTK utility.

Table 11. System Utilities and Supported Files for Windows

Toolkit Components Purpose

mr2kserv.exe Service required to run raidcfg.exe functions.

raidcfg.exe Creates and reports Redundant Array of Independent Disks (RAID) information.

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).

24 Downloading DTK

Toolkit Components Purpose

config.ini Configuration file used by raidcfg.exe.

CAUTION: Do not edit this file. Incorrect edits might cause raidcfg.exe to fail.

stsvc.ini Configuration file used by raidcfg.exe.

CAUTION: Do not edit this file. Incorrect edits might cause raidcfg.exe to fail.

sys.ini Configuration file used by DTK for deployment.

IDRAC Configures iDRAC 6.

NOTE: This feature may not be supported on all systems.

IDRAC7 Configures iDRAC7.

NOTE: This feature may not be supported on all systems.

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.

CONVERTER Has the utility dtktoracadm.exe to convert the SYSCFG scripts to equivalent RACADM scripts. The file is located in Toolkit\Tools\CONVERTER.

dtktoracadm_dict.map Displays the list of SYSCFG commands converted to equivalent RACADM commands.

windows_scripts.lst Displays the list of input SYSCFG sample scripts available to be converted to RACADM scripts.

For example, in the prompt, type the command: dtktoracadm.exe windows_scripts.lst. The command converts the list of sample .BAT files in the input file.

racscripts The racscripts folder is empty before running the utility command. After the .exe script is run, the SYSCFG scripts converted to equivalent RACADM scripts are available in this folder.

changed_tokens.log Displays the converted RACADM scripts log.

unchanged_tokens.log Displays the RACADM scripts logs which are not converted.

System utilities and supported files For Linux The following table lists the files, at /opt/dell/toolkit/bin and the supporting libraries located in /opt/dell/toolkit/lib on systems running the Linux operating system. The files are the core tools (utilities) that perform preoperating system configuration and deployment tasks. See

Downloading DTK 25

the Dell EMC OpenManage Deployment Toolkit Command Line Interface Reference Guide at dell.com/openmanagemanuals for complete information about the capabilities of each DTK utility.

Table 12. System Utilities and Supported Files for Windows

Toolkit Components Purpose

pci.ids Used with syscfg to report PCI devices.

racadm Wrapper script, which invokes racadm5, or racadm6 depending on the Remote Access Controller (RAC) on your system.

racadm5 Configures DRAC 5 RACs.

racadm6 Configures iDRAC 6.

NOTE: This feature may not be supported on all systems.

racadm7 Configures iDRAC7.

racadm8 Configures iDRAC8.

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 Reports and configures BIOS, BMC, and DRAC.

Maintains the system state between reboots.

Reports hardware devices and other system-related information.

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.

Converter Has the sample utility using python script. Type in the terminal python dtktoracadm.py command 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 the command: python dtktoracadm.py linux_scripts.lst. The command converts the list of sample.sh files in the input file.

racscripts The racscripts folder is empty before running the utility. After the python script is run, the SYSCFG scripts converted to equivalent RACADM scripts are at /opt/dell/toolkit/Converter/ racscripts.

changed_tokens.log Displays the converted RACADM scripts log.

unchanged_tokens.log Displays the RACADM scripts logs which are not converted.

26 Downloading DTK

SYSCFG equivalent RACADM commands The DTK SYSCFG deployment scripts are converted to equivalent RACADM scripts, that helps in migration to utilize RACADM in the deployment solution. Starting 12th generation of PowerEdge servers and later, selected set of SYSCFG commands are a part of the DTK sample scripts. The utility has the conversion tool for converting the SYSCFG scripts in both environments Microsoft Windows and Linux operating systems. The list of DTK sample scripts are present in \Toolkit\Tools\CONVERTER\ windows_scripts.lst for Microsoft Windows operating systems and toolkit/Converter/ linux_scripts.lst for Linux operating system. The converted scripts are available in the folder racscripts. The set of converted commands are available in dtktoracadm_dict.map.

The following table lists the set of commands:

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.Failover

--subnetmask iDRAC.IPv4.Netmask

--vanilla iDRAC.NIC.VLanID

--dnsserver1v6 get iDRAC.IPv6.DNS1

--dnsserver2v6 get iDRAC.IPv6.DNS2

--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.LineEdit

Downloading DTK 27

Group SYSCFG Commands Equivalent RACADM Commands

--tmcfgnewlineseq iDRAC.IPMISerial.NewLineSeq

--solcharaccuminterval iDRAC.IPMISOL.AccumulateInterval

--solbitrate iDRAC.IPMISOL.BaudRate

--solprivlevel iDRAC.IPMISOL.MinPrivilege

--solcharsendthreshold iDRAC.IPMISOL.SendThreshold

BIOS Option Settings --HddSeq BIOS.BiosBootSettings.HddSeq

Boot Settings --BootMode BIOS.BiosBootSettings.BootMode

--BootSeqRetry BIOS.BiosBootSettings.BootSeqRetry

--HddFailover BIOS.BiosBootSettings.HddFailover

--SetBootOrderFqddn BIOS.BiosBootSettings.SetBootOrderFqddn

--SetLegacyHddOrderFqddn BIOS.BiosBootSettings.SetLegacyHddOrderFqddn

Integrated Devices --EmbVideo BIOS.IntegratedDevices.EmbVideo

--IoatEngine BIOS.IntegratedDevices.IoatEngine

--IntegratedNetwork1 BIOS.IntegratedDevices.IntegratedNetwork1

--IntegratedNetwork2 BIOS.IntegratedDevices.IntegratedNetwork2

--IntegratedRaid BIOS.IntegratedDevices.IntegratedRaid

--InternalUsb BIOS.IntegratedDevices.InternalUsb

--OsWatchdogTimer BIOS.IntegratedDevices.OsWatchdogTimer

--SriovGlobalEnable BIOS.IntegratedDevices.SriovGlobalEnable

--Usb3Setting BIOS.IntegratedDevices.Usb3Setting

Memory Settings --DynamicCoreAllocation BIOS.ProcSettings.DynamicCoreAllocation

--CorrEccSmi BIOS.MemSettings.CorrEccSmi

--MemTest BIOS.MemSettings.MemTest

--NodeInterleave BIOS.MemSettings.NodeInterleave

--memopmode BIOS.memsettings.MemOpMode

Miscellaneous Settings --AssetTag BIOS.MiscSettings.AssetTag

--ErrPrompt BIOS.MiscSettings.ErrPrompt

--NumLock BIOS.MiscSettings.NumLock

--ForceInt10 BIOS.MiscSettings.ForceInt10

--insystemcharacterization BIOS.MiscSettings.InSystemCharacterization

Processor Settings --DcuIpPrefetcher BIOS.ProcSettings.DcuIpPrefetcher

--DcuStreamerPrefetcher BIOS.ProcSettings.DcuStreamerPrefetcher

--LogicalProc BIOS.ProcSettings.LogicalProc

28 Downloading DTK

Group SYSCFG Commands Equivalent RACADM Commands

--ProcExecuteDisable BIOS.ProcSettings.ProcExecuteDisable

--ProcHwPrefetcher BIOS.ProcSettings.ProcHwPrefetcher

--ProcVirtualization BIOS.ProcSettings.ProcVirtualization

--RtidSetting BIOS.ProcSettings.RtidSetting

--ProcX2Apic BIOS.ProcSettings.ProcX2Apic

--cpucore BIOS.ProcSettings.ProcCores

--cpuspeed BIOS.ProcSettings.ProcCoreSpeed

--logicproc BIOS.procsettings.LogicalProc

--proc1brand BIOS.procsettings.Proc1Brand

--proc1id BIOS.procsettings.Proc1Id

--proc1l2cache BIOS.procsettings.Proc1L2Cache

--proc1l3cache BIOS.procsettings.Proc1L3Cache

--proc1numcores BIOS.procsettings.Proc1NumCores

--proc2brand BIOS.procsettings.Proc2Brand

--proc2id BIOS.procsettings.Proc2Id

--proc2l2cache BIOS.procsettings.Proc2L2Cache

--proc2l3cache BIOS.procsettings.Proc2L3Cache

--proc2numcores BIOS.procsettings.Proc2NumCores

--proc64bit BIOS.procsettings.Proc64bit

--procadjcacheline BIOS.procsettings.ProcAdjCacheLine

--procbusspeed BIOS.procsettings.ProcBusSpeed

--proccorespeed BIOS.procsettings.ProcCoreSpeed

--qpispeed BIOS.procsettings.QpiSpeed

--procconfigtdp BIOS.procsettings.ProcConfigTdp

SATA Settings --WriteCache BIOS.SataSettings.WriteCache

--SecurityFreezeLock BIOS.SataSettings.SecurityFreezeLock

--Sembsataraid BIOS.SataSettings.EmbSata

--embsata BIOS.SataSettings.EmbSata

--sata0 BIOS.SataSettings.SataPortA

--sata1 BIOS.SataSettings.SataPortB

--sata2 BIOS.SataSettings.SataPortC

--sata3 BIOS.SataSettings.SataPortD

--sata4 BIOS.SataSettings.SataPortE

--sata5 BIOS.SataSettings.SataPortF

Downloading DTK 29

Group SYSCFG Commands Equivalent RACADM Commands

--sata7 BIOS.SataSettings.SataPortH

--sataporta BIOS.SataSettings.SataPortA

--sataportb BIOS.SataSettings.SataPortB

--sataportc BIOS.SataSettings.SataPortC

--sataportd BIOS.SataSettings.SataPortD

--sataporte BIOS.SataSettings.SataPortE

--sataportf BIOS.SataSettings.SataPortF

--sataportg BIOS.SataSettings.SataPortG

--sataportgmodel BIOS.SataSettings.SataPortGModel

--sataportgdrivetype BIOS.SataSettings.SataPortGDriveType

--sataportgcapacity BIOS.SataSettings.SataPortGCapacity

--sataporth BIOS.SataSettings.SataPortH

--sataporthmodel BIOS.SataSettings.SataPortHModel

--sataporthdrivetype BIOS.SataSettings.SataPortHDriveType

--sataporthcapacity BIOS.SataSettings.SataPortHCapacity

--sataporti BIOS.SataSettings.SataPortI

--sataportimodel BIOS.SataSettings.SataPortIModel

--sataportidrivetype BIOS.SataSettings.SataPortIDriveType

--sataporticapacity BIOS.SataSettings.SataPortICapacity

--sataportj BIOS.SataSettings.SataPortJ

--sataportjmodel BIOS.SataSettings.SataPortJModel

--sataportjdrivetyp BIOS.SataSettings.SataPortJDriveType

--sataportjcapacity BIOS.SataSettings.SataPortJCapacity

Serial Communication --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.SysSecurity.AcPwrRcvryDelay

--PwrButton BIOS.SysSecurity.PwrButton

--SetupPassword BIOS.SysSecurity.SetupPassword

--SysPassword BIOS.SysSecurity.SysPassword

System Power --maxpowercap System.Power.Cap.MaxThreshold

30 Downloading DTK

Group SYSCFG Commands Equivalent RACADM Commands

--minpowercap System.Power.Cap.MinThreshold

--capenable System.Power.Cap.Enable

Sample scripts for deployment Sample deployment scripts and configuration files for deployment of DTK on Dell systems.

Sample deployment configuration files for Windows The following table describes examples of Windows configuration files used to perform a scripted deployment. The Windows files for 64-bit supported systems are located in the following directories:

\Dell\x64\Toolkit\Template\Configs

NOTE: All configuration files are provided as examples only. These sample configuration files must be edited before they can be used in any deployment tasks.

Table 14. Sample Configuration Files for Windows

Toolkit Components Purpose Location

raccfg.ini Sample configuration file for DRAC4 remote access controllers. \Toolkit\Systems\

raidcfg.ini Sample output file to enable RAID replication. \Toolkit\Systems\

winbom.ini Sample file used to start the racsvc and mr2kserv services. \Toolkit\Template\Configs

winpeoem.sif Sample file to add support for Dell mass storage drivers. \Toolkit\Template\Configs

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 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 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.xml Sample file used with unattended installation of SUSE Linux Enterprise Server (version 12) operating system in UEFI mode.

Downloading DTK 31

Toolkit Components Purpose

autoinst-sles11.xml Sample file used with unattended installation of SUSE Linux Enterprise Server (version 11) operating system in BIOS mode.

autoinst_sles11_uefi.xml Sample file used with unattended installation of SUSE Linux Enterprise Server (version 11) operating system in UEFI mode.

ks-rhel6.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 6) operating system in BIOS mode.

ks_rhel6_uefi.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 6) operating system in UEFI mode.

ks-rhel7.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 7) operating system in BIOS mode.

ks_rhel7_uefi.cfg Sample file used with unattended installation of Red Hat Enterprise Linux Server (version 7) operating system in UEFI mode.

raccfg.ini Sample configuration file for DRAC 4 RACs.

raidcfg.ini Sample output file to enable RAID replication.

syscfg.ini Sample configuration file for SYSCFG utility to configure the BIOS, DRAC, and BMC settings.

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 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 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.CFG This file is used by UPINIT.BAT.

MOUNTUP.CFG This file is used by UPINIT.BAT.

UMOUNTUP.CFG This file is used by UPINIT.BAT.

DTKRUNALL.BAT Applies BIOS, BMC, RAC, and RAID settings saved in the files to the current system.

ERRHNDL.BAT Handles errors returned in DTK scripts.

32 Downloading DTK

Toolkit Components Purpose

PARTCFG.BAT Creates and populates the Dell utility partition and creates the operating system partition on a specified hard drive. The script cleans out all existing partitions on your system before creating and populating the partition.

RACCAP.BAT Captures Remote Access Controller (RAC) settings to a file for DRAC 4 remote access controllers.

RACREP.BAT Applies (replicates) the RAC settings saved in a file to the target system.

RAIDCAP.BAT Captures the RAID settings and saves them to a file.

RAIDCFG.BAT Configures the selected RAID controllers on the system.

RAIDREP.BAT Applies (replicates) RAID settings saved in a file to the target system.

SYSCAP.BAT Captures BIOS and BMC configuration settings and saves them to a file.

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. 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 6) operating system.

lininst7.sh Performs an unattended installation of a supported Red Hat Enterprise Linux Server (version 7) operating system.

partcfg.sh Creates and populates the Dell utility partition and creates the deployment partition on a specified hard drive. Before doing so, however, this script cleans out all existing partitions in your system.

raccap.sh Captures RAC settings to a file.

racrep.sh Applies (replicates) the RAC settings saved in a file to the target system.

Downloading DTK 33

Toolkit Components Purpose

raidcfg.sh Configures all RAID controllers detected in a system.

suseinst.sh Performs an unattended installation of a supported SUSE Linux Enterprise Server operating system.

syscap.sh Captures BIOS and BMC configuration settings and saves them to a file.

sysdrmk Used by upinit.sh to patch the boot sector.

sysrep.sh Applies (replicates) BIOS and BMC configuration settings and configures the target system.

tkenvset.sh Sets the path of DTK installation and variables for the specific system being deployed.

upinit.sh Creates and populates the Dell utility partition.

RPMs The following table describes all DTK RPMs at mnt/cdrom/RPMs. The syscfg and raidcfg RPMs are also available in Dell EMC Systems Management Tools and Documentation DVD.

Table 18. 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.

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. Documentation

Toolkit Components Purpose

Dell EMC OpenManage Deployment Toolkit Installation Guide

Contains information about installing and deploying DTK on supported Dell systems.

README Contains the latest information about supported systems, known issues, and important notes. On systems running the Linux operating system, it is located at /mnt/cdrom as well.

34 Downloading DTK

Drivers and Dell real mode kernel Hardware application programing interface (HAPI) drivers are essential for DTK tools to work in the embedded Linux environment. Dell Real Mode Kernel (DRMK) contains the mbr file necessary to create a bootable Dell Utility Partition.

Downloading DTK 35

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.

The advantages of seamless package are:

The size of the DTK seamless package is less (approximately 60MB) compared to that of the complete OM DVD size.

The DTK seamless package is posted independently on www.dell.com/support with OM and DTK releases.

The seamless package supports both interactive and non-interactive modes of DTK tool installation.

Interactive mode options:

Type the following command: ./DTKTOOLS_ _Linux64_ .Bin

The options displayed on the screen are as follows:

Deployment Tools Install Utility

Available install options:

[ ] 1. Command line BIOS configuration utility (syscfg utility)

[ ] 2. Command line RAID configuration utility (raidcfg utility)

[ ] 3. DRAC command line configuration utility

[ ] 4. All features

Enter the number to select/deselect (toggle selection) a component

Enter i to install the selected components.

Enter q to quit.

Once the DTK tools installation is complete, success message is displayed on the screen.

To uninstall the DTK tools, run the command

/opt/dell/toolkit/bin/dtktools-uninstall.sh d

Non-interactive mode:

4

36 DTK Seamless package

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:

./DTKTOOLS_ _Linux64_ .Bin [h/--help].

The seamless package uninstalls the older DTK tool set version, and upgrades it to a newer version if Server Administrator is not present in the system.

DTK Seamless package 37

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. For a network-based deployment, you must set up the directory structure on a network volume that is accessible from your workstation, the source system (to generate configuration information), and the target system (to deploy).

If you plan to run a scripted deployment from DTK sample scripts, make sure that the DTK files are correctly structured in the deployment directory. DTK sample scripts use this structure to set the default paths for deployment. If you make changes to the directory structure, you must also make changes to the sample scripts.

The deployment directory structure consists of the following files:

DTK Utilities And Files

System-Specific Files

Operating System Installation Files

NOTE: Do not create your DTK directory structure on a NetWare network volume. DTK network-based deployment is not supported from mapped NetWare systems.

Topics:

DTK utilities and files

System-specific files

Operating system installation files

DTK utilities and files All the necessary DTK files are provided as part of the initial installation. It is recommended that you use the default directory structure created in the initial installation of DTK components. The sample scripts provided with DTK are set up to use these default paths.

NOTE: If you choose to create a directory structure for DTK components, that is different from the one provided in the initial installation, carefully review and edit each sample script (wherever necessary) to reflect the different directory structure.

System-specific files The directory Toolkit\Systems in systems running Microsoft Windows and /opt/dell/toolkit/systems/system name in systems running Linux acts as a central repository for all the system-specific deployment 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 PowerEdge server in the directory Toolkit\Systems\ . These files can then be accessed from this directory when deploying multiple similar PowerEdge servers.

NOTE: If you choose to create a directory structure for the system-specific files that is different from the one suggested in this guide, ensure that you carefully review and edit each sample script (wherever necessary) to reflect the different directory structure.

5

38 Setting up a directory structure for deployment

Operating system installation files For more details on installing Windows Server and Linux operating system using DTK, see the Dell EMC OpenManage Deployment Toolkit Installation Guide available at dell.com/openmanagemanuals.

Setting up a directory structure for deployment 39

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.

There are four main tasks:

Using The Sample DTK Scripts To Run A Full Deployment

Editing The Sample Batch Files To Perform A Complete System Deployment

Using DTK Sample Scripts To Capture Configuration Information

Preparing The Operating System Installation Scripts

Topics:

Using the sample DTK scripts to run a full deployment

Editing the sample batch files to perform a complete system deployment

Editing example of TKENVSET and tkenvset

Editing DTK task scripts

Using DTK sample scripts to capture configuration information

Preparing the operating system installation scripts

Using the sample DTK scripts to run a full deployment A scripted DTK deployment relies on the master deployment file to integrate all the applicable DTK task scripts and utilities and perform preoperating system configuration tasks before launching the operating system installation files. The master deployment file, along with the TKENVSET.BAT (for Windows) or tkenvset.sh (for Linux) scripts, makes up the master set of instructions that drives the deployment process. This file is not provided with the sample scripts.

A sample DEPLOY.BAT is given below:

:: ***************************************************** ::Call TKENVSET.BAT to discover platform information ::as well as set paths and environment variables for ::Deployment Toolkit Tools and Scripts. ***************************************************** ***************************************************** :: call RAIDCFG.BAT to configure RAID. :: ***************************************************** ***************************************************** :: Replicate the system settings to the current SUT!. CALL SYSREP.BAT or DTKRUNALL.BAT. :: ***************************************************** ***************************************************** ::Partitioning the system hard disk. call PARTCFG.BAT. ***************************************************** ***************************************************** :: Put hdd as first in boot sequence (1-removable, 2- cdrom, 3-hdd) :: If the system configuration has changed (i.e. a ::boot device was added, removed, or enabled in BIOS) ::the following line should be modified to reflect the

6

40 Preparing the script files

::new hdd device number. :: This is calling Windows installer scripts. ***************************************************** ::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0 ::call WIN2K12.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.

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. While it is recommended that you use DTK sample scripts to automate your deployment tasks. You can create your own system deployment batch files using any ASCII text editor by incorporating the various DTK utilities and commands in the batch file.

NOTE: For more information about scripting batch files and specific batch file commands, see your Windows PE or Linux operating system documentation.

Each of the utilities, scripts, and system configuration files are described. Depending on your requirements, you may use all or only some of them in your deployment. You can write your master deployment file to perform a full deployment on a system with the help of utilities, scripts, and configuration files. This file is not provided with the sample scripts.

Scripts for deployment on systems running windows The following table lists the capture scripts for Windows.

Table 20. Capture Scripts for Windows

Script Name Description Associated Files

RACCAP.BAT Captures RAC settings to a file for Dell Remote Access Controller 4 (DRAC 4). TKENVSET.BAT Provides information to the tasks scripts about

the location of the DTK utilities, scripts, and configuration files.

RACADM.EXE Retrieves RAC information and configure settings.

SYSCAP.BAT Captures BIOS and Baseboard Management Controller (BMC) configuration settings and saves them to a file.

TKENVSET.BAT Provides information to the tasks scripts about the location of the DTK utilities, scripts, and configuration files.

SYSCFG.EXE Configures the BIOS and BMC settings.

RAIDCAP.BAT Captures the RAID settings and saves them to a file TKENVSET.BAT Provides information to the tasks scripts about

the location of the DTK utilities, scripts, and configuration files.

RAIDCFG.EXE Retrieves RAID information and configure settings.

Scripts for deployment on systems running Linux The following table lists the capture scripts for Linux.

Preparing the script files 41

Table 21. 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.sh Captures the RAID settings and saves them to a file. 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.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files.

syscfg Used by syscap.sh to configure the BIOS, DRAC, and BMC settings.

Replication scripts for deployment on systems running windows operating system The following table lists the replication scripts for systems running Windows.

Table 22. Replication Scripts for Windows

Script Name Description Associated Files

RACREP.BAT Applies the RAC configuration settings saved in a file to the current system. TKENVSET.BAT Used by RACREP.BAT to inform the task scripts

about where to find the DTK utilities, scripts, and configuration files.

RACADM.EXE Used by RACREP.BAT to replicate RAC information and to configure settings.

RAIDREP.BAT Applies the RAID settings saved in a file to the current system. RAIDCFG.EXE Used by RAIDREP.BAT to retrieve RAID information

and to configure settings.

SYSREP.BAT Applies the BIOS and BMC settings saved in a file to the current system. TKENVSET.BAT Used by SYSREP.BAT to inform the task scripts

where to find the DTK utilities, scripts, and configuration files.

SYSCFG.EXE Used by SYSREP.BAT to configure the BIOS and BMC settings.

Replication scripts for deployment on systems running Linux operating system The following table lists the replication scripts for systems running Linux.

42 Preparing the script files

Table 23. 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.

syscfg Used by racrep.sh to configure DRAC5.

sysrep.sh Applies the BIOS and BMC settings saved in a file to the current system. tkenvset.sh Used by sysrep.sh to inform the task scripts about where

to find the DTK utilities, scripts, and configuration files.

syscfg Used by sysrep.sh to configure the BIOS settings.

Deployment scripts for systems running windows operating systems The following table lists the deployment scripts for Windows.

Table 24. Deployment Scripts For Windows

Script Name Description Associated Files

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 W2K12INST.BAT to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.

SETUP.EXE Used by W2K12INST.BAT to install the operating system with the UNATTEND.XML answer file.

UNATTEND2K12.XML Used by W2K12INST.BAT with SETUP.EXE to install the operating system files in BIOS mode.

UNATTEND2K12_UEFI.XML Used by W2K12INST.BAT with SETUP.EXE to install the operating system files in UEFI mode.

W2K16INST.BAT Performs an unattended installation of supported Windows Server 2012 R2 operating systems.

NOTE: From Windows Server 2012 R2 onwards, Server Core is the default deployment configuration setting. However, you can modify the xml files to change the setting.

TKENVSET.BAT Used by W2K16INST.BAT to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.

SETUP.EXE Used by W2K16INST.BAT to install the operating system with the UNATTEND.XML answer file.

UNATTEND2K16.XML Used by W2K16INST.BAT with SETUP.EXE to install the operating system files in BIOS mode.

UNATTEND2K16_UEFI.XML Used by W2K16INST.BAT with SETUP.EXE to install the operating system files in UEFI mode.

Deployment scripts for systems running Linux operating systems The following table lists the deployment scripts for systems running Linux.

Preparing the script files 43

Table 25. 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.

tkenvset.sh Used by lininst.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.

grub Used to install the operating system with the unattended answer file in BIOS mode.

grub2 Used to install the operating system with the unattended answer file in UEFI mode.

NOTE: Both grub and grub2 use the following images with the unattended answer file to perform unattended operations:

initial ramdisk Available on the Dell Systems Build and Update Utility.

kernel image Available on the Linux operating system media.

ks-rhel6.cfg Used by lininst.sh with grub to install the Red Hat Enterprise Linux Server (versions 6) operating system files in BIOS mode.

ks_rhel6_uefi.cfg Used by lininst.sh with grub2 to install the Red Hat Enterprise Linux Server (versions 6) operating system files in UEFI mode.

ks-rhel7.cfg Used by lininst.sh with grub to install the Red Hat Enterprise Linux Server (versions 7) operating system files in BIOS mode.

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.

suseinst.sh Performs an unattended installation of a supported SUSE Linux Enterprise Server operating system.

tkenvset.sh Used by suseinst.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.

grub Used to install the operating system with the unattended answer file in BIOS mode.

grub2 Used to install the operating system with the unattended answer file in UEFI mode.

NOTE: Both grub and grub2 use the following images 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 with grub to install the operating system files.

autoinst-sles12.xml Used by suseinst.sh with grub to install the SUSE Linux Enterprise Server (version 12) operating system files in BIOS mode.

autoinst_sles12_uefi.xml Used by suseinst.sh with grub2 to install the SUSE Linux Enterprise Server (version 12) operating system files in UEFI mode.

Other scripts for systems running Windows operating systems The following table lists the other scripts for systems running Windows.

Table 26. Other Scripts for Windows

Script Name Description Associated Files

TKENVSET.BAT Sets the path of DTK installation and variables for the system to be deployed and configured. The variables and paths

SYSCFG.EXE Used by TKENVSET.BAT to discover the system type.

44 Preparing the script files

Script Name Description Associated Files

specified in this file must be specified before any of the other supporting scripts can be used.

RAIDCFG.BAT Configures the selected RAID controller detected in the system. TKENVSET.BAT Used by RAIDCFG.BAT to inform the task scripts

about where to find the DTK utilities, scripts, and configuration files.

RAIDCFG.EXE Used by RAIDCFG.BAT to retrieve RAID information and configure settings.

PARTCFG.BAT Creates and populates the Dell utility partition (UP) and the operating system partition on a specified disk.

TKENVSET.BAT Used by PARTCFG.BAT to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.

DISKPART.EXE Provided by Windows; this script is used to create partitions on your disk. When creating a Windows PE image, ensure that the DISKPART.EXE tool is present in the Windows PE image you created. This script uses the following files for unattended operations:

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. The variables and paths in this file must be specified before any of the other supporting scripts can be used.

syscfg Used by tkenvset.sh to discover the system type.

raidcfg.sh Configures the selected RAID controller detected in the system. tkenvset.sh Used by raidcfg.sh to inform the task scripts about

where to find the DTK utilities, scripts, and configuration files.

raidcfg Used by raidcfg.sh to retrieve RAID information and configure settings.

partcfg.sh In BIOS mode, creates and populates the Dell utility partition and the deployment partition (MBR type) on a specified disk. In UEFI mode, creates deployment partition (GPT type) on a specific disk. The partcfg.shscript uses a /tmpfolder to store a few temporary files critical to its execution.

tkenvset.sh Used by partcfg.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.

fdisk Used to create partitions on your disk in BIOS mode. When creating an embedded Linux ISO image, make sure that fdisk is present in the embedded Linux environment you created.

parted Used to create partitions on your disk in UEFI mode. When creating an embedded Linux ISO image, make sure that parted is present in the embedded Linux environment you created.

This script uses the following file for unattended operations:

upinit.sh Used by partcfg.sh to create and populate the Dell utility partition.

NOTE: Do not modify the upinit.sh script.

Preparing the script files 45

Script Name Description Associated Files

upinit.sh Creates and populates the Dell utility partition in BIOS mode.

NOTE: Do not modify the upinit.sh script.

tkenvset.sh Used by upinit.sh to inform the task scripts about where to find the DTK utilities, scripts, and configuration files.

fdisk Used to create partitions on your disk.

mbr File necessary to create a bootable Dell utility partition.

sysdrmk Used by upinit.sh to patch the boot sector.

unzip Used by upinit.sh for populating 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. Other task scripts may require edits in certain situations. These optional edits are discussed in Editing DTK Task Scripts. The TKENVSET.BAT or tkenvset.sh script sets the path of DTK utilities 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. Locate the Deployment Toolkit Installation Paths heading to find the following lines:

On systems running Windows:

set DT_DRIVE=X: set DT_PATH=%DT_DRIVE%\Dell\Toolkit set DT_TOOLS=%DT_PATH%\Tools set DT_SYSTEMS=%DT_PATH%\Systems set DT_SCRIPTS=%DT_PATH%\Template\Scripts set DT_STOP_ON_ERROR=FALSE On systems running Linux:

DT_PATH=$dt_drive/opt/dell/toolkit DT_TOOLS=$dt_path/bin DT_SYSTEMS=$dt_path/systems DT_SCRIPTS=$dt_path/template/scripts DT_STOP_ON_ERROR=FALSE DT_DRMK=$dt_path/opt/dell/drmk

Confirming or editing DTK installation path variables Perform the following steps to confirm and/or edit the installation path variables:

1 On systems running Windows, set the variable that defines the path to the full set of DTK deployment files (DT_DRIVE). On systems running Windows, this variable is set to X: by default in the sample script. For Windows, this variable is set to X: by default in the sample script. On systems running Linux, this variable is set to $dt_drive/opt/dell/toolkit by default in the sample script. Edit this drive letter to reflect the actual drive letter for DTK deployment files, if necessary.

2 Set the variable that defines the path to the full set of DTK deployment files (DT_PATH). This variable is set to %DT_DRIVE%\Dell \Toolkit (Windows) or $dt_drive/opt/dell/toolkit (Linux) by default in the sample script. Edit this path to reflect the actual location of DTK deployment files, if necessary.

3 Set the variable that defines the directory containing DTK utilities (DT_TOOLS). This variable is set to %DT_PATH%\Tools (Windows) or $dt_path/bin (Linux) by default in the sample script. Edit this path to reflect the actual location of DTK utilities, if necessary.

46 Preparing the script files

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) or $dt_path/template/scripts (Linux) by default in the sample script. Edit this path to reflect the actual location of DTK deployment scripts, if necessary.

6 Set the variable that indicates whether you want the deployment process to exit when any error is returned (DT_STOP_ON_ERROR). This variable is set to FALSE by default in the sample script, indicating that errors are handled by the ERRHNDL.BAT (Windows) or errhndl.sh (Linux) script. Set the value to TRUE only if you want the deployment to exit when any error is returned.

7 For Linux, set the variable that defines the directory containing the DRMK system files necessary to create a Dell utility partition (DT_DRMK). This variable is set to $dt_path/opt/dell/drmk by default in the sample script. Edit this path to reflect the actual location of the DRMK files, if necessary.

Specifying the SYSCFG variables

The SYSCFG replication file is set to syscfg.ini by default. If you used the SYSCAP.BAT (for Windows) or syscap.sh (for Linux) sample script to generate the file, there is no need to edit the default settings. If you have modified the sample scripts or to the suggested directory structure, confirm that syscfg.ini is correctly named and that the path is set correctly for deployment.

To edit the SYSCFG capture variables, locate the following lines:

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.ini

NOTE: If the replication requires a change in the memory redundancy mode, reboot the target server and execute the script again to complete the replication.

Specifying the RAC configuration variables

The IP address for your target system RAC is set in the sample script as 10.98.8.121 by default. Edit this value to reflect the actual IP address of your target system RAC, if applicable. Additionally, the RAC configuration file used to configure your RAC is set by default to raccfg.ini. If you use the RACCAP.BAT or raccap.sh sample script to generate the raccfg.ini file, there is no need to edit this default setting. If you have made any modifications to the sample scripts or to the suggested directory structure, you must confirm that raccfg.ini is correctly named and that the path is correctly set for your deployment.

To edit the RAC configuration variables, locate the following lines:

In RACCAP.BAT:

set DT_RAC_CAPFILE=%DT_SYSTEMS%\%DT_PLATFORM%\raccfg.ini

In raccap.sh:

DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.ini

To edit the RAC configuration variables, locate the following lines:

Preparing the script files 47

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.ini

Specifying variables used to create disk partitions and install the Dell utility partition

NOTE: If the primary deployment state (DT_PARTN) is set to OFF, the partitioning deployment state subsection is skipped.

The PARTCFG.BAT (Windows) or partcfg.sh (Linux) sample script provides the following disk partitioning default values. These values must be confirmed sometimes, and modified in other cases, before performing a deployment. Locates the partn label to find the following lines:

In PARTCFG.BAT:

set DT_PARTN_UP=ON set DT_MOUNT=H

:: Default Hard Drive 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.bin

# 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.

48 Preparing the script files

In partcfg.sh in UEFI mode:

DT_PARTN_UP=OFF

# Default Hard Drive DT_HD=/dev/sda

# PARTCFG section set DT_DP_SIZE_GPT=125

# RAIDCFG section DT_VD_SIZE=10480 # default size for virtual disk

Editing the default partition configuration values

Perform the following steps to edit the default partition configuration default values, as necessary:

1 Edit the default utility partitioning variable (DT_PARTN_UP), if necessary. Set this variable f you want to install the Dell utility partition.

2 Edit the default variable value for the default hard drive (DT_HD for Windows and DT_HD for Linux), if applicable.

NOTE: Ensure that the default variable value for DT_HD is set to a valid nonremovable disk, and not to removable media such as virtual media.

3 Edit the default variable value (DT_DP_SIZE in MB for BIOS mode and DT_DP_SIZE_GPT in MiB for UEFI mode) for the primary operating system partition, if applicable.

4 Edit the default variable value for file system type ( DT_OS_FSTYPE), if applicable.

NOTE: The valid values are FAT32 and NTFS.

5 If the DT_PARTN_UP variable is set to ON, edit the default variable value (in MB) for the utility partition (DT_UP_SIZE), if applicable.

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.

Editing DTK task scripts The task scripts called by the master batch file do not require any edits (with the following exceptions) if the default variable values are utilized in the TKENVSET.BAT or tkenvset.sh scripts. However, if you make any changes to the default values set by the TKENVSET.BAT or tkenvset.sh, you must make the same edits to the matching default values set in the appropriate task scripts. Locate the USER MODIFICATION REQUIRED heading in the task scripts to find the variable values you may need to edit. Each of the following task scripts can be called by the user-written master batch script during a full deployment:

RACREP.BAT or racrep.sh

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. On systems running Linux the racrep.sh script uses racadm wrapper script or the syscfg utility (depending on the version of RAC on your system) to configure RAC in the target system. The raccfg.ini is passed as the first parameter to these scripts. If this parameter is not passed, the default variables values used in these scripts are set in the TKENVSET.BAT or tkenvet.sh scripts. You can specify the IP address to configure the RAC as an

Preparing the script files 49

optional parameter. The raccfg.ini file is generated with the RACCAP.BAT or raccap.sh sample script. For information about using the RACCAP.BATor raccap.sh sample script to capture RAC configuration information, see RACCAP.BAT Or raccap.sh.

NOTE: On all PowerEdge systems, racrep.sh and sysrep.sh have duplicate functions. If you run racrep.sh followed by sysrep.sh, the latter overwrites the settings of the former.

RAIDCFG.BAT or raidcfg.sh The RAIDCFG.BAT or raidcfg.sh sample script configures RAID controllers detected on the system. User input is optional to run this script. The input 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. The default variable values used in this script are set in the TKENVSET.BAT or tkenvest.sh scripts. This script uses the RAIDCFG.EXE or raidcfg.sh utility to automatically configure the detected controllers on your target system. For example, for the first controller discovered, if RAIDCFG.EXE or raidcfg.sh discovers only one attached hard drive, the script tries to create RAID 0; if two hard drives are discovered, a RAID 1 configuration is enabled; if three or more hard drives are discovered, a RAID 5 configuration is enabled.

NOTE: On the detected controller, a RAID virtual disk is created only if the array disks connected to that particular controller have space available and, where applicable, are not part of existing array group.

SYSREP.BAT or sysrep.sh The SYSREP.BAT or sysrep.sh sample script applies SYSCFG options to the target system based on configuration information that has been saved in a configuration file. User input is optional to run this script, depending on the variable settings in the SYSREP.BAT or sysrep.sh scripts. This script uses the SYSCFG utility to configure the BIOS and BMC in the target system using the configuration file syscfg.in. The syscfg.in is the first parameter passed to this script. If this parameter is not passed, the default variables values used in this script are set in the SYSREP.BAT or sysrep.sh scripts. The syscfg.ini file is generated with the SYSCAP.BAT or syscap.sh sample script. For information about using the SYSCAP.BAT or syscap.sh sample script to capture BIOS and BMC 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.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.BAT or upinit.sh tool, see UPINIT.BAT Or upinit.sh. User input is not required to run this script. The default variable values used in this script are set in the TKENVSET.BAT or tkenvset.sh scripts.

NOTE: Ensure that DT_HD is set to the required disk to be configured before you execute the PARTCFG.BAT or partcfg.sh script.

Using DTK sample scripts to capture configuration information The SYSCFG and RACADM utilities can read the source system configuration and duplicate that configuration on a target system using a sample DTK script file. These configuration files are used during a full deployment to configure the BIOS, BMC, and RAC settings on the target system. The following sections provide instructions for:

Capturing The System BIOS And BMC Configuration With The SYSCAP Or syscap Sample Script

50 Preparing the script files

Capturing The RAC Configuration With The RACCAP Or raccap Sample Script

Capturing the system BIOS and BMC configuration with the SYSCAP or syscap.sh sample script You can replicate the system BIOS and BMC configurations from a source Dell system to an identical target Dell system.

NOTE: For the script to complete successfully, the source system must have access to the network share that includes the prebuilt DTK directory structure.

SYSCAP.BAT or syscap.sh

The SYSCAP.BAT or syscap.sh sample script captures BIOS and BMC 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. The SYSCAP.BAT or syscap.sh script uses the SYSCFG utility to retrieve BIOS and BMC configuration settings from the source system and to save the settings in a file named syscfg.ini in the Z:\Dell\Toolkit\Systems\ directory.

Running the SYSCAP.BAT or Syscap.sh

To run the SYSCAP.BAT or syscap.sh sample script to capture the BIOS and BMC configuration information in the syscfg.ini file:

1 Edit the startnet.cmd file (on your Windows PE image) or start-up script file (on your embedded Linux image) to call the SYSCAP.BAT or syscap.sh script after the network share with the pre-built DTK directory structure is mounted. For example, add:

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.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.

Capturing the RAC configuration with the RACCAP or raccap.sh sample script If your system has a RAC, you can replicate the RAC configuration from the RAC of a source Dell system to an identical target Dell system with an identical RAC.

NOTE: For the script to complete successfully, the source system must have access to the network share that includes the pre- built DTK directory structure.

Preparing the script files 51

Running RACCAP.BAT or raccap.sh

To run the RACCAP.BAT or raccap.sh sample script to capture the RAC configuration information in the raccfg.ini file:

1 Edit the startnet.cmd file (on your Windows PE image) or start-up script file (on your embedded Linux image) to call the RACCAP.BAT or raccap.sh script after the network share with the pre-built DTK directory structure is mounted. For example, add:

On systems running Windows:

Z:\Dell\x64\Toolkit\Template\Scripts\RACCAP.BAT Z:\raccfg.ini On systems running Linux:

/opt/dell/toolkit/template/scripts/raccap.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 on systems running Windows and /opt/dell/toolkit/systems/ directory on systems running 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 RAC configuration file is referred to as the .cfg file in the The Integrated Dell Remote Access Controller 9 (iDRAC9) User's Guide . See these guides for additional information about manually creating a RAC configuration file.

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 \ . 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/ .

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 in BIOS mode.

For details on the command line arguments to be used for UPINIT.BAT or upinit.sh, see the Dell EMC Deployment Toolkit Command Line Interface Reference Guide dell.com/openmanagemanuals.

52 Preparing the script files

Preparing the operating system installation scripts The 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 EMC 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 key during reboot.

W2K12INST.BAT and W2K16INST.BAT The W2K12INST.BATand W2K16INST.BATsample scripts are used to perform an unattended installation of the Windows Server 2012 R2 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 W2K12INST.BATand W2K16INST.BATare 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

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 2012 R2 operating system

source and the UNATTEND.XML (in BIOS mode) or UNATTEND_UEFI.XML file (in UEFI mode).

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.EXE utility to install the operating system files. For more information, about preparing the UNATTEND.XML file, see UNATTEND.XML AND UNATTEND_UEFI.XML.

Specifying the windows installation variables and installation paths

To edit the Windows operating system installation variables (in BIOS mode), locate the following lines in W2K12INST.BAT:

:: Location of Unattend.xml file

set DT_UNATTEND=%DT_SYSTEMS%\%DT_PLATFORM%\unattend.xml

Preparing the script files 53

UNATTEND.XML aND UNATTEND_UEFI.XML The UNATTEND.XML (in BIOS mode) and UNATTEND_UEFI.XML file (in UEFI mode) are the default name of the answer files for automating the Windows setup during an unattended installation. A sample copy of the UNATTEND.XML and UNATTEND_UEFI.XML file is provided as part of the DTK download in the \Toolkit\Template\Configs directory.

UNATTEND.XML and UNATTEND_UEFI.XML contains the headings and parameters that instruct Windows setup to perform various configuration tasks. In UNATTEND.XML and UNATTEND_UEFI.XML, specify various setup options, including how to partition disks and the location of the Windows image you want to install. Before a full deployment can be run, edit all appropriate headings and parameters, as necessary.

NOTE: On systems running Windows Server 2012 R2 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 2012 R2 operating system, save the completed file in the \Toolkit\os_deploy\ directory after you have completed all necessary modifications to the UNATTEND.XML or UNATTEND_UEFI.XML file.

After you have successfully edited your deployment scripts, you are ready to create your deployment media and run your deployment. For instructions on creating the deployment media and running a full deployment, see Running The Deployment Scripts.

Linux scripts The lininst.sh (for Red Hat Enterprise Linux 6) and lininst7.sh (for Red Hat Enterprise Linux 7) sample scripts are used to perform an unattended installation of the supported Red Hat Enterprise Linux Server operating system in both BIOS and UEFI mode. The variables and paths must be specified before the operating system can be installed.

Utilities used by Linux scripts

grub Used with the kernel image and initial ramdisk files, along with the unattended answer file to install the operating system in BIOS mode.

grub2 Used with the kernel image and initial ramdisk files, along with the unattended answer file to install the operating system in UEFI mode.

The following are the variables used in grub and grub2:

DT_OS_DISK Sets the disk to deploy the Red Hat Enterprise Linux Server 6 operating system.

DT_OS_NFS_LOC Sets the disk to deploy the Red Hat Enterprise Linux Server 7 operating system.

DT_OS_SRC Sets the location from where to copy the kernel image and initial ramdisk files.

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.

54 Preparing the script files

Answer files

Depending on the version of the Red Hat Enterprise Linux Server operating system, the ks-rhel6.cfg and ks-rhel7.cfg, ks_rhel6_uefi.cfg (only in UEFI mode), or ks_rhel7_uefi.cfg (only in UEFI mode) files are the default names of the answer files to automate an unattended Red Hat Enterprise Linux Server installation. A sample copy of the ks-rhel6.cfg/ks-rhel7.cfg file is provided as part of the DTK download in the /opt/dell/toolkit/template/configs directory. The ks-rhel6.cfg/ks-rhel7.cfg files contain the headings and parameters that instruct the installation utility to perform various configuration tasks. Before a full deployment can be run, edit all appropriate headings and parameters, as necessary.

Depending on the version of the CentOS Server operating system, the ks-centos6.cfg and ks-centos7.cfg, ks_centos6_uefi.cfg (only in UEFI mode), or ks_centos7_uefi.cfg (only in UEFI mode) files are the default names of the answer files to automate an unattended CentOS Server installation. A sample copy of the ks-centos6.cfg/ks-centos7.cfg file is provided as part of the DTK download in the /opt/dell/ toolkit/template/configs directory. The ks-centos6.cfg/ks-centos7.cfg files contain the headings and parameters that instruct the installation utility to perform various configuration tasks. Before a full deployment can be run, edit all appropriate headings and parameters, as necessary.

Depending on the version of the Red Hat Enterprise Linux Server operating system, the ks-rhel6.cfg, ks-rhel7.cfg, ks_rhel6_uefi.cfg (only in UEFI mode), or ks_rhel7_uefi.cfg (only in UEFI mode) files are the default names of the answer files to automate an unattended Red Hat Enterprise Linux Server installation. A sample copy of the ks.cfg/ks-rhel5.cfg/ks-rhel6.cfg/ks-rhel7.cfg file is provided as part of the DTK download in the /opt/dell/toolkit/template/configs directory. The ks.cfg/ks-rhel5.cfg/ks-rhel6.cfg/ks-rhel7.cfg files contain the headings and parameters that instruct the installation utility to perform various configuration tasks. Before a full deployment can be run, edit all appropriate headings and parameters, as necessary.

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 ks-rhel6.cfg (in BIOS mode), and ks_rhel6_uefi.cfg (in UEFI mode). To use the sample ks-rhel6.cfg file to install Red Hat Enterprise Linux Server (version 6) using lininst.sh, ensure that you rename the file to ks.cfg. To use the sample ks_rhel6_uefi.cfg file to install Red Hat Enterprise Linux Server (version 6) using lininst.sh, ensure that you rename the file to ks_uefi.cfg.

NOTE: The sample files provided to install Red Hat Enterprise Linux Server (version 7) are ks-rhel7.cfg (in BIOS mode), and ks_rhel7_uefi.cfg (in UEFI mode). To use the sample ks-rhel7.cfg file to install Red Hat Enterprise Linux Server (version 7) using linins7t.sh, ensure that you rename the file to ks.cfg. To use the sample ks_rhel7_uefi.cfg file to install Red Hat Enterprise Linux Server (version 7) using lininst7.sh, ensure that you rename the file to ks_uefi.cfg.

NOTE: The sample files provided to install CentOS Server (version 6.x) are ks-centos6.cfg (in BIOS mode), and ks_centos6_uefi.cfg (in UEFI mode). To use the sample ks-centos6.cfg file to install CentOS Server (version 6.x) using centinst6.sh, ensure that you rename the file to ks.cfg. To use the sample ks_centos6_uefi.cfg file to install CentOS Server (version 6.x) using centinst6.sh, ensure that you rename the file to ks_uefi.cfg.

NOTE: The sample files provided to install CentOS Server (version 7.x) are ks-centos7.cfg (in BIOS mode), and ks_centos7_uefi.cfg (in UEFI mode). To use the sample ks-centos7.cfg file to install CentOS Server (version 7.x) using centinst7.sh, ensure that you rename the file to ks.cfg . To use the sample ks_centos7_uefi.cfg file to install CentOS Server (version 7.x) using centinst7.sh, ensure that you rename the file to ks_uefi.cfg.

NOTE: See your operating system documentation for instructions on modifying the options in the kick start file to customize the scripted installation of your operating system.

When you have completed all necessary modifications of the kick start file, save the completed file in the /opt/dell/toolkit/systems/ directory.

Preparing the script files 55

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.

CAUTION: It is recommended that you consult your SUSE Linux Enterprise 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 key during reboot.

Utilities used by suseinst

grub Used with the kernel image and initial ramdisk files, along with the unattended answer file to install the operating system in BIOS mode.

grub2 Used with the kernel image and initial ramdisk files, along with the unattended answer file to install the operating system in UEFI mode.

Variables used

DT_OS_DISK Sets the disk on which to deploy the SUSE Linux Enterprise Server operating system.

DT_OS_SRC Sets the location from where to copy the kernel image and initial ramdisk files.

DT_OS_PART Sets the valid partition to install the grub files.

DT_OS_IMG_PATH Sets the network share where the operating system files are located.

DT_SUSE_AUTOINST Sets the network share from where the autoinst.xml file can be accessed.

External dependencies of suseinst.sh

The DT_PLATFORM variable is set during deployment by tkenvset.sh using platform discovery.

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.xml file is provided as part of DTK download in the /opt/dell/toolkit/template/configs directory. The autoinst.xml/autoinst_uefi.xml file contains the headings and parameters that instruct the installation utility to perform various configuration tasks. Before a full deployment can be run, edit all appropriate headings and parameters, as necessary.

NOTE: After installing SUSE Linux Enterprise, change the login password by editing the user node of the root user in autoinst.xml/autoinst_uefi.xml. You can also encrypt the password file by changing false to true in config:type="boolean">false.

NOTE: See your operating system documentation for instructions on modifying the options in the autoinst.xml/autoinst_uefi.xml file to customize the scripted installation of your operating system.

56 Preparing the script files

When you have completed all necessary modifications of the autoinst.xml/ autoinst_uefi.xml file, save the completed file in the /opt/dell/ toolkit/systems/ directory.

After you have successfully edited your deployment scripts, you are ready to create the deployment media and run the deployment. For instructions on creating the deployment media and running a full deployment, see Deployment Using Dell Provided Embedded Linux .

NOTE: During an unattended SUSE Linux Enterprise Server installation, if the installer lists out missing packages, delete the listed packages from autoinst.xml/autoinst_uefi.xml.

Preparing the script files 57

Running the deployment scripts This chapter provides best practices, procedures, and scenarios for using the Deployment Toolkit (DTK) to perform preoperating 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. Before running the deployment, however, create specific deployment media to facilitate your chosen deployment method. The common deployment scenarios are:

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 With A Network Connection (Media-Based) For Systems Running Windows

Deployment Using Removable Boot Media Without A Network Connection (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

Deployment Using Dell Provided Embedded Linux

Deployment Using Customized Embedded Linux

Using A Third-Party Deployment Solution Framework For Systems Running Linux

Topics:

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

Deployment using removable boot media with a network connection media-based for systems running windows For media-based deployment with a network connection:

1 Create a deployment media containing a bootable image with the appropriate media and network drivers, along with any utilities needed to connect to a network share. The deployment media initiates the deployment process by mapping to the network share where the deployment directory structure resides.

2 Insert the bootable media into the appropriate drive of the system to be deployed.

3 Boot or reboot the system.

The configuration process begins and the following tasks are completed:

Windows PE or Linux, as the case may be, is installed from the media.

7

58 Running the deployment scripts

Network shares are mapped.

The DTK scripts execute the necessary DTK utilities from the network share or the media itself.

Configuration information is read from the network share.

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.

For example the media-based deployment methods, the following tasks need to be completed:

Creating and Customizing Images For WinPE 5.1

Integrating The DTK Directory Structure

Creating A Bootable Media For WIN PE 5.1

Running The Image

Creating and customizing images for Windows PE 5.1 If you are using Windows 5.1, download Windows Assessment and Deployment Kit (ADK) from microsoft.com. By default, Windows ADK is copied to the C:\Program Files\Windows Kits directory.

Integrating DTK directory structure DTK provides WINPE5.x_driverinst.BAT (for Windows PE 5.1), and WINPE10.x_driverinst.BAT scripts to pre-install the Dell drivers into a base Windows PE 5.1 and Windows PE 10.0 images. To execute the script (for example, WINPE10.x_driverinst.BAT) on 64-bit systems:

NOTE: Make sure that you have administrator privileges before running the scripts.

1 At the command prompt, type the following command to change the directory to the location of the script, WINPE10.x_driverinst.BAT : cd C:\Dell\x64\Drivers\winpe10.x

2 Execute the script: WINPE10.x_driverinst.BAT where < WIMPATH> is the destination path to create the directory structure for Windows PE and < DTKPATH> is the path for the Dell drivers in the extracted DTK toolkit. For example, WINPE10.x_driverinst.BAT C:\winpe_10 C:\DELL\x64\DRIVERS.

This pre-installs the Dell drivers into Windows PE image. The successful execution of the above commands creates a bootable ISO image for Windows PE 5.1 and 10.0 at <WIMPATH>.

NOTE: The destination folder (C:\winpe_10) 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 5.1 To create a bootable media:

1 Click Start and navigate to All Programs > Microsoft Windows ADK.

2 Click Windows PE Tools Command Prompt to open a command prompt window.

Running the deployment scripts 59

3 Navigate to C:\program files\Windows AIK\Tools\amd64 directory on the system.

4 Execute the script: WINPE5.0_driverinst.bat where < WIMPATH> is the destination path to create the directory structure for Windows PE and < DTKPATH> is the path for the Dell drivers in the extracted DTK toolkit. For example, WINPE5.0_driverinst.bat C:\winpe_50 C:\DELL\x64\DRIVERS.

This pre-installs the Dell drivers into Windows PE image. The successful execution of the above commands creates a bootable ISO image for Windows PE 5.0 at <WIMPATH>.

NOTE: The destination folder (C:\winpe_50) 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_50\etfsboot.com c:\winpe_50\ISO c: \winpe_50\WinPE5.0.iso WinPE5.1 iso, a media bootable ISO image is created.

You can use any CD or DVD burning software to burn the image onto a CD or DVD. After burning the ISO image, ensure that it boots from the CD or DVD drive for all the supported Dell systems you plan to deploy. After it boots, you are advised to test all the tools and scripts on these systems to make sure that the integration is successful and that there are no issues with hardware components not being recognized.

Running the image You are now ready to use your bootable media to access the deployment components from the directory structure on the media:

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 media to complete the deployment process.

Media-Based local deployment with Networking enabled for systems running windows This method provides greater flexibility and is highly recommended in large deployments. The pre-requisites are the availability of network bandwidth and all target systems connected to the network.

NOTE: DTK network-based deployment is not supported from mapped Novell NetWare systems.

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 recreation 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.

Bootable Windows PE media with Networking enabled This process includes:

Creating a bootable Windows PE media with the appropriate network drivers. This step enables Networking services to start, get an IP address, and bring the target system into a functioning network.

NOTE: For more details on how to create a customized version of a single Windows PE bootable media that works across all Dell supported systems and provides an underlying Networking stack, see Running The Deployment Scripts.

Creating scripts to automatically map to a predefined network share.

Accessing scripts, configuration files, and operating system installation files from the network.

60 Running the deployment scripts

Preparing and populating the network share This process includes:

Creating a network share on a system that is always available over the network for the target systems to be deployed.

Ensuring that a large amount of space is available for storing operating system installation files.

Ensuring that proper permissions are assigned to this share so that the target systems can read files from and write files to the share.

You can also use the bootable media to call the deployment components from the directory structure on the media and the remaining components from the network share.

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 media-based 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. The media must also include the complete deployment directory structure, which contains all DTK utilities, scripts, and configuration files, an operating system installation answer file, and the required operating system installation files and drivers.

2 Insert the bootable media into the media drive of the system to be deployed (the target system).

3 Boot or reboot the target system.

The deployment process begins and the following tasks are completed:

Windows PE or embedded Linux, as the case maybe, is installed from the media.

The DTK scripts execute the necessary DTK utilities from the media.

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).

Using a third-party deployment solution framework for systems running windows You can use DTK with any existing third-party deployment solution framework that provides an Automated Deployment Services (ADS) booting infrastructure for Windows Deployment Services (WDS). Because each third-party deployment framework is unique, these solutions fall outside the scope of this document. If you plan to utilize a third-party deployment solution framework, keep in mind that DTK is a Windows PE-based set of tools and scripts, so the deployment solution framework must also support Windows PE as a pre-operating system environment.

Running the deployment scripts 61

Using Windows Pre-installation Environment driver CAB files for systems running Windows DTK boot-critical drivers are now available in the Windows Preinstallation Environment (WinPE) driver Cabinet (CAB) files at dell.com/ support. You can use the WinPE driver CAB files with deployment tools such as Dell Server Deployment Pack and System Center Virtual Machine Manager for OS deployment. You can download the WinPE driver CAB files depending on the WinPE environment, and use the available custom scripts to install the extracted drivers from the CAB files in the WinPE environment.

Deployment using Dell provided embedded Linux The two common scenarios for deployment using Dell provided embedded Linux are following:

Network Based Deployment

Media Based Deployment

Network-based deployment The two common scenarios for network-based deployment are:

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 Set up the Hypertext transfer protocol (HTTP) or Network file system (NFS) services and the Dynamic Host Configuration Protocol (DHCP) services on your network to boot the target system using PXE.

3 In BIOS mode, copy the contents of the embedded Linux DTK ISO image (SA.1, SA.2, and isolinux.cfg) from /mnt/cdrom/isolinux to the NFS share folder for booting DTK via NFS or to any destination folder to boot via HTTP protocol. In UEFI mode, copy the contents of the embedded Linux DTK ISO image (SA.1 and SA.2), from /mnt/cdrom/isolinux to the either NFS share folder or to any destination folder based on the protocol.

4 Edit the configuration file (isolinux.cfg for BIOS or efidefault for UEFI mode) by providing the following options:

IP address of the network share

Share path of the network share

Name of your startup script

The isolinux.cfg/efidefault file is ready for PXE-booting.

5 Copy isolinux.cfg file into the PXE configuration folder.

6 Create your own start-up script and place it in the network share specified in your modified isolinux.cfg/efidefault file.

The modified script is picked up and executed during the boot process.

NOTE: The network share on which you have the scripts and DTK files are mounted to /opt/dell/toolkit/ systems.

NOTE: Ensure that you specify the correct RAMDISK size in the PXE config file before booting through PXE. A sample pxe config file is provided in /mnt/cdrom/isolinux/isolinux.cfg.

62 Running the deployment scripts

Network file system or SMBFS file system based deployment

The procedure enables you to boot DTK and launch the start-up script automatically from a network share (NFS or SMBFS).

1 Obtain the ISO image of the embedded Linux available 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 script to a share (nfs/smbfs).

4 In UEFI mode, modify the corresponding shared section (nfs/smbfs) in EFI/BOOT/dtk_grub.cfg and create iso using mkisofs. For BIOS mode, modify the corresponding shared section (nfs/smbfs) in isolinux/isolinux.cfg and create iso using mkisofs as follows: mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load- size 4 -boot-info-table -pad -r -J -hide-joliet- trans-tbl -eltorito-alt-boot -e efiboot.img -no-emul-boot isoimage

NOTE: It is important to use mkisofs to make your customized image because the ISO Linux recognizes only the isolinux.cfg (and all files within /isolinux). If you do not use mkisofs, the HAPI libraries of the DTK cannot load and most of the Dell Update Packages do not work.

NOTE: The scripts that you copy into the media are copied to the RAM disk and run from the RAM disk. This task is done to make sure that the media is not locked. Ensure that your sample scripts have valid path names.

5 Burn the ISO contents to a media.

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.

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 systems installation process.

4 In /mnt/cdrom/isolinux/isolinux.cfg (for BIOS mode) or in /mnt/cdrom/EFI/BOOT/dtk_grub.cfg (for UEFI mode), edit the cd install section to point to your customized start-up script. In other words, add the share_script option and then use mkisofs to create the ISO image as follows:

mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load- size 4 -boot-info-table -pad -r -J -hide-joliet-trans-tbl -eltorito-alt-boot -e efiboot.img -no-emul-boot isoimage

NOTE: It is important to use mkisofs to make your customized image because the ISO Linux recognizes only the isolinux.cfg (and all files within /isolinux). If you do not use mkisofs, the HAPI libraries of the DTK cannot load and most of the Dell Update Packages do not work.

NOTE: The scripts that you copy into the media are copied to the RAM disk and run from the RAM disk. This task is done to make sure that the media is not locked. Ensure that your sample scripts have valid path names.

Running the deployment scripts 63

5 Burn the ISO contents to a media.

6 Your ISO image is ready for booting.

Using RPMs

You can install DTK using Red Hat Package Manger (RPM), Yellowdog Updater, Modified (YUM) or any other RPM Installation Manager, or using DTK tools.

Installing DTK RPMs using RPM

To install DTK RPMs using RPM:

1 Mount the DTK media at /mnt/cdrom.

2 Navigate to the /mnt/cdrom/RPMs directory.

NOTE: The /mnt/cdrom/RPMs directory contains all DTK RPMs and the dependency RPMs.

3 Install the required DTK RPMs.

NOTE: To resolve the RPM dependency related issues, install the missing RPMs from /mnt/cdrom/RPMs directory. If the RPMs are not available in this directory, install these RPMs from the operating system media.

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.repo file:

[DTK_RHEL6] name=DTK_RHEL6 baseurl=file:///mnt/cdrom/RPMs/rhel6/ enabled=true

4 Use the following command to install DTK RPMs: yum install -c dtk.repo -y , where < RPM> can be DTK binaries.

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 Install the required DTK RPMs using dtktools-setup.sh.

NOTE: To resolve the RPM dependency-related issues, install the missing RPMs from the /mnt/cdrom/SYSMGMT/ srvadmin/linux/RPMS directory. If the RPMs are not available in this directory, install these RPMs from the operating system media.

64 Running the deployment scripts

Post installation of RPMs

After installing the RPMs, perform the following:

1 For the binaries syscfg and raidcfg, export the PATH environment variable /opt/dell/toolkit/bin.

2 To start the services, navigate to /opt/dell/srvadmin/sbin, and type: srvadmin-services.sh start

NOTE: If the services are already running, restart the services.

NOTE: To execute the commands to configure the system as per the requirements, see the Dell EMC OpenManage Deployment Toolkit Command Line Interface Reference Guide available at dell.com/openmanagemanuals.

Deployment using USB

1 Download the ISO image of the embedded Linux from www.dell.com/support.

2 Download any third-party USB creator tool.

3 Install and launch the tool.

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.

Serial port configuration utilities (setserial and stty) for racadm.

Installed and working instrumentation drivers from /mnt/cdrom/tools.

Point-to-Point Protocol (PPP) tools.

Basic libraries and utilities for Linux to execute customized scripts.

Installed DTK and the dependency RPMs.

Necessary entries in the ld.so.config file so that the libraries are installed.

Integrate all the above mentioned libraries, Dell toolkit libraries, tools, and utilities into your embedded Linux environment and proceed with deployment.

NOTE: For more information on how Dellprovided utilities and drivers are installed, see start-stage3.sh, start-hapi.sh, or start- raid.sh available in /mnt/cdrom/tools.

NOTE: The /opt/dell/srvadmin/sharedand /opt/dell/srvadmin/hapi directories must have read-write permissions. For more details, see start-stage3.sh and start-hapi.sh.

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. If you plan to utilize a third-party deployment solution framework, make sure that the deployment solution framework supports embedded Linux as a pre-operating system environment.

Running the deployment scripts 65

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

Topics:

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 EMC Server Updates DVD or from www.dell.com/support.

2 Save the update packages on a network share.

3 Mount the network share where you saved the update packages and run the individual packages.

NOTE: See the Dell EMC Update Packages User's Guide available at dell.com/openmanagemanuals for help on using Dell Update Packages and information on error codes.

Running update packages in customized embedded Linux Before running update packages in customized embedded Linux environment, ensure that you meet the dependencies listed in the following table.

Table 28. Dependencies for Dell Update Packages to Run in Customized Embedded Linux

Update Packages Dependency Dependencies Available On

BIOS Instrumentation drivers

dell_rbu

/mnt/cdrom/tools

Kernel

ESM Instrumentation drivers /mnt/cdrom/tools

PERC /etc/dataeng

megaraid driver 2.4.2.0

SCSI drivers

/mnt/cdrom/tools

/mnt/cdrom/tools

Kernel

8

66 Running Dell update packages on systems running embedded Linux

Update Packages Dependency Dependencies Available On

RAC 5 Instrumentation drivers /mnt/cdrom/tools

iDRAC Instrumentation drivers /mnt/cdrom/tools

PowerVault 220S SCSI drivers Kernel

SAS SAS drivers Kernel

Any Update Package RPMs

sysvinit

grep

sed

awk

less

fmt

tar.gz

compat-libstdc

proc-mail

libxml2

Linux media or any open source website

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.

Running Dell update packages on systems running embedded Linux 67

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.

Topics:

Known issues

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.

RAIDCFG issues Due to a rounding limitation for RAID 0, RAID 1, and RAID 5, when creating a virtual disk, RAIDCFG can accept a disk size that is 1 MB

greater than the maximum allowable virtual disk size limit. However, RAIDCFG creates the maximum virtual disk size and does not display an error. If you want to use the maximum allowable virtual disk size, it is recommended that you do not provide the size in the CLI and let RAIDCFG calculate the size for the RAID type.

SYSCFG issues Setup passwords and system passwords cannot be cleared using DTK on systems prior to PowerEdge 12G systems.

Windows PE installation issues If virtual flash is enabled and does not contain a valid image (for example, if the virtual flash contains a corrupt or random image), you

may not be able to install Windows Server 2008 locally or remotely. To fix this issue, install a valid image on virtual flash or disable virtual flash if it is not used during the installation procedure.

Embedded Linux installation issues If internal SD card is present in the server, you may not be able to install the operating system using default partition. To fix this, remove

the SD card from the server.

9

68 Known issues and frequently asked questions

Frequently asked questions The following questions are organized by DTK utility or other function.

General deployment questions Q: While running SYSCFG.EXE on a Windows PE image, the SYSCFG.EXE tool silently fails.

A: Ensure that you have built your Windows PE image with the /WMI option. For more details, see Running The Deployment Scripts.

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. If you are deploying multiple systems, for example, provide unique information for each system when appropriate. To perform this task, modify each .ini (or other configuration script) file to reflect the unique information for each system you are deploying (such as the remote access controller (RAC) IP addresses and BIOS asset tags). There are many options available to optimize this process and it is suggested that you conduct an Internet search for available tools.

Q: When I change my hard drive controller from SCSI to RAID (or RAID to SCSI), the system prompts me for confirmation during POST. How can I stop this from happening?

A: Use the --noraidprompt option with the --embscsiraid option to prevent the system from prompting during POST. Data loss results from changing the state of the disk controller, so you must be certain before skipping the prompt. There is no method for using the noraidprompt in the input file. If you want to change the controller state through an input file, you must configure your script to call the SYSCFG.EXE utility twice, once to specify the input file, and once to change the controller state with the --noraidprompt option.

Q: What do I do if the PARTCFG script fails?

A: Ensure that DT_HD is set to the required disk to be configured before you execute the PARTCFG script.

Q: Pre-Boot Environment is not supported while booting DTK on TFTP boot method as this protocol is not supported for stage-2 booting process.

A: On some Dell PowerEdge 12th and 13th generation system servers, booting DTK using internal DVD drive in the UEFI mode may not boot as the drivers are not carried.

RAIDCFG questions Q: Why does RAIDCFG display an error message when I use an invalid read, write, and cache policies and/or stripe sizes for a particular controller?

A: All RAID controllers have their own default read, write, and cache policies and stripe sizes. It is possible that if you provide an invalid policy or a stripe size for a particular controller, RAIDCFG may not give an error but creates the virtual disk with the default policy and/or stripe size.

Q: When I execute RAIDCFG with the RAID level of "01," RAIDCFG creates RAID 1, not RAID 01.

A: This behavior occurs because the RAIDCFG CLI parser ignores zeros preceding any parameter value. For example, -r=01 is parsed as - r=1.

Known issues and frequently asked questions 69

Q: What is strict creation?

A: Strict creation is an optional flag that has been added to the create virtual disk command. It allows you to create virtual disks only if the array disks (that is, hard drives) are within a specified percentage of disk space of each other.

Q: Why is the drive location of array disks displayed like 0:0:0?

A: The nexus used to display array disks is "channel:target:lun." The Logical Unit Number (LUN) is always "0." The channel and the target IDs are necessary to identify array disks when dealing with SCSI devices.

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. The mandatory fields required to create virtual disks are the controller slot ID and the array disks.

Q: What is a hot spare (failover drive)?

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 features have changed from the MS-DOS version of RAIDCFG to the Windows PE and embedded Linux versions?

A: Windows PE and embedded Linux version of RAIDCFG support new controllers. For the list of supported controllers, see Dell EMC Systems Software Support Matrix at dell.com/openmanagemanuals.

Features that have been removed from the MS-DOS version include:

The --name and --wait options in the create command

The --runlocation and the --scratchlocation options

The --getpercentcomplete environment variables

Q: Why cannot I see any controllers using RAIDCFG?

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: PARTCFG cannot enumerate the virtual disks created by RAIDCFG. What must be done?

A: A reboot is required for PARTCFG to enumerate virtual disks after creating a virtual disk using the RAIDCFG command.

SYSCFG questions Q: Can I use the SYSCFG utility to configure Point-to-Point Protocol (PPP) over the serial port to access my RAC?

70 Known issues and frequently asked questions

A: No. The Baseboard Management Controller (BMC) firmware does not support PPP configurations for the serial port.

Q: The SYSCFG utility --lancfgparams option has suboptions that configure the IP address, Gateway, and Subnet Mask for the system BMC. There is also a MAC address. Are these the same as the operating system network parameter of the managed system?

A: No. The Baseboard Management Controller (BMC) has its own IP address, Gateway, Subnet Mask, and MAC address values.

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. Remote login using a NULL username is not allowed. It is recommended that you always provide a non-null, valid username for the user ID when you enable a BMC user ID.

Q: Are duplicate usernames allowed in the BMC?

A: No. If you enter a username value that already exists, the SYSCFG utility returns an error code of 89, which means This username is already in use. Enter a unique username.

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.

Embedded Linux questions Q: After installing Linux, I am not able to boot to the utility partition by pressing the key during reboot.

A: Re-create the utility partition using the upinit.sh script and install grub in the boot partition.

Q: When booting DTK through PXE, my system displays error messages, unknown behavior, and also leads to a kernel panic sometimes. However, booting from the media causes no problems.

A: Ensure that you specify the correct RAMDISK size in the pxe config file before booting through PXE. A sample pxe config file is provided in /mnt/cdrom/isolinux/isolinux.cfg.

Q: Can we use the same sample scripts that we have from earlier versions of DTK?

A: The scripts written for the previous versions of DTK do not work in the later versions for embedded Linux. For the sample scripts, see the directory /opt/dell/toolkit/template/scripts .

Q: After the DTK deployment is complete, the Red Hat Enterprise Linux Server installation keeps going into attended mode or halts with the message ks.cfg not found.

A: If the initrd.img is not available in the operating system, get the latest update of Red Hat Enterprise Linux Server or prepare driver disks for your network or disk controller.

Known issues and frequently asked questions 71

Q: How to apply driver disks during operating system installation?

A: You can apply driver disks as follows:

1 During operating system installation, after the first reboot, attach the driver-disk.iso file to the DVD-ROM or virtual media.

2 At the grub prompt, press

followed by

and, then press . 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 Delete the entry: Run efibootmgr -b XYZ B Q: Is Fiber channel cards work with DTK pre-boot environment? A: No, there is no ether-net feature and also firmware update may not work. 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. The dynamic-link library (DLL) file can be copied to the correct location of the installation by placing it in the I386\$Oem$\$$\OEMDIR folder. (OEMDIR is the destination folder where the file would normally be located, if installed to a running operating system. For example, INF files are normally found in the %SystemRoot%\INF folder. The correct OEMDIR destination can be found by searching the INF file used to install the device or driver.) For more information, see Microsoft Knowledge Base Article 275334 available at Microsoft website. Q: In Windows, I see a blue screen when I delete a virtual disk and create a new one without initialization and attempt to format the disk. A: Initialize (fast init) the drives before formatting the disk. This prevents the issue.

Manualsnet FAQs

If you want to find out how the OpenManage Connection Dell works, you can view and download the Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide on the Manualsnet website.

Yes, we have the User's Guide for Dell OpenManage Connection as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The User's Guide should include all the details that are needed to use a Dell OpenManage Connection. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell OpenManage Connection Deployment Toolkit V6.2 Software User's Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.