Dell External OEMR 2850 User Manual
  1. Manuals
  2. Brands
  3. Dell Manuals
  4. Software
  5. External OEMR 2850
  6. User manual

Dell External OEMR 2850 User Manual

User guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Dell™ OpenManage™
Deployment Toolkit
User's Guide
w w w . d e l l . c o m | s u p p o r t . d e l l . c o m

Advertisement

Table of Contents
loading

Related Manuals for Dell External OEMR 2850

Summary of Contents for Dell External OEMR 2850

  • Page 1 Dell™ OpenManage™ Deployment Toolkit User’s Guide w w w . d e l l . c o m | s u p p o r t . d e l l . c o m...
  • Page 2 Use the sample scripts at your own risk. Dell shall not be liable for any direct or indirect damages incurred in using the sample scripts. In no event shall Dell or its suppliers be responsible for any direct or indirect damages whatsoever (including, without...

  • Page 3: Table Of Contents

    Deploying ..... . Other Dell Documents You Might Need ..Other Supporting Documents You Might Need .
  • Page 4 Choosing a Microsoft Windows PE-Based Deployment Method ....Choosing a Deployment Method for Microsoft Windows PE ....CD-Based Local Deployment .
  • Page 5 Setting Up a Directory Structure for Deployment ..... DTK Utilities and Files ....System-Specific Files .
  • Page 6 Preparing the Operating System Installation Scripts for Windows PE ....WININST.BAT ....UNATTEND.TXT .
  • Page 7 Documentation ....Drivers and Dell Real Mode Kernel (DRMK) ....
  • Page 8 ....Configuring a Source System ....How to Obtain Dell Utility Partition Files ..RAC Configuration .
  • Page 9 Running Deployment Scripts Using DTK and Embedded Linux ..Deployment Using Dell-Provided Embedded Linux ....Deployment Using Customized Embedded Linux .
  • Page 10 10 Running Dell Update Packages in Embedded Linux ....Running Update Packages in Dell-Provided Embedded Linux ...

  • Page 11: Introduction

    Introduction The Dell™ OpenManage™ Deployment Toolkit (DTK) includes a set of utilities for configuring and deploying Dell systems. The DTK is designed for customers who need to build scripted installations to deploy large numbers of systems in a reliable fashion without having to dramatically change their current deployment processes.

  • Page 12: Introduction Tox The Dtk User's Guide

    Users might find many alternative solutions to the best practices guidelines described in this guide and many additional uses for the DTK utilities beyond what is covered in this guide or in the Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide. CAUTION:...
  • Page 13 Scripts Using DTK and Using DTK and Embedded Linux" • Creating deployment media Microsoft Windows • Running the deployment PE" Running Dell Update Packages in Not applicable "Running Dell Update the embedded Linux environment Packages in on supported Dell systems. Embedded Linux"...

  • Page 14: What's New

    Support for new Dell systems NOTE: For the list of Dell systems supported for this version of DTK, see the readme.txt file in the root folder, or the Dell Systems Software Support Matrix on the Dell Systems Management Tools and Documentation DVD or on the Dell Support website at support.dell.com.

  • Page 15: Supported Operating Systems To Run Dtk Utilities

    Server (version 4, update 4) 32-bit. Supported Systems For the list of Dell systems supported for this version of DTK, see the readme.txt in the root folder, or the Dell Systems Software Support Matrix on the Dell Systems Management Tools and Documentation DVD or on the Dell Support website at support.dell.com.

  • Page 16: Deployment Prerequisites

    • All DTK utilities, sample scripts, and sample configuration files • All other utilities and files necessary to perform the deployment, including all required Windows PE drivers, operating system drivers, and the Dell utility partition image file • DTK documentation: –...
  • Page 17 The Dell Systems Management Tools and Documentation DVD • NOTE: You can also obtain the latest drivers from the Dell Support website at support.dell.com. • Your operating system software and documentation • An optimally configured source system with network access...

  • Page 18: Deploying Operating Systems

    The DTK, on the other hand, offers a complete set of utilities and sample scripts that can be used to automate deployment of large numbers of Dell systems. This guide is designed to help guide you through some of the most basic planning considerations, logistical preparations, and deployment procedures to get you started using the DTK to deploy Dell systems.

  • Page 19: Dtk Deployment Overview

    3 Set up an optimally configured source system by using the Dell Systems Build and Update Utility to install your operating system; and the Systems Service and Diagnostics Tools to load drivers.
  • Page 20 Service and Diagnostics Tools on the Dell Systems Management Tools and Documentation DVD to load drivers. NOTE: You can also obtain the latest drivers from the Dell Support website at support.dell.com. 4 Install an operating system on a target system.

  • Page 21: Deploying

    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 the DTK utilities to deploy Dell systems, this guide focuses on the two most common methods for Windows PE and embedded Linux: CD-based deployment (local) and network-based deployment (remote).
  • Page 22 Deployment Using Removable Boot Media Without a Network Connection (CD-Based) 1 Create a deployment CD containing a bootable image with the appropriate drivers. The CD must also include the complete deployment directory structure, which contains all the DTK utilities, scripts, and configuration files, an operating system installation answer file, and the required operating system installation files and drivers.

  • Page 23: Other Dell Documents You Might Need

    Interface Reference Guide, both of which are available as part of the DTK download and on the Dell Support website at support.dell.com, you can find the following guides either on the Dell Support website or on the on the Dell Systems Management Tools and Documentation DVD: •...

  • Page 24: Other Supporting Documents You Might Need

    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. Additionally, the Deployment Toolkit readme.txt file, which is available as part of the DTK download and on the Dell Support website at support.dell.com, provides the latest available information for the...

  • Page 25: Obtaining Technical Assistance

    For more information about these help tools, see "Getting Help" in your system's Hardware Owner's Manual. Additionally, Dell Enterprise Training and Certification is available; see www.dell.com/training for more information. This service may not be offered in all locations. Introduction...
  • Page 26 Introduction...

  • Page 27: Choosing A Microsoft Windows Pe-Based Deployment Method

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

  • Page 28: Cd-Based Local Deployment With Networking Enabled

    See "Running Deployment Scripts Using DTK and Microsoft Windows PE" for details on how to create a customized version of a single Windows PE image that can work across all supported Dell systems. You must include Dell-customized drivers and instrumentation drivers into your Windows PE CD-based operating system.

  • Page 29: Using A Third-Party Deployment Solution Framework

    See "Running Deployment Scripts Using DTK and Microsoft Windows PE" for details on how to create a customized version of a single Windows PE bootable CD that works across all Dell supported systems and provides an underlying networking stack. •...

  • Page 30: Deployment Matrix (Windows Pe)

    document. If you plan to utilize a third-party deployment solution framework, keep in mind that the DTK is a Windows PE-based set of tools and scripts, so the deployment solution framework must also support embedded Windows PE as a pre-operating system environment. Deployment Matrix (Windows PE) Depending on the scope, current business needs, network setup, and process, you might select any of the suggested methods of deployment.
  • Page 31 Table 2-1. Deployment Method Matrix (continued) Deployment Complexity Advantages Disadvantages Methods Remote Moderate • Everything is in one place • Must have deployment over a in a network share. network network (bootable connection. • Easy to manage— Windows PE CD changes have to be made •...
  • Page 32 Choosing a Microsoft Windows PE-Based Deployment Method...

  • Page 33: Preparing The Directory Structure

    DTK. This step is necessary because the environments and requirements for DTK version 3.x are completely different. Obtaining DTK The DTK components are provided in a self-extracting zip file on the Dell™ Support website at support.dell.com. The self-extracting file can be opened ®...
  • Page 34 Perform the following steps to extract the DTK components to a workstation running Windows: 1 Download the DTK file DTK3.X-WINPE-XX.exe from the Dell Support website at support.dell.com and save it anywhere on your system. 2 After the file downloads, double-click the file.
  • Page 35 The DTK utilities are in Z:\Dell\Toolkit\Tools. The DTK sample scripts are in Z:\Dell\Toolkit\template\scripts. The DTK sample configuration files are in Z:\Dell\Toolkit\template\Configs. The DTK User’s Guide and Command Line Interface Reference Guide are in Z:\Dell\Toolkit\Docs. Preparing the Directory Structure for Deployment in Microsoft Windows PE...

  • Page 36: Dtk Contents

    The DTK contains Windows PE-based utilities, sample scripts, sample configuration files, drivers, and documentation for automating the deployment of Dell systems. The following sections provide a complete list of the DTK contents and a short description of each component. For a more complete explanation of the DTK utilities, see the Command Line Interface Reference Guide.
  • Page 37 Table 3-1. System Utilities and Supporting Files (continued) Toolkit Components Purpose iDRAC Configures iDRAC6. NOTE: This feature may not be supported on all systems. racadmErrorCodes.txt Lists the error codes and messages for the RACADM.EXE tool. RAIDCFG.EXE Creates and reports Redundant Array of Independent Disks (RAID) information.

  • Page 38: Sample Configuration Files

    Sample Configuration Files Table 3-2 describes examples of configuration files used to perform a scripted deployment. These files are located in Z:\Dell\Toolkit\template\Configs folder. 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.

  • Page 39: Sample Scripts

    Some customers may need to develop their own scripts entirely from scratch. Customers deploying multiple systems must provide unique information for each Dell system where appropriate. For example, system host names, IP addresses, and BIOS asset tags need to be unique for each system.
  • Page 40 MOUNTUP .CFG This file is used by UPINIT.BAT. PARTCFG.BAT Creates and populates the Dell utility partition and creates the operating system partition on a specified hard drive. Before doing so, however, this script cleans out all existing partitions in your system.

  • Page 41: Documentation

    Documentation Table 3-4 describes documents containing reference information for each DTK utility and instructions for using the DTK utilities and sample scripts. Documentation can be found at Z:\Dell\Toolkit\Docs. Table 3-4. Documentation Toolkit Components Purpose...

  • Page 42: Drivers

    Recommended drivers for NICs. common\RAC 4 Essential drivers for RACADM to work. common\RAIDCFG Essential drivers for RAIDCFG to work. Miscellaneous The document readme.txt, located at Z:\Dell\Toolkit, provides the latest product information. Preparing the Directory Structure for Deployment in Microsoft Windows PE...

  • Page 43: Other Supporting Tools And System Files

    Other Supporting Tools and System Files While the DTK provides all the necessary utilities and scripts for deploying Dell systems, there are additional applications, utilities, and system files needed to create the pre-operating system environment in which this toolkit is used. Table 3-6 is a matrix of system files and other tools for you to be able to use the DTK utilities and its sample scripts.
  • Page 44 UNZIP.EXE and will be copied to that it supports the -d option to extract the windows\system32 contents to a specified folder by the dell directory. driver installation script VPE_Driveinst.bat for Windows PE 2.0. upimg.bin...

  • Page 45: Setting Up A Directory Structure For Deployment

    (where necessary) to reflect the different directory structure. A 32-bit unzip utility is needed to create the Dell utility partition. Ensure that you copy this utility into one of the path directories of your Windows PE 1.0 image, preferably \I386\system32;...

  • Page 46: System-Specific Files

    System-Specific Files The directory Z:\Dell\Toolkit\Systems acts as a central repository for all the system-specific deployment information. For example, you can store all profile configuration files for an optimally configured PowerEdge™ 2850 in the directory Z:\Dell\Toolkit\Systems\pe2850. See Figure 3-2. These files can then be accessed from this directory when deploying multiple PowerEdge 2850 systems.
  • Page 47 Figure 3-2. DTK System-Specific File Structure Preparing the Directory Structure for Deployment in Microsoft Windows PE...

  • Page 48: Operating System Installation Files

    Operating System Installation Files Figure 3-3. Sample Operating System-Specific File Structure (Windows Server 2003) Preparing the Directory Structure for Deployment in Microsoft Windows PE...
  • Page 49 3 Create two folders Dell and W2K3SRC under this shareable directory os_deploy. 4 Copy the Dell folder from WinPE DTK CD to Dell folder created under os_deploy folder on the management station. 5 Copy i386 folder from the Windows Server 2003 operating system CD to the W2K3SRC folder created under the os_deploy folder on the management station.
  • Page 50 PERC 5, you must retain the following vers entry and remove the rest of the entries under the field MassStorageDrivers. DELL PERC5 RAID Controller Driver (Server 2003 for x64)"="OEM" 10 Boot the server with the WinPE DTK media. 11 After WinPE comes up make sure that the server is able to ping the management station.
  • Page 51 14 Navigate to the mount point z:\\<share>\dell\toolkit\template\scripts, and run the partcfg.bat script to create the partition and then run the following to install the operating system: wininst.bat NET 15 Reboot the server once you are at the command prompt and the system starts booting to the hard drive for operating system installation.

  • Page 52: Configuring A Source System

    11 From your system, run TKENVSET.BAT under Z:\Dell\Toolkit\template\scripts 12 On your system, set DT_DRIVE=Z: 13 Navigate to Z:\Dell\Toolkit\template\scripts and run W2K8INST.BAT. Figure 3-4. Sample Operating System-Specific File Structure (Windows Server 2008) 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.

  • Page 53: Rac Configuration

    Dell OpenManage™ systems management software. NOTE: You can also obtain the latest drivers from the Dell Support website at support.dell.com. For complete information about using the Systems Build and Update Utility...
  • Page 54 Preparing the Directory Structure for Deployment in Microsoft Windows PE...

  • Page 55: Preparing The Script Files For Deployment Using Microsoft

    Preparing the Script Files for Deployment Using Microsoft Windows PE This section describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment of a target system in the ® ® Microsoft Windows PE environment. There are four main tasks: •...

  • Page 56: Using The Sample Dtk Scripts To Run A Full Deployment In Windows Pe

    Using the Sample DTK Scripts to Run a Full Deployment in Windows PE The Master Batch File (DEPLOY.BAT) A scripted DTK deployment relies on the master batch file (DEPLOY.BAT) to integrate all the applicable DTK task scripts and utilities and perform pre-operating system configuration tasks before launching the operating system installation files.

  • Page 57: Editing The Sample Batch Files To Perform A Complete System Deployment In Windows Pe

    ***************************************************** :: 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 ::new hdd device number.
  • Page 58 Table 4-1. Scripts For Deployment Capture Scripts Replication Scripts Deployment Scripts Others RACCAP .BAT — RACREP .BAT — WININST.BAT — TKENVSET.BAT Captures RAC Applies the RAC Performs an — Sets the path of settings to a file for configuration unattended the DTK installation DRAC 4.
  • Page 59 Table 4-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts Deployment Scripts Others SYSCAP .BAT — SYSREP .BAT — W2K8INST.BAT— RAIDCFG.BAT — Captures BIOS and Applies the BIOS Performs an Configures the BMC configuration and BMC settings unattended selected Redundant settings and saves saved in a file to the installation of...
  • Page 60 RAIDREP .BAT— PARTCFG.BAT — Captures the RAID Applies the RAID Creates and settings and saves settings saved in a populates the Dell™ them to a file. file to the current utility partition (UP) system. and the operating • TKENVSET.BAT system partition on a •...
  • Page 61 Capture Scripts Replication Scripts Deployment Scripts Others • UPINIT.BAT— Used by PARTCFG.BAT to create and populate the Dell utility partition. • FORMAT.EXE — Provided by Windows to format the partition. Preparing the Script Files for Deployment Using Microsoft Windows PE...
  • Page 62 Table 4-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts Deployment Scripts Others UPINIT.BAT — Creates and populates the Dell utility partition. NOTE: Do not make any modifications to the UPINIT.BAT script. • TKENVSET.BAT — Used by UPINIT.BAT to inform the task...
  • Page 63 Replication Scripts Deployment Scripts Others • UPIMG.BIN — DTKRUNALL. BAT— Applies Contains the BIOS, BMC, RAC, zipped contents of and RAID settings the Dell utility saved in the files to partition. the current system. • SYSDRMK.EXE • TKENVSET.BAT — Used by UPINIT.BAT to —...

  • Page 64: Tkenvset.bat

    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 by default in the sample script. Edit this path to reflect the actual location of the DTK deployment files, if necessary.
  • Page 65 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 by default in the sample script. 5 Set the variable that defines the directory containing the DTK deployment scripts (DT_SCRIPTS).
  • Page 66 :: RAC section set 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 ( ) is set to DT_PARTN PARTCFG.BAT, the partitioning deployment state subsection is skipped.
  • Page 67 Perform the following steps to edit the default partition configuration default values, as necessary. 1 Edit the default utility partitioning variable (DT_PARTN_UP=ON), if necessary. This variable sets whether you want to install the Dell utility partition. NOTE: Dell recommends that you install the Dell utility partition.

  • Page 68: Editing Dtk Task Scripts

    4 Edit the default variable value for file system type (DT_OS_FSTYPE= FAT32), if applicable. NOTE: The valid values are FAT32 and NTFS. 5 If the DT_PART_UP variable is set to ON, edit the default variable value (in MB) for the utility partition (DT_UP_SIZE=32), if applicable. 6 If the DT_PART_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), if applicable.
  • Page 69 passed, the default variables values used in this script are set in the TKENVSET.BAT scripts. An optional second parameter can be passed to this file, which specifies the IP address to be used to configure the RAC. The raccfg.ini file is generated with the RACCAP .BAT sample script. See "RACCAP .BAT"...

  • Page 70: Using The Dtk Sample Scripts To Capture Configuration Information In Windows Pe

    Capturing the System BIOS and BMC Configuration With the SYSCAP.BAT Sample Script You can replicate the system BIOS and BMC configurations from a source Dell system to an identical target Dell system (for example, from one PowerEdge™ 1850 to another PowerEdge 1850). NOTE: For the script to complete successfully, the source system must have access to the network share that includes the prebuilt DTK directory structure.

  • Page 71: Capturing The Rac Configuration With The Raccap.bat Sample Script

    Capturing the RAC Configuration With the RACCAP.BAT Sample Script If your system has a RAC, you can replicate the RAC configuration from a source Dell system’s RAC to an identical target Dell system with an identical RAC (for example, from one PowerEdge 1850 with a DRAC4/I to another PowerEdge 1850 with a DRAC4/I).
  • Page 72 CAUTION: The existing Dell utility partition should be the first primary partition on the hard disk. Also, the Dell utility partition must be greater than or equal to 32 MB and less than 2 GB. For details on the command line arguments to be used for UPINIT.BAT, refer to the Deployment Toolkit Command Line Interface Reference Guide.

  • Page 73: Preparing The Operating System Installation Scripts For Windows Pe

    Preparing the Operating System Installation Scripts for Windows PE The WININST.BAT and W2K8INST.BAT scripts are used to install supported Windows operating systems. WININST.BAT The WININST.BAT sample script is used to perform an unattended installation of Windows 2000 Server and Windows Server 2003 operating systems.

  • Page 74: Unattend.txt

    DT_OSSRC=%DT_DRIVE%\W2KSRC\I386 :: Location of Unattend.txt file set DT_UNATTEND= %DT_SYSTEMS%\%DT_PLATFORM%\unattend.txt :: Location of platform-specific Dell drivers set DT_OEM=%DT_SYSTEMS%\%DT_PLATFORM%\configsets After you have either confirmed or edited the Windows operating system installation variables, you are ready to prepare the UNATTEND.TXT file to be used in the operating system installation.
  • Page 75 W2K8INST.BAT The W2K8INST.BAT sample script is used to perform an unattended installation of Windows Server 2008 operating system. The variables and paths must be specified before the operating system can be installed. CAUTION: It is strongly 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.

  • Page 76: Unattend.xml

    :: Location of Unattend.xml file set DT_UNATTEND= %DT_SYSTEMS%\%DT_PLATFORM%\unattend.xml :: Location of platform-specific Dell drivers set DT_OEM= %DT_SYSTEMS%\%DT_PLATFORM%\$OEM$%DT_WINDOWS% UNATTEND.XML The UNATTEND.XML file is the default name of the answer file that you use to automate Windows Setup during an unattended installation. A sample copy of the UNATTEND.XML file is provided as part of the DTK download...

  • Page 77: Running Deployment Scripts Using Dtk And Microsoft Windows Pe

    This section provides best practices procedures and scenarios for using the Deployment Toolkit (DTK) to perform pre-operating system configuration tasks and to install supported operating systems on supported Dell™ systems. After you have populated the deployment directory structure with all necessary files and carefully edited the deployment scripts and configurations files, you are ready to begin the final stage of the deployment process.

  • Page 78: Creating A Standard Windows Pe

    4 Copy factory.exe and netcfg.exe from <cd-drive>:\tools\x86 directory to the \WinPE_OPKTools directory. 5 Remove the Windows OPK CD or Windows PE CD from the CD drive. Creating a Standard Windows PE For building a standard Windows PE with OPK tools, refer to the help files available on the OPK CD.

  • Page 79: Integration Of Dtk Directory Structure In Windows Pe Build

    These files include drivers that are part of the Windows Server 2003 CD. These drivers may be old and may not recognize the new peripherals integrated in your new Dell system. Proceed to add the latest drivers in the standard Windows PE build you just created.

  • Page 80: Creating A Bootable Windows Pe Iso Image

    In the winpeoem.sif file (available under I386\SYSTEM32 in your Windows PE directory), edit the following text to remove the semicolons from the Oem Driver Params section and append the directory names for the Dell mass storage drivers: OemDriverRoot="" OemDriverDirs=MRAID, PERC4IM, PERC5, SAS5 NOTE: A sample winpeoem.sif file is available under...

  • Page 81: Cd-Based Local Deployment

    CD. After burning the ISO image, ensure that it boots from the CD 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 ensure that the integration went well and there are no issues with hardware components not being recognized.

  • Page 82: Using A Third-Party Deployment Solution Framework

    Windows AIK is copied to the C:\Program Files\Windows AIK directory. Integration of DTK Directory Structure in Windows PE Build DTK provides a script, VPE_driverinst.bat, to pre-install the Dell drivers into a base Windows PE 2.0 image (winpe.wim) offline. Use the following steps to...

  • Page 83: Creating A Bootable Cd

    After burning the ISO image, ensure that it boots from the CD 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 ensure that the integration went well and there are no issues with hardware components not being recognized.

  • Page 84: Cd-Based Local Deployment With Networking Enabled

    CD-Based Local Deployment With Networking Enabled You can also use your bootable CD to call the deployment components from the directory structure on the CD and the remaining components from the network share: 1 Boot the target system with the bootable deployment CD. 2 Execute the master batch file, which calls individual task scripts and utilities from the network share to complete the deployment process.

  • Page 85: Choosing An Embedded Linux-Based Deployment Method

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

  • Page 86: Network-Based Deployment

    Network-Based Deployment NOTE: The DTK network-based deployment is not supported from mapped ® ® Novell NetWare systems. The general network-based deployment process includes the following steps: 1 Modify the appropriate section in pxe config file. 2 Boot the target server from PXE. The DTK start-up phase mounts the network share specified in the pxe config file.

  • Page 87: Using A Third-Party Deployment Solution Framework

    See "Running Deployment Scripts Using DTK and Embedded Linux" for details on how to create a customized version of a single embedded Linux bootable CD that works across all Dell systems and provides an underlying network stack. Using a Third-Party Deployment Solution Framework...
  • Page 88 Creating a Customized Bootable CD See "Running Deployment Scripts Using DTK and Embedded Linux" for details on how to create a customized version of a single embedded Linux image that can work across all Dell systems. Choosing an Embedded Linux-Based Deployment Method...

  • Page 89: Deployment Matrix (Embedded Linux)

    Using DTK Utilities and Scripts From a Customized Bootable CD After the customized bootable embedded Linux CD is created, IT administrators can take advantage of the sample scripts to automate the entire deployment process. In this purely CD-based deployment, it is necessary to add the operating system installation files on the CD media.
  • Page 90 Table 6-1. Deployment Method Matrix (continued) Deployment Complexity Advantages Disadvantages Methods Remote Moderate • Everything is in • Must have network deployment over a one place in a connection. network (bootable network share. • Deployment tasks must embedded Linux • Easy to manage— be performed at the CD with network changes have to...
  • Page 91 Table 6-1. Deployment Method Matrix (continued) Deployment Complexity Advantages Disadvantages Methods PXE boot High • Everything is in • Must have high-speed one place on a connectivity to network network share. (LAN). • Easy to manage— • Set up time is longer. changes have to be made in only in one place.
  • Page 92 Choosing an Embedded Linux-Based Deployment Method...

  • Page 93: Preparing The Directory Structure

    DTK version 3.xx are completely different. Installation for Embedded Linux The DTK components are provided in an ISO image on the Dell™ Support website at support.dell.com. You can use a CD-burning software to burn the ISO image on a bootable CD or loop mount the ISO image to access the image contents.
  • Page 94 /etc. openipmi Contains IPMI drivers and support /mnt/cdrom/tools scripts to install them. These drivers are required for all Baseboard Management Controller (BMC) and Dell Remote Access Controller (DRAC) related commands. Preparing the Directory Structure for Deployment in Embedded Linux...
  • Page 95 Initial RAM disk containing the /mnt/cdrom/isolinux embedded Linux component and the DTK tools Source RPMS Contains open source components /mnt/cdrom/srpms (SRPMs) used in the Dell-provided embedded Linux srvadmin- Contains a set of drivers and /mnt/cdrom/tools hapi.<version libraries used by the DTK tools to number>.i386.rpm interact with the hardware.
  • Page 96 Boot the CD onto a target system. Figure 7-2 shows the directory structure on the target system. Figure 7-2. Target System Directory Structure Preparing the Directory Structure for Deployment in Embedded Linux...

  • Page 97: Dtk Contents

    The DTK contains embedded Linux-based utilities, sample scripts, sample configuration files, drivers, and documentation for automating the deployment of Dell systems. The following sections provide a complete list of the DTK contents and a short description of each component. For a more complete explanation of the DTK utilities, see the Command Line Interface Reference Guide.
  • Page 98 Wrapper script which invokes racadm3 or racadm4, depending on the remote access controller (RAC) on your system. racadm3 Configures Dell Remote Access Controller (DRAC) III, DRAC III/XT, embedded remote access (ERA), ERA/O, and ERA/MC RACs. racadm4 Configures DRAC 4/P and DRAC 4/I RACs.

  • Page 99: Sample Configuration Files

    Lists the error codes and messages for upinit.sh. Sample Configuration Files Table 7-4 describes examples of configuration files used to perform a scripted deployment. These files are located at opt/dell/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.

  • Page 100: Sample Scripts

    Some customers may need to develop their own scripts entirely from scratch. Customers deploying multiple systems must provide unique information for each Dell system where appropriate. For example, system host names, IP addresses, and BIOS asset tags need to be unique for each system.

  • Page 101: Documentation

    Drivers and Dell Real Mode Kernel (DRMK) Hardware application programing interface (HAPI) drivers are essential for DTK tools to work in the embedded Linux environment. DRMK contains a file necessary to create a bootable Dell utility partition. This file is mbr. Miscellaneous The document readme.txt, located at mnt/cdrom/docs, provides the latest...
  • Page 102 To unzip files in Linux. Any system running a In the path. Linux operating system. upimg Contains system-specific /opt/dell/toolkit/ /opt/dell Dell utility partition files. systems, the Dell /toolkit/ Support website at systems NOTE: In the previous support.dell.com, or the releases, each Dell system Dell Systems Build and required a unique upimg file.

  • Page 103: Setting Up A Directory Structure For Deployment

    (where necessary) to reflect the different directory structure. NOTE: The unzip utility is needed to create the Dell utility partition. This utility should be copied into the /systems folder. System-Specific Files The directory /opt/dell/toolkit/systems/system name acts as a central repository for all the system-specific deployment information.
  • Page 104 These files can then be accessed from this directory when deploying multiple PowerEdge 2850 systems. For more information about obtaining Dell utility partition files, see "How to Obtain Dell Utility Partition Files." This directory can also be subdivided into multiple system-specific directories such as: /opt/dell/toolkit/systems/pe2850 for Dell PowerEdge 2850 systems and /opt/dell/toolkit/systems/pe1850 for Dell PowerEdge 1850 systems.

  • Page 105: Creating Operating System Installation Directories For Supported Linux Operating Systems

    (from the Linux operating system CD) • initial ramdisk from the Dell Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD See Figure 7-4 for a sample directory structure for deployment of a supported Linux operating system.
  • Page 106 Figure 7-4. Sample Operating System-Specific File Structure (Linux Operating System) Preparing the Directory Structure for Deployment in Embedded Linux...

  • Page 107: Configuring A Source System

    DTK scripts, syscap.sh and raccap.sh, to generate SYSCFG and RAC configuration files that are used to configure the target system. You can use the Dell Systems Build and Update Utility and the Systems Service and Diagnostics Tools on the Dell Systems Management Tools and Documentation DVD supplied with your system to: •...

  • Page 108: How To Obtain Dell Utility Partition Files

    RAC Configuration Configure the RAC on your source system using the racadm utility, if applicable. See the Dell Remote Access Controller Racadm User's Guide for comprehensive information about using the racadm utility to configure the RAC on your source system.

  • Page 109: Preparing The Script Files For

    Preparing the Script Files for Deployment Using Embedded Linux This section describes the steps required to use the Deployment Toolkit (DTK) sample scripts to perform a full deployment of a target system in the embedded Linux environment. There are four main tasks: •...

  • Page 110: Editing The Sample Batch Files To Perform A Complete System Deployment In Embedded Linux

    Editing the Sample Batch Files to Perform a Complete System Deployment in Embedded Linux Using the Sample Scripts in a Scripted Deployment The sample scripts utilize the 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 of the target system.
  • Page 111 Captures RAC the RAC Performs an the path of the settings to a file for configuration unattended DTK installation Dell™ Remote settings saved in a installation of a and variables for ® Access Controller file to the current supported Red Hat the system to be ®...
  • Page 112 Configures the BMC configuration settings saved in a Available on selected RAID settings and saves file to the current the Dell controller detected them to a file. system. Systems Build in the system. and Update • tkenvset.sh — • tkenvset.sh —...
  • Page 113 Captures the RAID the RAID settings Performs an Creates and settings and saves saved in a file to the unattended populates the Dell them to a file. current system. installation of a utility partition and ® supported SUSE the deployment •...
  • Page 114 Enterprise – upinit.sh— Server Used by operating partcfg.sh to system CD create and – kernel populate the image— Dell utility Available on partition. the SUSE Linux Enterprise Server operating system CD • autoinst.xml — Used by suseinst.sh in conjunction with...
  • Page 115 Capture Scripts Replication Scripts Deployment Scripts Others dtkrunall.sh— upinit.sh — Applies BIOS, BMC, Creates and RAC, and RAID populates the Dell settings saved in the utility partition. files to the current NOTE: Do not make system. any modifications • tkenvset.sh —...

  • Page 116: Tkenvset.sh

    • upimg.bin — Contains the zipped contents of the Dell utility partition. The majority of the editing required for the DTK sample scripts involves the following script. As a result, the majority of the scripting discussion focuses on: tkenvset.sh Other task scripts might require edits in certain situations.
  • Page 117 Dell systems (DT_SYSTEMS). This variable is set to $dt_path/systems 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/pe1850 4 Set the variable that defines the directory containing the DTK deployment scripts (DT_SCRIPTS).
  • Page 118 6 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.
  • Page 119 To edit the RAC configuration variables, locate the following lines 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 ( ) is set to...
  • Page 120 # 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 will not override the setting and the utility partition will not be created.

  • Page 121: Editing Dtk Task Scripts

    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.sh scripts. However, if you make any changes to the default values set by the tkenvset.sh, you must make the same edits to the matching default values set in the appropriate task scripts.
  • Page 122 raidcfg.sh The raidcfg.sh sample script configures RAID controllers detected on the system. User input is optional to run this script. The 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.

  • Page 123: Using The Dtk Sample Scripts To Capture Configuration Information In Embedded Linux

    Capturing the System BIOS and BMC Configuration With the syscap.sh Sample Script You can replicate the system BIOS and BMC configurations from a source Dell system to an identical target Dell system (for example, from one PowerEdge™ 1850 to another PowerEdge 1850). NOTE: For the script to complete successfully, the source system must have access to the network share that includes the prebuilt DTK directory structure.

  • Page 124: Capturing The Rac Configuration With The Raccap.sh Sample Script

    Capturing the RAC Configuration With the raccap.sh Sample Script If your system has a RAC, you can replicate the RAC configuration from a source Dell system’s RAC to an identical target Dell system with an identical RAC (for example, from one PowerEdge 1850 with a DRAC4/I to another PowerEdge 1850 with a DRAC4/I).
  • Page 125 The upinit.sh tool is used to create and populate the Dell 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. You can also use this script to upgrade or downgrade an existing Dell utility partition.

  • Page 126: Preparing The Operating System Installation Scripts

    Preparing the Operating System Installation Scripts Red Hat Enterprise Linux Server Operating Systems The lininst.sh script is used to install supported Red Hat Enterprise Linux Server operating systems. NOTE: While installing Linux, ensure that you install grub in the boot partition. Otherwise, you will not be able to boot to the utility partition by pressing the F10 key during reboot.

  • Page 127: Ks.cfg (For Red Hat Enterprise Linux Server Version 4) And Ks-Rhel5.Cfg (For Red Hat Enterprise Linux Server Version 5)

    Perform the following steps to install Red Hat Enterprise Linux (32-bit) using the lininst.sh script: 1 Create the virtual disk using raidcfg command. 2 Run the partcfg.sh script before running lininst.sh to create Dell Utility partition and OS partition. 3 Create a directory under /tmp. for example os_src.

  • Page 128: Suse Linux Enterprise Server Operating Systems

    8 Edit the file ks.cfg. Set the NFS IP Address where RHEL 32-bit images are available and the NFS share path. 9 Run export DT_OS_DISK=/dev/sda, the disk device on which the Dell Utility partition was created. 10 Run export DT_OS_SRC=/tmp/os_src, where vmlinuz,initrd.img and ks.cfg available.

  • Page 129: Autoinst.xml (For Suse Linux Enterprise Server)

    SUSE Linux Enterprise Server installation. A sample copy of the autoinst.xml file is provided as part of the DTK download in the /opt/dell/toolkit/template/configs directory. The autoinst.xml file contains the headings and parameters that instruct the installation utility to perform various configuration tasks.
  • Page 130 When you have completed all necessary modifications of the autoinst.xml file, save the completed file in the /opt/dell/toolkit/systems/<target system> directory. After you have successfully edited your deployment scripts, you are ready to create your deployment media and run your deployment. For instructions on creating deployment media and running a full deployment, see "Running...

  • Page 131: Running Deployment Scripts

    This section provides best practices procedures and scenarios for using the Deployment Toolkit (DTK) to perform pre-operating system configuration tasks and to install supported operating systems on supported Dell™ systems. After you have populated the deployment directory structure with all necessary files and carefully edited the deployment scripts and configurations files, you are ready to begin the final stage of the deployment process.
  • Page 132 /mnt/cdrom/isolinux/isolinux.cfg.) CD-Based Deployment 1 Obtain the ISO image of the embedded Linux available on the Dell Support website at support.dell.com. 2 Burn the ISO image using any commonly available CD burning software. NOTE: When you create a bootable CD, this image is supplied to the CD burning software along with the complete deployment directory structure, which includes all necessary supporting files to perform the deployment.
  • Page 133 /isolinux). If you do not use , DTK’s openipmi and HAPI libraries mkisofs will not load and most of the Dell Update Packages will not work. NOTE: The scripts that you copy into the CD will be copied to the RAM disk and run from the RAM disk.

  • Page 134: Deployment Using Customized Embedded Linux

    Deployment Using Customized Embedded Linux Ensure that you have the following basic libraries, Dell toolkit libraries, tools, and utilities required for DTK to work in your customized Linux deployment environment (see Table 7-1 for details on files and RPMs to customize your embedded Linux): •...

  • Page 135: Running Dell Update Packages In Embedded Linux

    The common scenarios for running Update Packages are: Running Update Packages in Dell-Provided Embedded Linux 1 Obtain the required update packages from the Dell Server Updates DVD or from the Dell Support website at support.dell.com. 2 Save the update packages on a network share.
  • Page 136 Table 10-1. Dependencies for Dell Update Packages to Run in Customized Embedded Linux (continued) Update Dependency Dependencies Available On Packages PERC /etc/dataeng /mnt/cdrom/tools megaraid driver 2.4.2.0 /mnt/cdrom/tools SCSI drivers Kernel RAC3 /etc/racser /mnt/cdrom/tools /mnt/cdrom/tools racser3.sh /mnt/cdrom/tools RAC4 Open IPMI /mnt/cdrom/tools...
  • Page 137 After ensuring that you have met all the dependencies, run the update packages in your customized embedded Linux environment as follows: 1 Obtain the required update packages from the Dell Server Updates DVD or from the Dell Support website at support.dell.com.
  • Page 138 Running Dell Update Packages in Embedded Linux...

  • Page 139: Known Issues And Frequently Asked Questions

    Known Issues and Frequently Asked Questions This section describes known issues with the Deployment Toolkit (DTK) utilities and scripts, including answers to some frequently asked questions. Known Issues The following issues are organized by the DTK utility or other function. General Issues •...

  • Page 140: Racadm Issues

    Only Back Ports On, the USB port will be automatically Set to Off during the next reboot. RACADM Issues • Dell™ Remote Access Controller (DRAC) III, DRAC III/XT, embedded remote access (ERA), ERA/O, and ERA/MC controllers are not supported on Windows PE. Windows PE Installation Issues •...

  • Page 141: Raidcfg Questions

    Q: When I use the sample DTK scripts to deploy multiple systems, do I need to 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.
  • Page 142 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 will be parsed as -r=1. Q: On PowerEdge 1655MC system running embedded Linux, RAIDCFG displays the error: megadev: Bad file descriptor.
  • Page 143 ® Q: What features have changed from the MS-DOS version of RAIDCFG to the Windows PE and embedded Linux versions? A: New features for the Windows PE embedded Linux RAIDCFG include: Support for the following controllers: • PERC 3/DC, PERC 3/QC, and PERC 3/SC •...
  • Page 144 For PERC 5 controllers: • RAID 0: 100MB • RAID 1: 100MB • RAID 5: 100MB For PERC 6 controllers: • RAID 0: 100MB • RAID 1: 100MB • RAID 5: 100MB • RAID 6: 100MB • RAID 60: 100MB Q: Why can’t I see any controllers using RAIDCFG? A: Ensure that the RAID controller(s) can be seen in the BIOS during POST.

  • Page 145: Syscfg Questions

    SYSCFG Questions NOTE: In a Linux environment, the DTK utilities do not have a .exe extension. Q: On x7xx systems, when I set arguments for --sata0 and --sata1 using DTK CLI and reboot the system, the BIOS setup shows the earlier settings for -- sata0 and --sata1.

  • Page 146: Embedded Linux Questions

    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.

  • Page 147: Windows Pe Questions

    DTK 3.x versions for embedded Linux. See the directory /opt/dell/toolkit/template/scripts for the sample scripts. Q: After I install a legacy operating system on a newer Dell system, the Linux kernel does not boot and panics. A: After installing the initial ramdisk image, you could install the driver or you could update to a newer version of the kernel.
  • Page 148 Preinstallation Kit (OPK) CD], the DRVINST.EXE fails with an error message that there are some files missing. A: Dell recommends that you use DRIVERINST.BAT (provided with DTK). However, if you use DRVINST.EXE from Microsoft to install the NIC drivers into your Windows PE image, you need to download and extract required NIC drivers for Windows 2000 and Windows Server 2003 to a common directory.

  • Page 149: Glossary

    Glossary The following list defines or identifies technical terms, abbreviations, and acronyms used in your system documents. adapter card An expansion card that plugs into an expansion-card connector on the system's system board. An adapter card adds some specialized function to the system by providing an interface between the expansion bus and a peripheral device.
  • Page 150 asset tag code An individual code assigned to a system, usually by a system administrator, for security or tracking purposes. autoexec.bat file The autoexec.bat file is executed when you boot your system (after executing any commands in the config.sys file). This start-up file contains commands that define the characteristics of each device connected to your system, and it finds ®...
  • Page 151 Abbreviation for baseboard management controller, which is the controller interface between the RAC and the managed system’s ESM. boot routine When you start your system, it clears all memory, initializes devices, and loads the operating system. Unless the operating system fails to respond, you can reboot (also called warm boot) your system by pressing <Ctrl><Alt><Del>;...
  • Page 152 CERC Cost-Effective RAID Controller (CERC) is a half-sized Peripheral Component Interconnect (PCI) adapter card that provides a way to improve the performance and availability of your storage subsystems. CHAP Acronym for Challenge-Handshake Authentication Protocol, an authentication scheme used by PPP servers to validate the identity of the originator of the connection upon connection or any time later.
  • Page 153 console redirection Console redirection is a function that directs a managed system’s display screen, mouse functions, and keyboard functions to the corresponding devices on a management station. You may then use the management station’s system console to control the managed system. controller A chip that controls the transfer of data between the microprocessor and memory or between the microprocessor and a peripheral device such as a disk drive or the...
  • Page 154 Abbreviation for direct memory access. A DMA channel allows certain types of data transfer between RAM and a device to bypass the microprocessor. DRAC 4 Acronym for Dell™ OpenManage™ Remote Access Controller, version 4. DRAM Acronym for dynamic random-access memory. A system's RAM is usually made up entirely of DRAM chips.
  • Page 155 EPROM Acronym for erasable programmable read-only memory. Abbreviation for embedded remote access. ERA/MC Abbreviation for embedded remote access modular computer. See modular system. ERA/O Abbreviation for embedded remote access option. Abbreviation for embedded systems management, which is a set of instruction coding in system software and firmware that notifies a user about potential hardware problems on a system.
  • Page 156 Acronym for file allocation table. FAT and FAT32 are file systems that are defined as follows: FAT — A file system used by MS-DOS, Windows 3.x, Windows 95, and • ® Windows 98. Windows NT and Windows 2000 also can use the FAT file system.
  • Page 157 Acronym for Hardware Abstraction Programming Interface, which is the lowest layer that is installed on the operating system by the Instrumentation Service. This layer is re-used by Dell Update Packages and firmware tools, and flash utilities to access the hardware through a reusable pipe.
  • Page 158 HPFS Abbreviation for the High Performance File System option in the Windows NT operating systems. HTTP Abbreviation for Hypertext Transfer Protocol. HTTP is the client-server TCP/IP protocol used on the World Wide Web for the exchange of HTML documents. HTTPS Abbreviation for HyperText Transmission Protocol, Secure.
  • Page 159 Abbreviation for interrupt request. A signal that data is about to be sent to or received by a peripheral device travels by an IRQ line to the microprocessor. Each peripheral connection must be assigned an IRQ number. For example, the first serial port in your system (COM1) is assigned to IRQ4 by default.
  • Page 160 memory A system can contain several different forms of memory, such as RAM, ROM, and video memory. Frequently, the word memory is used as a synonym for RAM; for example, an unqualified statement such as "a system with 16 MB of memory" refers to a system with 16 MB of RAM.
  • Page 161 Acronym for network interface controller. NTFS Abbreviation for the Windows NT File System option in the Windows NT operating system. NTFS is an advanced file system designed for use specifically within the Windows NT operating system. It supports file system recovery, extremely large storage media, and long file names.
  • Page 162 PERC Acronym for PowerEdge™ Expandable RAID controller. peripheral device An internal or external device—such as a printer, a disk drive, or a keyboard— connected to a system. Plug and Play An industry-standard specification that makes it easier to add hardware devices to personal computers.
  • Page 163 Acronym for random-access memory. A system's primary temporary storage area for program instructions and data. Each location in RAM is identified by a number called a memory address. Any information stored in RAM is lost when you turn off your system. RAM disk A memory-resident program that emulates a hard drive.
  • Page 164 Short for Serial Attached SCSI, SAS is an evolution of parallel SCSI into a point- to-point serial peripheral interface in which controllers are linked directly to disk drives. SATA Abbreviation for Serial Advanced Technology Attachment, it refers to a newer interface standard for PC hard-disk drives.
  • Page 165 SMBIOS Acronym for system management BIOS. SNMP Abbreviation for Simple Network Management Protocol. SNMP, a popular network control and monitoring protocol, is part of the original TCP/IP protocol suite. SNMP provides the format in which vital information about different network devices, such as network servers or routers, can be sent to a management application.
  • Page 166 System Setup program A BIOS-based program that allows you to configure your system's hardware and customize the system's operation by setting such features as password protection and energy management. Some options in the System Setup program require that you reboot the system (or the system may reboot automatically) in order to make a hardware configuration change.
  • Page 167 unicode A fixed width, 16-bit world wide character encoding, developed and maintained by the Unicode Consortium. upper memory area The 384 KB of RAM located between 640 KB and 1 MB. If the system has an Intel386 or higher microprocessor, a utility called a memory manager can create UMBs in the upper memory area, in which you can load device drivers and memory-resident programs.
  • Page 168 virtual memory A method for increasing addressable RAM by using the hard drive. For example, in a system with 16 MB of RAM and 16 MB of virtual memory set up on the hard drive, the operating system would manage the system as though it had 32 MB of physical RAM.
  • Page 169 Windows 95 An integrated and complete Microsoft Windows operating system that does not require MS-DOS and that provides advanced operating system performance, improved ease of use, enhanced workgroup functionality, and simplified file management and browsing. Windows NT High-performance server and workstation operating system software developed by Microsoft that is intended for technical, engineering, and financial applications.
  • Page 170 Glossary...

  • Page 171: Index

    BIOS & Windows PE, 66 BMC configuration embedded Linux, 123 Windows PE, 70 CD-Based local deployment Dell Real Mode Kernel embedded Linux, 87 embedded Linux, 101 Windows PE, 27 Windows PE, 42 CD-Based local deployment, deployment directory structure...
  • Page 172 document organization, 12 drivers Master Batch File embedded Linux, 101 sample, 56 Windows PE, 42 what is, 56 DTK, 97 embedded Linux contents, 97 installing, 93, 108 DTK deployment overview, 19 operating system installation files DTK prerequisites and embedded Linux, 105 requirements, 14 Windows PE, 48 overview...
  • Page 173 134 embedded Linux, 99 using customized embedded Windows PE, 38 Linux, 134 sample script files using Dell-provided embedded master deployment file for Linux, 131 embedded Linux, 116 running a scripted deployment, sample scripts using Dell-provided embedded Linux, 100...
  • Page 174 Windows PE, 15 sysrep.sh, 112, 122 tkenvset.sh, 111 supported systems, 15 upinit.sh, 115, 125 supporting documentation scripted deployment in Windows other dell documents you might need, 23 capturing the RAC other documents you might configuration, 71 need, 24 PARTCFG.BAT, 60, 70 supporting tools and system files RACCAP .BAT, 71...
  • Page 175 utilities and files needed for deployment embedded Linux, 103 Windows PE, 45 what’s new for this release, 14 Windows PE contents DTK, 36 Index...
  • Page 176 Index...

This manual is also suitable for:

Openmanage deployment toolkit

Table of Contents