Release Notes

The user notes, known issues and workaround are mentioned separately in each operating system section in this document.
For more details on limitations and supported operating system, see iDRAC Service Module User's Guide.
User Notes, Known Issues & Limitations
NOTE: With iDRAC firmware versions 3.22.22.22 or older, if iSM is installed when the iDRAC attribute Disable iDRAC Local
Configuration using RACADM is enabled in the iDRAC, Watchdog timer expired message is logged in iDRAC Lifecycle Logs.
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, SUSE
Linux Enterprise Server and Ubuntu
• To perform an Express Install on the Red Hat Enterprise Linux, SUSE Linux Enterprise Server and Ubuntu 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.
• You do not have the permission to run the ISM_Lx.sh script directly on the SMINST disk partition. Please use the format sh
ISM_Lx.sh to run the script and initiate iDRAC Service Module installation.
2
Dell EMC iDRAC Service Module 3.3.1 Release Notes