Release Notes

● Issue 20
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 21
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 22
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 23
Description:
When using Windows 2012 R2 operating system, the context sensitive online help content is launched displaying an error
message.
Workaround:
As a solution, update the operating system using the latest KB articles, and then view the online help content.
● Issue 24
Description:
When you delete a server or all the servers in an update group from OMIMSSC, and rediscover them you cannot perform any
other operations on these servers like updating firmware, exporting and importing LC logs, exporting and importing server
profiles.
Workaround:
As a workaround, after rediscovering the deleted server or servers, perform firmware updates using the Deploy
Operational Template feature in Server View and for other maintenance scenarios use iDRAC.
● Issue 25
Description:
When you are creating an Operational Template, if you select and clear a dependent attribute’s check box having pool value,
you are not able to save the Operational Template with the following error message:
Select atleast one attribte, under the selected components, before creating the
Operational Template.
Workaround:
As a workaround, perform any one of the following:
○ Select any other dependent attribute having pool value or the same dependent attribute and save the Operational
Template.
10
OpenManage Integration Version 7.2.1 for Microsoft System Center Release Notes