Release Notes

As a workaround, clear the storage pool and disk configuration having existing cluster details and then create the Windows
server HCI cluster. For more information on clearing the storage pool, see Troubleshoot Windows server HCI health and
operational states section from Microsoft documentation.
● Issue 18
Description:
When multiple Microsoft consoles are enrolled to an OMIMSSC Appliance, and you try to discover a server, if even one of
the MECM consoles are not reachable, then the server discovery job will fail.
Workaround:
As a workaround, de-enroll the MECM console that is not reachable, or fix the errors and ensure that the MECM console is
reachable from OMIMSSC Appliance.
● Issue 19
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 20
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 22
Description:
After the firmware update of PowerEdge MX7000 components, the comparison report under Available Updates in the
Maintenance Center page, displays incorrect number of updates even if the firmware update is successful.
Workaround:
As a work-around, go to Maintenance Settings and click Test Connection of update source that is used while updating
the firmware. Go to Maintenance Center to view the correct number of updates.
● Issue 23
Description:
After de-enrolling SCVMM from the appliance, OMIMSSC page can still be opened through SCVMM console.
Workaround:
As a work-around, ensure to uninstall SCVMM console plug-in after de-enrolling SCVMM from the appliance.
● Issue 24
Description:
If the update source does not contain update for the selected device, the firmware update for complete MX chassis group
does not complete.
Workaround:
Ensure to select devices for which updates are available in the selected update source.
Or
Select only the devices that have applicable updates which are based on the selected update source for firmware update job
to complete.
● Issue 25
Description:
Known issues and resolutions
11