Release Notes

Msiexec.exe /i iDRACSvcMod.msi ADDLOCAL="WSMAN_Enablement" CP_SELF_SIGN_CERT="2"
CP_WSMAN_PORT="1234" CP_CERTIFICATE="1" CP_NEGOTIATE="1" /qn
Known Issues on Microsoft Windows Operating Systems
Issue 1
Description: On Microsoft Windows 2012 operating systems; if an iDRAC reset operation is performed when any of the iDRAC
sessions are opened using iDRAC access via Host OS feature, then the connection between iDRAC Service Module and iDRAC
may not be re-established. Also, the Microsoft Windows service IP Helper might stop running.
In such scenarios, do the following:
1. Restart the iDRAC Service Module.
2. Restart the Microsoft Windows IP Helper service.
3. If OpenManage Server Administrator is running, restart the dsm_sa_datamgr service.
Example:
● Open iDRAC GUI via the iDRAC access via Host OS feature.
● Perform an iDRAC firmware update from the GUI. This will reboot iDRAC with the new firmware.
● The iDRAC Service Module in the Host does not restart communication with iDRAC.
● IP Helper services stops running.
You can configure the Windows Remote Management (WinRM) Listener using a server authenticating certificate. If the
server authenticating certificate is not available, iDRAC Service module will force-enable the WinRM listener using a self-sign
certificate. To configure the Windows Remote Management (WinRM) listener, you can create a self-signed certificate using
the PowerShell cmdlet New-SelfSignedCertificate from Microsoft Windows Server 2012 or later. In operating systems prior to
Microsoft Windows Server 2012 you cannot create a self-signed certificate due to the absence of PowerShell cmdlet.
Issue 2: JIT-87075
While uninstalling iDRAC Service Module, a popup is displayed if the Firefox browser is opened. The popup prompts that
Firefox browser needs to be closed before continuing the uninstallation. Close the Firefox browser and click the Retry option to
continue the uninstallation.
Limitations on Microsoft Windows Operating Systems
● Do not specify user profile folders like a desktop folder (C:\Users\administrator\Desktop) as custom installation paths for
installing iDRAC Service Module. This is because services running on the system account cannot access such folders.
● You cannot view Lifecycle Controller logs in the new folder in the Event Viewer (169898) if you have recently changed
the folder name of the Lifecycle Controller logs in the Event Viewer. Microsoft recommends that you reboot the operating
system to be able to view the Lifecycle Controller logs under the new view name.
● On Windows operating system, a feature that is enabled using the installer and disabled using any interface other than the
installer, can only be enabled using the same interface or the installer in GUI mode.
User Notes for Supported Red Hat Enterprise Linux and SUSE
Linux Enterprise Server
To perform an Express Install on the Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems:
Execute dcism-setup.sh -x from the SYSMGMT/iSM/linux directory.
For more information on the installation instructions, including silent installation, see the "iDRAC Service Module User's Guide".
NOTE:
You do not have the permission to run the script directly on the disk partition. Use the format sh ISM_LX.sh to
run the script and then install iDRAC Service Module.
5