We fixed an issue where updating a product logo affected the saved department logo.
Learn more about the 9.5.37 release in the Release Notes.
In this release, we added the ability to rebrand the MFA page with a different logo. For more information on how to set up the logo, see Changing the UI Logo and Theme.
We enabled handling error messages for Azure in case the customer is unable to register with a specific (Microsoft.ClassicCompute) resource provider.
In this release, there were also a number of bug fixes for Network Configuration Management, Reports and Dashboards, Topology Discovery and Visualization, and a few other areas of the product.
Learn more about the 9.5.36 release in the Release Notes.
This release added support of Microsoft Hyper-V Server 2016 and 2019. For more information, see the System Requirements topic.
We added the ability to save a report in .csv format in Reports > Custom > Message Event History, by clicking the Save CSV button.
To enhance security we added the session Hash parameter and removed duplicates cookie values.
In this release, there were also bug fixes for Test Discovery/Parameter Rediscovery and UI Workflow/Usability.
Learn more about the 9.5.35 release in the Release Notes.
This release updated ‘\apps\tomcat\conf\server.xml’ to remove TLSv1.1 and weak ciphers.
In this release, there were also bug fixes for Actions & Notifications, Reports & Dashboards, Network Configuration Management and UI Workflow/Usability.
Learn more about the 9.5.34 release in the Release Notes.
New Features
In this release, we added the ability to discover and monitor the Azure Cloud Services instances and tests.
You can monitor the following if your Azure user subscription supports Microsoft Classic Compute resource provider:
If not, SQL instances/virtual machines/load balancers will be discovered.
Note: To enable the new Azure monitoring feature, you must update your Traverse license. To obtain the required license update, please submit a request to technical support and update the license after the version upgrade.
For more information, see the Cloud Discovery topic.
In this release, we added account lockout for users to enhance security. Traverse users will be locked out for 60 seconds (by default) after 5 failed attempts to log in with invalid credentials or using invalid multi-factor authentication (MFA) codes. You can configure the number of failed attempts and lockout time in the Configuration of Login Attempts section.
Enhancements
In this release, we added timestamps in cronjob.log for backup scripts.
In addition to this, there were also bug fixes for Actions & Notifications, Network Configuration Management, Test Discovery/Parameter Rediscovery, Traverse VSA Module and UI Workflow/Usability.
Learn more about the 9.5.33 release in the Release Notes.