Release Notes

All the features of OMIMSSC does not perform as expected on the managed systems due to a Transport Layer Security (TLS)
version.
Workaround:
If you are using iDRAC firmware version 2.40.40.40 or later, Transport Layer Security (TLS) versions 1.1 or later is enabled by default.
Before installing the console extension, install the update to enable TLS 1.1 and later as mentioned in the following KB article:
Support.microsoft.com/en-us/kb/3140245. It is recommended that you enable support for TLS 1.1 or later on your
SCVMM server and SCVMM console to ensure that OMIMSSC operates as expected. And for more information about iDRAC, see
Dell.com/idracmanuals.
• Issue 44
Description:
Operational Template compliance is not displayed for Active Directory attribute, since the attribute value is present in managed device
and not in Operational Template.
• Issue 45
Description:
If you are accessing local FTP using proxy credentials created by CCProxy server, then the local FTP site is not accessible.
• Issue 46
Description:
In BIOS Settings, the snoop mode attribute does not support ClusterOnDie option.
• Issue 47
Description:
The action in comparison report for operating system collector component is displayed as downgrade even if it an upgrade action.
• Issue 48
Description:
While creating a logical switch or a hypervisor profile, when selecting host groups in OMIMSSC, the groups are not listed in nested
form as present in SCVMM.
• Issue 49
Description:
After discovering the servers in OMIMSSC for SCCM console extension, the server may not get added into All Dell Lifecycle
Controller Servers collection.
Workaround:
As a workaround, delete the All Dell Lifecycle Controller Servers collection and then discover the server. The collection is
automatically created in SCCM and the server is added to this group.
• Issue 50
Description:
When you create a Storage Spaces Direct cluster on nodes that were part of an existing cluster, then the storage pool and the disk
configurations have the configurations of the existing cluster. Hence, the cluster storage pool might not be created and if the cluster
storage pool is created the health status may be displayed as unknown.
Workaround:
As a workaround, clear the storage pool and disk configuration having existing cluster details and then create the Storage Spaces
Direct cluster. For more information on clearing the storage pool, see Troubleshoot Storage Spaces Direct health and operational
states section from Microsoft documentation.
• Issue 51
Description:
When multiple Microsoft consoles are enrolled to an OMIMSSC Appliance, and you try to discover a server, if even one of the SCCM
consoles are not reachable, then the server discovery job will fail.
Workaround:
As a workaround, de-enroll the SCCM console that is not reachable, or fix the errors and ensure that the SCCM console is reachable
from OMIMSSC Appliance.
• Issue 52
Description:
Dell EMC OpenManage Integration for Microsoft System Center Version 7.1.1 for System Center Configuration Manager and System
Center Virtual Machine Manager Release Notes
11