Workspace Environment Management service
- Workspace Environment Management service is available globally, but it currently has only US-based instances. We are working to enable Workspace Environment Management service instances in other regions.
- For information about Workspace Environment Management service customer data storage, retention, and control, see Customer data management.
Workspace Environment Management service uses intelligent resource management and profile management technologies to deliver the best possible performance, desktop logon, and application response times for Citrix Virtual Apps and Desktops deployments. It is a software-only, driver-free solution.
Resource management - To provide the best experience for users, Workspace Environment Management service monitors and analyzes user and application behavior in real time, and then intelligently adjusts RAM, CPU, and I/O in the user workspace environment.
Profile management - To deliver the best possible logon performance, Workspace Environment Management service replaces commonly used Windows Group Policy Object objects, logon scripts, and preferences with an agent which is deployed on each virtual machine or server. The agent is multi-threaded and applies changes to user environments only when required, ensuring that users always have access to their desktop as quickly as possible.
Simplified setup and configuration - Workspace Environment Management service eliminates most of the setup tasks required by the on-premises version of Workspace Environment Management. This can concentrate on using the web-based administration console to tune Workspace Environment Management behavior.
Workspace Environment Management (WEM) service has the following architecture:
The following components are hosted in Citrix Cloud and administered by Citrix as part of the service:
Infrastructure services. The infrastructure services are installed on a multi-session OS. They synchronize various back-end components (SQL Server and Active Directory) with front-end components (administration console and agent). We ensure that sufficient infrastructure services are provided on Citrix Cloud.
Administration console. You use the administration console, available on the service’s Manage tab, to manage your user environments using your web browser. The administration console is hosted on a Citrix Cloud-based Citrix Virtual Apps server, with a Citrix Workspace app for HTML5 connection to the console on the Citrix Virtual Apps server.
Azure SQL Database. Workspace Environment Management service settings are stored in a Microsoft Azure SQL Database service, deployed in an elastic pool. This is managed by Citrix.
The following components are installed and managed in each resource location by the customer/partner:
Agent. The Workspace Environment Management service agent connects to the Workspace Environment Management infrastructure services and enforces settings you configure in the administration console. All communications are over HTTPS using the Citrix Cloud Messaging Service. You can deploy the agent on a Virtual Delivery Agent (VDA). Doing so lets you manage single-session or multi-session environments. You can also deploy the agent on a physical Windows endpoint.
All agents use local caching. This ensures that agents are able to continue using the latest settings if network connection is interrupted.
The Transformer feature is not supported on multi-session operating systems.
Microsoft Active Directory Server. Workspace Environment Management service requires access to your Active Directory to push settings to your users. The infrastructure service communicates with your Active Directory using the Citrix Cloud identity service.
Cloud Connector. The Citrix Cloud Connector is required to allow machines in your resource locations to communicate with Citrix Cloud. You must install Citrix Cloud Connector on at least one machine in every resource location you are using. For continuous availability, install multiple Cloud Connectors in each of your resource locations. We recommend at least two Cloud Connectors in each resource location to ensure high availability. If one Cloud Connector is unavailable for any period of time, the other Cloud Connectors can maintain the connection.
To install the current release, see Install and configure.