Release Notes

For a list of supported Dell systems that you can use as target systems and the operating systems that you can
deploy on these target systems, see the “Dell Lifecycle Controller Integration Version 3.2 for Microsoft System Center
Configuration Manager User’s Guide”.
Important Notes
• DLCI 3.2 has minimum pre-requisite of Windows Server 2008 SP2 for the site systems and server running
Dell Provisioning Service (DPS).
• When you deploy an operating system on a target system with iDRAC configured in a shared network
mode, the Windows PE environment may fail to startup on the network drivers, causing the system to
restart before reaching the task sequence.
• If the Lifecycle Controller of a system is in use, the system is not discovered.
• If the Lifecycle Controller of the target system is locked by another process, the following error message is
displayed in the DLCTaskManager.log file: "Lifecycle Controller is being used by another process."
• If you do not enter the service tag name of the target system correctly, the discovery and handshake fails
and the following error message is displayed: "[Server Name] - Handshake - getCredentialsInternal():[Server
Name]: NOT AUTHORIZED: No credentials returned."
• During Discovery and Handshake, the DPS.log displays an empty Site code: followed by a cryptography
exception. You can ignore this.
• During Discovery and Handshake, the DPS.log displays numerous messages such as “createDellCollecions()
Either Connection Mgr param is NULL or Collection not yet created.” You can ignore this.
• The System Viewer utility does not display the latest RAID configuration. To view the latest configuration,
re-launch the System Viewer utility.
• The modular systems cannot use the hostname in the path to the Common Internet File System (CIFS)
share, but monolithic systems can use the hostname. For modular systems, usse the IP address instead of
hostname.
• After deploying Non-Windows operating system using DLCI, the service tag of system name is displayed as
Hostname in configuration manager console.
Limitations
• DLCI for System Center Configuration Manager 2012 does not support operating system deployment on
Dell PowerEdge R330, R230, T330, and T130 Platforms.
• When you deploy Red Hat Enterprise Linux or ESXi OS on servers having iDRAC on shared Lan on
Motherboard (LOM), the deployment may fail. To resolve this, disable STP on PowerEdge switches (ports
connecting to the Shared LOM port directly) and enable Rapid Spanning Tree Protocol (RSTP), PortFast, or
FastLink on those switches.
• If the Windows PE environment is unresponsive while running an operating system deployment, the system
may have run out of memory. By default, WindowsPE allocates 32 megabytes (MB) of writeable memory,
known as scratch space. You can increase the scratch space up to 512 MB.
• Before upgrading to DLCI version 3.2, make sure that all the scheduled firmware update jobs are either
completed or deleted.
• During installation of DLCI, the Configuration Manager credentials specified are not validated. Installation
succeeds and an error in import.log indicates the same. Use DPS configure utility (import.exe) to specify the
correct credentials before proceeding with discovery of servers.
• The Advertise option does not appear in an existing task sequence after uninstalling and reinstalling DLCI
for Configuration Manager. To advertise the task sequence, edit the task sequence and correct if there are
any errors.
• If Active Directory (AD) authentication is used for communicating with iDRAC on modular servers, ensure
the iDRAC version is upgraded to 3.32. Affected version: DLCI 3.2 with 11G iDRAC 3.30 (or earlier).