Release Notes
Table Of Contents
- SupportAssist Enterprise Version 2.0.60 Release Notes
- Release summary
- Compatibility
- 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
- Tool tips 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
- Unable to create cases for alerts received from Force10 networking devices through OpenManage Enterprise adapter version 1.6.0
- Analytics collection for more than 3000 devices takes five hours
- Text on user interface not translated
- Tech Support Report logs are not collected
- SupportAssist recommendations are not generated
- Incorrect device information is displayed
- Collections are automatically initiated
- Incomplete collections performed on ME4 devices
- Translated column titles are not displayed properly
- Limitations
- Installation and uninstallation
- SupportAssist Enterprise resources
- Contacting Dell EMC
Install/upgrade of OMSA fails on Red Hat Enterprise
Linux 8.0 operating system
Description On Red Hat Enterprise Linux 8.0 operating systems, install/upgrade of OMSA fails because the
libcrypto.so package is not available.
Workaround Install the libcrypto.so package and retry the operation.
Tracking Number SAENTK-973
Unable to receive alerts from SupportAssist
Enterprise
Description Unable to receive alerts from SupportAssist Enterprise that is installed on a system running Linux
operating system.
Workaround Install the wget package on the system running the Linux operating system.
Tracking Number SAENTK-939
Unable to create cases for alerts received from
Force10 networking devices through OpenManage
Enterprise adapter version 1.6.0
Description
In alerts received from a Force10 networking device inventoried through OpenManage Enterprise adapter
version 1.6.0, an incorrect enterprise OID is received. So, SupportAssist Enterprise is unable to create
cases for these alerts.
Workaround Upgrade to OpenManage Enterprise adapter version 1.7.0.
Tracking Number SAENTK-1503
Analytics collection for more than 3000 devices takes
five hours
Description
When analytics collections are initiated on more than 3000 devices, the time that is taken to complete the
collection is approximately five hours. The delay is due to the increase in time taken for collection from
each device. When the collection is underway, is displayed in the Collection Status column on the
Analytics Collection page.
Workaround None
Tracking Number SAENTK-1558
Text on user interface not translated
Description
Certain text or messages displayed on the SupportAssist Enterprise user interface are not translated
correctly. Although, if your system language or the browser language is configured as German or French,
you may view the text or messages in English.
Known issues — To be fixed in future releases 17