Dell OpenManage Deployment Toolkit 3.
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. © 2010 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 . . . . . . . . . . 12 . . . . . . . . . . . . . . . . . . . . . . . 14 Prerequisites and Requirements . . . . . . . . . . . . Supported Operating Systems to Run DTK Utilities . . . . . . . . . Supported Systems . 14 . . . . . . . . . 15 . . . . . . . . . . . . . . . . 15 Supported BIOS Firmware Versions . . . . . . . . 15 Installation Prerequisites . . . . . . . . .
2 Choosing a Microsoft Windows PE-Based Deployment Method . . . . . . . . 25 . . . . . . . . . . 25 . . . . . . . . . . . 25 Choosing a Deployment Method for Microsoft Windows PE . . . . . . . CD-Based Local Deployment . CD-Based Local Deployment With Networking Enabled . . . . . . . . . . . . . . . . 26 . . . . . . . . . . 28 . . . . . . . . . . . 28 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 . . . . . . . . . . . . . . 54 The Master Batch File (DEPLOY.BAT) . . . . . . . 54 Editing the Sample Batch Files to Perform a Complete System Deployment in Windows PE . . . . . . . . . . . . . . . . . . . . . . .
5 Running Deployment Scripts Using DTK and Microsoft Windows PE . . . . . . . . . . . . . . 73 Creating and Customizing Images for Windows PE 1.0 . . . . . . . . . . . . . . . . . . . . . 73 Obtaining Windows OEM Preinstallation Kit (OPK) or Windows PE CD . . . . . . . . . . . . . . . . . 73 Copying Tools From OPK or Windows PE CD on a Development System . . . . . . . . . . . . . 73 . . . . . . . . . 74 Creating a Standard Windows PE Integration of DTK Directory Structure in Windows PE Build . .
CD-Based Local Deployment With Networking Enabled . . . . . . . . Using a Third-Party Deployment Solution Framework . . . . . . 6 . . . . . . . . 81 . . . . . . . . . . 82 Choosing an Embedded Linux-Based Deployment Method . . . . . . . . . . . . . . . . . 83 Choosing a Deployment Method for Embedded Linux . . . . . . . . . . . Network-Based Deployment . . . . . . . . . . . 83 . . . . . . . . . . . 84 Using a Third-Party Deployment Solution Framework . . . . . . . . . . . . . . . .
Setting Up a Directory Structure for Deployment . . . . 100 DTK Utilities and Files . . . . . . . . . . . . . . . 101 System-Specific Files . . . . . . . . . . . . . . . . 101 Creating Operating System Installation Directories for Supported Linux Operating Systems . . . . . . . . . . . Configuring a Source System . . . . . . 102 . . . . . . . . . . . . . . 104 . . . . . . 105 . . . . . . . . . . . . . . . . .
Preparing the Operating System Installation Scripts . . . . . . . Red Hat Enterprise Linux Server Operating Systems . . . . . . . lininst.sh . . . . . . . . . . 125 . . . . . . . . . . . . . . . . . . . . . . 125 ks.cfg and ks-rhel5.cfg 126 . . . . . . . . . . . . SUSE Linux Enterprise Server Operating Systems . . . . . . suseinst.sh 126 . . . . . . . . . . . . . . . Install Linux Using lininst.sh . . . . . . . . . . . 127 . . . . . . . . . . . . . . . . . . . . . 127 autoinst.
General Issues . . . . . . . . . . . . . . . . . . . 139 RAIDCFG Issues . . . . . . . . . . . . . . . . . . 139 RACADM Issues . . . . . . . . . . . . . . . . . . 140 Windows PE Installation Issues Frequently Asked Questions . . . . . . . . . . 140 . . . . . . . . . . . . . . 140 . . . . . . . . . . 140 . . . . . . . . . . . . . . . . 141 . . . . . . . . . . . . . . . . . 145 General Deployment Questions RAIDCFG Questions SYSCFG Questions Embedded Linux Questions Windows PE Questions .
1 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.
Introduction to the DTK User’s Guide While the DTK is designed to be flexible and expandable, this guide is limited to providing general, best practices procedures that focus on the basic tasks for a successful deployment. Users might find many alternative solutions to the best practices guidelines described in this guide and many additional uses for the DTK utilities beyond what is covered in this guide or in the Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide.
Table 1-1.
What’s New The new features for this release include: • Support for Windows PE 3.
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]), Windows PE 2.0(created using 32-bit and 64-bit version built on the Windows Vista kernel), and Windows PE 3.0(created using 32-bit and 64bit version built on the Windows 7 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 Microsoft Windows Server 2003 (with SP1) to build Windows PE 1.0 • Windows AIK 1.1 released with Vista SP1 and Windows 2008 to build Windows PE 2.0 • Windows AIK for Windows 7 to build Windows PE 3.
– 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. Obtain the latest drivers from the Dell Support website at support.
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).
• The Dell OpenManage Legacy Compatibility Guide provides compatibility information about Server Administrator installation and operation on various hardware platforms (or systems) running supported Windows, Red Hat Enterprise Linux Server, and SUSE Linux Enterprise Server operating systems. • The Dell Systems Software Support Matrix provides information about the various Dell systems, the operating systems supported by these systems.
Other Supporting Documents You Might Need Besides the Dell-provided documentation, there are numerous other resources to aid you in planning and executing a DTK-assisted deployment: • Operating system documentation to prepare for and execute the unattended installation process. In addition, you should consult the available Web-based resources such as: – The Microsoft Tech Net database at www.microsoft.com/technet – The Red Hat Enterprise Linux support pages at www.redhat.
Choosing a Microsoft Windows PE-Based Deployment Method 2 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.
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 for Windows PE 1.0 or Windows Deployment Services (WDS) booting infrastructure for Windows PE 2.0 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.
Table 2-1. Deployment Method Matrix Deployment Methods Complexity Local deployment Relatively (bootable CD) simple Advantages Disadvantages • Necessary if a network connection is not available or is too slow. • Any change requires the creation of a new bootable CD. • Can install supported Windows operating systems. • Limited space on CD for some operating system installation files. • Deployment tasks must be performed at the individual target system. • For Windows PE 1.
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.
3 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 optim
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:\.
The files are unzipped in the directory structure shown in Figure 3-1. 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.
DTK utilities for 32-bit systems are located in the following directories: • Utilities: Z:\Dell\x32\Toolkit\Tools • Sample scripts: Z:\Dell\x32\Toolkit\template\scripts • Sample configuration files: Z:\Dell\x32\Toolkit\template\Configs DTK utilities for 64-bit systems are located in the following directories: • Utilities: Z:\Dell\x64\Toolkit\Tools • Sample scripts: Z:\Dell\x64\Toolkit\template\scripts • Sample configuration files: Z:\Dell\x64\Toolkit\template\Configs The directory Z:\Dell\x32\To
Table 3-1. System Utilities and Supporting Files Toolkit Components Purpose config.ini Configuration file used by RAIDCFG.EXE. NOTE: Do not edit this file. Incorrect edits might cause RAIDCFG.EXE to fail. mr2kserv.exe Service that needs to be running for RAIDCFG.EXE to function. IDRAC Configures iDRAC6. NOTE: This feature may not be supported on all systems. pci.ids Used with SYSCFG.EXE to report PCI devices. RAC 4 Configures Dell Remote Access Controller (DRAC) 4/P and DRAC 4/I.
Table 3-1. System Utilities and Supporting Files (continued) Toolkit Components Purpose SyscfgErrorCodes.txt Lists the error codes and messages for the SYSCFG.EXE tool. sysdrmk.exe Used by UPINIT.BAT to patch the boot sector and Master Boot Record (MBR). UpinitErrorCodes.txt Lists the error codes and messages for UPINIT.BAT. version.txt Contains the DTK version in use. Sample Configuration Files Table 3-2 describes examples of configuration files used to perform a scripted deployment.
Table 3-2. Sample Configuration Files (continued) Toolkit Components Purpose Location UNATTEND. TXT Sample file used in Move to the directory Windows PE 1.0 \Toolkit\Systems\ after the environment with UNATTEND.TXT file is edited. unattended installation of Microsoft Windows operating systems. This file is populated with all the necessary information for Dell-supported mass storage devices. UNATTEND. XML Sample file used in Windows PE 2.
Sample Scripts Table 3-3 lists sample scripts of those necessary to perform a scripted deployment. The sample scripts are located in Toolkit\template\scripts. NOTE: All DTK scripts are provided as examples only. The batch scripts and configuration files must be modified to reflect the unique information for each deployed system. Table 3-3. Sample Scripts Toolkit Components Purpose createup.cfg This file is used by UPINIT.BAT. DISKPARTCLR.CFG Used by PARTCFG.
Table 3-3. Sample Scripts (continued) Toolkit Components Purpose UMOUNTUP.CFG This file is used by UPINIT.BAT. UPINIT.BAT Creates and populates the Dell utility partition. 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.
Drivers Table 3-5 describes the essential and optional drivers required for Dell-supported hardware to build your Windows PE environment. NOTE: The drivers provided have been tested successfully in the Windows PE environment built during the test. Table 3-5. Drivers Drivers Purpose winpe1.x\ DRIVERINST.BAT Used to install Dell-provided drivers, from Z:\Dell\x32\Drivers or Z:\Dell\x64\Drivers, into the customized Windows PE 1.0 image. winpe2.x\ Used to install Dell-provided drivers, from VPE_DRIVERINST.
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 lists the 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 Source Save in DTK location upimg.bin Contains systemspecific Dell utility partition files. Save in the \Toolkit\Systems, the Dell Support website at \Toolkit\Systems directory. support.dell.com, or the Dell Systems Build and Update Utility on NOTE: In the previous releases, the Dell Systems each Dell system Management Tools and required a unique Documentation DVD upimg.bin file. Starting in DTK 2.3 , the upimg.
NOTE: Do not create your DTK directory structure on a NetWare network volume. The DTK network-based deployment is not supported from mapped NetWare systems. DTK Utilities and Files All necessary DTK files are provided as part of the initial installation. It is strongly suggested that you use the default directory structure created in the initial installation of the DTK components. The sample scripts provided with the DTK are set up to use these default paths. See Figure 3-1.
Figure 3-2.
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.
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 \Toolkit\template\scripts 12 On your system, set DT_DRIVE=Z: 13 Navigate to Toolkit\template\scripts and run W2K8INST.BAT. Figure 3-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 Windows PE" for instructions on using the sample DTK scripts, SYSCAP.BAT and RACCAP.BAT, to generate SYSCFG and RAC configuration files that are used to configure the target system.
RAC Configuration Configure the RAC on your source system using the RACADM.EXE utility, if applicable. See the Dell Remote Access Controller Racadm User's Guide for comprehensive information about using the RACADM.EXE utility to configure the RAC on your source system. After you have successfully prepared your directory structure for a deployment and fully configured your source system, you are ready to write, review, or edit the deployment sample scripts.
Preparing the Directory Structure for Deployment in Microsoft Windows PE
Preparing the Script Files for Deployment Using Microsoft Windows PE 4 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.
***************************************************** :: Put hdd as first in boot sequence (1-removable, 2cdrom, 3-hdd) :: If the system configuration has changed (i.e. a ::boot device was added, removed, or enabled in BIOS) ::the following line should be modified to reflect the ::new hdd device number. :: This is calling Windows installer scripts. ***************************************************** ::%DT_TOOLS%\syscfg --bootseq=hdd.emb.0 ::call WININST.
Scripts for Deployment You may need the following scripts for deployment: Table 4-1. Capture Scripts Script Name Description Associated Files RACCAP.BAT Captures RAC settings • TKENVSET.BAT — Used by to a file for DRAC 4. RACCAP.BAT to inform the task scripts where to find the DTK utilities, scripts, and configuration files. • RACADM.EXE — Used by RACCAP.BAT to retrieve RAC information and to configure settings. SYSCAP.BAT Captures BIOS and • TKENVSET.BAT — Used by BMC configuration SYSCAP.
Table 4-2. Replication Scripts Script Name Description Associated Files RACREP.BAT Applies the RAC configuration settings saved in a file to the current system. • TKENVSET.BAT — Used by RACREP.BAT to inform the task scripts where to find the DTK utilities, scripts, and configuration files. • RACADM.EXE — Used by RACREP.BAT to replicate RAC information and to configure settings. RAIDREP.BAT Applies the RAID • RAIDCFG.EXE — Used by RAIDREP.
Table 4-3. Deployment Scripts Script Name Description Associated Files WININST.BAT Performs an • TKENVSET.BAT — Used by unattended installation W2K8INST. of supported Windows BAT to inform the task scripts 2000 Server and where to find the DTK Windows Server 2003 utilities, scripts, and operating systems. configuration files. • SETUP.EXE — Used by W2K8INST. BAT to install the operating system in conjunction with the UNATTEND. XML answer file. • UNATTEND. XML — Used by W2K8INST.
Table 4-4. Others (continued) Script Name Description Associated Files RAIDCFG.BAT Configures the selected • TKENVSET.BAT — Used by RAIDCFG.BAT to inform the Redundant Array of task scripts where to find the Independent Disks DTK utilities, scripts, and (RAID) controller configuration files. detected in the system. • RAIDCFG.EXE — Used by RAIDCFG.BAT to retrieve RAID information and to configure settings. PARTCFG.BAT Creates and populates • TKENVSET.BAT — Used by PARTCFG.
TKENVSET.BAT Example Editing 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 script. Other task scripts might require edits in certain situations. These optional edits are discussed in "Editing DTK Task Scripts." 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.
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\x32\Toolkit\Template\Scripts\SYSCAP.BAT 2 Boot the source system into Windows PE.
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\x32\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 \Toolkit\Template\Configs directory. UNATTEND.
5 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 Extracting the following files from your Windows Server 2003 product CD to \Dell\Toolkit\Tools: • rpcns4.dl_ • rpcrt4.dl_ • rpcss.dl_ NOTE: The directory name should not have any spaces. NOTE: You can now proceed to customize Windows PE per your requirements. Creating a Bootable Windows PE ISO Image After you have completed the DTK integration and customization, you are now ready to convert all the files in into an ISO image using the OPK tool.
CD-Based Local Deployment You are now ready to use your bootable CD to call the deployment components from the directory structure on the CD: 1 Boot the target system with the bootable deployment CD. 2 Execute the master batch file, which calls individual task scripts and utilities from the CD to complete the deployment process. Running the Windows PE 1.
Creating and Customizing Images 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. NOTE: DTK 3.2 for 64-bit systems supports only Windows PE 2.0. Integration of DTK Directory Structure in Windows PE Build DTK provides a script, VPE_driverinst.bat, to pre-install the Dell drivers into a base Windows PE 2.0 image (winpe.
3 Replace the customized winpe.wim image to the folder VistaPE_x86\ISO\sources. For example: Copy c:\vistaPE_x86\winpe.wim c:\vistaPE_X86\ISO\sources\boot.wim Creating a Bootable CD Use the following steps to create bootable media: 1 Click Start, navigate to All ProgramsMicrosoft 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.
Creating and Customizing Images for Windows PE 3.0 If you are using Windows PE 3.0, download Windows AIK from the Microsoft website at www.microsoft.com. By default, Windows AIK is copied to the C:\Program Files\Windows AIK directory. NOTE: DTK integrated with Win PE 3.0 does not support PERC 4 controllers. Integration of DTK Directory Structure in Windows PE 3.0 Build DTK provides a script, WINPE3.0_driverinst.bat, to pre-install the Dell drivers into a base Windows PE 3.0 image (winpe.wim).
Creating a Bootable CD Use the following steps to create bootable media: 1 Click Start, navigate to All ProgramsMicrosoft Windows AIK. 2 Click Windows PE Tools Command Prompt to open a command prompt window. 3 Move to the C:\program files\Windows AIK\Tools\x32 or C:\program files\Windows AIK\Tools\amd64 directory based on the system. 4 Run the following command: oscdimg -n -bc:\winpe_30\etfsboot.com c:\winpe_30\ISO c:\winpe_30\WinPE3.0.iso This command creates a CD bootable ISO image called WinPE3.0.iso.
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 6 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
7 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 c
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.
Boot the CD onto a target system. Figure 7-2 shows the directory structure on the target system. Figure 7-2.
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.
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. The batch scripts and configuration files must be modified to reflect the unique information for each deployed system. Table 7-5. Sample Scripts Toolkit Purpose Components 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.
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. ReadMe Provides the latest product information. It is located in the mnt/cdrom/docs directory.
Table 7-7. Supporting Tools and System Files (continued) Additional Tools Purpose upimg Contains system-specific Dell utility partition files. Source Save in DTK location /opt/dell /opt/dell/toolkit/ /toolkit/ systems, the Dell systems Support website at NOTE: In the previous releases, each Dell system support.dell.com, or the required a unique upimg file.
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.
See Figure 7-4 for a sample directory structure for deployment of a supported Linux operating system. NOTE: If you choose to create a directory structure for the Linux installation 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 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 Directory Structure for Deployment in Embedded Linux
8 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. Capture Scripts Script Name Description Associated Files raccap.sh Captures RAC settings • tkenvset.sh — Used by to a file for Dell raccap.sh to inform the task Remote Access Conscripts where to find the DTK troller (DRAC) 4. utilities, scripts, and configuration files. • racadm — Used by raccap.sh to retrieve RAC information and to configure settings. The wrapper script, racadm, calls racadm3 or racadm4 depending on the system configuration. • syscfg — Used by raccap.
Table 8-2. Replication Scripts Script Name Description Associated Files racrep.sh Applies the RAC configuration settings saved in a file to the current system. • tkenvset.sh — Used by racrep.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. • racadm — Used by racrep.sh to replicate RAC information and to configure settings. racadm is the wrapper script which calls racadm3 or racadm4 depending on the system configuration. • syscfg — Used by racrep.
Table 8-3. Deployment Scripts Script Name Description Associated Files lininst.sh Performs an unat• tkenvset.sh — Used by tended installation of a lininst.sh to inform the task supported Red Hat scripts where to find the DTK Enterprise Linux utilities, scripts, and Server operating sysconfiguration files. tem. • grub — Used to install the operating system in conjunction with the unattended answer file.
Table 8-3. Deployment Scripts Script Name Description Associated Files suseinst.sh Performs an unat• tkenvset.sh — Used by suseinst.sh to inform the task tended installation of a scripts where to find the DTK supported SUSE Linux utilities, scripts, and Enterprise Server operconfiguration files. ating system. • grub — Used to install the operating system in conjunction with the unattended answer file.
Table 8-4. Other Scripts Script Name Description Associated Files tkenvset.sh Sets the path of the • syscfg — Used by tkenvset.sh DTK installation and to discover the system type. variables for the system to be deployed and configured. The variables and paths specified in this file must be specified before any of the other supporting scripts can be used. raidcfg.sh Configures the selected • tkenvset.sh — Used by raidcfg.
Table 8-4. Other Scripts Script Name Description Associated Files partcfg.sh Creates and populates • tkenvset.sh — Used by partcfg.sh to inform the task the Dell utility partiscripts where to find the DTK tion and the deployutilities, scripts, and ment partition on a configuration files. specified disk. The partcfg.sh script uses a • fdisk — Used to create /tmp folder to store a partitions on your disk. When few temporary files criticreating an embedded Linux cal to its execution.
Table 8-4. Other Scripts Script Name Description Associated Files upinit.sh • tkenvset.sh — Used by upinit.sh to inform the task scripts where to find the DTK utilities, scripts, and configuration files. Do not make any modifications to the upinit.sh • fdisk — Used to create partitions on your disk. script. Creates and populates the Dell utility partition. • mbr — File necessary to create a bootable Dell utility partition. • sysdrmk — Used by upinit.sh to patch the boot sector.
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.
ks.cfg and ks-rhel5.cfg Depending on the version of the Red Hat Enterprise Linux Server operating system, the ks.cfg or ks-rhel5.cfg files are the default names of the answer files that you use to automate an unattended Red Hat Enterprise Linux Server installation. A sample copy of the ks.cfg/ ks-rhel5.cfg files are provided as part of the DTK download in the /opt/dell/toolkit/template/configs directory. The ks.cfg/ksrhel5.
8 Edit the file ks.cfg. Set the NFS IP Address where RHEL 32-bit images are available and the NFS share path. 9 Run export DT_OS_DISK=/dev/sda, the disk device on which the Dell Utility partition was created. 10 Run export DT_OS_SRC=/tmp/os_src, where vmlinuz,initrd.img and ks.cfg available. 11 Run export DT_HD=/dev/sda. 12 From /opt/dell/toolkit/template/scripts, run ./lininst.sh script. 13 After 20 seconds, the server reboots and boots to the GRUB prompt.
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 SUSE Linux Enterprise Server operating system. • DT_OS_SRC— Sets the location from where to copy the kernel image and initial ramdisk files. • DT_OS_PART— Sets the valid partition to install the grub files.
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.
Preparing the Script Files for Deployment Using Embedded Linux
Running Deployment Scripts Using DTK and Embedded Linux 9 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.
10 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 Dependency Dependencies Available On PERC /etc/dataeng /mnt/cdrom/tools megaraid driver 2.4.2.0 /mnt/cdrom/tools SCSI drivers Kernel 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
11 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.
• On PowerEdge 1950, 2950, and PowerVault NX 1950 systems with internal USB, you can configure BIOS settings for internal USB Port only if the User Accessible/external (UA) USB ports are set to All Ports On. If the UA USB ports are not set to All Ports On and you try to configure BIOS setting for the internal USB port using SYSCFG, the configuration will appear to be successful but the changes will not take effect after the next reboot.
scratch. If you are deploying multiple systems, for example, you will need to provide unique information for each system when appropriate. To perform this task, you will need to modify each .ini (or other configuration script) file to reflect the unique information for each system you are deploying (such as the remote access controller (RAC) IP addresses and BIOS asset tags).
A: This behavior occurs because the RAIDCFG CLI parser ignores zeros preceding any parameter value. For example, -r=01 will be parsed as -r=1. Q: What is strict creation? A: Strict creation is an optional flag that has been added to the create virtual disk command. It allows you to create virtual disks only if the array disks (that is, hard drives) are within a specified percentage of disk space of each other.
Q: What features have changed from the MS-DOS version of RAIDCFG to the Windows PE and embedded Linux versions? A: New features for the Windows PE embedded Linux RAIDCFG include: Support for the following controllers: • PERC 4/SC, PERC 4/DC, PERC 4/Di, and PERC 4/IM • PERC 4e/DC, PERC 4e/Di, and PERC 4e/Si • PERC 5/E Adapter, PERC 5/I Integrated, and PERC 5/i Adapter • SAS 5iR Integrated, SAS 5iR Adapter • SAS 6iR Integrated, SAS 6iR Adapter • PERC 6/E Adapter, PERC 6/i Integrated, PERC 6/i Adapt
• RAID 1: 100MB • RAID 5: 100MB • RAID 6: 100MB • RAID 60: 100MB Q: Why can’t I see any controllers using RAIDCFG? A: Ensure that the RAID controller(s) can be seen in the BIOS during POST. 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.
SYSCFG Questions NOTE: In a Linux environment, the DTK utilities do not have a .exe extension. Q: On x7xx systems, when I set arguments for --sata0 and --sata1 using DTK CLI and reboot the system, the BIOS setup shows the earlier settings for -sata0 and --sata1. A: You need to set the --idectrl to auto before you can change the settings for --sata0 and --sata1. Q: On x7xx systems, the BIOS setup shows --conred arguments of --serial1 and --rac, whereas the DTK CLI shows them of --serial1 and --serial2.
Q: Are duplicate usernames allowed in the BMC? A: No. If you enter a username value that already exists, the SYSCFG utility returns an error code of 89, which means This username is already in use. Enter a unique username. Q: In --solcfgparams, when I set the Serial Over LAN (SOL) character send threshold using solcharsendthreshold to be 225, I get a Hardware subsystem error. Invalid data field in request.
Q: Can we use the same sample scripts that we have from earlier versions of DTK? A: The scripts written for the previous versions (2.x) of DTK will not work in DTK 3.x versions for embedded Linux. See the directory /opt/dell/toolkit/template/scripts for the sample scripts. Q: After I install a legacy operating system on a newer Dell system, the Linux kernel does not boot and panics.
by searching the INF file used to install the device or driver.) For more information, see Microsoft Knowledge Base Article 275334 on the Microsoft website. Q: When I try to install network interface controller (NIC) drivers into my Windows PE image using DRVINST.EXE [provided in the OEM Preinstallation Kit (OPK) CD], the DRVINST.EXE fails with an error message that there are some files missing. A: Dell recommends that you use DRIVERINST.BAT (provided with DTK). However, if you use DRVINST.
Index C capturing configuration information embedded Linux, 122 Windows PE, 66 capturing the system BIOS & BMC configuration embedded Linux, 122 Windows PE, 66 CD-Based local deployment embedded Linux, 85 Windows PE, 25 CD-Based local deployment, networking enabled embedded Linux, 84 Windows PE, 26 choosing a deployment method embedded Linux, 83 Windows PE, 25 configuration files, 11 configuring an optimally configured source system embedded Linux, 104 contents DTK embedded Linux, 95 DTK Windows PE, 34 crea
embedded Linux contents, 95 installing, 91, 105 O DTK prerequisites and requirements, 14 operating system installation files embedded Linux, 102 Windows PE, 45 E overview deploying, 21 preparing for deployment, 19 editing DTK task scripts embedded Linux, 120 Windows PE, 64 P DTK deployment overview, 19 editing the files embedded Linux, 108 Windows PE, 55 embedded Linux contents DTK, 95 I installation prerequisites embedded Linux, 15 Windows PE, 15 installing DTK, 91, 105 embedded Linux, 91 M Mast
third-party deployment solution framework, 77, 82 configuring, 51 Running, 135 running a scripted deployment embedded Linux, 135 Windows PE 2005, 73 running a scripted deployment, embedded Linux network-based deployment, 135 third-party deployment solution framework, 134 using customized embedded Linux, 134 using Dell-provided embedded Linux, 131 running a scripted deployment, using Dell-provided embedded Linux CD-based deployment, 132 Network-based deployment, 131 running a scripted deployment, Windows PE
capturing the RAC configuration, 67 PARTCFG.BAT, 66 RACCAP.BAT, 67 RACREP.BAT, 64 RAIDCFG.BAT, 65 SYSCAP.BAT, 66 SYSREP.BAT, 57, 65 TKENVSET.BAT, 58 UNATTEND.TXT, 70 UPINIT.BAT, 68 W2K8INST.BAT, 71 WININST.
