Release Notes
Table Of Contents
- Dell EMC iDRAC Service Module 3.2 Release Notes
- Importance
- What’s New
- User Notes for Supported Microsoft Windows Operating Systems
- Known Issues on Microsoft Windows Operating Systems
- Limitations on Microsoft Windows Operating Systems
- User Notes for Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server
- Known Issues on Linux Operating Systems
- Limitations on Linux Operating Systems
- Known Issues on VMware ESXi Operating Systems
- Limitations and Workarounds on VMware ESXi operating Systems
Importance
RECOMMENDED: Dell recommends applying this update during your next scheduled update cycle. This version contains some
new features, feature enhancements and bug fix.
What’s New
● Support for Redhat Enterprise Linux 7.5 operating system (64-bit)
●
Support for VMware ESXi 6.7
● Support for Citrix XenServer 7.1 CU1
● Support for ESXi Live VIB upgrade
● Support for SupportAssist Anonymous upload 12G and 13G
● Support for ESXi package download from iDRAC
NOTE: For a complete list of supported platforms and supported operating systems, see the iDRAC Service Module Guide
version 3.2 at dell.com/openmanagemanuals.
User Notes for Supported Microsoft Windows Operating
Systems
To enable WS-man silently, run the following CLI command:
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.
2