Dell EMC OpenManage Deployment Toolkit Version 6.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction....................................................................................................................................................4 DTK Deprecation Message............................................................................................................................................... 4 Documents you may need.................................................................................................................................................
1 Introduction The 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.
• For Dell EMC Remote Enterprise Systems Management documents — Dell.com/esmmanuals • For iDRAC and Dell EMC Lifecycle Controller documents — Dell.com/idracmanuals • For Dell EMC OpenManage Connections Enterprise Systems Management documents — Dell.com/ OMConnectionsEnterpriseSystemsManagement • For Dell EMC Serviceability Tools documents — Dell.com/ServiceabilityTools • a Go to Dell.com/Support/Home. b Click Choose from all products.
• Working knowledge of Windows Deployment Services (WDS) or any other third party deployment system or tool for Windows PE. • A workstation with the following capabilities: • 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, and sample configuration files.
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:\PER740. NOTE: The unattendw2k12.
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, PR7920). 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
• All operating system RPM packages that DTK RPMs require. NOTE: Tools such as Yellowdog Updater Modified (YUM), Yet Another Setup Tool (YAST), and Advanced Packaging Tool (APT) can be used to manage RPM dependency issues. • All other utilities and files necessary to perform the deployment, including all required Linux drivers, operating system drivers, and the Dell utility partition file. • Systems Management Tools and Documentation DVD. • Your operating system software and documentation.
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. For example, os_src. 11 Mount the NFS Share to /tmp/os_src. 12 Copy ks.cfg/ks-rhelx.cfg (in BIOS mode) or ks_uefi.cfg/ks_rhelx_uefi.cfg (in UEFI mode) from /opt/dell/toolkit/template/configs to NFS share on the source machine. Here, x indicates the version of the operating system.
Installing SUSE Linux server Operating System using DTK CAUTION: It is recommended that you consult your SUSE Linux Enterprise Server operating system documentation and unattended deployment documentation to develop a thorough understanding of the unattended installation process before attempting to perform a full scripted deployment. NOTE: While installing Linux, ensure that you install grub in the boot partition. Otherwise, you cannot boot to the utility partition by pressing the key during reboot.
To convert from DTK to RACADM deployment and to install SUSE Linux Enterprise Server using the suseinst.sh script: 1 On the source system, navigate to the location of the required SUSE Linux Enterprise Linux operating system image. 2 Perform the steps 2 to 11 from the section Installing SUSE Linux server Operating System using DTK. 3 From /opt/dell/toolkit/converter, run the command python dtktoracadm.py or python dtktoracadm.py linux_scripts.lst, where linux_scripts.
16 From /opt/dell/toolkit/template/scripts, run /centinst6.sh or /centinst7.sh. The server reboots to the grub prompt. The CentOS Linux operating system unattended installation is initiated . NOTE: For more information on installing, see en.community.dell.com/techcenter/systems-management/w/wiki/ 1772.dell-openmanage-deployment-toolkit.aspx.
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.
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.
