Dell OpenManage Deployment Toolkit Version 5.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction........................................................................................................... 4 Documents you may need....................................................................................................................4 Accessing documents from Dell support site...................................................................................... 4 Prerequisites...............................................................................................
Introduction The Dell OpenManage Deployment Toolkit (DTK) includes a set of utilities, sample scripts, and sample configuration files that you can use to deploy and configure the Dell systems. You can use DTK to build script-based and RPM-based installation for deploying large number of systems on a pre-operating system environment in a reliable way, without changing their current deployment processes.
• Using search engines: – Type the name and version of the document in the search box. Prerequisites Before using DTK to deploy Microsoft Windows Pre-installation Environment (PE) or Linux environment (Red Hat Enterprise Linux or SUSE Linux Enterprise Server), ensure you have the following prerequisites: Table 1. Prerequisites for Installation Windows PE Environment Linux Environment The DTK self-extracting zip file (DTKX.X-WINPE-XX.exe) available at dell.com/support.
• A target system with a media drive and network access, if performing a network deployment. • All DTK utilities, sample scripts, and sample configuration files. • Dell Systems Management Tools and Documentation DVD. • Your operating system software and documentation. • An optimally configured source system with network access. NOTE: You can also download the latest drivers from www.dell.com/support. Preparing Windows PE environment for deployment If you are using the Windows PE environment: 1.
10. Copy the extracted driver file to Out-of-Box Drivers folder on the source system. 11. On the target system, to map the shared folder WinServer_deploy on to the target system, run the following command: net use z: \\ \WinServer_deploy /USER: Password: 12. Navigate to \Toolkit\Template\Configs. 13. From \Toolkit\Template\Configs, copy Unattend.xml to z:\PER730. NOTE: The unattend.
Installing Windows client Operating System using DTK To install Windows client operating system using DTK: 1. On the source system, create an operating system-specific folder. For example, WinClient_deploy. 2. Make WinClient_deploy folder shareable. 3. In the folder WinClient_deploy, create two folders sources and platform name (for example, PR7910). NOTE: The platform name must be a DTK standard name. To know the platform name, run TKENVSET.BAT located in the x:\Dell\Toolkit\Template\Scripts directory
• A workstation with the following capabilities: – A writable media drive – Network access • A target system with a media drive, if performing a local deployment. • A target system with a media drive and network access, if performing a network deployment. • All DTK utilities, sample scripts, sample configuration files, and RPM packages. • All operating system RPM packages that DTK RPMs require.
3. Share /home/rhelshare. NOTE: If the folder you want to share is /home, then the /etc/exports file must contain the “/ home *(rw)” line. 4. Restart the NFS service. 5. Copy the operating system image to the NFS share. 6. Copy initrd.img for Red Hat Enterprise Linux to NFS share. 7. Copy vmlinuz from Red Hat Enterprise Linux operating system image to NFS share. 8. Boot DTK on the target machine. 9. Create the virtual disk using the raidcfg command. 10. Create a directory under /tmp.
NOTE: Using RACADM scripts is an alternative method to install Red Hat Enterprise Linux server operating system. This feature is supported on Dell’s 12th generation of PowerEdge Servers and later systems. For information see, Dell OpenManage Deployment Toolkit User’s Guide or Dell OpenManage Deployment Toolkit Command Line Interface Reference Guide available at dell.com/ openmanagemanuals . To convert from DTK to RACADM deployment and to install Red Hat Enterprise Linux using the lininst.sh / lininst7.
a. Run export DT_OS_DISK=/dev/sda on the disk device on which the Dell utility partition was created. b. Run export DT_OS_SRC=/tmp/os_srcwhere linux, initrd.img, and autoinst.xml/ autoinst.xml_uefi are available. c. Run export DT_OS_PART=/dev/sda. d. Run export DT_OS_IMG_PATH=nfs:///osimage. e. Run export DT_SUSE_AUTOINST= nfs:///dtkosinstall/autoinst.xml. f. Run export DT_HD=/dev/sda. 12. Run partcfg.
Installing CentOS Linux Server Operating System CAUTION: Do not change the bootmode before executing installation scripts using syscfg. If you do, reboot the system and start executing installation scripts. NOTE: See your operating system documentation for instructions on modifying the options in the ks.cfg/ks-centosx.cfg/ks_centosx_uefi.cfg file to customize the scripted installation of your operating system, where x indicates the version of the operating system.
Downloading Seamless package The DTK seamless package is a single installer package which carries Linux DTK RPMs (RHEL, SLES) and its dependency. Seamless package auto recognizes the OS type and its respective dependency during the installation and installs SYSCFG, RAIDCFG and RACADM tools on Linux post operating system. The size of the DTK tools seamless package is less (60MB) compared to that of the complete OM DVD contents size. DTK seamless package is posted independently on www.dell.
./DTKTOOLS__Linux64_.Bin -- delete [-d] Upgrading your DTK version When upgrading from a previous release of DTK, ensure that you create the environment for new DTK version separately from the previous version. This step is necessary because the environments and requirements for the new DTK versions are completely different.