Connect[productSupport]
You must have the latest published version of SOTI Connect 2024.1 installed on your system before installing version 2024.2. You cannot directly install SOTI Connect 2024.2 from an earlier version. In addition, SOTI Connect 2024.2 requires .NET 8 Runtime and ASP.NET Core Runtime 8 for upgraded .NET compatibility.
With the most recent database and process management improvements and the migration to .NET 8, SOTI Connect 2024.2 is now more powerful and faster than ever. The modifications to the overall SOTI Connect system have resulted in significant performance improvements that double its capacity for managing devices per instance.
Permissions management has been enhanced to provide more granular control and flexibility for administrators and users. By adding and leveraging Microsoft Entra ID support, we ensure a more secure and efficient workflow while seamlessly integrating with the Microsoft Azure ecosystem.
Rule creation within SOTI Connect has been enhanced to give users more control and flexibility, thereby streamlining the process of automation. Adding sequential rule actions allows users to choose between sequential and concurrent rule-firing modes, enabling them to tailor rule execution to match their workflow preferences.
Automation options have been expanded with the introduction of device property-to-property comparison, which allows users to define conditions based on specific device attributes. Additionally, the integration of advanced relations in rules such as "startswith," "endswith," and "contains" furthers the user’s ability to create advanced and precise rules to meet their needs.
SOTI Connect has greatly expanded its search capabilities for this release. The saved searches functionality allows users to define and save their search queries, providing the convenience of accessing frequently used search criteria without having to recreate them repeatedly. SOTI Connect now also supports the use of the OR condition in search criteria, enhancing search flexibility and accuracy.
We are pleased to announce the release of SOTI Connect 2024.2 OEM Update. In this release, we added Cab as a new partner for printer support, upgraded our firmware support for Zebra printers and added a new device category for Zebra with RFID Sled support.
SOTI Connect has added Cab as a certified printer manufacturer and now supports the full range of Cab SQUIX label printers for device management.
Zebra and SOTI have combined to provide support for a new range of devices in SOTI Connect, adding device management for Zebra RFID readers. For this release, SOTI has certified the RFD40 and RFD90 UHF RFID Sleds to work with SOTI Connect 2024.2 and later.
Zebra has recently released an updated printer firmware version called Link OS 7.0 for its industrial and mobile printers. SOTI Connect has certified the printers included in that release for use with SOTI Connect 2024.2 and later. Please see the Certified Device List to verify which printers are included.
Users will get the OEM Update when installing or upgrading to the latest version of SOTI Connect. For those on an earlier build of 2024.2, the OEM Update is supported via a Device Type Definition (DTD) file release targeted for SOTI Connect 2024.2 installations. Users can import this file into SOTI Connect to update supported devices without requiring a SOTI Connect upgrade. These updates can contain new supported device firmware versions, new devices and more. To install the DTD file, users need to:
Further instructions can be found in the SOTI Connect Help for 2024.2.
SOTI Connect introduces several upgrades designed to improve the user experience. Some include:
| IOT‑17299 | Sorting columns on the device panel caused functionality issues |
| IOT‑18557 | Connection status remained as “not reachable” while device actions were completed successfully |
| IOT‑21161 | Bulk import of mappings created wrong Automatic Group Mappings |
| IOT‑21164 | Rules with relative time conditions did not execute correctly |
| IOT‑21356 | Sorting logic for Device Name and Device Type properties were inconsistent |
| IOT‑21376 | Actions were not visible when editing configurations |
| IOT‑21390 | The Management Server would not start after a 2024.1 to 2024.2 upgrade |
| IOT‑21499 | Automatic Group Mappings did not run when a device was added/moved to a group |
| IOT‑19804 | Automatic Group Mapping not working for custom attributes with Datetime type |
| IOT‑21052 | Generating and deploying a new certificate does not automatically update the certificate list in the device details |
