Release Notes
Table Of Contents
- SupportAssist Enterprise Version 2.0.70 Release Notes
- Release summary
- Version
- Release date
- Priority and recommendations
- Compatibility
- Minimum requirements for installing and using SupportAssist Enterprise
- New and enhanced features
- Known issues—To be fixed in future releases
- SupportAssist Enterprise services do not start automatically
- The snmptrapd service may not start automatically
- The Remote Collector or adapter displays a validation in progress status
- iSCSI and non-iSCSI adapter attributes may not be available
- Collections from PowerVault MD Series storage arrays may display incorrect values
- No action occurs when you click the Install/Upgrade OMSA option
- Tooltips are not displayed
- SupportAssist Enterprise is unable to connect to the remote system
- Refreshing the Devices or Cases page opens the first page
- Collections from networking devices do not contain the IP address of the networking device
- SCSI and non-iSCSI interfaces section is not available
- Installation of SupportAssist Enterprise on Debian operating system is unsuccessful
- Service Tag is not available in Deployment collections
- Displays section may be blank
- SATA Controller information is not available
- Uninstallation of SupportAssist Enterprise does not uninstall the OpenManage Enterprise adapter automatically
- Number of Active sessions is displayed as 'Not available' in iDRAC collections
- Incorrect Physical Disk name is displayed in Physical Device ID
- Periodic inventory validation does not start on the same day
- System information does not include controller TTY logs
- Incorrect manufacturer details
- Incorrect hostname details
- Incorrect time zone list options
- Concurrent operations are unsuccessful
- System Center Operations Manager adapter displays a disconnected status
- Device Overview pane does not display the operating system version details
- Unable to edit the adapter
- Alerts not processed from Dell PowerVault MD Series device
- Service Tag of a chassis is displayed instead of the Service Tag of a blade server
- Alerts from OpenManage Enterprise adapter are not processed
- Incorrect postal code and incorrect state or province value
- Integrating TechDirect with SupportAssist Enterprise is not supported
- Unable to filter group name
- Collection report does not display all attributes
- Install/upgrade of OMSA fails on Red Hat Enterprise Linux 8.0 operating system
- Unable to receive alerts from SupportAssist Enterprise
- Collections are automatically initiated
- Incomplete collections performed on ME4 devices
- Devices moved to Default group during adapter sync
- Limitations
- Installation and uninstallation
- SupportAssist Enterprise resources
- Contacting Dell EMC
Number of Active sessions is displayed as 'Not available' in iDRAC
collections
Description Number of Active sessions is displayed as 'Not available' in iDRAC in-band and out-of-band collections
that are performed from SupportAssist Enterprise.
Workaround Perform a SupportAssist TSR collection to view the missing information.
Tracking Number SAE-10914
Incorrect Physical Disk name is displayed in Physical Device ID
Description Collections that are performed from managed nodes that are configured with PCIe-SSD controllers and
with OMSA 9.1, display Physical Disk name with three digits in Physical Device ID instead of two digits.
Workaround None
Tracking Number SAE-11280
Periodic inventory validation does not start on the same day
Description After upgrading SupportAssist Enterprise, periodic inventory validation runs automatically within the next
hour. If you restart SupportAssist Enterprise service or the system restarts within 1 hour of the upgrade,
the periodic inventory validation starts only on the next scheduled date.
Workaround To run periodic inventory validation on the same day, go to the Preferences page and set the periodic
inventory validation date to the current date.
Tracking Number SAE-14658
System information does not include controller TTY logs
Description
System information collected from servers running OMSA does not include controller TTY logs for the
HBA controller.
Workaround None
Tracking Number SAE-12736
Incorrect manufacturer details
Description
System information collected from ESXi host may contain incorrect manufacturer details for adapters
displayed in the iSCSI HBA section.
Workaround None
Tracking Number SAE-11232
Incorrect hostname details
Description
System information collected from a chassis may contain incorrect hostname details for quarter height
blade servers displayed in the Chassis Slot section.
Workaround None
Tracking Number SAE-14489
Release summary 5