Dell Openmanage Deployment Toolkit Version 3 5 Owners Manual Readme Windows PE
2014-11-13
: Dell Dell-Openmanage-Deployment-Toolkit-Version-3-5-Owners-Manual-117757 dell-openmanage-deployment-toolkit-version-3-5-owners-manual-117757 dell pdf
Open the PDF directly: View PDF 
.
Page Count: 8
| Download | |
| Open PDF In Browser | View PDF |
######################################################################
DELL(TM) OPENMANAGE(TM) DEPLOYMENT TOOLKIT FOR MICROSOFT(R)
WINDOWS(R) PREINSTALLATION ENVIRONMENT (WINDOWS PE)
######################################################################
Version 3.5
Release Date: March 2011
This file contains updated information for your "Dell OpenManage
Deployment Toolkit User's Guide" and any other technical
documentation included with the Deployment Toolkit (DTK) for Windows
PE.
The Deployment Toolkit documentation includes the "Command Line
Interface Reference Guide" and the "User's Guide."
See the Dell Support website at "support.dell.com" for the most
current information on the "Command Line Interface Reference Guide",
"User's Guide", and "ReadMe".
######################################################################
CONTENTS
######################################################################
* Criticality
* Compatibility/Minimum Requirements
* Release Highlights
* Installation
* Upgrading
* User Notes
* Known Issues
######################################################################
CRITICALITY
######################################################################
3 - Optional
Dell recommends that you review the specifics about the update to
determine if it applies to your system. The update contains changes
that may impact only certain configurations, or provides new features
that may or may not apply to your environment.
######################################################################
COMPATIBILITY/MINIMUM REQUIREMENTS
######################################################################
The following subsections lists supported systems that are
compatible with the Deployment Toolkit version 3.5.
======================================================================
Supported Systems
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
======================================================================
The Deployment Toolkit version 3.5 supports all Dell PowerEdge x8xx
and later systems that are supported by OpenManage versions 5.5 to 6.5.
For a complete list of supported Dell PowerEdge systems, see
the Dell Systems Software Support Matrix available at
support.dell.com/manuals. On the Manuals page, click Software->
Systems Management-> Dell OpenManage Releases. Click the appropriate
product version to access the Support Matrix.
To deploy your system, select the model of your system and download and
import the applicable Dell Deployment ToolKit and Dell Systems Management
Tools and Documentation DVD from support.dell.com.
NOTE: Other systems may be supported with this release. See the Dell
Support website at "support.dell.com" to verify the supported
systems and to download the latest version of the toolkit.
The sample scripts included with DTK have been tested with the
deployment of the following operating systems:
- Microsoft Windows Server 2008 R2 with SP2
- Windows Server 2008 R2
- Windows Server 2008 SP2 (32-bit and 64-bit)
- Windows Server 2003 R2 with SP2 (32-bit and 64-bit)
======================================================================
Installation Prerequisites
======================================================================
Before installing Deployment Toolkit components, ensure that you have:
* The Deployment Toolkit self-extracting installation file
("dtk-3.Xwinpe-AXX.exe"), which contains the utilities, sample
scripts, sample configuration files, and documentation you need to
deploy your Dell system.
* A Windows workstation that has at least 512 MB of RAM.
======================================================================
Deployment Prerequisites
======================================================================
Before beginning the deployment process, ensure that you have the
following tools, software, and information ready to use or consult:
* Advanced knowledge of Windows.
* Windows Automated Installation Kit (AIK) to build Windows PE.
* An unzip utility.
* Working knowledge of Microsoft Remote Installation Services (RIS)
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
and Automated Deployment Services (ADS) (including setting up of
RIS and ADS environments), or any other third party deployment
system or tool.
* 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:
-- A writable CD/DVD drive and CD/DVD writing software
-- Network access
* A target system with a CD/DVD drive if you are performing a local
deployment or network access if you are performing a network
deployment.
* All Deployment Toolkit utilities, sample scripts, and sample
configuration files.
* All required Windows PE drivers, operating system drivers, and the
Dell utility partition image file.
* A minimum BIOS version is recommended on some of the platforms for
all the DTK options to work correctly. In general, it is good
practice to use the latest ("n") version of BIOS firmware or the
"n-1" version that is available on "support.dell.com."
For more information refer to the OS Support Matrix available
in the support.dell.com.
######################################################################
RELEASE HIGHLIGHTS
######################################################################
Deployment Toolkit version 3.5 has the following new feature:
* Support for Microsoft Windows Server 2008 R2 with SP2
* Support for the following Dell Power Edge systems: R210 II, T110 II,
M915,R910, R810, and M910
* Support for following BIOS options: coreperformanceboost, memdynamicpower,
memprefailurenotify, and inteltxt
######################################################################
INSTALLATION
######################################################################
For complete installation instructions, see the "Dell OpenManage
Deployment Toolkit User's Guide."
######################################################################
USER NOTES
######################################################################
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
This section provides information that can help enhance your
experience with the Deployment Toolkit.
======================================================================
SCRIPT NOTES
======================================================================
* The sample scripts are provided as examples for customers who want
to develop their own deployment process. Some customers may find
that the scripts work well in their environment, while some
customers may need to develop their own scripts entirely from
scratch. Customers deploying multiple systems need to provide
unique information for each server when appropriate. For example,
system host names, IP addresses, and system service tags need to
be unique for each system. The batch scripts and configuration files
need to be modified to reflect the unique information for each
system being deployed. Many options are available to optimize this
process.
* Installation of Dell utility partition is not supported on
Windows PE 2.0 and Windows PE 3.0.
======================================================================
TOOLS NOTES
======================================================================
* SYSCFG:
- Some options may not be present on all systems, which may
be due to the BIOS version or hardware feature set. The usage
information generated by running SYSCFG without arguments shows
only those options that are valid for your system.
- The "--devseq" option is present only if you have an
available, bootable hard-disk partition. If this option is
present in the configuration file, but not present on your
system, you will receive a usage error.
- It is recommended to perform a warm reboot after applying the
syscfg settings changes.
- If you perform operations that change the "--redmem"
option, reboot your system immediately. This is applicable
to both command-line and "--infile" usage.
NOTE: The "--redmem" option should not be issued
with any other command and should be immediately followed
by a system reboot. This note is important when you
develop scripts that can alter the "--redmem" setting.
==========================
- For options that use text strings such as username,
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
password, hostname, and community string, using characters
such as , "<," ">," "|," "=" on the command line can be
misinterpreted by the command line parser and may cause errors.
Use only alphanumeric characters to avoid these errors.
- 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:
- 19200 for PowerEdge x8xx systems.
- 57600 for PowerEdge x9xx systems without Dell Remote
Access Controller 5 (DRAC 5).
- 115200 for PowerEdge x9xx systems with DRAC 5.
If you enter an unsupported baud rate, you may receive an error,
"Parameter out of range."
* RAIDCFG:
- When creating virtual disks, the chunk (stripe) size is always
in KBs. Do not specify any units of measure for the chunk size.
- When providing multiple physical disks for the "create
virtual disk" command, do not separate the disks with spaces.
For example, "-ad=1:4, 1:5" causes an error. The correct way
to display multiple physical disks is "-ad=1:4,1:5,1:6."
- If you change the controller mode from SCSI mode to RAID mode,
data loss may occur. Back up any data you require
before changing the modes.
######################################################################
KNOWN ISSUES
######################################################################
RAIDCFG Issues:
* If you delete a virtual disk on PERC 4I/M on Windows PE, you need
to reboot the system for the changes to take effect.
* You cannot delete a virtual disk on CERC SATA 2S when RAID 1 is
created with the "--clear" option. The virtual disk can be cleared
from the controller BIOS.
* Perform copy operations using the "XCOPY" command, because the
DOS "COPY" command may fail when copying across a network share.
The message "invalid file handle" may be displayed. This issue
is specific to R805 and R900 systems and is an intermittent
error that is usually caused by the network connection.
If the problem persists, check your network settings.
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
* You can assign upto 10 Global Hotspares using Raidcfg. Use
The Dell(TM) OpenManage(TM) Server Administrator Storage Management
for assigning more than 10 Global Hot spares.
* SW RAID controllers S100 and S300 will not be detected in the Microsoft
Windows Server 2003 with SP1 (32-bit).
* DTK does not support Non RAID (Volume) mode on s100/s300
controller.
* S300 controller Cachepolicy setting is "Not Applicable". Hence
VD created with different cachepolicy settings from OROM utility
will be displayed as "Not Applicable".
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.
* The Demand-based Power Management (DBPM) option does not work on
PowerEdge 1855 systems with BIOS versions earlier than A05.
* On Windows PE 3.0, when you run the syscfg command to list all
available options, if you press CTR + C before the command fully
executes, an error message is displayed. Click OK.
You can ignore the message.
* The Demand-based Power Management (DBPM) option does not work on
PowerEdge 1855 systems with BIOS versions earlier than A05.
* The option for "powerctl," which is "softshutdown," does not
work in Windows PE.
* The "--solbitrate" option in "solcfgparams" and the
"--mgscommbitrate" option in "serialcfgparams" accept a baud rate
of 57600, but tools such as "ipmish" and "solproxy" do not
function at that baud rate for PowerEdge systems.
RACADM Issues:
* If you use virtual media to boot into Windows PE, executing
certain RACADM commands may cause Windows PE to crash.
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
* After generating the rac configuration file using the
"racadm getconfig -f " command, comment out the following
properties in the configuration file before you update a
configuration using the "racadm config -f " command:
#cfgRacTuneCtrlEConfigDisable=0
#cfgRacTuneLocalConfigDisable=0
* VLAN objects (cfgNicVLanEnable, cfgNicVLanId, and cfgNicVLanPriority)
displayed using the local RACADM command
"racadm getconfig -g cfgLanNetworking"
or VLAN objects generated in the configuration file using the
local RACADM command
"racadm getconfig -f " do not contain the leading "#" symbol
which indicates that they are read-only.
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 2003, locally or remotely. To fix this issue, install
a valid image on virtual flash or disable virtual flash if it
will not be used during the installation procedure.
* 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.
* Windows 2008 64-bit cannot be installed using DTK with
Windows PE 3.0. Use Windows PE 2.0 for installing
Windows 2008 64-bit.
* When using the H200 driver provided in Windows PE 3.0 (x64),
the diskpart command does not list the first virtual disk
created. Download the latest driver from the support site
at support.dell.com.
* Windows PE 3.0 does not support PERC 4 controllers.
######################################################################
Information in this document is subject to change without notice.
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
(C) 2011 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without
the written permission of Dell is strictly forbidden.
Trademarks used in this text: "Dell," "PowerEdge," and
"OpenManage" are trademarks of Dell Inc.; "Microsoft," "Windows," and
"Windows Server" are either trademarks or registered trademarks
of Microsoft Corporation in the United States and/or other countries.
Other trademarks and trade names may be used in this document to refer
to either the entities claiming the marks and names or their products.
Dell Inc. disclaims any proprietary interest in trademarks and trade
names other than its own.
The sample scripts provided with the Dell OpenManage Deployment
Toolkit are provided "as is." Dell disclaims any and all warranties,
express, implied or statutory, with respect to the sample scripts,
including, but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, title and any
warranty of non-infringement. Use the sample scripts at your own risk.
Dell shall not be liable for any direct or indirect damages incurred
in using the sample scripts. In no event shall Dell or its suppliers
be responsible for any direct or indirect damages whatsoever
(including, without limitation, damages for loss of profits, loss of
use, loss of data, business interruption, or other pecuniary loss, nor
for punitive, incidental, consequential, or special damages of any
kind, under any part of this agreement, even if advised or aware of
the possibility of such damage.
March 2011
file:///T|/htdocs/SOFTWARE/dtk/3_5/readme/Windows_README.TXT[10/22/2012 4:29:56 PM]
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : No Format : application/pdf Title : Readme Windows PE Creator : Dell Inc. Subject : Release Notes2 Description : Release Notes2 Producer : Acrobat Web Capture 10.0; modified using iTextSharp 5.1.3 (c) 1T3XT BVBA Keywords : all-products#esuprt_electronics#esuprt_software#esuprt_ent_sys_mgmt#dell opnmang dplymnt toolkit v3.5#dell-opnmang-dplymnt-toolkit-v3.5#Release Notes2 Create Date : 2012:10:22 16:29:55-05:00 Creator Tool : Adobe Acrobat 10.0 Modify Date : 2012:11:07 12:09:18-06:00 Page Count : 8 Author : Dell Inc. Productcode : dell-opnmang-dplymnt-toolkit-v3.5 Typecode : rn2 Typedescription : Release Notes2 Languagecodes : en-us Sectioncode : Sectiondescription : Publishdate : 2011-03-15 00:00:00 Expirydate : 9999-09-09 00:00:00 Manualurl : http://ftp.dell.com/manuals/all-products/esuprt_electronics/esuprt_software/esuprt_ent_sys_mgmt/dell-opnmang-dplymnt-toolkit-v3.5_Release Notes2_en-us.pdf Readytocopy : false Futureproductindication : Yes Categorypathforfutureproducts : all-products/esuprt_electronics/esuprt_software/esuprt_ent_sys_mgmt Businesskeywords : Filesize : 26 Creationdate : D:20121022162955-05'00' Moddate : D:20121107070135-06'00'EXIF Metadata provided by EXIF.tools