Release Notes
Export server profiles—including firmware images on components such as Basic Input
Output System (BIOS), Redundant Array of Independent Disks (RAID), Network Interface
Controller (NIC), integrated Dell Remote Access Controller (iDRAC), LC and so on, to an
internal (Vflash) or external location.
Import server profiles—either retaining or excluding the current RAID settings for the same
server or server groups when the existing server profile is corrupt.
Filters—are used to display information based on the criteria selected in the Maintenance
Center.
Allow Downgrade—if enabled, allows you to downgrade the firmware version to an earlier
version.
Cluster-Aware Updating (CAU)—automates the software updating process by leveraging the
features of Microsoft on cluster update groups while maintaining the server’s availability.
Integration with Dell Repository Manager (DRM 2.2 Version)—providing the server inventory
information of the existing servers from the appliance to DRM.
Fixes
Bug 61681: PT-Update Group-Empty cluster update group does not get deleted during
autodiscovery or synchronization.
Bug 60425: Firmware update on two identical servers with different set of components for
each server, performs the firmware update of all selected components on both the servers,
irrespective of the selection per server.
Important Notes
Once you upgrade to the current version of DLCI for SC2012 VMM, edit and save the hardware profiles
created in earlier versions before you apply them on the servers.
Known Issues & Resolutions
42439: When you want to create a hardware profile using a reference server that was deployed by DLCI
for SC2012 VMM, you may see empty set of disks or the message “Unable to get RAID topology.” The
reason for this is that the iDRAC system inventory is not updated.
Workaround: (Do this action only once.) Reset iDRAC in the reference server and then recreate the
hardware profile.
Versions Affected:
11th and 12th generation of Dell PowerEdge servers
38365: When an add-in is imported into the SC2012 VMM console, the console may crash.
Workaround: See issue 5 in this knowledge base URL:
support.microsoft.com/kb/2785682
Do this update irrespective of the version of the update rollup that is installed.