Dell™ OpenManage™ Deployment Toolkit Version 2.4 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 Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. Abbreviations and Acronyms For a complete list of abbreviations and acronyms, see "Glossary." ____________________ Information in this document is subject to change without notice. © 2007 Dell Inc. All rights reserved.
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 . . . . . . . . . . . . . . . . 27 Choosing a Deployment Method for Microsoft Windows PE . . . . . . . CD-Based Local Deployment . . . . . . . . . . . 27 . . . . . . . . . . . 27 CD-Based Local Deployment With Networking Enabled . . . . . . . . . . . . . . . . 28 . . . . . . . . . . 29 . . . . . . . . . . . 30 Using a Third-Party Deployment Solution Framework . . . . . .
Configuring a Source System RAC Configuration 4 . . . . . . . . . . . . . . 50 . . . . . . . . . . . . . . . . . 51 Preparing the Script Files for Deployment Using Microsoft Windows PE . . . . . . . . . 53 Using the Sample DTK Scripts to Run a Full Deployment in Windows PE . . . . . . . . . . . . The Master Batch File (DEPLOY.BAT) . . . . . . . Editing the Sample Batch Files to Perform a Complete System Deployment in Windows PE 54 . . . . . 55 . . . . . . . . . . . 55 . . . . . . . . . . . .
5 Running Deployment Scripts Using DTK and Microsoft Windows PE . . . . . . . . . . . 75 For Windows PE 2005 . . . . . . . . . . . . . . . . . . 75 Obtaining Windows OEM Preinstallation Kit (OPK) or Windows PE CD . . . . . . . . . . . . . . . . . . 75 Copying Tools From OPK or Windows PE CD on a Development System . . . . . . . . . . . . . . . Creating a Standard Windows PE . 75 . . . . . . . . . 76 Integration of DTK Directory Structure in Windows PE Build . . . . . . . . . . . . . . . . .
6 Choosing an Embedded Linux-Based Deployment Method . . . . . . . . . . . . . . . . 83 . . . . . . . . . . 83 . . . . . . . . . . . 83 Choosing a Deployment Method for Embedded Linux . . . . . . . . . . . Network-Based Deployment . Using a Third-Party Deployment Solution Framework . . . . . . 7 . . . . . . . . . . 85 CD-Based Local Deployment for Embedded Linux . . . . . . . . . . . . . . . . . . 85 Deployment Matrix (Embedded Linux) . . . . . . . . .
Configuring a Source System . . . . . . . . . . . . . . . . . . . . 104 . . . . . . . . . . . . . . . . . 104 How to Obtain Dell Utility Partition Files RAC Configuration 8 Preparing the Script Files for Deployment Using Embedded Linux Using the Sample DTK Scripts to Run a Full Deployment in Embedded Linux . The Master Deployment File . . . 105 . . . . . . . . . . . . 105 . . . 106 . . . . . . . . . . . 106 . . . . . . . . . . . . . . . . . . . . .
suseinst.sh autoinst.xml (for SUSE Linux Enterprise Server) 9 123 . . . . . . . . . . . . . . . . . . . . . 124 . . . . . . . . Running Deployment Scripts Using DTK and Embedded Linux . . . . . . 125 Deployment Using Dell-Provided Embedded Linux . . . . . . . . . . 125 Deployment Using Customized Embedded Linux . . . . . . . . . . . . . . . . . . 128 Using a Third-Party Deployment Solution Framework . . . . . . . . . . . . . . . . 128 10 Running Dell Update Packages in Embedded Linux . .
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . 134 . . . . . . . . . . . . . . . . 135 . . . . . . . . . . . . . . . . . 138 General Deployment Questions RAIDCFG Questions SYSCFG Questions 134 . . . . . . . . . . . . 139 . . . . . . . . . . . . . . 141 Embedded Linux Questions Windows PE Questions . Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Index 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
NOTICE: 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.
This guide also includes a "Known Issues and Frequently Asked Questions" section. What’s New The Deployment Toolkit version 1.0 was the first release of a Dell-designed and tested suite of MS-DOS®—based utilities, sample script files, and best practices models to use for configuring and deploying Dell systems in a customized, predictable, and unattended manner. The new features for DTK version 2.
Because of the open nature of the utilities and scripts and the environment in which they can be used, it is strongly recommended that DTK users have an advanced understanding of the Windows PE and Linux environment and scripting knowledge for the respective environments. DTK users with an advanced understanding of Windows PE and Linux can take full advantage of the utilities and exploit their capabilities above and beyond what the sample scripts can provide.
Installation Prerequisites Before installing the DTK components for Windows PE, ensure that you have the following: • The DTK self-extracting zip file (dtk-2.X-winpe-AXX.
• A target system with a CD drive, if performing a local deployment • A target system with a CD drive and network access, if performing a network deployment • 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: • – Dell OpenManage Deployment Toolkit Version 2.
• • DTK documentation: – Deployment Toolkit Version 2.4 CLI Reference Guide – Deployment Toolkit Version 2.4 User’s Guide The Systems Service and Diagnostics Tools CD NOTE: If your system does not have a Systems Service and Diagnostics Tools CD, obtain the latest drivers from the Dell Support website at support.dell.com.
Deployment Methods Dell systems can be deployed using several different methods. The most common method is using the Systems Build and Update Utility CD that is shipped with your system. Currently, this method is used to deploy a single system at a time with the installation wizard. 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.
4 Edit the DTK sample script files that read the system configuration files to set up the system BIOS, BMC, RAID, and RAC and then install an operating system on a target system. 5 Generate a system BIOS, BMC, RAID, and/or RAC configuration profile from the optimally configured source system. (This source system will be the master server that will be used to replicate settings onto target servers.
5 Generate a system BIOS, BMC, RAID, and/or RAC configuration profile from the optimally configured source system. (This source system will be the master server that will be used to replicate settings onto target servers.) You can obtain the system BIOS, BMC, RAID, and/or RAC configuration files by booting from the DTK Linux ISO image and running the syscap.sh, raidcap.sh, and raccap.sh scripts. Then, copy the generated configuration files to a read/write share onto the workstation.
• The DTK scripts execute the necessary DTK utilities from the network share or the CD itself. • Configuration information is read from the network share. • The operating system is installed from a network share. (This installation may happen after your system reboots.) Deployment Using Removable Boot Media Without a Network Connection (CD-Based) 1 Create a deployment CD containing a bootable image with the appropriate drivers.
Other Dell Documents You Might Need In addition to this User's Guide and the Deployment Toolkit CLI 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/Modular Chassis User's Guide provides information about installation, configuration, and maintenance of the Dell Remote Access Controller/Modular Chassis (DRAC/MC). • The Dell Remote Access Controller Racadm User's Guide provides comprehensive information about using the RACADM command line utility.
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 PEBased 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.
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 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 dtk-2.X-winpe-AXX.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 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). See "Setting Up a Directory Structure for Deployment" for further discussion of the deployment directory structure.
Table 3-1. System Utilities and Supporting Files (continued) Toolkit Components Purpose RAC 5 Configures DRAC 5. 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.txt Lists the error codes and messages for the RAIDCFG.EXE tool. stsvc.ini Configuration file used by RAIDCFG.EXE. NOTE: Do not edit this file. Incorrect edits might cause RAIDCFG.EXE to fail. sys.
Table 3-2. Sample Configuration Files Toolkit Components Purpose RACCFG.INI Sample configuration file Move to the directory for DRAC 4 remote access Z:\Dell\Toolkit\Systems\. controllers. RAIDCFG.INI Sample output file to enable RAID replication. Move to the directory Z:\Dell\Toolkit\Systems\. SYSCFG.INI Sample configuration file for SYSCFG utility to configure the BIOS and BMC settings. Move to the directory Z:\Dell\Toolkit\Systems\. UNATTEND.
Table 3-2. Sample Configuration Files (continued) Toolkit Components Purpose Location WINBOM.INI Sample file used to start the racsvc and mr2kserv services. Z:\Dell\Toolkit\template\Configs WINPEOEM. SIF Sample file to add support Z:\Dell\Toolkit\template\Configs for Dell mass storage drivers. Sample Scripts Table 3-3 lists sample scripts of those necessary to perform a scripted deployment. The sample scripts are located in Z:\Dell\Toolkit\template\scripts.
Table 3-3. Sample Scripts (continued) Toolkit Components Purpose 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. RACCAP.BAT Captures remote access controller (RAC) settings to a file for DRAC 4 remote access controllers. RACREP.BAT Applies (replicates) the RAC settings saved in a file to the target system. RAIDCFG.
Table 3-4. Documentation Toolkit Components Purpose CLI 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. Drivers Table 3-5 describes the essential and optional drivers required for Dell-supported hardware to build your Windows PE environment.
Miscellaneous The document readme.txt, located at Z:\Dell\Toolkit, provides the latest product information. 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.
Table 3-6. Supporting Tools and System Files (continued) Additional Tools Purpose Source Save in DTK location 32-bit unzip utility Unzip utility partition images in Windows PE. www.info-zip.org Save in one of the path directories of your Windows PE image, preferably \I386\system32. upimg.bin Contains systemspecific Dell utility partition files. NOTE: This utility is not provided with the Dellsupplied DTK zip file.
directory structure on a network volume that is accessible from your workstation, the source system (to generate configuration information), and the target system (to deploy). If you plan to run a scripted deployment from the DTK sample scripts, ensure that the following files are correctly structured in the deployment directory. The DTK sample scripts use this structure to set the default paths for deployment. If you make changes to the directory structure, you must also make changes to the sample scripts.
This directory can also be subdivided into multiple system-specific directories such as: Z:\Dell\Toolkit\Systems\pe2850 for PowerEdge 2850 systems and Z:\Dell\Toolkit\Systems\pe1850 for PowerEdge 1850 systems. See Figure 3-2. NOTE: If you choose to create a directory structure for the system-specific files that is different from the one suggested in this guide, be sure to carefully review and edit each sample script (where necessary) to reflect the different directory structure. Figure 3-2.
Operating System Installation Files Creating Operating System Installation Directories for Supported Windows 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.
5 Create a \textmode directory in the \$OEM$ directory. For example: X:\Dell\Toolkit\Systems\PE1950\$OEM$.NET\textmode The \textmode directory is created as a repository for the mass storage device drivers and the Txtsetup.oem mass storage configuration file. NOTE: All files listed in the [OEMBootFiles] section of the UNATTEND.TXT answer file must be placed in the \textmode directory. 6 Create a \$1 directory in the \$OEM$ directory. For example: X:\Dell\Toolkit\Systems\PE1950\$OEM$.
Figure 3-3.
Creating Operating System Installation Directories for Windows Server 2008 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. NOTE: Microsoft Windows Server 2008 is scheduled to be available in the first half of 2008.
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. See "Using the DTK Sample Scripts to Capture Configuration Information in Windows PE" for instructions on using the sample DTK scripts, SYSCAP.BAT and RACCAP.
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 software. NOTE: If your system does not have a Dell Systems Service and Diagnostics Tools CD, obtain the latest drivers from the Dell Support website at support.dell.com.
Preparing the Directory Structure for Deployment in Microsoft Windows PE
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, make 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 RACREP.BAT to 2003 operating scripts where to inform the task 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. SYSCAP.BAT to configure the BIOS and BMC settings. SYSREP.BAT to configure the BIOS and BMC settings. W2K8INST.BAT— RAIDCFG.
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 NOTICE: 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.
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. User input is optional to run this script. The parameter is a name or path to a log file.
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. NOTE: Microsoft Windows Server 2008 is scheduled to be available in the first half of 2008. For the latest information, see http://www.microsoft.com/windowsserver2 008/default.mspx.
set DT_OSSRC=%DT_DRIVE%\sources :: 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.
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 \DellWinPEBuild specifies the path where the files necessary to create the Windows PE are temporarily stored. If this directory does not already exist, mkimg.cmd creates it. This process extracts all the necessary files from \I386 on the Windows Server 2003 product CD and puts them in \DellWinPEBuild drive. 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.
4 Starting required services: mr2kserv service should be installed and started for RAID to function; racsvc service should be installed and started for RACADM to function. For details on how to start the required services, see the sample winbom.ini file under \Dell\Toolkit\template\Configs. NOTE: When booting the target system, ensure that the RAC and the mr2kserv services are running. 5 Extracting the following files from your Windows Server 2003 product CD to \Dell\Toolkit\Tools: • rpcns4.
After you create an ISO image, you can use any CD burning software to burn the image onto a 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.
For Windows PE 2.0 If you are using Windows PE 2.0, download Windows Automated Installation Kit (Windows AIK) from the Microsoft website at www.microsoft.com. By default, 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 offline.
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. 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.
Running Deployment Scripts Using DTK and Microsoft Windows PE
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.
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. Alternatively, you can integrate the DTK components into an existing third-party deployment solution framework. See "Using a Third-Party Deployment Solution Framework.
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. For example, pre-operating system configuration tasks can be deployed from the network and operating system files can be installed.
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 • CLI 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. rac 5 Configures DRAC 5 RACs.
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. Table 7-4. Sample Configuration Files Toolkit Components Purpose autoinst.
Table 7-5. Sample Scripts Toolkit Components Purpose errhndl.sh Handles errors returned in the DTK scripts. lininst.sh Performs an unattended installation of a supported Red Hat Enterprise Linux Server operating system. partcfg.sh Creates and populates the Dell utility partition and creates the deployment partition on a specified hard drive. Before doing so, however, this script cleans out all existing partitions in your system. raccap.sh Captures RAC settings to a file. racrep.
Table 7-6. Documentation Toolkit Components Purpose CLI 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. 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.
Table 7-7. Supporting Tools and System Files (continued) Additional Tools Purpose Source Save in DTK location upimg Contains system-specific Dell utility partition files. kernel image Used during a Linux unattended installation. initial ramdisk Available on the Linux /opt/dell operating system CD or /toolkit NOTE: For legacy operating on the Systems Build and /systems Update Utility CD. systems, you may need to load the driver disk.
If you plan to run a scripted deployment from the DTK sample scripts, ensure that the following files are correctly structured in the deployment directory. The DTK sample scripts use this structure to set the default paths for deployment. If you make changes to the directory structure, you must also make changes to the sample scripts.
Figure 7-3. DTK System-Specific File Structure 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. Sample Operating System-Specific File Structure (Linux Operating System) 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.
• Access and load the latest utilities, drivers, and diagnostics for your system • Install Dell OpenManage™ systems management software NOTE: If your system does not have a Systems Service and Diagnostics Tools CD, obtain the latest drivers from the Dell Support website at support.dell.com.
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 RACs. racrep.sh — Applies the RAC configuration settings saved in a file to the current system. • tkenvset.sh — Used by raccap.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. Deployment Scripts Others lininst.
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. • tkenvset.sh — Used by raidcap.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. • raidcfg— Used by raidcap.sh to retrieve RAID information and to configure settings. Deployment Scripts Others suseinst.
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. • sysrep.sh — Used by dtkrunall.sh to apply the BIOS and BMC settings saved in a file to the current system. • raidrep.
Table 8-1. Scripts For Deployment (continued) Capture Scripts Replication Scripts Deployment Scripts Others • mke2fs — Used to make a ext2 file system. • 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.
Perform the following steps to confirm and/or edit the installation path variables: 1 Set the variable that defines the path to the full set of DTK deployment files (DT_PATH). This variable is set to $dt_drive/opt/dell/toolkit by default in the sample script. Edit this path to reflect the actual location of the DTK deployment files, if necessary. 2 Set the variable that defines the directory containing the DTK utilities (DT_TOOLS). This variable is set to $dt_path/bin by default in the sample script.
scripts or to the suggested directory structure, you must confirm that the syscfg.ini file is correctly named and that the path is set correctly for your deployment. To edit the SYSCFG capture variables, locate the following lines in syscap.sh: set DT_SYS_CAPFILE= $dt_systems/$dt_platform/syscfg.ini To edit the SYSCFG replication variables, locate the following lines in sysrep.sh: DT_SYS_REPFILE=$dt_systems/$dt_platform/syscfg.
Specifying Variables Used to Create Disk Partitions and Install the Dell Utility Partition NOTE: If the primary deployment state (DT_PARTN) is set to off, the partitioning deployment state subsection is skipped. The partcfg.sh sample script provides the following disk partitioning default values. These values must be confirmed, in some cases, and modified, in other cases, before performing a deployment. Locate the partn label to find the following lines in partcfg.
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. 2 Edit the default variable value for the default hard drive (DT_HD=sda), if applicable.
racrep.sh The racrep.sh sample script applies RAC configuration options to the target system based on configuration information that has been saved in a configuration file. User input is optional, depending on variables set in the racrep.sh sample script. This script uses the racadm wrapper script or the syscfg utility (depending on the version of RAC on your system) to configure the RAC in the target system using the RAC configuration file, raccfg.ini, passed as the first parameter to this script.
syscfg.ini, passed as the first parameter to this script. If this parameter is not passed, the default variables values used in this script are set in the sysrep.sh scripts. The syscfg.ini file is generated with the syscap.sh sample script. See "syscap.sh" for information about using the syscap.sh sample script to capture BIOS and BMC settings. The second parameter is a name or path to a log file. This parameter is not set to any value by default, and no log file is generated.
NOTE: For the script to complete successfully, the source system must have access to the network share that includes the prebuilt DTK directory structure. syscap.sh The syscap.sh sample script captures BIOS and BMC configuration settings and saves them to a specified location. An optional user input can be passed as a parameter. You can provide the path or file name as an input to this script.
raccap.sh The raccap.sh sample script captures RAC configuration settings and saves them to a specified location. An optional user input can be passed as a parameter. You can provide the path or filename as an input to this script. The default variable values used in this script are set in the script to the correct default values to perform a scripted deployment. The raccap.
upinit.sh 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. Upgrades or downgrades can be made only to existing Dell utility partitions to capture BIOS and BMC settings.
Utilities Used grub — Used in conjunction with the kernel image and initial ramdisk files, along with the unattended answer file to install the operating system. Variables Used • DT_OS_DISK — Sets the disk on which to deploy the Red Hat Enterprise Linux Server operating system. • DT_OS_SRC — Sets the location from where to copy the kernel image and initial ramdisk files. External Dependencies The DT_PLATFORM variable is set during deployment by tkenvset.sh using platform discovery. The lininst.
When you have completed all necessary modifications of the ks.cfg/ ksrhel5.cfg file, save the completed file in the /opt/dell/toolkit/systems/ directory. SUSE Linux Enterprise Server Operating Systems The suseinst.sh script is used to install supported SUSE Linux Enterprise 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.
External Dependencies The DT_PLATFORM variable is set during deployment by tkenvset.sh using platform discovery. The suseinst.sh script uses the unattended answer file in conjunction with the grub utility and kernel image and initial ramdisk files to install the operating system files. See "autoinst.xml (for SUSE Linux Enterprise Server)" for more information about preparing the unattended answer file. autoinst.xml (for SUSE Linux Enterprise Server) The autoinst.
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.
The CD burning software creates a self-bootable CD when the CD is booted. 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 (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, 118 Windows PE, 68 capturing the system BIOS & BMC configuration embedded Linux, 118 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, 103 contents DTK embedded Linux, 95 DTK Windows PE, 36 crea
drivers embedded Linux, 99 Windows PE, 41 DTK, 95 embedded Linux contents, 95 installing, 91, 104 M Master Batch File sample, 54 what is, 54 DTK deployment overview, 19 O DTK prerequisites and requirements, 14 operating system installation files embedded Linux, 102 Windows PE, 46 E editing DTK task scripts embedded Linux, 116 Windows PE, 66 editing the files embedded Linux, 106 Windows PE, 55 embedded Linux contents DTK, 95 I installation prerequisites embedded Linux, 16 Windows PE, 16 installing DTK
creating a standard Windows PE, 76 creating bootable Windows PE ISO image, 78 integrating DTK directory structure, 77 third-party deployment solution framework, 79, 81 prerequisites for installation embedded Linux, 16 Windows PE, 16 R RAC configuring, 51 Running, 129 running a scripted deployment embedded Linux, 129 Windows PE 2.
raidcfg.sh, 108, 117 suseinst.sh, 123 sysrep.sh, 108, 117 tkenvset.sh, 107 upinit.sh, 111, 121 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.TXT, 72 UPINIT.BAT, 60, 70 W2K8INST.BAT, 73 WININST.
utilities and files needed for deployment embedded Linux, 101 Windows PE, 44 W what’s new for this release, 14 Windows PE contents DTK, 36 Index 169
Index
