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 Citrix.com). 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.
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]
Spring has sprung and COVID-19 is retreating, so Citrix has a new WEM release. Citrix has released the first version 2106 of WEM. You can download the new version here (requires Platinum/Premium licenses and login to Citrix.com). I’ve provided the release notes below.
What’s new in 2106
Overwrite or merge application security rules
This release adds two settings, Overwrite and Merge, to the Administration Console > Security > Application Security tab. The settings let you determine how the agent processes application security rules.
Select Overwrite if you want to overwrite existing rules. When selected, the rules that are processed last overwrite rules that were processed earlier. We recommend that you apply this setting only to single-session machines.
Select Merge if you want to merge rules with existing rules. When conflicts occur, the rules that are processed last overwrite rules that were processed earlier.
We added support for the Windows 10 2009 (also known as 20H2) template introduced in Citrix optimizer. You can now use Workspace Environment Management to perform template-based system optimizations for Windows 10 2009 machines. In addition, we have updated all existing templates to reflect changes introduced in the latest standalone Citrix optimizer. For information about using Citrix optimizer, see Citrix Optimizer.
Workspace Environment Management 2106 contains the following fixed issues compared to Workspace Environment Management 2013:
For logging level changes to take effect immediately, the WEM agent might access certain registry keys very frequently, thus affecting performance. [WEM-11217]
The WEM agent might become unresponsive when processing applications, failing to process them successfully. [WEM-11435, CVADHELP-16706]
With an action group assigned to multiple users or user groups, if you unassign it from a user or user group, the assignment might not work as expected. For example, you assign an action group to two user groups: Group A and Group B. If you unassign the action group from Group A, the action group is unassigned from Group B rather than Group A. [WEM-11459, WEMHELP-75]
You might experience performance issues such as slow logon or slow session disconnect when launching or disconnecting from published application sessions. The issue occurs with WEM agent 2005 and later. [WEM-11693]
When you configure an environment variable (Actions > Environment Variables), attempts to use the $Split(string,[splitter],index)$ dynamic token might fail. The issue occurs because the dynamic token does not support multi-line strings. [WEM-11915]
If you assign a file system operations action and update the action later, the files or folders that were previously copied to the user environment might be deleted. The issue occurs because the WEM agent reverts the assignment made earlier after you update the action. [WEM-11924, CVADHELP-16916]
With Agent Type set to CMD on the Advanced Settings > Configuration > Main Configuration tab, the Monitoring > Daily Reports > Daily Login Report tab might fail to display a summary of logon times across all users connected to the current configuration set. [WEM-12226]
The memory optimization feature might fail to work on WEM version 2012 and 2103. [WEM-12913, CVADHELP-17426]
New Year, new WEM release. Citrix has released the first version of WEM for 2021, version 2103. You can download the new version here (requires Platinum/Premium licenses and login to Citrix.com). I’ve provided the release notes below.
What’s new in 2103
Workspace Environment Management 2103 includes the following new features. For information about bug fixes, see below.
Workspace Environment Management now supports all versions of Profile Management through 2103. Also, the following new options are now available in the Administration Console > Policies and Profiles > Citrix Profile Management Settings interface:
Enable Local Cache for Profile Container
Available on the Profile Container Settings tab.
If enabled, each local profile serves as a local cache of its profile container.
Enable multi-session write-back for profile containers
Available on the Advanced Settings tab.
Replaces Enable multi-session write-back for FSLogix Profile Container of previous releases to accommodate multi-session write-back support for Citrix Profile Management profile containers.
Enable Profile Streaming for Folders
Available on the Streamed User Profiles tab.
If enabled, folders are fetched only when they are being accessed.
Workspace Environment Management 2103 contains the following fixed issues compared to Workspace Environment Management 2012:
After you upgrade the WEM agent to version 1912, the memory consumption of Citrix WEM Agent Host Service might exceed 2G. If debug mode is enabled, you can see that the following messages appear many times in the Citrix WEM Agent Host Service Debug.log file:
Adding history entry to the DB writer queue
Initializing process limitation thread for process [WEM-9432, CVADHELP-15147]
After you upgrade the WEM agent to version 2005, Citrix WEM Agent Host Service might consume between 10% and 30% of the total CPU resources, affecting the user experience. [WEM-9902, WEMHELP-47]
When using the application security feature, you see a green checkmark next to a user or user group in the Assigned column of the Assignments section in the Edit Rule or Add Rule window. The green checkmark icon does not necessarily indicate that the rule is assigned to that user or user group. Only a user or user group that has a blue highlight in the background is the one to which the rule is assigned. [WEM-10047]
While the WEM agent performs application processing during logon, Windows might display the Problem with Shortcut dialog box, prompting end users to delete a shortcut that no longer works properly. The issue occurs when the item to which the shortcut refers has been changed or moved. [WEM-10257, CVADHELP-15968]
When you attempt to edit an exception for an application security rule on the Exceptions tab of the Edit Rule window, the administration console might exit unexpectedly. The following message appears:
Connection to the management console closed
The issue occurs when you edit an exception before performing any Add Rule actions. [WEM-10612]
When you use VUEMRSAV.exe to view results about assigned actions for the current user, the Applied Actions tab fails to display actions related to Action Groups. (VUEMRSAV.exe is located in the agent installation folder: %ProgramFiles%\Citrix\Workspace Environment Management Agent\VUEMRSAV.exe.) [WEM-10889]