Product Documentation

What’s new

For information about upgrading, see Upgrade a deployment

What’s new in Workspace Environment Management 1808

Workspace Environment Management 1808 includes the following new features. For information about bug fixes, see Fixed issues.

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:

Is Was
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 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 1808.

In earlier releases of this product (Workspace Environment Management 4.7 and earlier), version numbers were displayed in the format: 4.version, where the version value incremented by one for each release. For example, the release following 4.6 was 4.7. Those earlier releases will not be updated with the new numbering format.

Administration console

In this release, 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.

Profile management

As of this release, Workspace Environment Management supports configuring all settings for Citrix Profile Management 1808. The following new options are now available in the administration console:

  • 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)

Documentation

Workspace Environment Management documentation is updated to reflect current product behavior.

The Workspace Environment Management SDK documentation is updated to version 1808.

What’s new in previous releases

What’s new in Workspace Environment Management 4.7

New-wemDatabase PowerShell cmdlet updated

PowerShell modules in the Workspace Environment Management SDK are updated at this release. A new parameter CommandTimeout is provided for the New-wemDatabase cmdlet which allows you to configure timeout period for connection attempts to the WEM database. After the timeout period an error message is displayed. The default timeout is 300 seconds.

Documentation

Workspace Environment Management documentation is updated to reflect current product behavior.

The Workspace Environment Management SDK documentation is updated to version 4.7.

What’s new in Workspace Environment Management 4.6

Assigned applications can include StoreFront store apps

You can now assign resources published in Citrix StoreFront stores as application shortcuts in Workspace Environment Management. This allows you to configure Start menu shortcuts which Workspace Environment Management end users can use to easily access remote store resources. Agent host machines configured to use the Transformer feature show shortcuts to Citrix StoreFront store resources inside the Applications tab. Configure the StoreFront stores that Citrix Receiver connects to using a new Advanced Settings tab. Then add store resources as applications in the Add Application dialog, which contains a redesigned General settings tab. For more information see Applications.

Transformer integrated with Receiver for Windows SDK

Transformer is now integrated with the Citrix Receiver for Windows SDK. This allows you to make StoreFront-based assigned application actions available to Transformer kiosk users, and for Citrix Receiver pass-through authentication to be used. Only published applications which users have permission to access are displayed in the Transformer kiosk Applications tab.

Note:

If you have previously configured Transformer for Enable Autologon Mode and now wish to configure users for Transformer integrated with Receiver for Windows SDK, you must clear the option Enable Autologon Mode (in the “Transformer Settings > Advanced > Logon/Logoff & Power settings” tab). This allows users to log in to the Transformer client endpoint machine using their own credentials. These credentials are passed through to provide access to their assigned StoreFront-based applications.

Active Directory performance

The Active Directory Subsystem has been redesigned to improve performance and stability. Performance improvements are particularly noticeable when you add AD or OU objects, and dead forests or domains are detected in your environment.

User interface

The administration console user interface has changed:

  • In Advanced Settings > Configuration pane, there is a new StoreFront tab for configuring the StoreFront stores that Citrix Receiver connects to.
  • In Actions > Applications, the Add Application dialog General Settings tab is redesigned for adding StoreFront store resources as applications. The Advanced Settings tab Application Type option is removed.
  • In Active Directory Objects, there is a new Advanced pane. The AD Settings tab contains a new option Active Directory search timeout for configuring how long Active Directory searches are performed before they time out. The default value is 1000 msec. We recommend that you use a timeout value of at least 500 msec to avoid timeouts before searches complete.

Agent administrative templates

The administrative templates provided to configure the agent have been renamed to make the filenames versionless. For more information see Configure the agent.

Documentation

Workspace Environment Management documentation is updated to reflect current product behavior.

What’s new in Workspace Environment Management 4.5

Application security

Application Security functionality has been added to the administration console Security pane. This allows you to control the applications users are permitted to run by defining rules in Workspace Environment Management. This functionality is similar to Windows AppLocker but gives you the additional ability to:

  • define rules without immediately assigning them
  • bulk-assign rules to users
  • import rules from Windows AppLocker

For more information, see Security.

Workspace Environment Management SDK PowerShell Modules

PowerShell modules are released as the first part of a Workspace Environment Management SDK. The modules are installed by the infrastructure services installation process. You can perform the following administrative tasks by running the cmdlets in the modules directly from the PowerShell console, or from PowerShell scripts:

  • create a Workspace Environment Management database
  • update a Workspace Environment Management database
  • get the configuration from a local or remote infrastructure server
  • set the configuration of a local or remote infrastructure server

For more information, see the Citrix Developer Documentation.

Support for SQL Server Always On availability groups

Workspace Environment Management has been tested with SQL Server Always On availability groups, and is now certified for use on that technology. For more information and advice, see System requirements.

Process optimization

History now user-centric. Workspace Environment Management (WEM) intelligent optimization relies on WEM “remembering” how many times a process infringes rules configured in the administration console. Based on this “memory,” WEM optimizes (or not) the process when it is next started.

In previous releases, this “memory” was based only on process name. In other words, if a process infringed a rule when it was running as User A, it was also considered to be infringing for all users connecting to the agent, and the process was optimized globally for all users.

Starting in this release, the intelligent optimization “memory” is based on both process name and user details. This means that intelligent optimization is now user-centric. In other words, if a process infringes a rule when it was running as User A, but does not infringe a rule when it was running as User B, the process is optimized only when running as User A.

History now in local database. Workspace Environment Management (WEM) has two local databases: one contains the agent local cache, and another stores local data. Historically, WEM’s intelligent optimization memory was stored either in the agent registry or in an XML file. An XML file was used if the custom argument UseNonPersistentCompliantHistory was set during agent installation.

From this release, WEM’s intelligent optimization memory is stored in the agent local database (LocalAgentDatabase) located in the agent installation folder.

AgentServiceUseNonPersistentCompliantHistory custom argument for agent installation

The Citrix Workspace Environment Management Agent Setup executable no longer acknowledges the AgentServiceUseNonPersistentCompliantHistory custom argument. This custom argument previously allowed you to save agent service process optimization history to an XML file. The optimization history is now stored in the agent local database (LocalAgentDatabase) located in the agent installation folder.

User interface

The following changes are made to the administration console user interface:

  • A new Application Security pane is added to the Security tab.

Documentation

Workspace Environment Management documentation is updated to reflect current product behavior.

Workspace Environment Management SDK documentation is added to the Citrix Developer Documentation.

What’s new in Workspace Environment Management 4.4

Data analytics

From this release, the Workspace Environment Management infrastructure service sends anonymous usage data to Google Analytics. For more information, and for opt-out instructions, see Infrastructure services.

Profile Management

From this release, Workspace Environment Management supports Citrix Profile Management 7.15. The following new options are now available in the administration console:

  • Enable Logon Exclusion Check (option for controlling file system exclusions)
  • Enable Profile Streaming Exclusion List - Directories (option for controlling user profile streaming)

Database maintenance

In the Infrastructure Services Configuration utility, the Database Maintenance tab has a new option Agent registrations retention period. This allows agent registration logs to be deleted after a set time, which reduces the size of the database. It also reduces lag in populating the Registrations tab in the administration console.

User interface

The following changes are made to the administration console user interface:

  • A new Security tab is introduced to contain settings controlling end-user activity.
  • The Process Management controls have been moved to the new Security tab.

Documentation

At this release, Workspace Environment Management documentation is updated to reflect current product behavior. The documentation has also been remodeled as a single “versionless” documentation set describing the “current release.” This approach reduces duplication in the online documentation set, gives more focused search results, and is better suited to agile release processes. Associated changes include:

  • A top level “current release” article contains links to previous documentation sets in PDF format only. (HTML documentation for previous releases is no longer provided.)
  • “What’s new” summarizes the new functionality at the current release, and in previous releases.
  • A new “Reference” section gathers reference information in one location. Port information previously in the introductory article is relocated to “Reference.”

What’s new in Workspace Environment Management 4.3

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.

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 rationalized 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 described in a new glossary.

Documentation

Workspace Environment Management 4.3 documentation is updated to reflect current product behavior. 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.

What’s new in Workspace Environment Management 4.2

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.

What’s new in Workspace Environment Management 4.1

Transformer module re-enabled

The Transformer module is available in the Administration Console. Transformer allows you to configure your physical machines to operate a locked-down thin client version of Windows.

Agent Host enhancements

Improvements to the Agent Host remove the communication between the WEM Broker Service and Agent Host executable. All communication now occurs between the WEM Broker Service and Agent Host Service, which then passes its instructions down to the Agent Host executable. This includes local cache access.

Documentation on docs.citrix.com

Workspace Environment Management 4.1 documentation is now available from docs.citrix.com. These PDFs are no longer included in the download. Filter conditions are now documented in the Administration Guide.