Fall is here and so is a new pumpkin-spice flavor of WEM. Citrix has released version 2109 of WEM. You can download the new version here (requires Platinum/Premium licenses and login to I’ve provided the release notes below.

What’s new in 2109

Workspace Environment Management 2109 includes the following new features. For information about bug fixes, see Fixed issues.

Support for running Workspace Environment Management in FIPS mode

You can now run Workspace Environment Management (WEM) in a FIPS environment. See FIPS support for information on FIPS-related configurations in WEM and upgrade and agent considerations.

Fixed Issues

Workspace Environment Management 2109 contains the following fixed issues compared to Workspace Environment Management 2106:

  • If you assign a printer to a user based on a filter and the assignment satisfies the filter criteria, the WEM agent assigns the printer to the user. However, the agent still assigns the printer to the user the next time the user logs on even when the assignment does not satisfy the filter criteria. [WEM-11680]
  • With the Windows PowerShell script execution policy set to Allow only signed scripts on the agent host machine, WEM fails to perform Profile Management health checks. With the policy set to Allow local scripts and remote signed scripts or Allow all scripts, WEM can perform Profile Management health checks but writes error information to the Windows Event Log. [WEM-11917]
  • On a non-English version of the Microsoft Windows operating system, the WEM agent during logon writes errors to the Windows Event Log even if users experience no issues with their environment. [WEM-12603]
  • When you assign an action to a user or user group through an action group, the action still takes effect even if it is set to Disabled in the administration console. [WEM-12757]
  • The WEM agent installs VUEMRSAV.exe (Workspace Environment Management Resultant Actions Viewer), a utility that lets users view the WEM configuration defined for them by administrators. However, on the Agent Settings tab of the utility, users cannot see the setting that is associated with the Use Cache to Accelerate Actions Processing option configured in the administration console. [WEM-12847]
  • Attempts to upgrade the WEM database from version 2003 or earlier to version 2009 or later might fail if you specify a different schema (not dbo) as the default schema. [WEM-13319]
  • If you use the [ADAttribute:objectSid] dynamic token to extract the objectsid attribute, the WEM agent fails to extract the attribute of the corresponding AD object. [WEM-13746]
  • When you attempt to configure Windows Server 2022 as the matching result of a filter condition (with Client OS as the filter condition type), you find that Windows Server 2022 is missing from the Matching Result menu. [WEM-14036]
  • When the WEM agent belongs to an OU or a group whose name contains certain characters (for example, forward slash, plus sign, and equal sign), the agent might fail to register with a configuration set. As a result, the agent fails to appear on the Administration console > Administration > Agents > Registrations tab. [WEM-14316]
  • If you use the administration console to set desktop wallpaper, the WEM agent fails to fill, fit, or tile the wallpaper. [WEM-14408]


Click here to see deprecated features.

Value for Value

If you received any value from reading this post, please help by becoming a supporter.

Thanks for reading,