TMT Fleet Maintenance V.2024.1.3 Release Notes

This document contains information on the latest version, including:

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

PDF version

General information

All information in this section applies to all 2024 releases except where noted.

Warnings

PLEASE READ BEFORE UPGRADING

TMT SOAP APIs

A security update has been made to the TMT SOAP APIs, and we highly recommend upgrading to TMT 2023.3.3 or 2024.1.

If you are a TMT and TruckMate client, pay close attention to the following information, as an integration authentication update will also be available soon for TruckMate.

  • If you plan to upgrade TMT to 2023.3.3 or 2024.1 you must WAIT to upgrade TMT until the TruckMate 24.1.2 version is also available.

  • TruckMate 24.1.2 will be backwards compatible with TMT 2023.3.2 and earlier versions. The TruckMate authentication update will also be backported to versions 23.1, 23.2, 23.3 and 23.4.

  • Once the TruckMate update is available you may upgrade BOTH TMT and TruckMate at the same time, or upgrade TruckMate FIRST, followed by TMT.

AMSLIC database

Starting with V.2022.2, the AMSLIC (license) database has been merged with the TMWAMS (TMT) database. The installer now works with the new merged database alone.

Existing customers must:

  • Run the provided installer migration script to copy all the data from their AMSLIC database to the TMT database.

  • Perform the upgrade using this merged TMT database. The AMSLIC database will become an invalid input in the SQL setup page of the installer.

After doing an upgrade, the web.config file should only have a TMT database, so that the application will launch without issues. The web.config file will still have two database connect entries, as they exist today, but both will refer to the same database.

New customers with a fresh database do not need to run the installer migration script. They can install the program using the TMT database alone.

If you are currently using an older Client-Server version, you must upgrade to at least V.2019.4 before running the merger script to upgrade to V.2022.2.

Important information, please read:

  • SQL Server Cardinality

    Changes to SQL Server cardinality are affecting the performance of TMT Web. The issue happens when SQL Server compatibility mode is set to 120 or greater. This has been identified through Trimble benchmarking and customer feedback.

    At this time, Trimble recommends that you set the SQL Server option for Legacy Cardinality Estimation to ON. This will lessen the effects of the new SQL Server cardinality behavior, which still needs further assessment/improvements in TMT Web.

  • Trimble Technician Portal (TTP) single sign-on (SSO)

    • If you will be using TTP SSO, you must allow pop-up windows. You cannot block them. This applies to Apple and Android phones and tablets. If you block pop-up windows, SSO will not work correctly.

    Follow the directions for your tablet and browser to allow pop-up windows.

    • If you have issues with TTP after upgrading, you may need to clear your browser cache. Close the TTP application and follow the directions for your browser to clear the cache.

    • If you have bookmarked a TTP URL that has a version number, such as 21-3, you should delete that bookmark. Use and bookmark this URL instead: https://tmt-ttp.trimble-transportation.com/

  • TMT Client-Server (Delphi) 2019.4.1 or any earlier version cannot be used with TMT Fleet Maintenance 2022.1 or later. Do not upgrade unless you are ready to go to TMT Web only.

  • Customers using both Integration Options and Windows Authentication should set up their systems so that User dropdown lists use the WINUSER value, instead of the USERNAME value.

  • This version requires .Net Framework 4.8. See the hardware requirements for more information.

  • Customers who are on versions of TMT Web before 2021.3 may be exposed to a vulnerability documented by one of our third-party software vendors (Telerik). Guidance varies depending on the installed TMT Web version (see below). For information directly from Telerik, please use this link: https://docs.telerik.com/devtools/aspnet-ajax/knowledge-base/common-allows-javascriptserializer-deserialization

    • 2021.3, 2021.3.2, 2021.3.3, 2022.1, and later

      These versions use an upgraded Telerik version that has patched the vulnerability. No changes are needed.

    • 2019.4

      A future service pack will include patched Telerik DLLs. In the meanwhile, remediation is possible via web.config changes.

    • 2019.2

      • Remediation possible with web.config changes in this version and higher (2019.2-2021.2.X).

    • Before 2019.2:

      • Remediation is not possible with web.config changes. You must upgrade.

      • For Delphi/Web hybrid customers, see 2019.4 section above. For all others, we would suggest you upgrade to the latest version of TMT Web.

        Telerik Vulnerability Remediation

        Please refer to this link for detailed steps on patching this vulnerability:

      https://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security

    This involves web.config changes, and it can be done without taking an upgrade. However, we strongly encourage you to upgrade to a later version of TMT Web for the greatest level of mitigation.

Before upgrading your production environment, Trimble recommends that you read the hardware requirements and install the latest version in a test environment. If you have questions, please contact your Trimble customer representative.

Changes to hardware requirements

You must be using SQL Server 2016 or later to use TMT Web V.2022.1 or later.

For SQL Server 2016, the minimum compatibility mode is 130. TMT Web will also support modes 140 and 150.

Two files from Microsoft are required for this version:

  • SQL Server 2016 CLR Types

  • SQL Server 2016 Shared Management Objects

You must download and run both files using these links before upgrading to TMT Web V.2022.1:

You must not delete the 2008R2 CLR/SMO SQL Server components from any TMT Web environment when installing or upgrading. The installer is still using these components at this time.

Windows Server and SQL Server upgrades are included in TMT Web software as a service (TMT Web SaaS). For information about upgrading to TMT Web SaaS or other technical questions, contact Dawn Siegel at [email protected].

If you have technical questions, contact TMT Support:

Windows Server and SQL Server Support

  • Windows Server 2012, 2016, and 2019 support SQL Server 2016.

  • Windows Server 2022 does not support SQL Server 2016.

  • Windows Server 2012, 2016, 2019, and 2022 support SQL Server 2017.

  • Windows Server 2016, 2019, and 2022 support SQL Server 2019.

  • Windows 2012 does not support SQL Server 2019.

Trimble Technician Portal (TTP) Update

Trimble will upgrade TTP to V.2024. 1 on Sunday, April 21, 2024. Users should clear their cache when logging back in following the update, please refer to the Security Administrator guide for instructions. The production URL will stay the same: https://tmt-ttp.trimble-transportation.com/.

If you are using TTP on premise, and you do not want to upgrade to V.2022.2 or higher, you can still use the same TTP URL as above.

Interactive Workstation replaced by TTP

Effective with V.2022.3, Trimble has replaced Interactive Workstation (IWS) with Trimble Technician Portal (TTP). Mechanics Workstation (MWS) has also been replaced by TTP.

For more information, see V.2022.3 Release Notes.

Resolutions

Orders > Warranty Claims Listing

  • TMT-324489

    The Warranty Claims Listing page now shows the correct number of claims per page with correct totals. When you apply filters, the search results show up on any page number that you are on.

Orders > Warranty Potential Claims

  • TMT-324491

    The Warranty Potential Claims page now shows the correct number of claims per page with correct totals. When you apply filters, the search results show up on any page number that you are on.