Hey Guys,

Below are the latest release notes from Traverse:

This release contains the following enhancements and bug fixes:


  • IT Complete - The Login page and top navigation bar have been updated with a clean new look. (TV-6852) (TV-6853)
  • Monitoring - Enhanced the purgeOldMessages.pl script by adding the following new command line options: (TV-6382)

--export="path" - This exports purged messages to the specified directory. The script attempts to compress output after it has been written to disk, by using gzip or zip, if available.

Use the next three options to control execution and scaling of deletes. The script performs passes, deleting records, and sleeps for y seconds between passes. The script's default values (batch size: 50,000, passes: 100, and sleep: 5) have not been changed. These options provide a mechanism to easily override the defaults for a given customer or environment.

--batch=n, where n is the maximum number of files deleted in each pass.
--passes=n, where n is the number of passes the script performs.
--sleep=n, where n is the number of seconds the script sleeps before executing the next pass.

Note: The other options of the script remain the same. The updated script is backward compatible with the previous script framework.

  • RMM 2.0 - To ensure that the latest DGEx version is used when deploying DGExs to agents, Traverse on Linux installations now add the latest the DGEx installer (DGEx-installer.zip) to this directory: /usr/local/traverse/apps. (TV-6945)
  • RMM 2.0 - VSA now requires that organization names contain alphanumeric characters only. The use of special characters is no longer supported. (TV-6958)
  • RMM 2.0 - You can now view summary details by device. Navigate to Traverse > Device Health and click a Device Name in the list. The Device Summary page displays information about the device's health, configuration, tests, clients, and applications: (TV-6851)

  • RMM 2.0 - You can now view test details right from the Traverse > Device Health page. To view details, select a device in the list. In the Tests detail area below, click a test name link:

  • RMM 2.0 - Any change to the Traverse ExternalLoginKey is now detected and applied to integration settings. This ensures seamless communication between VSA and Traverse any time the key is changed (either by installing Traverse updates or by editing the Traverse web.xml file). (TV-6995)
  • RMM 2.0 - You can now uninstall a DGEx by using the Traverse > Administration > Data Collectors page: (TV-6954)
    • On the Traverse > Administration > Data Collectors page, select an agent in the list.
    • Click Uninstall Collector.

The uninstall task is added to the agent schedule and will be removed by the agent. The Deployment icon changes to  , indicating the DGEx is scheduled for uninstall.

  • Click OK to close the confirmation message.

  • Security improvements - We continually strive to ensure that our applications are secure. This will continue to be a theme across all of the Kaseya products. (TV-6219)
  • SQL Monitoring - Added support for integrated Windows authentication for Microsoft SQL Server. To configure this feature: (TV-440)
    • In VSA, navigate to Traverse > Security > Users and add the Windows machine user to SQL Server for the selected database.
    • In SQL Server Management Studio, create a Windows user that has permission to access the database and map it to the Windows machine.
    • Verify that the client and server can ping each other.
    • In SQL Server Management Studio, verify that you can connect to SQL Server by using Windows authentication.
    • If needed, enable access for other SQL Servers using these steps:
      • Log in to the SQL Server and launch SQL Server Configuration Manager.
      • Click TCP Protocol Properties and enable the TCP and Named Piped Client protocols for use over port 1433.
      • Restart SQL Server.


  • Linux Installer - Fixed an upgrade issue where Perl was not being installed. (TV-6984)
  • Monitoring - Fixed a calculation error in the database optimization tools (db_optimize.pl and db_optimize.sh). (TV-4928)
  • RMM 2.0 -
    • Discovery - Fixed an issue where more than one discovery session could exist with the same name. Additional identifiers have been added to these names to ensure that each can be uniquely identified. (TV-6885)
    • Discovery - Fixed a hostname assignment issue that could cause duplicate devices to be listed on the Discovery > Discovered Devices page. (TV-6785)
    • Login Page - Fixed a session tracking issue that could cause an error when a user attempted to log in for a second time. (TV-6959)
    • Traverse Onboarding Wizard - Fixed an Unable to return VSA organizations... error caused by a timezone offset issue. (TV-6940) (TV-6947) (TV-7010)
    • Traverse Onboarding Wizard - Fixed an issue that caused DGEx deployment to fail with the following error: DGE extension unsuccessfully deployed with status not-configured on agent with IP address ... Asset synchronization will not begin. (TV-6941)
    • DGEx Installation - Fixed an issue where DGEx services failed to start after the DGEx had been deployed successfully. (TV-7013)
    • Traverse > Administration > Integration Settings - Fixed an issue where adding a new Traverse integration could fail with a Failed to parse the Traverse response... error. This error occurred after entering correct settings and clicking Save on the Integration Settings page. (TV-6948) (TV-6929)
    • Superuser > Health > Component Status - Fixed an issue where the Component Status page displayed data from previous DGEx deployments and did not display data for the current DGEx deployment. (TV-7011)
  • Administration > Containers - Fixed an issue where updating a container could clear the Populated dynamically based on a rule option and the remove the rule definition from Define Rule. (TV-5568)
  • UI -
    • Superuser > Health > Component Status - The Installed Version no longer includes the build number suffix. (TV-6226)
    • Superuser > Health > Component Status - Fixed a misspelling in the ...server reloaded message that displays upon refreshing the Component Status page. (TV-6313)