Release Notes

Workaround: As a workaround, restart the Appliance, and then create the update source of type HTTP or FTP.
• Issue 12
Description: Firmware update jobs submitted from OMIMSSC to the iDRAC fail, and the OMIMSSC main log displays the following
error: JobQueue Exceeds the size limit. Delete unwanted JobID(s).
Workaround: As a workaround, manually delete the completed jobs in iDRAC, and retry the rmware update job. For more information
on deleting jobs in iDRAC, see the iDRAC RACADM CLI Guide.
• Issue 13
Description: After scheduling a rmware update job on a cluster update group, the rmware update job may fail due to various reasons
such as: IG is unreachable, the cluster group becomes unresponsive, or the rmware update job was canceled in CAU for an in-progress
job.
Workaround: As a workaround, delete all the les in the Dell folder, and then schedule a rmware update job.
• Issue 14
Description: A rmware update job started on 11th generation of the PowerEdge servers may fail due to incompatible versions of
iDRAC and LC with the following error message: 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 start the rmware update job.
• Issue 15
Description: The rmware update job may fail if you are using DRM update source with insucient access to the share folders. If the
Windows credential prole provided while creating DRM update source is not a part of domain administrator group or the local
administrator group, the following error message is displayed: Local cache creation failure.
Workaround: As a workaround, perform the following steps:
a After creating the repository from DRM, right-click on the folder, click the Security tab, and then click Advanced.
b Click Enable inheritance, and select the Replace all child object permission entries with inheritable permission entries from this
object option, and then share the folder with everyone with read-write permission.
• Issue 16
Description: After scheduling a job on an update group, if all the servers are moved out of the update group and the update group is
empty, then the scheduled job fails.
Workaround: As a workaround, cancel the scheduled job, add the servers to another update group, and then schedule a job on the
update group.
• Issue 17
Description: After submitting the Deploy the Operational Template job on the servers, if the attributes or attribute values are not
appropriate for the selected .CSV le, or the iDRAC IP or iDRAC credentials are changed due to the template, then the job in iDRAC is
successful. However, the status of this job in OMIMSSC is shown as unsuccessful or fail due to invalid .CSV le, or the job
cannot be tracked due to the iDRAC changes on the target server.
Workaround: As a workaround, ensure the selected .CSV le has all the proper attributes and attribute values, and the iDRAC IP or
credentials do not change due to the template.
• Issue 18
Description: Modular servers cannot use the host name in the path to the CIFS share but monolithic systems can use the host name.
Workaround: As a workaround, specify the IP address of the CIFS share for modular systems.
• Issue 19
8
OpenManage Integration Version 7.0 for Microsoft System Center Release Notes