New product names and version numbers were introduced in Workspace Environment Management service 1807. That information is retained in this article for reference. For more information, see New product names and New product and component version numbers in this article.
A goal of Citrix is to deliver new features and product updates to Workspace Environment Management service customers when they are available. New releases provide more value, so there is no reason to delay updates. Updates are rolled out to the service release approximately every three weeks.
This process is transparent to you. Updates are applied to Citrix internal sites initially, and are then applied to customer environments gradually. Delivering updates incrementally in waves helps ensure product quality and maximize availability.
For information about the service level goal for the Workspace Environment Management service for cloud scale and service availability, see Service Level Goals. To monitor service interruptions and scheduled maintenance, see the Service Health Dashboard.
Agents for the Workspace Environment Management service are different from agents for the on-premises version of Workspace Environment Management. The service-specific agents release on the same schedule as other Workspace Environment Management service components, features, and technologies. Generally, the service-specific agents release at the same time as the Workspace Environment Management service product.
- For information about agent platforms and features that are no longer supported, see Deprecation. The Deprecation article also includes platforms and features that are scheduled to be unsupported in a future release (such as which operating systems support agent installation).
Support for communications over TLS 1.2
Workspace Environment Management (WEM) service secures communications by utilizing the Transport Layer Security (TLS) 1.2 protocol. TLS 1.2 provides a higher level of security than earlier TLS versions.
How this change impacts you
To enable TLS 1.2, you must use the latest version of the WEM service agent. The latest WEM service agent allows only TLS 1.2 communications.
What to do
If you want to enable only TLS 1.2, upgrade your agent to the latest version. For information about upgrading the WEM service agent, see Upgrade.
Workspace Environment Management service now supports all versions of Profile Management through 1903. The following new option is now available on the Administration Console > Policies and Profiles > Citrix Profile Management Settings > Synchronization tab:
- Enable Profile Container (option for eliminating the need to save a copy of the folders to the local profile)
Workspace Environment Management integration with Endpoint Management
This release includes the following enhancement to the Workspace Environment Management integration with Endpoint Management:
- The machines on which the WEM service agent is running are associated with a configuration set automatically. There is no need to manually add the machines (agent hosts) to a configuration set in the WEM service administration console. As a result, you can now directly configure WEM settings (group policies) using the Endpoint Management console after you install the service agent on the applicable machines. For more information, see Windows GPO Configuration device policy.
An “Enable Notifications” option is provided on the Advanced Settings > Configuration > Agent Options tab. You can use this option to control whether the agent displays notification messages on the agent host when the connection to the infrastructure service is lost or restored.
When you click Apply Filter or Refresh Report on the Administration Console > Monitoring > User Trends > Devices Types tab, you might not be able to view the report. Instead, you are returned to the Administration Console > Actions > Applications > Application List tab. [WEM-3254]
On Windows 10 version 1809 and Windows Server 2019, Workspace Environment Management fails to pin the applications to the task bar. [WEM-3257]
After WEM upgrades to the latest version, if you still use the earlier versions of the agent, the agent fails to work properly in offline mode. This issue occurs because of the scope changes of the agent local cache file in the latest release. As a workaround, delete the old agent local cache file, and then restart the WEM Agent Host Service (Norskale Agent Host service). [WEM-3281]
On the Security tab of the administration console, if you create an AppLocker rule for a file with an .exe or a .dll extension using a file hash condition, the rule does not work. This issue occurs because WEM calculates the hash code of that file incorrectly. [WEM-3580]
On the Security tab of the administration console, if you create an AppLocker rule for a file using a publisher condition, the rule does not work. This issue occurs because WEM resolves the file name incorrectly. [WEM-3582]
The Enable AutoEndTasks option on the Policies and Profiles > Environmental Settings > SBC / HVD Tuning tab of the administration console does not work. [WEM-3749, LD0876]
If you click Add OU on the administration console, WEM might not display anything on the Organizational Units window. The issue occurs when a forest (current or trusted) contains a large number of OUs. As a workaround, you might need to click Cancel and then click Add OU multiple times. [WEM-3818, UCOHELP-1211]
The Application Security feature does not work on Windows servers that use non-English Windows operating systems. This issue occurs because WEM fails to start the Application Identity service in non-English language environments. [WEM-3957, LD1185]
- Attempts to migrate your WEM database into the WEM service can fail. The issue occurs when the entries in the VUEMTasksHistory table of your on-premises WEM database contain special characters. As a workaround, delete those entries from your on-premises WEM database, and then restart the migration process. [WEM-3817, UCOHELP-1567]
Workspace Environment Management integration with Endpoint Management
As of this release, Workspace Environment Management service supports configuring group policies through the Endpoint Management console. To configure group policies from the Endpoint Management console, make sure that you are running the latest version of the Workspace Environment Management service agent. For more information about the integration, see Citrix Endpoint Management.
The following issues have been fixed in the current release:
With language packs installed, options in the Start menu > User Account menu might not be displayed in the language you selected. [WEM-1176, LC8811]
Attempts to access the administration console from the Workspace Environment Management service Manage tab fail. As a workaround, refresh your browser window and try again. [WEM-2401]
After your WEM service is upgraded to version 1811, the administration console might exit unexpectedly when you click OK if WEM does not display anything on the Organizational Units window. [WEM-3612, UCOHELP-655]
Attempts to migrate your on-premises WEM database into the WEM service might fail after uploading your SQL file. The issue occurs because database creation in Azure times out. [WEM-3783, UCOHELP-983, UCOHELP-987]
A new process allows you to migrate an on-premises Workspace Environment Management database to the Workspace Environment Management service. The process is provided on the WEM service’s Downloads tab. For more information, see Migrate.
The administration console user interface changes:
An “Everyone” default group is provided on the Assignments > Action Assignment tab. To simplify assigning actions for all users in Active Directory, you can use the “Everyone” default group to assign the actions.
A Profile Management health status column is provided on the Administration > Agents > Statistics tab. As of this release, Workspace Environment Management supports performing automated status checks on your agent hosts to determine whether Profile Management is configured optimally. You can view the status in the column.
As of this release, Workspace Environment Management service supports configuring all settings for Citrix Profile Management 1808. The following new options are now available in the administration console on the service’s Manage tab:
- Enable application profiler (option for defining application-based profile handling)
- Enable search index roaming for Microsoft Outlook users (option for improving the user experience when searching mail in Microsoft Outlook)
- Enable Large File Handling (option for eliminating the need to synchronize large files over the network)
New product names
If you’ve been a Citrix customer or partner for a while, you’ll notice new names in our products and in this product documentation. If you’re new to this Citrix product, you might see different names for a product or component.
The new product and component names stem from the expanding Citrix portfolio and cloud strategy. Articles in this product documentation use the following names.
Citrix Virtual Apps and Desktops: Citrix Virtual Apps and Desktops offers a virtual app and desktop solution, provided as a cloud service and as an on-premises product, giving employees the freedom to work from anywhere on any device while cutting IT costs. Deliver Windows, Linux, web, and SaaS applications or full virtual desktops from any cloud: public, on premises or hybrid. Virtual Apps and Desktops was formerly XenApp and XenDesktop.
Citrix Workspace app: The Citrix Workspace app incorporates existing Citrix Receiver technology as well as the other Citrix Workspace client technologies. It has been enhanced to deliver additional capabilities to provide end users with a unified, contextual experience where they can interact with all the work apps, files, and devices they need to do their best work. For more information, see this blog post.
Citrix Provisioning: The Citrix Provisioning is a solution for managing virtual machine images, combining previous technologies known as Machine Creation Services (MCS) and Citrix Provisioning Services (PVS). Citrix Provisioning was formerly Provisioning Services.
Here’s a quick recap:
|Citrix Virtual Apps and Desktops||XenApp and XenDesktop|
|Citrix Workspace app||Citrix Receiver|
|Citrix Provisioning||Provisioning Services|
Implementing this transition in our products and their documentation is an ongoing process.
In-product content might still contain former names. For example, you might see instances of earlier names in console text, messages, and directory/file names.
It is possible that some items (such as commands and MSIs) might continue to retain their former names to prevent breaking existing customer scripts.
Related product documentation and other resources (such as videos and blog posts) that are linked from this product’s documentation might still contain former names.
Your patience during this transition is appreciated. For more detail about our new names, see https://www.citrix.com/about/citrix-product-guide/.
New product and component version numbers
In this release, product and component version numbers are displayed in the format: YYMM.c.m.b.
- YYMM = Year and month when the features are finalized. For example, if the features are finalized in August, a release in September 2018 appears as 1808.
- c = Maintenance version (if applicable).
- m = Citrix Cloud release number for the month.
- b = Build number. This field is shown only on the About page of the product, and in the OS’s feature for removing or changing programs.
For example, Workspace Environment Management service 1808.0.1 indicates that the released product with features finalized in August 2018 is associated with Citrix Cloud release 1 in that month, and is not a maintenance version. Some UI elements display only the version’s year and month, for example, Workspace Environment Management service 1808.
The following issues have been fixed in the current release:
In the Security tab, when you clear the option Process DLL Rules, the rule count reported next to the “DLL Rules” collection is set to zero, regardless of the actual number in the WEM database. [WEM-425]
The Workspace Environment Management Agent Host screen capture feature allows end users to take screenshots of error messages in their environment. They can then send the screenshots to the administrator via Microsoft Outlook for support. However, when end users click the Send to Support button, the following error message appears: “Error encountered while sending email.” [WEM-1123]
Attempts to upgrade the WEM database using the command line might fail. [WEM-1410]
The on-premises version of WEM lets you use Active Directory security groups as containers for WEM agents. However, the WEM service does not support using Active Directory security groups as agent containers. The on-premises infrastructure service also supports using direct and indirect OUs as agent containers. For example, suppose WEM agent AGENT1 belongs to OU2, and OU2 belongs to OU1 (OU1>OU2>AGENT1). The on-premises infrastructure service recognizes AGENT1 as a member of both OU1 and OU2. However, the WEM service does not support indirect OUs. In the example above, the WEM service recognizes AGENT1 only as a member of OU2. [WEM-1619]
In the WEM administration console’s Assignments section, when you use the Modeling wizard for a global view of WEM actions assigned to a specific user, the User Groups tab in the Actions Modeling wizard displays the groups to which the user belongs. However, in WEM service, the User Groups tab in the Actions Modeling wizard does not display the groups to which the user belongs. [WEM-1632]
After you apply a percentage of the CPU’s processing power for a process on the System Optimization > CPU Management > CPU Clamping tab of the administration console for the first time and configure a different percentage for the same process later, the change does not take effect. [WEM-1993, LD0110]
After you upgrade the WEM agent to Version 4.7, if you select Enable Intelligent CPU Optimization and/or Enable Intelligent I/O Optimization on the System Optimization > CPU Management > CPU Management Settings tab of the administration console, error messages about Error 87 frequently appear in Windows Event logs. This issue does not affect the user experience, thus you can dismiss these error messages. [WEM-2051]
When the Citrix WEM agent starts, a Citrix WEM Agent Init file (.log) and a Citrix WEM Agent file (.log) are created separately in the root of the current user’s Users folder. However, while WEM agent switches from the Citrix WEM Agent Init file to the Citrix WEM Agent file, some logs might be missing. [WEM-2233]
Agent group policy template: This template allows you to specify a list of Citrix Cloud Connectors. You must do this before you install the agent. See Install and configure.
Workspace Environment Management service agent: A service-specific agent is provided which has the ability to connect to the Workspace Environment Management service. You must deploy Citrix Cloud Connector in your user domain before you install the agent. See Install and configure.
Workspace Environment Management administration console: A web-based administration console is provided to manage your WEM installation from the service’s Manage tab using your web browser. This provides the same functionality as the on-prem version of the administration console.
Search index roaming for Microsoft Outlook users: A new option is provided to improve the user experience when searching mail in Microsoft Outlook. See Citrix Profile Management Settings.