Owner's Manual

ManualsBrandsDell ManualsSoftwareDell OpenManage Deployment Toolkit Version 4.1

Dell OpenManage

Deployment Toolkit

Version 4.1

Readme

Summary of content (6 pages)

PAGE 1
Dell OpenManage Deployment Toolkit Version 4.
PAGE 2
What’s New The new features for this release include:  Added support for the following operating systems: o Red Hat Enterprise Linux 6.2 (64-bit) o Red Hat Enterprise Linux 5.8 (32-bit and 64-bit)  Deprecated the following operating systems: o Red Hat Enterprise Linux 6.1 (32-bit and 64-bit) o Red Hat Enterprise Linux 5.7 (32-bit and 64-bit) Supported Systems For a complete list of supported Dell PowerEdge systems, see the Dell Systems Software Support Matrix available at support.dell.com/manuals.
PAGE 3
Installation For complete installation and deployment instructions, see the "Dell OpenManage Deployment Toolkit User's Guide." Installation Prerequisites Before extracting Deployment Toolkit components, ensure that you have:  The Deployment Toolkit self-extracting installation file ("DTKX.X-WINPE-XX.exe")  A Windows workstation that has at least 512 MB of RAM.
PAGE 4
 If you set the username using the syscfg "username" option, SOL access for the corresponding user will be enabled by default. You can disable SOL access for a user using the "syscfg solaction --userid= --action=disable" command.  The maximum reliably supported baud rates (--solbitrate) are:  57600 for PowerEdge x9xx systems without Dell Remote Access Controller 5 (DRAC 5).  115200 for PowerEdge x9xx systems with DRAC 5.
PAGE 5
SYSCFG Issues  In DRAC 5, the --virtualmedia and --vflash options do not work if there is an active virtual media session. Disconnect the virtual media using the DRAC GUI. Log into DRAC. Click Media > Virtual Media > Disconnect.  The syscfg --bootseq command detects CD-ROM with SAS/SATA controllers as unk.emb.1.  On R815, syscfg power --profile option allows to set to apc, though apc is not supported on R815. syscfg does not throw an error message.  On Windows PE 3.
PAGE 6
 Running partcfg.bat may fail when virtual media is enabled. For the hard disk, partcfg.bat uses the driver letter "c:". When virtual media is enabled, sometimes, the virtual device gets assigned with the drive letter "c:" And, partcfg.bat execution fails. To run partcfg.bat successfully, either disable the virtual media or use the diskpart command to assign a free driver letter for partcfg.bat. Windows PE Issues     Windows PE 2.0 and 3.0 for 64-bit do not support racadm.exe for DRAC 4.