Product Documentation

Workspace Environment Management 4.3

May 30, 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

Site management

In previous releases, site settings were stored on the agent side and it was possible to change them from the agent GPO. Workspace Environment Management 4.3 introduces a different approach to site management which improves product security. Sites are now assigned to machines (or Security Groups or OUs) by the infrastructure service (broker) using a new Machines page in the administration console. A new Registrations tab under Administration>Agents in the administration console indicates machines which are bound incorrectly to multiple sites, so that you can take the appropriate action to remove the duplicate binding. A new Registrations tab on the Agents page shows agent registration information.

From this release, Workspace Environment Management "sites" are referred to as "configuration sets" in the user interface and documentation.

Agent localization improvements

The session agent user interface is now localized for the following languages: German, Spanish, French, Italian, Japanese, Korean, Dutch, Russian, Traditional and Simplified Chinese.

User interface improvements

Various text labels and messages in the installation wizards, administration console, and GPO templates have been rationalised and made mutually consistent to improve the user experience. For example, fields used to enter the same parameters in different installation wizards now use the same labels. Current and changed terminology is describe in a new glossary.

Documentation

Workspace Environment Management 4.3 documentation is updated to reflect current product behaviour. Various minor improvements have also been made, including the following improvements designed to assist users:

  • a number of installation field descriptions have been revised to better explain their purpose
  • the documentation uses new standardized terminology visible in the installation wizards, GPO templates, and in the administration console. For example, the term "broker" is replaced by "infrastructure service".
  • a glossary has been added to explain the new terminology seen in the installation wizards, the administration console, and the documentation. Changed terms are also indicated.
  • the technical overview diagram is updated
  • a new port information table has been added to summarize port usage

Fixed issues

The following issues have been fixed since Version 4.3:

  • When the Workspace Environment Management session agent is running in command line mode, User Statistics data is not reported to the WEM infrastructure services.
    [WEM-41]

  • The Workspace Environment Management session agent interface does not render correctly when a computer display is extended to external displays connected via a dock. This problem, which occurs when extending to multiple displays with different screen resolution settings, results in a portion of the right-hand side of the display not rendering completely. This prevents users seeing the home button or being able to change other native Workspace Environment Management settings.
    [WEM-90]

  • The Workspace Environment Management session agent causes the mouse to stop working on virtual machines which have the System Center Configuration Manager (SCCM) client installed with Power Management enabled.
    [WEM-115]

  • When you are using the Transformer feature, the session agent generates an unhandled exception if Wi-Fi is turned off using "ms-settings:network-wifi."
    [WEM-133]

  • The Workspace Environment Management session agent causes the mouse to stop working on virtual machines after an interruption to network access is restored.
    [WEM-159]

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]

Deprecated

The announcements in this section are intended to give you advanced notice of platforms and Workspace Environment Management features which are being phased out so that you can make timely business decisions. Citrix monitors customer use and feedback to determine when they are withdrawn. This list is subject to change in subsequent releases and may not include every deprecated feature or functionality.

The following platforms and Workspace Environment Management features are deprecated. This does not mean that they are removed immediately. Citrix will continue to support them up to and including the next XenApp and XenDesktop Long Term Service Release (LTSR) release.. Deprecated items will be removed in a Current Release following the next LTSR. Alternatives for deprecated items are suggested where possible.
For complete details about product lifecycle support, see Product Lifecycle Support Policy.

Item Announced in Alternative

Support for assigning and binding existing (pre-version 4.3) agents to sites via GPO.

4.3

Upgrade agents to Workspace Environment Management 4.3.

The 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

4.2

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

4.2

Removed

T he following platforms, Citrix products, and features are either removed in Workspace Environment Management 4.3 or are no longer supported in Workspace Environment Management 4.3.

Item Replacement

Support for assigning and binding version 4.3 agents to sites via GPO.

Assign and bind version 4.3 agents to sites via administration console.

Technical overview

Workspace Environment Management (WEM) has the following architecture:

localized image

Infrastructure services. The infrastructure services are installed on a Windows server. They synchronize the various back-end components (SQL Server, Active Directory) with the front-end components (administration console, agent).

Note

Infrastructure services cannot be installed on a domain controller. Kerberos authentication issues prevent the infrastructure service from working in this scenario.

Administration console. The Workspace Environment Management administration console is installed on a Windows client or on a server operating system (OS). It connects to the 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).

Agent. The Workspace Environment Management agent 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 agent cannot be installed on the infrastructure server. The agent installer fails in this scenario.

Note

The Transformer feature is not supported on server operating systems.

SQL Server Database: Workspace Environment Management requires an 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.

 

Port information

Source Destination Type Port Details

Infrastructure service

Agent host

TCP

49752

"Agent port". Listening port on the agent host which receives instructions from the infrastructure service.

Administration console

Infrastructure service

TCP

8284

"Administration port". Port on which the administration console connects to the infrastructure service.

Agent

Infrastructure service

TCP

8286

"Agent service port". Port on which the agent connects to the infrastructure server.

Agent cache synchronization process

Infrastructure service

TCP

8285

"Cache synchronization port". Port on which the agent cache synchronization process connects to the infrastructure service to synchronize the agent cache with the infrastructure server.

Infrastructure service

Citrix License Server

TCP

27000

"Citrix License Server port". The port on which the Citrix License Server is listening and to which the infrastructure service then connects to validate licensing.

Monitoring service

Infrastructure service

TCP

8287

"WEM monitoring port". Listening port on the infrastructure server used by the monitoring service. (Not yet implemented.)