Users Guide

Generic scenarios in OMIMSSC
This section contains troubleshooting information which are independent of any workflow in OMIMSSC.
Failure to access CIFS share using hostname
The modular servers are not able to access the CIFS share using the host name for performing any job in OMIMSSC.
As a workaround, specify the IP address of the server having the CIFS share instead of the host name.
Failure to display Jobs and Logs page in console extension
The Jobs and Logs Center page is not displayed in OMIMSSC console extensions.
As a workaround, re-enroll the console and then launch the Jobs and Logs page.
Failure of operations on managed systems
All the features of OMIMSSC does not perform as expected on the managed systems due to a Transport Layer Security (TLS)
version.
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.
Failure to launch online help for OMIMSSC
When using Windows 2012 R2 operating system, the context sensitive online help content is launched displaying an error
message.
As a solution, update the operating system using the latest KB articles, and then view the online help content.
OMIMSSC job failures because of unsupported network share
password
Some OMIMSSC jobs fail because of some of the special characters in the network share password are not supported by the
iDRAC.
Following is the list of job failures and the error messages associated with the respective job failures:
● Failure to export LC logs - Failed to Export Complete LC Logs from iDRAC IP <IP address> Cannot
access network share
● Failure to deploy RHEL and ESXi operating system - Inaccessible network share
● Failure to update firmware using DRM - Firmware update failed on server with iDRAC IP <IP address>
for <Component>
● Failure to deploy windows operating system - Inaccessible network share for iDRAC <IP address>
● Failure to export and import server profile - Failed to invoke Export Server Profile on iDRAC IP:
<iDRAC_IP> with error Cannot Access Network Share
As a workaround, ensure to use iDRAC recommended password for network share. For more information see, iDRAC
documentation.
Troubleshooting
97