deviceTRUST 25.3 for Windows, macOS, Ubuntu and eLux are now available.
×
Search

deviceTRUST 25.3

deviceTRUST 25.3 is now built into the Citrix Virtual Apps and Desktops and the Citrix Workspace app.

  1. Supported platforms
  2. Licensing
  3. Citrix Virtual Channel Allow List
  4. Custom Properties and Custom Process Task
  5. Compatibility with previous clients
  6. Compatibility

Supported platforms

The supported platforms have been updated. Please refer to the Platform Compatibility for more information.

Licensing

A deviceTRUST license is no longer required when using the Citrix ICA/HDX protocol and a deviceTRUST Policy is applied. A license is still required when using an RDP protocol.

Citrix Virtual Channel Allow List

The Citrix virtual channel allow list must be updated to support deviceTRUST Agent 2503, due to a rename of the virtual channel to CTXDT, and a new installation path. More details can be found in the Configuring Citrix Virtual Channel Security Knowledge Base article.

Custom Properties and Custom Process Task

Custom Property Scripts and Custom Process Tasks of the remote device are now disabled by default and can be enabled via a Windows Registry entry, or an environment variable on non-Windows platforms. More details can be found in the Enabling Custom Scripts on Remote Devices Knowledge Base article.

Compatibility with previous clients

The deviceTRUST Client Extension v25.3 is not compatible with the previous deviceTRUST Agent v23.1 due to a change of the virtual channel name. More details can be found in the Virtual Channel Compatibility Knowledge Base article.

Compatibility

This compatibility section builds on our general approach to compatibility which can be found within the Lifecycle page.

If upgrading from a previous release, be sure to check out the deviceTRUST 23.1.410 compatibility notes.

The deviceTRUST Agents can read policies created by previous releases of the deviceTRUST Console. However, they cannot read policies created by a newer console. Therefore, you must ensure that the deviceTRUST Agent 25.3 is deployed before applying policy that has been written by the deviceTRUST Console 25.3.