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.
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:
-S: Refreshes agent host settings.
-I: Reinitializes the agent cache when used together with the
For more information, see Agent cache utility options.
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 value, Delete value, Create key, Delete 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.
- 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:
- Stop Citrix WEM Agent Host Service.
- 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]
Click here to see deprecated features.
Thanks for reading,