Release Notes

Supported Target Systems and Operating Systems
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.3 for Microsoft System Center Configuration Manager User’s
Guide”.
What’s New
This release of DLCI for Configuration Manager provides support for the following:
• Support for Microsoft System Center Configuration Manager Version 1610.
• Support for Agent-free properties for configuration manager.
• Support for deployment of Windows 2016, ESXI 6.0 U2, and RHEL 6.8.
• Support for 64-bit firmware update.
Important Notes
• DLCI 3.3 has minimum prerequisite 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, then the system is not discovered.
• If the Lifecycle Controller of the target system is locked by another process, then the following error message is displayed in the
following path <Microsoft Configuration Manager installation \XmlStorage\Extensions\DLCPlugin\DLCTaskManager.log file:
folder>\AdminConsole "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 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 use the IP address instead of hostname.
• After deploying Non-Windows OS 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 the 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, Windows PE allocates 32 megabytes (MB) of writeable memory, known as scratch space. You can increase
the scratch space up to 512 MB.
2