WEM 2106 UPDATE AVAILABLE

Intro

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.

For more information, see Application Security.

Support for the Windows 10 2009 template

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.

Fixed Issues

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]

Deprecation

Click here to see deprecated features.

Thanks for reading,
Alain

WEM 2103 UPDATE AVAILABLE

Intro

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.

Profile Management

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.

For more information, see Citrix Profile Management Settings.

SDK documentation

This release updates PowerShell modules in the Workspace Environment Management SDK. The following cmdlets are no longer usable:

  • Property SDKInfrastructureServiceConfiguration.AgentSyncPort
  • Property Commandlets.SetWemInfrastructureServiceConfiguration.AgentSyncPort

Version 2103 of the Workspace Environment Management SDK documentation reflects the update.

Fixed Issues

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]

Deprecation

Click here to see deprecated features.

Thanks for reading,
Alain

WEM 2012 UPDATE AVAILABLE

Intro

What a year 2020 has been. Despite all the ups and downs, Citrix continues to push out updates. They have released the last version of WEM for 2020, version 2012. 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 2012

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

WEM agent integration with the Citrix Virtual Apps and Desktops product software

The WEM agent is integrated with the Citrix Virtual Apps and Desktops product software, letting you include the WEM agent when installing a Virtual Delivery Agent (VDA). This integration is reflected in the Citrix Virtual Apps and Desktops 2012 product software and later. For more information, see Citrix Virtual Apps and Desktops 7 2012.

If you enable the Citrix Workspace Environment Management check box on the Additional Components page, the WEM Agent page appears. That page is titled Citrix Cloud Connectors used by WEM Agent. Enter a comma-separated list of Cloud Connector FQDNs or IP addresses. Then click Add. The WEM agent on the VDA communicates with those Cloud Connectors.

Optimized WEM agent startup

Previously, the WEM agent startup workflow had the following issues:

  • The agent did not refresh the Citrix Cloud Connector settings after startup. As a result, the Cloud Connector settings deployed to the agent through group policies did not work as expected.
  • In a non-persistent environment, when the agent cache file resided in the base image, the agent could experience cache synchronization issues. As a result, WEM settings might not be applied properly.

Starting with this release, the agent refreshes Cloud Connector settings after startup, just like it refreshes other settings. To ensure that the agent cache is up to date, the agent automatically recreates the cache in non-persistent environments. For more information, see Agent startup behaviors.

For information about how to make the WEM agent work optimally, see Prerequisites and recommendations.

New agent cache utility options

This release adds the following agent cache utility options:

  • -RefreshSettings or -S: Refreshes agent host settings.
  • -Reinitialize or -I: Reinitializes the agent cache when used together with the -RefreshCache option.

For more information, see Agent cache utility options.

Citrix optimizer

Citrix optimizer now provides you with an additional option that enables WEM to automatically select templates for your OSs:

  • Automatically Select Templates to Use. If you are unsure which template to use, use this option to let WEM select the best match for each OS. You can also apply this option to custom templates with different name formats by using the Enable Automatic Selection of Templates Starting with Prefixes option.

For more information, see Citrix optimizer.

Support for the Windows 10 2004 template

WEM adds support for the Windows 10 2004 template introduced in Citrix optimizer. You can now use WEM to perform template-based system optimizations for Windows 10 2004 machines. For information about using Citrix optimizer, see Citrix optimizer.

Support for editing Group Policy settings

Previously, you could change only the name and description for a GPO after importing your GPO settings. You can now edit registry operations associated with a GPO. You can also add new registry operations to a GPO if needed. Currently, WEM supports adding and editing only Group Policy settings that are associated with the HKEY_LOCAL_MACHINE and the HKEY_CURRENT_USER registry hives.

When editing Group Policy settings, you have the following actions: Set valueDelete valueCreate keyDelete key, and Delete all values. For more information, see Edit Group Policy settings.

Multiple selection support for action groups

Previously, when adding actions to an action group, you moved each action present in the Available pane to the Configured pane one by one. You can now move multiple actions in a single step. For more information about action groups, see Action Groups.

WEM agent (advanced notice)

Microsoft Sync Framework 2.1 will reach End of Life on January 12, 2021. WEM will retire the associated legacy agent cache sync service and switch to using the latest agent cache sync service to keep the agent cache in sync with the infrastructure services. The latest agent cache sync service relies on Dotmim.Sync, an open-source sync framework. How does this change impact you?

  • If you use Workspace Environment Management 1912 or later, this change does not require action on your part.
  • If you use Workspace Environment Management 1909 or earlier, upgrade to Workspace Environment Management 1912 or later.

This change is scheduled to be rolled out in March 2021.

Known issues

  • 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]
  • The WEM administration console might fail to display the changes you made to the working directory for an installed application the next time you edit the application. [WEM-10007, CVADHELP-15695]
  • 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]
  • In non-persistent environments, changes you make through the administration console might fail to take effect on the agent hosts. The issue occurs because the agent cache file in the base image might cause cache synchronization problems. As a workaround, users need to first delete the cache on their agent hosts and then refresh the cache manually to synchronize the cache with the infrastructure services.

The recommended best practice is to use a persistent location for the agent cache. If the agent cache resides in a non-persistent location, take these steps before sealing the base image:

  1. Stop Citrix WEM Agent Host Service.
  2. Delete these agent local database files: LocalAgentCache.db and LocalAgentDatabase.db. [WEM-10082]
  • The following options are not mutually exclusive. However, the administration console does not allow you to configure them at the same time.
    • Hide Specified Drives from Explorer and Restrict Specified Drives from Explorer (on the Policies and Profiles > Environmental Settings > Windows Explorer tab) [WEM-10172, WEMHELP-52]

Deprecation

Click here to see deprecated features.

Thanks for reading,
Alain