WEM 2112 UPDATE AVAILABLE

Intro

Happy holidays! Citrix has released the last WEM version of 2021 as an early Christmas present. 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 2112

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

Privilege elevation

This release introduces the privilege elevation feature. The feature lets you elevate the privileges of non-administrative users to an administrator level necessary for some executables. As a result, those users can start those executables as if they are members of the administrators group.

You can configure privilege elevation using two types of rules: executable rules and Windows installer rules. You can configure how a rule behaves according to the type of the operating system. You can also configure whether a rule takes effect at a particular point in time or within a time range. You assign a rule on a per user or per user group basis.

For more information, see Privilege elevation. For more information, see Privilege elevation.

Support for optimizing multi-session OS machines

Multi-session OS machines are used to run multiple sessions from a single machine to deliver desktops and applications to users. A disconnected session remains active and its applications continue to run. The disconnected session can consume resources needed for connected desktops and applications that run on the same machine. With this feature, you can optimize multi-session OS machines where disconnected sessions are present. The feature improves the user experience of connected sessions by limiting the number of resources disconnected sessions can consume. For more information, see Multi-session Optimization.

Administration console

The administration console user interface has changed:

  • In System Optimization, there is a new Multi-session Optimization node. On the node, there is a new Multi-session Optimization tab for you to configure settings designed to optimize multi-session OS machines with disconnected sessions.
  • In Security, there is a new Privilege Elevation node. On the node, there is a Privilege Elevation tab for controlling whether to enable the feature and to apply global settings. Below the node, there are two subnodes:
    • Executable Rules with a Privilege Elevation tab where you can apply privilege elevation using executable rules.
    • Windows Installer Rules with a Privilege Elevation tab where you can apply privilege elevation using Windows installer rules.

Deprecation

Click here to see deprecated features.

Thanks for reading,
Alain

WEM 2109 UPDATE AVAILABLE

Intro

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.

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]

Deprecation

Click here to see deprecated features.

Thanks for reading,
Alain

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