Product Documentation

Workspace Environment Management 4.2

Apr 12, 2017

Workspace Environment Management

Workspace Environment Management uses intelligent resource management and Profile Management technologies to deliver the best possible performance, desktop logon, and application response times for XenApp and XenDesktop deployments. It is a software-only, driver-free solution.

Resource management

To provide the best experience for users, Workspace Environment Management monitors and analyzes user and application behavior in real time, 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 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 users always have access to their desktop as soon as possible.

What's new

Profile Management

Workspace Environment Management 4.2 now supports all versions of Profile Management up to v5.6. New options are now provided in the Citrix Profile Management Settings pages in the Administration Console.

Documentation

Workspace Environment Management 4.2 documentation is now provided in HTML format in docs.citrix.com. Articles can be downloaded as PDF as required. Advice on load balancing has been added to the section Install infrastructure services.

Fixed issues

The following issues have been fixed since Version 4.1:

  • File Association actions cannot be processed by the Agent Host on Windows 8, 8.1, Server 2012, Server 2012 R2, and Server 2016 due to registry access issues.

[#WEM-15]

  • The Agent Host waits about 5 minutes before starting if Workspace Environment Management is installed on Windows version 8, 8.1, 10, Server 2012, Server 2012 R2, or Server 2016 (all branches and builds) and a language pack is installed.

[#WEM-17]

Known issues

This release contains the following issues:

  • On Windows Server 2012 R2, if Adobe Acrobat Reader is installed it prevents Workspace Environment Management associating files of type .PDF with other PDF reader applications. Users are forced to manually select the PDF reader application to use each time they open a PDF.

[#WEM-33]

Future removals

The platforms, Citrix products, and features described below will be removed in future. Citrix will continue to support them up to and including the next XenApp and XenDesktop Long Term Service Release (LTSR) release, but they are expected to be removed in a subsequent Current Release. When possible, alternatives are offered for items that are deprecated.

The announcements below are intended to give you advanced notice of features which are being phased out so that you can make timely business decisions. Citrix monitors customer use and feedback about feature removal to determine when they are withdrawn.

Platform support in XenApp and XenDesktop generally ends when the platform's manufacturer ends extended support. See the System requirements article for exceptions.

Announced in Workspace Environment Management 4.2

Citrix Workspace Environment Management Administration Console will not be supported on the following platforms after the next LTSR:

  • Windows XP SP3 32-bit and 64-bit
  • Windows Vista SP1 32-bit and 64-bit
  • Windows 8.x 32-bit and 64-bit
  • Windows Server 2003 32-bit and 64-bit
  • Windows Server 2003 R2 32-bit and 64-bit
  • Windows Server 2008
  • Windows Server 2008 R2

Citrix Workspace Environment Management will not be supported on the following software after the next LTSR:

  • Microsoft .NET Framework 4.0
  • Microsoft .NET Framework 4.5.0
  • Microsoft .NET Framework 4.5.1

Technical overview

Workspace Environment Management has the following architecture:

localized image

Workspace Environment Management Infrastructure Services. The Infrastructure Services broker is installed on a Windows server. It synchronizes the various back-end components (SQL Server, Active Directory) with the front-end components (Administration Console, Agent Host).

Note

Workspace Environment Management Infrastructure Services cannot be installed on a domain controller. Kerberos authentication issues prevent the broker service from working in this scenario.

Workspace Environment Management Administration Console. The Administration Console is installed on a Windows client or on a server operating system (OS). It connects to the Workspace Environment Management Infrastructure Services. You use the Administration Console to manage your Workspace Environment Management installation (to create and assign resources, manage policies, authorize users, and so on).

Workspace Environment Management Agent Host. The Agent Host can either be deployed on VDAs or on physical Windows devices (for Transformer use cases). It can be installed on a Windows client (to manage client environments) or on a Windows Server (to manage server environments, or to manage published desktops and applications). It connects to the Workspace Environment Management Infrastructure Services and is responsible for enforcing the settings you configure by using the Administration Console.

Note

The Workspace Environment Management Agent Host cannot be installed on the Workspace Environment Management Infrastructure Services server. The Agent Host installer fails in this scenario.

Note

The Transformer feature is not supported on server operating systems.

SQL Server Database: Workspace Environment Management requires a SQL Server database to store its settings. The Workspace Environment Management database requires a minimum of 50 MB of disk space.

Microsoft Active Directory Server: Workspace Environment Management requires access to your Active Directory to push settings to your users.