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 .
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this document is subject to change without notice. © 2009 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . Introduction to the DTK User’s Guide What’s New 11 . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . 14 Prerequisites and Requirements . . . . . . . . . . . . Supported Operating Systems to Run DTK Utilities . . . . . . Supported Systems . 14 . . . . . . . . . . . 15 . . . . . . . . . . . . . . . . 15 . . . . . . . . 15 Installation Prerequisites . . . . . . . . . . . . .
2 Choosing a Microsoft Windows PE-Based Deployment Method . Choosing a Deployment Method for Microsoft Windows PE . . . . . . . . . . 27 . . . . . . . . . . . . 27 CD-Based Local Deployment . . . . . . . . . . . . CD-Based Local Deployment With Networking Enabled . . . . . . . . . . . . . . . . 28 . . . . . . . . . . 29 . . . . . . . . . . . 30 Using a Third-Party Deployment Solution Framework . . . . . .
Setting Up a Directory Structure for Deployment . . . . . . . . . . . . . . . . . . . . . 45 DTK Utilities and Files . . . . . . . . . . . . . . . 45 System-Specific Files . . . . . . . . . . . . . . . 46 . . . . . . . . 47 . . . . . . . . . . . . . . 51 . . . . . . . . . . . . . . . . . 52 Operating System Installation Files Configuring a Source System RAC Configuration 4 Preparing the Script Files for Deployment Using Microsoft Windows PE . . . . . . . . . . . . . . . .
Preparing the Operating System Installation Scripts for Windows PE . . . . . . . . . . . 71 . . . . . . . . . . . . . . . . . . . 71 UNATTEND.TXT . . . . . . . . . . . . . . . . . . 72 UNATTEND.XML . . . . . . . . . . . . . . . . . . 74 WININST.BAT . 5 . . . . . . Running Deployment Scripts Using DTK and Microsoft Windows PE . . . . . . . . . . . . . For Windows PE 2005 . . . . . . . . . 75 . . . . . . . . . . . . . . . . . .
6 Choosing an Embedded Linux-Based Deployment Method Choosing a Deployment Method for Embedded Linux . . . . . . . . . . . . 83 . . . . . . . . . . . . 83 Network-Based Deployment . . . . . . . . . . . . Using a Third-Party Deployment Solution Framework . . . . . . 7 . . . . . . . . . . 84 85 CD-Based Local Deployment for Embedded Linux . . . . . . . . . . . . . . . . . . 85 Deployment Matrix (Embedded Linux) . . . . . . . . . 87 . . . . . . . . . . 91 . . . . . . . . . . . . . .
Setting Up a Directory Structure for Deployment . . . . 101 DTK Utilities and Files . . . . . . . . . . . . . . . 101 System-Specific Files . . . . . . . . . . . . . . . . 101 Creating Operating System Installation Directories for Supported Linux Operating Systems . . . . . . . Configuring a Source System . . . . . . . 103 . . . . . . . . . . . . . . 105 . . . . . . 106 . . . . . . . . . . . . . . . . .
Preparing the Operating System Installation Scripts . . . . . . . Red Hat Enterprise Linux Server Operating Systems . . . . . . . lininst.sh . . . . . . . . . . 124 . . . . . . . . . . . . . . . . . . . . . . 124 ks.cfg (for Red Hat Enterprise Linux Server Version 4) and ks-rhel5.cfg (for Red Hat Enterprise Linux Server Version 5) . . . . . . . Install Linux Using lininst.sh . . . . . . . . 125 . . . . . . . . . . . . 125 SUSE Linux Enterprise Server Operating Systems . . . . . . suseinst.sh . .
11 Known Issues and Frequently Asked Questions Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 137 . . . . . . . . . . . . . . . . . . . 137 RAIDCFG Issues . . . . . . . . . . . . . . . . . . 137 RACADM Issues . . . . . . . . . . . . . . . . . . 138 General Issues . . . . . . . . . . 138 . . . . . . . . . . . . . . 138 Windows PE Installation Issues Frequently Asked Questions . . . . . . . . . . 138 . . . . . . . . . . . . . . . . 139 . . . . . . . . . .
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.
CAUTION: The best practices guidelines described in this document were developed and tested on specific systems with specific hardware and software configurations. As a result, the examples and instructions described in this guide are not applicable to every environment. The open nature of the DTK utilities and scripting methodology is designed to allow the flexibility to modify the examples, procedures, and suggestions to best fit your specific environment.
Table 1-1.
What’s New The new features for DTK version 3.0 include: • 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. • Support for new CLI commands. See Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide for more information.
Supported Operating Systems to Run DTK Utilities For Windows PE, the DTK utilities support Windows PE version 2005 (created using 32-bit versions of Microsoft Windows Server 2003 family with Service Pack 1 [SP1]) and Windows PE 2.0 (created using 32-bit version built on the Windows Vista kernel). NOTE: DTK utilities do not support Windows PE created with any 64-bit version of Microsoft Windows Server 2003.
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: 16 • Advanced knowledge of Windows • OEM Preinstallation Kit (OPK) or Windows PE CD and Windows Server 2003 (with SP1) to build Windows PE 2005 • Windows Automated Installation Kit (Windows AIK) version 936330 or later CD to customize Windows PE 2.
• 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.
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 the DTK. While these sample configuration files are operating system specific, they have been enhanced for Dell systems. See your operating system documentation for more information about how to modify these unattended installation files.
DTK Deployment Overview Preparing for Deployment The deployment process can be separated into two main tasks: preparation and the actual deployment. To prepare for using the DTK utilities and scripts to deploy to a target system in the Windows PE environment: 1 Copy or extract the DTK utilities, sample scripts, sample configuration files, and drivers provided (in the zip file) into the Windows PE image.
To prepare for using the DTK utilities and scripts to deploy to a target system in the embedded Linux environment: 1 Obtain the DTK Linux ISO image, which is a self-contained bootable ISO image. 2 Use and customize the sample scripts per your requirements. 3 Set up an optimally configured source system by using the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD to install your operating system.
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).
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. 2 Insert the bootable CD into the CD drive of the system to be deployed (the target system).
Other Dell Documents You Might Need In addition to this User's Guide and the Deployment Toolkit Command Line Interface Reference Guide, both of which are available as part of the DTK download and on the Dell Support website at support.dell.
• The Dell Remote Access Controller Racadm User's Guide provides comprehensive information about using the RACADM command line utility. • 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.
Obtaining Technical Assistance If at any time you do not understand a procedure described in this guide or if your product does not perform as expected, help tools are available to assist you. 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
Choosing a Microsoft Windows PE-Based Deployment Method 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 The Deployment Toolkit (DTK) is designed to be flexible enough to fit into almost any deployment plan.
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 CD. This method does not provide a writable media, making it necessary to use predefined and tested configuration files.
Bootable Windows PE CD With Networking Enabled This process includes: • Creating a bootable Windows PE CD 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.
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.
Table 2-1. Deployment Method Matrix (continued) Deployment Methods Complexity Remote Moderate deployment over a network (bootable Windows PE CD with network stack loaded) Advantages • Everything is in one place • Must have in a network share. network connection. • Easy to manage— changes have to be made • Deployment tasks in only one place. must be performed at the • Data captured (profiles) individual target can be stored in a system. network share. • Data can be replicated from a network share.
Choosing a Microsoft Windows PE-Based Deployment Method
Preparing the Directory Structure for Deployment in Microsoft Windows PE 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 the DTK components • Setting up a directory structure to facilitate a successful deployment, including a list of the supporting components that are not included with the DTK, but are needed to use the DTK • Setting up an optimall
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. 3 Click OK. 4 Click Unzip. By default, files are unzipped to C:\.
Figure 3-1. Sample DTK Default File Structure 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. 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. The directory Z:\Dell\Toolkit\Systems is created as a placeholder that can be used for all system information that is captured using sample scripts and tools (for example, the system specific basic input/output system (BIOS) and baseboard management controller (BMC) configuration files used by the DTK utilities for configuring a system).
Table 3-1. System Utilities and Supporting Files (continued) Toolkit Components Purpose RAC 4 Configures Dell Remote Access Controller (DRAC) 4/P and DRAC 4/I. RAC 5 Configures DRAC 5/iDRAC. 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. RaidcfgErrorCodes.
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. Table 3-2. Sample Configuration Files Toolkit Components Purpose RACCFG.
Table 3-2. Sample Configuration Files (continued) Toolkit Components Purpose Location UNATTEND. XML Sample file used in Windows PE 2.0 environment with unattended installation of Microsoft Windows operating systems. This file is populated with all the necessary information for Dell-supported mass storage devices. Move to the directory Z:\Dell\Toolkit\Systems\ after the UNATTEND.TXT file is edited. STARTNET. CMD Sample script called by Windows PE 2.0 when it boots up.
Table 3-3. Sample Scripts 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. ERRHNDL.BAT Handles errors returned in the DTK scripts. LISTUP.CFG This file is used by UPINIT.BAT. MOUNTUP.CFG This file is used by UPINIT.BAT. PARTCFG.
Table 3-3. Sample Scripts (continued) Toolkit Components Purpose WININST.BAT Performs an unattended installation of a supported Microsoft Windows 2000 and Windows Server® 2003 operating systems. W2K8INST.BAT Performs an unattended installation of supported Microsoft Windows Server 2008 operating system. DTKRUNALL.BAT Applies BIOS, BMC, RAC, and RAID settings saved in the files to the current system.
Table 3-5. Drivers Drivers Purpose winpe1.x\ DRIVERINST.BAT Used to install Dell-provided drivers (from Z:\Dell\Drivers) into the customized Windows PE 2005 image. winpe2.x\ Used to install Dell-provided drivers (from Z:\Dell\Drivers) VPE_DRIVERINST.BAT into the customized Windows PE 2.0 image. common\Hardware application programming interface (HAPI) Essential drivers for the DTK tools to work. winpe1.
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. NOTE: Ensure that the tools are 32-bit compatible. Table 3-6.
Table 3-6. Supporting Tools and System Files (continued) Additional Tools Purpose 32-bit unzip utility Unzip utility www.info-zip.org partition image in NOTE: This utility is not Windows PE. provided with the Dellsupplied DTK zip file. However, if you choose to use any other unzip utility than the one specified above, ensure that you rename the utility to UNZIP.EXE and that it supports the -d option to extract the contents to a specified directory. upimg.
Setting Up a Directory Structure for Deployment To perform a 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 and can be used successively as a testing space, a repository for a network deployment, and a repository to build a bootable deployment CD.
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.
Operating System Installation Files Figure 3-3.
Creating Operating System Installation Directories for Windows Server 2003 Operating Systems For deployment of Windows Server 2003 operating systems, perform the following steps: 1 On a management station create a folder, for example os_deploy. 2 Make this folder shareable. 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.
9 Edit unattend.txt and modify the following mandatory fields: Table 3-7. Mandatory Fields in unattend.txt Field Description Example OEMBootFiles List of files in the driver folder. For example, in a system that has PERC 5, you must retain the following entry and remove the rest of the entries under the field OEMBootFiles. DELL_PERC5_PERC6_W2K3 percsas.sys oemsetup.inf nodev.inf percsas.
14 Navigate to the mount point z:\\\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.
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.
You can use the Systems Build and Update Utility and Systems Service and Diagnostics Tools available on the Dell Systems Management Tools and Documentation DVD supplied with your system to streamline the operating system installation; to setup and configure your system, including automatic discovery and configuration of Dell-provided RAID controllers and network adapters; to access and load the latest utilities, drivers, and diagnostics for your system; and to install Dell OpenManage™ systems management sof
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: • Writing the deployment master batch file (as an example, referred to as DEPLOY.BAT in this document) or deployment script, editing the TKENVSET.
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. DEPLOY.BAT, along with the TKENVSET.BAT scripts, makes up the master set of instructions that drives the deployment process.
:: 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. :: This is calling Windows installer scripts. ***************************************************** ::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0 ::call WININST.
Table 4-1. Scripts For Deployment Capture Scripts Replication Scripts Deployment Scripts Others RACCAP.BAT — Captures RAC settings to a file for DRAC 4. RACREP.BAT — WININST.BAT — Applies the RAC Performs an configuration unattended settings saved in a installation of • TKENVSET.BAT file to the current supported system. Windows 2000 — Used by RACCAP.BAT to • TKENVSET.BAT Server and Windows Server® inform the task — Used by 2003 operating scripts where to RACREP.BAT systems.
Table 4-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts Deployment Scripts Others SYSCAP.BAT — Captures BIOS and BMC configuration settings and saves them to a file. SYSREP.BAT — Applies the BIOS and BMC settings saved in a file to the current system. W2K8INST.BAT— RAIDCFG.BAT — Performs an Configures the unattended selected Redundant installation of Array of Independent supported Windows Disks (RAID) controller detected • TKENVSET.BAT • TKENVSET.BAT Server 2008. • TKENVSET.
Table 4-1. Scripts For Deployment (continued) Capture Scripts RAIDCAP.BAT— Captures the RAID settings and saves them to a file. Replication Scripts Deployment Scripts Others RAIDREP.BAT— Applies the RAID settings saved in a file to the current • TKENVSET.BAT system. — Used by • RAIDCFG.EXE RAIDCAP.BAT — Used by to inform the task RAIDREP.BAT scripts where to to retrieve RAID find the information and DTK utilities, to configure scripts, and settings. configuration files. • RAIDCFG.EXE — Used by RAIDCAP.
Table 4-1. Scripts For Deployment (continued) 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.
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 scripts where to find the DTK utilities, scripts, and configuration files. • DISKPART.EXE — Provided by Windows, it is used to create partitions on your disk. • UNZIP.EXE — Used by UPINIT.
Table 4-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts Deployment Scripts Others DTKRUNALL. BAT— Applies BIOS, BMC, RAC, and RAID settings saved in the files to the current system. • TKENVSET.BAT — Used by DTKRUNALL. BAT to find the DTK utilities and scripts. • UPIMG.BIN — Contains the zipped contents of the Dell utility partition. • SYSDRMK.EXE — Used by UPINIT.BAT to patch the boot sector and Master Boot Record (MBR). • RACREP.BAT — Used by DTKRUNALL.
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.BAT Other task scripts might require edits in certain situations. These optional edits are discussed in "Editing DTK Task Scripts." TKENVSET.BAT The TKENVSET.BAT script sets the path of the DTK installation and variables for the system to be deployed and configured.
3 Set the variable that defines the directory containing the DTK utilities (DT_TOOLS). This variable is set to %DT_PATH%\Tools by default in the sample script. Edit this path to reflect the actual location of the DTK utilities, if necessary. 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.
Specifying the RAC Configuration Variables The IP address for your target system RAC is set in the sample script to 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 sample script to generate the raccfg.ini file, there should be no need to edit this default setting.
:: 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 set 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 will not override the setting and the utility partition will not be created.
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. You should have already copied the UPIMG.
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" for information about using the RACCAP.BAT sample script to capture RAC configuration information. RAIDCFG.BAT The RAIDCFG.BAT sample script configures RAID controllers detected on the system.
PARTCFG.BAT The PARTCFG.BAT sample script creates and populates the Dell utility partition using UPINIT.BAT and creates the operating system partition on a specified disk. (See "UPINIT.BAT" for more information about using the UPINIT.BAT tool.) User input is not required to run this script. The default variable values used in this script are set in the TKENVSET.BAT scripts. NOTE: Ensure that DT_HD is set to the required disk to be configured before you execute the PARTCFG.BAT script.
settings from the source system and to save the settings in a file named syscfg.ini in the Z:\Dell\Toolkit\Systems\ directory. Perform the following steps to run the SYSCAP.BAT sample script to capture BIOS and BMC configuration information in the syscfg.ini file: 1 Edit the startnet.cmd file on your Windows PE image to call the SYSCAP.BAT script after the network share with the prebuilt DTK directory structure is mounted. For example, add: call Z:\Dell\Toolkit\Template\Scripts\SYSCAP.
Perform the following steps to run the RACCAP.BAT sample script to capture RAC configuration information in the raccfg.ini file: 1 Edit the startnet.cmd file on your Windows PE image to call the RACCAP.BAT script after the network share with the prebuilt DTK directory structure is mounted. For example, add: call Z:\Dell\Toolkit\Template\Scripts\RACCAP.BAT \Z:\raccfg.ini 2 Boot the source system into 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. The variables and paths must be specified before the operating system can be installed.
Specifying the Windows Installation Variables and Installation Paths To edit the Windows operating system installation variables, locate the following lines in WININST.BAT: :: The location where source files for the OS reside set DT_OSSRC=%DT_DRIVE%\W2KSRC\I386 :: Location of Unattend.txt file set DT_UNATTEND= %DT_SYSTEMS%\%DT_PLATFORM%\unattend.
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.
:: 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 in the Z:\Dell\Toolkit\Template\Configs directory. UNATTEND.
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.
4 Copy factory.exe and netcfg.exe from :\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. You can get to the help files after you install OPK on your development system. Brief instructions are provided here on how to build a standard Windows PE.
The specifies the location of the Windows Server 2003 product CD. • If the is a CD drive, you need to specify only the drive letter. • If the is a network path, the path must be to the parent directory of the \I386 directory. NOTE: Do not include a trailing slash in the . NOTE: If you plan to use virtual media within your Windows PE environment, ensure that your Windows PE image has cdrom.sys and flpydisk.sys drivers.
3 Adding support for mass storage drivers into Windows PE: NOTE: You must implement this step to ensure mass storage drivers are installed into Windows PE. 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.
Here, ETFSBOOT.COM (boot sector file) is a part of the OPK tools you copied in \WinPE_OPKTools directory. These files make the Windows PE CD bootable. For example, if the final target folder for storing ISO image is C:\FINALBUILD, and your Windows PE file set is in , the following command line creates a bootable ISO image called Dellx86winpe.iso: C:\WINPE_OPKTOOLS\OSCDIMG -bETFSBOOT.COM -n c:\DELLWINPEBUILD C:\FINALBUILD\Dellx86winpe.
utilities. Because each third-party deployment framework is unique, however, these solutions fall outside the scope of this 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 Windows PE as a pre-operating system environment. For Windows PE 2.0 If you are using Windows PE 2.
Creating a Bootable CD Use the following steps to create bootable media: 1 Click Start, navigate to All Programs→ Microsoft Windows AIK. 2 Click Windows PE Tools Command Prompt to open a command prompt window. 3 Run the following command: oscdimg -n -bc:\vistaPE_x86\etfsboot.com c:\vistaPE_x86\ISO c:\vistaPE_x86\WinPE2.0.iso This command creates a CD bootable ISO image called WinPE2.0.iso. You can use any CD burning software to burn the image onto a CD.
Using a Third-Party Deployment Solution Framework You can use the DTK with any existing third-party deployment solution framework that provides a Automated Deployment Services (ADS) booting infrastructure that can be used as the transport mechanism for the DTK utilities. Because each third-party deployment framework is unique, however, these solutions fall outside the scope of this document.
Choosing an Embedded LinuxBased Deployment Method 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 The Deployment Toolkit (DTK) is designed to be flexible enough to fit into almost any deployment plan.
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. The DTK start-up phase runs the script (name specified in the pxe config file) from the network.
system—the space on a network share can be very large, and a single set of utilities and scripts can be accessed by many systems, making the deployment process easy to manage. After a network drive is mapped from a target system to a network share, all of the utilities and scripts are available to use. The master deployment script on the network share can be called from the bootable CD to perform a task or multiple tasks on the target server.
This deployment method is the easiest to assemble, but is the least flexible. Any change to the system configuration, for example, requires the creation of a new bootable CD. This method does not provide a writable media making it necessary to use predefined and tested configuration files. Creating a Bootable CD Bootable CDs can be created using any commonly available CD burning software in a two-part process that requires a self-bootable ISO image with drivers that load from system files.
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.
Table 6-1. Deployment Method Matrix (continued) Deployment Methods Complexity Remote Moderate deployment over a network (bootable embedded Linux CD with network stack loaded) Advantages Disadvantages • Everything is in one place in a network share. • Must have network connection. • Deployment tasks must • Easy to manage— be performed at the changes have to individual target system. be made in only • Must locate the one place. appropriate embedded • Data captured Linux network drivers.
Table 6-1. Deployment Method Matrix (continued) Deployment Methods Complexity Advantages Disadvantages PXE boot High • Everything is in one place on a network share. • Must have high-speed connectivity to network (LAN). • Easy to manage— • Set up time is longer. changes have to be made in only in one place. • High flexibility for remote deployment. • No media required. • Faster deployment.
Choosing an Embedded Linux-Based Deployment Method
Preparing the Directory Structure for Deployment in Embedded Linux 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 the DTK components • Setting up a directory structure to facilitate a successful deployment, including a list of the supporting components that are not included with the DTK, but are needed to use the DTK • Setting up an optimally conf
Figure 7-1. CD Directory Structure Table 7-1 describes the files, components, and other contents of the mounted CD. Table 7-1. Mounted CD Contents Contents Details Location dchipm32.ini Configuration file for the instrumentation software. /opt/dell/toolkit/lib/bin docs Contains: /mnt/cdrom/docs • Command Line Interface Reference Guide • User’s Guide LICENSING Contains all the licenses for the open source components used in this CD. /mnt/cdrom/ LICENSING omreg.
Table 7-1. Mounted CD Contents (continued) Contents Details Location prereqcheck Contains files that are used by srvadmin-openipmi.sh to run preliminary requisite checks. /mnt/cdrom/tools/ openipmi/ supportscripts sa.1 Contains the Linux kernel images /mnt/cdrom/isolinux sa.
Figure 7-2. Target System Directory Structure Table 7-2 describes the contents of the directory structure on the target system.
Table 7-2. Target System Directory Structure Contents Contents Details /lib The libraries and drivers required for embedded Linux to function. /bin Basic utilities (ls, chmod, and so on) /sbin Utilities that are required by the system superuser to perform administrative tasks. /opt The libraries, binaries, and scripts required for the toolkit to function, which are available at: /mnt/cdrom/tools/dell.tar.gz. NOTE: The /opt/dell/srvadmin directory should be writable.
Table 7-3. System Utilities and Supporting Files Toolkit Components Purpose config.ini Configuration file used by raidcfg. pci.ids Used with syscfg to report PCI devices. racadm 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. racadm5 Configures DRAC 5 RACs.
Table 7-3. System Utilities and Supporting Files (continued) Toolkit Components Purpose sys.ini A .ini file used with syscfg. UpinitErrorCodes.txt 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.
Sample Scripts Table 7-5 lists sample scripts necessary to perform a scripted deployment. NOTE: All DTK scripts are provided as examples only. Many of these sample scripts must be edited before they can be used in a deployment. 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.
Documentation Table 7-6 describes documents containing reference information for each DTK utility and instructions for using the DTK utilities and sample scripts. Documentation can be found at mnt/cdrom/docs. Table 7-6. Documentation Toolkit Components Purpose Command Line Interface Reference Guide Describes all DTK utilities, including all command line arguments and values, syntax, help, and examples. User’s Guide Contains best practices guidelines for performing a scripted deployment.
Table 7-7. Supporting Tools and System Files Additional Tools Purpose Source Save in DTK location mkfs.* To format hard-drive partitions. Any system running a In the path. Linux operating system. fdisk To partition the hard drive. Any system running a In the path. Linux operating system. unzip To unzip files in Linux. upimg Contains system-specific Dell utility partition files. Any system running a In the path. Linux operating system.
Setting Up a Directory Structure for Deployment To perform a 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 and can be used successively as a testing space, a repository for a network deployment, and a repository to build a bootable deployment CD.
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. See Figure 7-3.
Creating Operating System Installation Directories for Supported Linux Operating Systems NOTE: The following procedures are provided as a best practices guideline for creating operating system distribution folders compatible with the DTK sample scripts. For complete instructions on setting up an installation directory structure for an unattended installation, see your operating system documentation.
Figure 7-4.
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. See "Using the DTK Sample Scripts to Capture Configuration Information in Embedded Linux" for instructions on using the sample DTK scripts, syscap.sh and raccap.sh, to generate SYSCFG and RAC configuration files that are used to configure the target system.
How to Obtain Dell Utility Partition Files Obtain the Dell utility partition files from /opt/dell/toolkit/systems, the Dell Support website at support.dell.com, or the Systems Build and Update Utility on the Dell Systems Management Tools and Documentation DVD. RAC Configuration Configure the RAC on your source system using the racadm utility, if applicable.
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: • Writing the master deployment file and editing the tkenvset.
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.
Table 8-1. Scripts For Deployment Capture Scripts Replication Scripts raccap.sh — Captures RAC settings to a file for Dell™ Remote Access Controller (DRAC) 4. racrep.sh — Applies the RAC configuration settings saved in a file to the current system. Deployment Scripts Others lininst.sh — Performs an unattended installation of a supported Red Hat® Enterprise Linux® Server operating • tkenvset.sh — • tkenvset.sh — Used by raccap.sh Used by racrep.sh system.
Table 8-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts syscap.sh — Captures BIOS and BMC configuration settings and saves them to a file. sysrep.sh — Applies the BIOS and BMC settings saved in a file to the current system. • tkenvset.sh — Used by syscap.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. • tkenvset.sh — Used by sysrep.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files.
Table 8-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts raidcap.sh— Captures the RAID settings and saves them to a file. raidrep.sh— Applies the RAID settings saved in a file to the current system. Deployment Scripts Others suseinst.sh — Performs an unattended installation of a ® • tkenvset.sh — • raidcfg — Used by supported SUSE Linux Enterprise raidrep.sh to Used by Server operating raidcap.sh to retrieve RAID inform the task information and to system.
Table 8-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts Deployment Scripts Others – initial ramdisk— Available on the SUSE Linux Enterprise Server operating system CD – kernel image— Available on the SUSE Linux Enterprise Server operating system CD This script uses the following file for noninteractive (unattended) operations: – upinit.sh— Used by partcfg.sh to create and populate the Dell utility partition. • autoinst.xml — Used by suseinst.
Table 8-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts dtkrunall.sh— Applies BIOS, BMC, RAC, and RAID settings saved in the files to the current system. • tkenvset.sh — Used by dtkrunall.sh to find the DTK utilities and scripts. • racrep.sh — Used by dtkrunall.sh to apply the RAC configuration settings saved in a file to the current system. Deployment Scripts Others upinit.sh — Creates and populates the Dell utility partition.
Table 8-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts • sysrep.sh — Used by dtkrunall.sh to apply the BIOS and BMC settings saved in a file to the current system. • raidrep.sh— Used by dtkrunall.sh to apply the RAID settings saved in a file to the current system. Deployment Scripts Others • sysdrmk — Used by upinit.sh to patch the boot sector. • unzip — Used by upinit.sh to populate the Dell utility partition. • mke2fs — Used to make a ext2 file system. • upimg.
Specifying DTK Installation Paths The 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.
5 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 will be handed by the errhndl.sh scripts. Set the value to TRUE only if you want the deployment to exit on any error. 6 Set the variable that defines the directory containing the DRMK system files necessary to create a Dell utility partition (DT_DRMK).
To edit the RAC configuration variables, locate the following lines in raccap.sh: DT_RAC_CAPFILE=$dt_systems/$dt_platform/raccfg.ini 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.
# 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 will not override the setting and the utility partition will not be created. 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.
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. Locate the "USER MODIFICATION REQUIRED" heading in the task scripts to find the variable values you might need to edit.
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. The default variable values used in this script are set in the tkenvset.sh scripts. This script uses the raidcfg.sh utility to automatically configure the detected controllers on your target system.
partcfg.sh The partcfg.sh sample script creates and populates the Dell utility partition using upinit.sh and creates the deployment partition on a specified disk. (See "upinit.sh" for more information about using the upinit.sh tool.) User input is not required to run this script. The default variable values used in this script are set in the tkenvset.sh scripts. NOTE: Ensure that DT_HD is set to the required disk to be configured before you execute the partcfg.sh script.
Perform the following steps to run the syscap.sh sample script to capture BIOS and BMC configuration information in the syscfg.ini file: 1 Edit the start-up script file on your embedded Linux image to call the syscap.sh script after the network share with the prebuilt DTK directory structure is mounted. For example, add: source/opt/dell/toolkit/template/scripts /syscap.sh 2 Boot the source system into embedded Linux.
Perform the following steps to run the raccap.sh sample script to capture RAC configuration information in the raccfg.ini file: 1 Edit the start-up script file on your embedded Linux image to call the raccap.sh script after the network share with the prebuilt DTK directory structure is mounted. For example, add: source/dell/toolkit/template/scripts/raccap.sh 2 Boot the source system into embedded Linux.
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. lininst.sh The lininst.
External Dependencies The DT_PLATFORM variable is set during deployment by tkenvset.sh using platform discovery. The lininst.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. See "ks.cfg (for Red Hat Enterprise Linux Server Version 4) and ks-rhel5.cfg (for Red Hat Enterprise Linux Server Version 5)" for more information about preparing the unattended answer file. ks.
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. 4 Mount your NFS Share to /tmp/os_src. 5 Copy the file initrd.img for RHEL 32-bit to the NFS Share. 6 Copy vmlinuz from RHEL 32-bit 1st CD to the NFS Share. 7 Copy the ks.
suseinst.sh 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.
autoinst.xml (for SUSE Linux Enterprise Server) The autoinst.xml file is the default name of the answer file that you use to automate an unattended 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.
Running Deployment Scripts Using DTK and Embedded Linux 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.
3 Set up the Trivial File Transfer Protocol (TFTP) services and the Dynamic Host Configuration Protocol (DHCP) services on your network to boot the target system using Pre-Boot Execution Environment (PXE). 4 Copy the contents of the embedded Linux DTK ISO image (SA.1, SA.2, and isolinux.cfg) from /mnt/cdrom/isolinux to the tftp folder. 5 The isolinux.cfg file has various boot options. Select the method you want, and edit the isolinux.
4 Copy your custom scripts into the folder you created in step 3. (See "Installation for Embedded Linux" for an example of the folder structure.) NOTE: Your scripts should also take care of copying miscellaneous items to unlock the CD, so that the CD can be mounted and ejected as required by the operating system’s installation process. 5 In /mnt/cdrom/isolinux.cfg, edit the cd install section to point to your customized start-up script.
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): • Drivers for all your hardware installed in your embedded Linux (from the Dell Support website at support.dell.
Running Dell Update Packages in Embedded Linux This section provides best practice procedures and scenarios for running Dell™ Update Packages in the embedded Linux environment on supported Dell systems. 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.
Table 10-1. Dependencies for Dell Update Packages to Run in Customized Embedded Linux (continued) Update Packages PERC Dependency Dependencies Available On /etc/dataeng /mnt/cdrom/tools megaraid driver 2.4.2.0 /mnt/cdrom/tools SCSI drivers Kernel /etc/racser /mnt/cdrom/tools PPP /mnt/cdrom/tools racser3.sh /mnt/cdrom/tools Open IPMI /mnt/cdrom/tools Instrumentation drivers /mnt/cdrom/tools racser4.
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. 2 Store the update packages on a network share. 3 Mount the network share where you stored the update packages and run the individual packages.
Running Dell Update Packages in Embedded Linux
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 • Virtual disk creation and/or deletion takes a long time on Microsoft® Windows® PE.
SYSCFG Issues • Setup passwords and system passwords cannot be cleared using DTK. 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 • 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 2000 or Windows Server® 2003 locally or remotely.
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 will result from changing the state of the disk controller, so you should be certain before skipping the prompt. There is no method for using the --noraidprompt in the input file.
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 nonzero.
Features that have been removed from the DOS version include: • The --name and --wait options in the create command • The --runlocation and the --scratchlocation options • The --getpercentcomplete environment variables Q: What is the minimum virtual disk size that I can create? A: For CERC-SATA 1.
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. If the BIOS does not detect the controller, then RAIDCFG will also 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 is the field needed when you try to create a RAID 50. The number represents the span size of the RAID 5.
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 managed system’s operating system network parameters? A: No. The BMC has its own IP address, Gateway, Subnet Mask, and MAC address values.
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 CD 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: What is the version of the Linux kernel used? A: The Linux kernel is derived from 2.6.9-42.
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.
Known Issues and Frequently Asked Questions
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. Examples of adapter cards include network cards, sound cards, and SCSI adapters.
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 and executes programs stored in locations other than the Active Directory®. backup A copy of a program or data file.
BMC 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 ; otherwise, you must perform a cold boot by pressing the reset button or by turning the system off and then back on.
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. CLI Abbreviation for command line interface.
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 keyboard.
directory Directories help keep related files organized on a disk in a hierarchical, "inverted tree" structure. Each disk has a "root" directory; for example, a C:\> prompt normally indicates that you are at the root directory of hard drive C. Additional directories that branch off of the root directory are called subdirectories. Subdirectories may contain additional directories branching off of them. DKS Abbreviation for dynamic kernel support. DMA Abbreviation for direct memory access.
EPROM Acronym for erasable programmable read-only memory. ERA 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. ESM 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. expanded memory A technique for accessing RAM above 1 MB.
FAT 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. The operating system maintains a table to keep track of the status of various segments of disk space used for file storage. • FAT32 — A derivative of the FAT file system.
graphics mode A video mode that can be defined as x horizontal by y vertical pixels by z colors. GUI Acronym for graphical user interface. GUID Abbreviation for Globally Unique Identifier, which is a random number used in software applications. Each generated GUID is supposed to be unique. HAPI Acronym for Hardware Abstraction Programming Interface, which is the lowest layer that is installed on the operating system by the Instrumentation Service.
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. HTTPS is a variant of HTTP used by Web browsers for handling secure transactions. HTTPS is a unique protocol that is simply SSL underneath HTTP.
IRQ 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. Two devices can share the same IRQ assignment, but you cannot operate both devices simultaneously. KB Abbreviation for kilobyte(s), 1024 bytes.
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. memory address A specific location, usually expressed as a hexadecimal number, in the system's RAM.
NIC 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. It also supports object-oriented applications by treating all files as objects with user-defined and system-defined attributes. See also FAT.
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. Plug and Play provides automatic installation and configuration, compatibility with existing hardware, and dynamic support of mobile computing environments. POST Acronym for power-on self-test.
RAM 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. read-only file A read-only file is one that does not allow you to edit or delete it. A file can have read-only status if: • Its read-only attribute is enabled.
SAS Short for Serial Attached SCSI, SAS is an evolution of parallel SCSI into a pointto-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. Each SATA port communicates through a small cable, to a single hard drive. schema A collection of class definitions that describes managed objects in a particular environment.
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.
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. Because the System Setup program is stored in NVRAM, any settings remain in effect until you change them again. system.
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. URL Abbreviation for Uniform Resource Locator (formerly Universal Resource Locator). USB Abbreviation for Universal Serial Bus.
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. VT-100 Abbreviation for Video Terminal 100, which is used by the most common terminal emulation programs. WAN Abbreviation for wide area network.
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.
Glossary
Index C capturing configuration information embedded Linux, 121 Windows PE, 68 capturing the system BIOS & BMC configuration embedded Linux, 121 Windows PE, 68 CD-Based local deployment embedded Linux, 85 Windows PE, 27 CD-Based local deployment, networking enabled embedded Linux, 84 Windows PE, 28 choosing a deployment method embedded Linux, 83 Windows PE, 27 configuration files, 11 configuring an optimally configured source system embedded Linux, 105 contents DTK embedded Linux, 95 DTK Windows PE, 36 cre
deployment prerequisites embedded Linux, 17 Windows PE, 16 M document organization, 11 Master Batch File sample, 54 what is, 54 drivers embedded Linux, 99 Windows PE, 41 O DTK, 95 embedded Linux contents, 95 installing, 91, 106 DTK deployment overview, 19 DTK prerequisites and requirements, 14 E editing DTK task scripts embedded Linux, 119 Windows PE, 66 editing the files embedded Linux, 108 Windows PE, 55 embedded Linux contents DTK, 95 I installation prerequisites embedded Linux, 15 Windows PE, 15
prerequisites for deployment embedded Linux, 17 Windows PE, 16 prerequisites for installation embedded Linux, 15 Windows PE, 15 R RAC configuring, 52 Running, 133 running a scripted deployment embedded Linux, 133 Windows PE 2.
scripted deployment in embedded Linux autoinst.xml, 128 capturing the RAC configuration, 122 ks.cfg, 125 lininst.sh, 109, 124 partcfg.sh, 111, 121 raccap.sh, 122 raccfg.sh, 109 racrep.sh, 119 raidcfg.sh, 110, 120 suseinst.sh, 127 sysrep.sh, 110, 120 tkenvset.sh, 109 upinit.sh, 113, 123 scripted deployment in Windows PE capturing the RAC configuration, 69 PARTCFG.BAT, 58, 68 RACCAP.BAT, 69 RACCFG.BAT, 56 RACREP.BAT, 66 RAIDCFG.BAT, 57, 67 SYSCAP.BAT, 68 SYSREP.BAT, 57, 61, 67 TKENVSET.BAT, 56, 62 UNATTEND.
U upgrading embedded Linux, 91 Windows PE, 33 using the DTK sample scripts embedded Linux, 107 preparing for a full deployment, 53, 107 Windows PE, 54 utilities and files needed for deployment embedded Linux, 101 Windows PE, 45 W what’s new for this release, 14 Windows PE contents DTK, 36 Index 173
Index
