This release contains bug fixes and minor changes to the deviceTRUST Host, Client and Console. See deviceTRUST 20.2.200 release notes for full details of the new features introduced in 20.2.200. If upgrading, please refer to Compatibility for changes in this release.
The deviceTRUST 20.2.320 update includes bugfixes and support for the latest PCoIP Standard Agent 20.10.4 currently being deployed across Amazon WorkSpaces.
The deviceTRUST 20.2.330 update includes additional bugfixes.
The deviceTRUST 20.2.340 update includes bugfixes and support for the forthcoming Amazon WorkSpaces Client 4.0.
Changes in 20.2.300
- Added a new option to the Deny Access task to Always show sign out button, which ensures Sign out is always displayed instead of Disconnect.
- The AppLocker Policy Settings have been extended with the option to import new rules for Cisco WebEx, LogMeIn GoToMeeting/Webinar, Verizon Bluejeans Meetings and Zoom Meetings.
- The AppLocker Policy Settings can now save the AppLocker policy to the AppLocker CSP MDM profile when using Windows Virtual Desktops.
- The Audit Event task now includes a list of evaluated contexts when including a report detailing why the task was executed.
- Added Linux to the supported client Operating Systems.
- Various updates to the templates.
Changes in 20.2.340
- The Custom Process tasks audit events now include the name of the task that was executing. This can be useful for clarity of which custom process is executing, especially when using embedded scripts.
Additionally, the Details tab of the audit event includes the following fields:
- ActionName - The name of the action where the Custom Process task is located.
- SequenceIndex - The zero based index of the sequence within the action where the Custom Process task is located.
- TaskName - The name of the Custom Process task.
Bug Fixes in 20.2.300
- Fixed an issue seen with Citrix VDA 1912 CU2 where tasks could fail to revert during disconnect.
- Fixed an issue where DEVICE_NETWORK_X_IPV4 (and same for IPV6) were not automatically requested from the remote device when used within a context or action.
- Fixed an issue where the DEVICE_DOMAIN properties which changed in 20.2.200 were not automatically upgraded when the remote device was using 19.4.100 or earlier.
- Additional reliability fixes have been added to the deviceTRUST Host for Amazon WorkSpaces.
Bug Fixes in 20.2.320
- Added support for PCoIP Standard Agent 20.10.4 which requires a 64-bit virtual channel. The previous 32-bit virtual channel continues to be supported.
- Fixed a compatibility issue with Citrix published apps where a maximised published app could overlap the taskbar.
- Fixed an issue with VMware Horizon View where a reconnect could temporarily display a black screen and then fail to determine properties of the remote device.
- Fixed an issue where printers could be remapped when the case of the detected printer differs from that defined by policy.
- Fixed an issue where the DEVICE_IGEL_UMS_SERVER property would not work with multiple UMS servers.
Bug Fixes in 20.2.330
- Fixed an issue where the deviceTRUST Client was not always copied into per-user installs of Amazon WorkSpaces.
- Fixed an issue where the deviceTRUST Host on Amazon WorkSpaces did not always detect the reconnection during a live switch between different clients.
- Fixed an issue where the deviceTRUST Host did not generate a Shell Ready trigger or dynamically monitor for property changes, when the OS is configured to use a custom shell.
- Fixed an issue where the deviceTRUST Console could insert hidden states into the context.
- Fixed an issue where the WHOIS country and ISP could be inaccurate for IP addresses administered by RIPE but allocated by ARIN.
Bug Fixes in 20.2.340
- Added support for the forthcoming Amazon WorkSpaces Client 4.0 which has changed from 32-bit to 64-bit.
- Added an automatic repair of the virtual channel registration on the deviceTRUST Host on Amazon WorkSpaces when the PCoIP Standard Agent is rolled back to a previous version.
- Fixed an issue on Amazon WorkSpaces where disconnecting and reconnecting whilst a reconnection was already in progress, could result in the properties of the remote device being unavailable.
- Fixed an issue where context conditions which used the operator Version Greater Than Or Equals would always evaluate successfully, regardless of the version of the property.
- Fixed an issue where it was not possible to run signed embedded PowerShell scripts from within a Custom Process task. To run a signed embedded PowerShell script, the script must use the UTF-8 encoding with a byte-order-mark (BOM). This is the default for scripts initially created with PowerShell ISE, although not the default for scripts created within other editors such as notepad.exe. Notepad++ can be used to confirm the ‘UTF-8-BOM’ encoding.
If upgrading from deviceTRUST 20.1.200 or earlier, be sure to refer to the deviceTRUST 20.1.200 Compatibility notes.
If upgrading from deviceTRUST 20.2.100, ensure all deviceTRUST Hosts are upgraded before applying policy that has been written by the deviceTRUST Console 20.2.200 or later.
There have been no changes to the ADMX policy definitions.