Citrix group policies may fail to appear in Studio post upgrade to CVAD Versions 2311 or 2402, and on Citrix DaaS. VDAs that expect the missing policies to be applied may behave differently.

This issue is currently under investigation and a standalone tool will be provided to run checks on policies. While that is in progress we recommend you check the following policy settings for the presence of invalid data:

1. WebSockets trusted origin server list.

2. Rendezvous proxy configuration.

3. List of applications excluded from failure monitoring.

4. Browser content redirection proxy configuration.

5. Universal printing optimization defaults.

6. Allowed URLs to be redirected to VDA.

7. Allowed URLs to be redirected to Client.

8. Client USB device optimization rules

9. User layer repository path

10. Loss tolerant mode thresholds

NOTE : Here is an example of how invalid data may persist in a policy setting:

Virtual channel allow list may have the following invalid input:

ABCD,C:\Program.exe

A1

B2

Expected input:

Each line should be in the format: VCNAME,ProgramExecutable. 

Hence, here lines A1 and B2 are not allowed with the validation.

Problem Cause

• Additional setting validations were added as part of an update to Citrix DaaS, CVAD 2311, and CVAD 2402 releases.
• Settings from previous releases that have invalid entries will fail to pass validation on the data. This causes the policy data processing to abort early. Policies that were already processed are intact, but any policies after the error are removed from the site.

New Environments will not be impacted by these changes