Release Notes

Workaround: There is no functional impact. No action is required by the user.
Tracking ID: 122750.
Issue 2: Configuring the Windows Remote Management
(WinRM) Listener using a server authenticating certificate
Description: 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 force-enables the WinRM listener using a self-signed certificate.
Workaround: To configure the Windows Remote Management (WinRM) listener, you can create a self-signed certificate using the
PowerShell New-SelfSignedCertificate cmdlet 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.
Known issues on Linux operating systems
Issue 1: iSM communication with iDRAC through IPv6 does
not support "InBand iDRAC Launcher"
Description: iSM communication with iDRAC through IPv6 in Linux operating system does not support "InBand iDRAC Launcher" feature
though the configuration shows successful message.
Workaround: Currently this feature is supported through IPv4 communication.
Tracking number: 133769
Issue 2: iSM Auto communication with iDRAC fails when
USB NIC IP address is changed in iDRAC while iSM is
running
Description: iSM Auto communication with iDRAC fails and the services do not start automatically when USB NIC IP address in iDRAC is
changed while iSM is still in running state.
Workaround: There is no workaround available.
Tracking number: 118654
Issue 3: ismtechuser does not get deleted when iDRAC
Service Module is uninstalled.
Description: ismtechuser does not get deleted when the user is logged in and, iDRAC Service Module is uninstalled.
Workaround: ismtechuser should be deleted manually.
Tracking number: 131851
Issue 4: Launching SSO for Sudo user on RHEL 8 displays
iDRAC launcher script location path in OS logs.
Description: On Red Hat Enterprise Linux 8 operating system (64-bit), while launching iDRAC GUI for the first time using iDRAC
Launcher.sh script or using the Dell EMC iDRAC GUI Launcher short-cut, the below message is displayed in the operating system logs.
“localhost dbus-daemon[2369]: [system] Activating via systemd: service
name='net.reactivated.Fprint'unit='fprintd.service' requested by ':1.18176' (uid=0 pid=126684
Known Issues
9