Dell Lifecycle Controller Integration Version 3.3 for Microsoft System Center Configuration Manager Release 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.