Release Notes

Creating DRM update source on management server running on Windows 10 Operating System (OS) may fail, displaying
the following error message: Failed to reach location of update source. Please try again with
correct location and/or credentials.
Refer the omimsscappliance_main log in OMIMSSC Admin portal, if the error message displayed is: Unix command
failed SmbException: com.dell.pg.tetris.business.samba.smbclient.SmbException: session
setup failed: NT_STATUS_IO_TIMEOUTwhere EnableSMB1Protocol = false.
● Issue 9
Description:
The Deploy option is not displayed in an existing task sequence after uninstalling and reinstalling OMIMSSC console
extension for MECM.
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 10
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 MECM.
Workaround:
As a workaround, install the MECM client server, and then perform a synchronization to add the servers in Managed
Lifecycle Controller Lifecycle Controller (ESXi) collection.
● Issue 13
Description:
After scheduling an export server profile job, the server profile is not exported, and the following error message is displayed:
The selectors for the resource are not valid.
Workaround:
As a workaround, reset iDRAC, and then schedule the export server profile job. For more information, see iDRAC
documentation available at dell.com/support.
● Issue 15
Description:
After collecting the LC logs, when you try to view the LC log file for a server, the following error message is displayed:
“Failed to perform the requested action. For more information see the activity log”.
Workaround:
As a workaround, reset iDRAC, and then collect and view the LC logs. For information about resetting iDRAC, see iDRAC
documentation available at dell.com/support.
● Issue 16
Description:
After discovering the servers in OMIMSSC for MECM 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 MECM and the server is added to this group.
● Issue 17
Description:
When you create a Windows server HCI 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:
10
Known issues and resolutions