Release Notes

As a workaround, run the DISM command to clean up all previously mounted images in Microsoft console, and then retry to update
the WinPE image.
• Issue 28
Description:
Firmware updates applied on 11
th
generation of PowerEdge servers may fail due to incompatible versions of iDRAC and LC with the
following error: WSMan command failed to execute on server with iDRAC IP <IP address>.
Workaround:
As a workaround, upgrade the iDRAC and LC to the latest versions, and then apply the firmware updates. The table lists out the latest
versions of LC and iDRAC.
• Issue 29
Description:
After proving the details of a local update source, the test connection may fail as the required files may be not accessible.
Workaround:
As a workaround, ensure that catalog.gz file is present in the following folder structure.
○ For local HTTP update source: http:\\IP address\catalog\catalog.gz
○ For local FTP update source: ftp:\\IP address\catalog\catalog.gz
○ For local DRM update source: \\IP address\\catalog\<catalogfile>.gz
• Issue 30
Description:
After deploying the Operational Template on the selected servers, the attributes or attribute values are not appropriate for the
selected .CSV file, or the iDRAC IP or iDRAC credentials are changed due to the configurations in the template. The job in iDRAC is
successful, however the status of this job in OMIMSSC is shown as unsuccessful or failure due to invalid .CSV file, or the job cannot
be tracked due to the iDRAC changes on the target server.
Workaround:
As a workaround, ensure the selected .CSV file has all the proper attributes and attribute values, and the iDRAC IP or credentials do
not change due to the configurations in the template.
• Issue 31
Description:
The Deploy option is not displayed in an existing task sequence after uninstalling and reinstalling OMIMSSC console extension for
SCCM.
Workaround:
As a workaround, open the task sequence for editing, re-enable the Apply option, and click OK. The Deploy option is displayed again.
• Issue 32
Description:
If the DHCP lookup fails while operating system deployment, then the server times out and the server is not moved into Managed
Lifecycle Controller Lifecycle Controller (ESXi) collection in SCCM.
Workaround:
As a workaround, install the SCCM client server, and then perform a synchronization to add the servers in Managed Lifecycle
Controller Lifecycle Controller (ESXi) collection.
• Issue 33
Description:
Hypervisor deployment fails displaying the following error message in activity log: Error New-SCVMHost failed with
following error : An out of band operation (SMASH) for the BMC <IP ADDRESS> failed on IDRAC
IP : <IP ADDRESS>.
Workaround:
This error may occur due to one of these reasons:
○ Dell Lifecycle Controller’s state is bad.
As resolution, log in to iDRAC user interface and reset Lifecycle Controller.
After resetting Lifecycle Controller, if you still face the problem try the following alternative:
10
Dell EMC OpenManage Integration for Microsoft System Center Version 7.1 for System Center Configuration Manager and System Center
Virtual Machine Manager Release Notes