######################################################################
DELL(TM) DEPLOYMENT PACK FOR MICROSOFT(R) SYSTEM CENTER CONFIGURATION
MANAGER
######################################################################
Version: 1.0
Release Date: February 2009
This file contains updated information for the “Dell(TM) Deployment
Pack for Microsoft(R) System Center Configuration Manager
(ConfigMgr).”
The Dell Deployment Pack documentation includes the “Dell Deployment
Pack for Microsoft System Center Configuration Manager
User's Guide.”
######################################################################
CONTENTS
######################################################################
* Criticality
* Compatibility/Minimum Requirements
* Installation
* 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 list the supported systems and operating
Systems that are compatible with the Dell Deployment Pack for
Microsoft System Center Configuration Manager Version 1.0
(Dell Deployment Pack 1.0).
======================================================================
SUPPORTED SYSTEMS
======================================================================
The Dell Deployment Pack 1.0 supports the following Dell
PowerEdge(TM) systems:
800, 830, 840, 850, 860, 1850, 1855, 2800, 2850, 6800, 6850, 1900,
1950, 1955, 2900, 2970, 6950, SC1435, 2950, T105, R200, R900, R805,
M600, M605, T605, R300, T300, R805, PV0100, PV0500, PV0600, NX1950,
M805, M905, and R905.
======================================================================
SUPPORTED OPERATING SYSTEMS
======================================================================
Site Server Operating Systems:
* Microsoft Windows Server(R) 2003 x86, x64 Edition SP2 and SP2 R2
* Microsoft Windows Server(R) 2008 Standard and Enterprise Editions
(x86) and (x64)
Admin Console Operating Systems:
* Microsoft Windows Server 2003 x86, x64 Enterprise Edition
* Microsoft Windows Server 2008 x86, x64 Enterprise Edition
* Microsoft Windows XP(R) SP2 x86
* Microsoft Windows Vista(R) Business Edition x86
======================================================================
INSTALLATION/UN INSTALLATION PREREQUISITES
======================================================================
Before installing Dell Deployment Pack components, ensure that:
* you have the Dell Deployment Pack Microsoft Windows
Installer (MSI) package file
* you have
ConfigMgr 2007 SP1 installed
* the version of default “boot image” present in the installed
ConfigMgr package is “6.0.6001.18000.” and above.
* ConfigMgr is not running during DDP installation and uninstallation
Note:
After you confirm, DDP will close ConfigMgr during installation.
======================================================================
IMPORTANT INFORMATION
======================================================================
Using OS Deployment tasks from multiple OEMs within the same task
---------------------------------------------------------------------sequence
--------
Scenario:
---------
To create a task sequence in Configuration Manager that performs
system hardware configuration and operating system deployment, and
works on multiple hardware platforms, enabling you to add
Original Equipment Manufacturer (OEM) hardware configuration steps
from more than one vendor into the same task sequence.
Note: All references to OEMs below do not include Dell.
Issue:
------
The OEM add-ons for system hardware configuration utilize
pre-configured templates to arrange steps in the task sequence
in a proper order. When you add a new OEM step into a task
sequence, it first checks to see if the task sequence already has
any OEM steps in it. If there are no steps, it prompts you for
automatic configuration of the steps. In certain cases, such as the
addition of a “Reboot to PXE or USB” step, if you do not allow the
automatic reconfiguration, it will result in failure.
In the first released version of the integration components on which
the OEM hardware configuration add-ins are built, the form checks
for pre-existing OEM task steps, but does not check for other
existing OEM steps. This causes an issue where adding one OEM step
to an existing task sequence created by another OEM’s automatic
configuration cause the newly-added step to be taken as the
first OEM step in the task sequence.
In the case of hardware configuration step, cancel the
reconfiguration because it would still add a valid
task step to the sequence. However, if you are adding a “Reboot to
PXE or USB” step, canceling the automatic reconfiguration will leave
the task step un-configured and invalid. Accepting the
reconfiguration will re-apply the original grouping and
reorganization to the task sequence, which will also render it
invalid.
Solution:
---------
The initial OEM release works correctly on its own and subsequent
versions of the underlying integration components will check for
existing steps from any OEM. Therefore, ensure that you use the
following procedure for using steps from multiple OEMs in a task
sequence:
* Create a new task sequence with OEM configuration steps
(preferably, use the right-click action on the “Task
Sequences” node).
* You can now add steps from any OEM into a task sequence and
it will be handled correctly.
######################################################################
INSTALLATION
######################################################################
Before you proceed, ensure that you are logged in as administrator on
the system where you want to install the Dell Deployment Pack.
Note: If you are running Windows Server 2008 or Windows Vista, open
the command prompt using the "Run As Administrator" option, navigate
to the MSI location and launch it through the command prompt.