Citrix Workspace Environment Management 1811 User manual

Workspace Environment

Management 1811

Citrix Product Documentation | docs.citrix.com April 1, 2019

Workspace Environment Management 1811

Contents

Workspace Environment Management 1811 3

What’s new 5

Fixed issues 14

Known issues 19

Third party notices 20

Deprecation 20

Quick start guide 23

System requirements 73

Install and configure 78

Infrastructure services 78

Administration console 91

Agent 94

Upgrade a deployment 97

User experience 101

Ribbon 102

Applications 104

Printers 107

Network drives 108

Virtual Drives 109

Registry Entries 110

Ports 112

Ini Files 113

External Tasks 114

Workspace Environment Management 1811

File System Operations 116

User DSN 117

File Associations 118

Filters 119

Assignments 121

System Optimization 123

CPU Management 124

Memory Management 128

I/O Management 129

Fast Logo 130

Policies and Profiles 130

Environmental Settings 131

Microso USV Settings 133

Citrix Profile Management Settings 134

VMware Persona settings 139

Security 141

Active Directory Objects 147

Transformer settings 149

Advanced settings 153

Administration 160

Monitoring 166

Port information 167

Dynamic tokens 169

Common Control Panel applets 172

Workspace Environment Management 1811

Log parser 174

XML printer list configuration 175

Filter conditions 180

Environmental Settings registry values 197

WEM Integrity Condition List Manager 219

Glossary 235

Workspace Environment Management 1811

January 10, 2019

Workspace Environment Management 1811 is the current release. For documentation about earlier

releases and about the Citrix Cloud Workspace Environment Management service, see the following

sections:

•Workspace Environment Management 1808

•Workspace Environment Management 4.7

•Workspace Environment Management 4.6

•Workspace Environment Management 4.5

•Workspace Environment Management 4.4

•Earlier Workspace Environment Management versions

•Workspace Environment Management service

For information about upgrading, see Upgrade a deployment.

To install the current release, see Install and configure.

Note:

Workspace Environment Management is covered by the Current Releases (CR) lifecycle of Citrix

Virtual Apps and Desktops. For more information, see Product Matrix.

Introducing Workspace Environment Management

Workspace Environment Management uses intelligent resource management and profile man-

agement technologies to deliver the best possible performance, desktop logon, and application

response times for Citrix Virtual Apps and Desktops deployments. It is a soware-only, driver-free

solution.

Resource management - To provide the best experience for users, Workspace Environment Manage-

ment 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 Man-

agement replaces commonly used Windows Group Policy Object objects, logon scripts, and prefer-

ences 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.

Workspace Environment Management 1811

Technical overview

Workspace Environment Management (WEM) has the following architecture:

Infrastructure services. The infrastructure services are installed on a Windows server. They synchro-

nize 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 is-

sues 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 connects to the Workspace Environment

Management infrastructure services and is responsible for enforcing the settings you configure by

using the administration console. The 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 environ-

ments) or on a Windows Server (to manage server environments, or to manage published desktops

and applications).

Note:

• The agent cannot be installed on the infrastructure server. The agent installer fails in this

scenario.

Workspace Environment Management 1811

• 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 database can be hosted in an SQL Server Always On availability group if re-

quired. (For more information, see System requirements.)

Microso Active Directory Server: Workspace Environment Management requires access to your

Active Directory to push settings to your users.

What’s new

January 8, 2019

For information about upgrading, see Upgrade a deployment.

What’s new in Workspace Environment Management 1811

Workspace Environment Management 1811 includes the following new features. For information

about bug fixes, see Fixed issues.

Administration console

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.

Documentation

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

What’s new in previous releases

What’s new in Workspace Environment Management 1808

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 dierent names for a

product or component.

Workspace Environment Management 1811

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 oers 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 technol-

ogy 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 Provi-

sioning 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 for-

mer 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.

Workspace Environment Management 1811

•YYMM = Year and month when the features arefinalized. 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 num-

bers were displayed in the format: 4.version, where the version value incremented by one for each re-

lease. 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 Microso Outlook users (option for improving the user ex-

perience when searching mail in Microso 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.

What’s new in Workspace Environment Management 4.7

New-wemDatabase PowerShell cmdlet updated

Workspace Environment Management 1811

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. Aer 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 Re-

ceiver pass-through authentication to be used. Only published applications which users have permis-

sion 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 con-

figure users for Transformer integrated with Receiver for Windows SDK, you must clear the option

Enable Autologon Mode (in the “Transformer Settings > Advanced > Logon/Logo & Power set-

tings” tab). This allows users tolog 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.

Workspace Environment Management 1811

Active Directory performance

The Active Directory Subsystem has been redesigned to improve performance and stability. Perfor-

mance 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 file-

names 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 En-

vironment Management. This functionality is similar to Windows AppLocker but gives you the addi-

tional 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 1811

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 require-

ments.

Process optimization

History now user-centric. Workspace Environment Management (WEM) intelligent optimization re-

lies on WEM “remembering” how many times a process infringes rules configured in the administra-

tion 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 (Lo-

calAgentDatabase) located in the agent installation folder.

Workspace Environment Management 1811

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 opti-

mization 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 Documen-

tation.

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 aer a set

time, which reduces the size of the database. It also reduces lag in populating the Registrations tab in

the administration console.

Workspace Environment Management 1811

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” documenta-

tion set describing the “current release.” This approach reduces duplication in the online documenta-

tion 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 pre-

viously 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 dierent 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.

Workspace Environment Management 1811

User interface improvements

Various text labels and messages in the installation wizards, administration console, and GPO tem-

plates have been rationalized and made mutually consistent to improve the user experience. For ex-

ample, fields used to enter the same parameters in dierent 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 be-

havior. 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 con-

figure your physical machines to operate a locked-down thin client version of Windows.

Workspace Environment Management 1811

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.

Fixed issues

January 22, 2019

Fixed in Workspace Environment Management 1811

The following issues have been fixed in the current release:

• On 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]

• Attempts to upgrade the WEM database using the command line might fail. [WEM-1410]

• Aer you apply a percentage of the CPU’s processing power for a process on the System Opti-

mization >CPU Management >CPU Clamping tab of the administration console for the first

time and configure a dierent percentage for the same process later, the change does not take

eect. [WEM-1993, LD0110]

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

• When a forest (current or trusted) contains a large number of OUs (for example, 10,000), if you

click Add OU from the administration console, you might find some OUs to be missing from the

Organizational Units window. This issue occurs because the search task times out before the

search completes. [WEM-2378, LD0428]

Workspace Environment Management 1811

• The Workspace Environment Management node has been moved from Computer Configu-

ration >Policies >Administrative Templates >Citrix to Computer Configuration >Policies

>Administrative Templates >Citrix Components. [WEM-2582]

Fixed in previous releases

Fixed in Workspace Environment Management 1808

• 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 Microso 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]

• Application Security features are not available if the Workspace Environment Management ad-

ministration console is installed on Windows 7 SP1 or Windows Server 2008 R2 SP1 (or earlier

versions). In the Security tab, none of the Application Security options can be selected. [WEM-

1216, LC9023]

• When the number of connected agents exceeds a certain threshold (for example, 5,000), if you

frequently specify users, computers, groups, and organizational units, you might find that the

Norskale Broker Service.exe consumes more than 2GB of RAM several days later. The issue oc-

curs because some Microso LDAP APIs used by Norskale Broker Service.exe are unable to re-

lease the consumed RAM automatically. [WEM-1494, LC9623]

• When a forest (current or trusted) contains more than 1,000 OUs, if you click Add OU from the

administration console, you might find some OUs to be missing from the Organizational Units

window. The issues occurs because LDAP API FindAll() returns no more than 1,000 results

by default. [WEM-1986, LD0121]

• Aer you upgrade the WEM agent to Version 4.7, if you select Enable Intelligent CPU Optimiza-

tion and/or Enable Intelligent I/O Optimization on the System Optimization > CPU Manage-

ment > CPU Management Settings tab of the administration console, error messages about

Error 87 frequently appear in Windows Event logs. This issue does not aect the user experi-

ence, thus you can dismiss these error messages. [WEM-2051]

Fixed in Workspace Environment Management 4.7

• You can use the Citrix Workspace Environment Management Infrastructure Services Setup.exe

to install the Citrix Workspace Environment Management SDK without installing the infrastruc-

ture service (by selecting “Custom” installation type and deselecting “Default feature”). How-

ever, if you leave the option “Start the Database Management Utility” selected then click “Fin-

Workspace Environment Management 1811

ish,” an error message about Error 2753 is displayed. You can click OK to dismiss this error dialog,

which is benign. [WEM-541]

• When you are configuring the Workspace Environment Management database, if you use incor-

rect settings the system may become unresponsive for up to six minutes. The system then dis-

plays an error message reporting “A network-related or instance-specific error occurred while

establishing a connection to SQL Server. Examples of incorrect settings include incorrect SQL

user name and password or invalid database instance. This happens because Workspace Envi-

ronment Management makes multiple database connection retries with the incorrect settings.

[WEM-790]

• In the administration console Active Directory Objects section Machines tab, when you click Add

OU, the Organization Units dialog does not list all the items it should. There are two scenarios

to be aware of:

–When the infrastructure server and administration console are not installed on the parent

domain (for example, they are installed on the tree-domain or on a sub-domain), none of

the Active Directory structure or OUs (forests, domains, sub-domains, and so on) outside

the current forest are shown.

–When the infrastructure server and administration console are installed on the parent do-

main, only the parent domain OU is shown. The OUs of sub-domains and tree-domains in

dierent forests are not shown.

To add machines which are in a dierent forest, in the Machines tab, click Add Object and select

the other forest. [WEM-1069]

• When end-users access applications via Workspace Environment Management, the CPU usage

of NorSkale Agent Host service.exe increases to 20% and remains there for 5 to 60 seconds, thus

aecting the user experience. [WEM-1094, LC9230]

• WEM agents are randomly reported with the following dierent status under Administration

> Agents > Registrations: “Agent <AgentHostName> is bound to multiple configuration sets.”

“Agent <AgentHostName> is not be bound to any Configuration Set.” This issue occurs only

when using OUs as AD objects in Configuration Sets. It prevents agents registering successfully

with infrastructure servers. [WEM-1302, LC9524]

• The Workspace Environment Management administration console Administration > Agents

tab reports the Netscaler Subnet IP address instead of the agent IP address. This prevents the

agent cache being refreshed because the Agents tab times out. [WEM-1406, LC9645]

• When users log on, the Workspace Environment Management session agent reports “processing

applications…”, but this never completes. This occurs only when customer assigns multiple

applications to the agent and enables multi-functions. [WEM-1740, LC8601]

• Attempting to add an application of type URL in the Workspace Environment Manage-

ment administration console fails. The event and broker logs show “AdminBrokerSer-

Workspace Environment Management 1811

vice.CreateVuemApp():Cannot insert the value NULL into column ‘WorkingDirectory’, table

‘CitrixWEM.dbo.VUEMApps’; column does not allow nulls. INSERT fails.” [WEM-1741, LC9551]

Fixed in Workspace Environment Management 4.6

• When you uninstall the Workspace Environment Management agent, the uninstall process does

not delete the Windows Firewall inbound rule “Norskale agent in”. Manually delete this rule in

the Windows Firewall with Advanced Security dialog. [WEM-312]

• When the option “Launch Agent at Reconnect” is selected, the Workspace Environment Man-

agement agent executable does not run when reconnecting with published desktops on agent

hosts which are running Windows desktop operating systems, via ICA. (RDP sessions are unaf-

fected.) [WEM-322, LC8816]

• If you attempt to add an agent host machine to a configuration set when the agent host ma-

chine is in a dierent forest to the infrastructure service, it can take several minutes before the

agent host is added, depending on the actual AD topology involved. During this time, the ad-

ministration console displays the message “Please Wait loading…” and further activities are not

possible. [WEM-358]

• Attempts to create or update a WEM database, on an SQL Server instance which uses case-

sensitive collation, fails. Ensure that the SQL Server instance uses *case-insensitive *collation

before attempting to create or update a WEM database. [WEM-540]

• The Workspace Environment Management agent randomly crashes aer VDAs are upgraded to

XenApp and XenDesktop 7.16. [WEM-937, LC8926]

• In the Workspace Environment Management administration console Citrix Profile Management

Settings, the Synchronization tab option “Enable File Mirroring” does not match the Citrix Stu-

dio Profile Management policy setting it is derived from. The option should read “Enable File

Synchronization” and allow files to be added. [WEM-971, LC9090]

• When you are adding an Application Security executable rule of type “Publisher”, dragging the

Publisher info slider to “File name” or above causes an exception in the Workspace Environment

Management administration console. [WEM-1199, LC9255]

• On laptop machines in transformer mode, the Transformer battery icon does not stay synchro-

nized with the battery percent reported by the OS. When the power cable is connected or discon-

nected, the transformer battery icon is refreshed with the correct percentage value, but it then

continues to show the same fixed value until the next power cable change is detected. [LC9261]

• The WEM agent installs VUEMRSAV.exe (Workspace Environment Management Resultant

Actions Viewer), a utility which allows users to view the WEM configuration defined for them

by the administrator. If an administrator assigns an action directly to a specific user, when

that user runs VUEMRSAV.exe, the assigned action is missing in the Applied Actions tab. If

an administrator assigns an action to a User Group to which the user belongs (for example,

‘Domain Users’), when that user runs VUEMRSAV.exe, the assigned action is visible in the

Workspace Environment Management 1811

Applied Actions tab, which is the correct behavior. [WEM-1200]

Fixed in Workspace Environment Management 4.5

• When you examine the properties of rules in the Microso Security Policy Editor (secpol.msc),

script rules set to “Audit” mode in the Workspace Environment Management Security tab are

incorrectly shown as not configured. (PowerShell can be used to confirm that these rules are

actually in audit mode.) [WEM-352]

• In the WEM Infrastructure Server Configuration wizard Advanced tab, if you select the option

Use cache even if online, it is not saved when you close the wizard. A workaround is to set the

registry key BrokerUseCacheEvenIfOnline = 1 in HKLM\System\CurrentControlSet\Control\Norskale\Infrastructure

Services. [WEM-396]

• While in the Security Tab and switching between Configuration Sets, the side panel may incor-

rectly display its state, either enabled/disabled. Switching to another tab and back resolves this

issue. [WEM-405]

• When you select multiple rules and click Edit, any changes to rule assignments you make are

applied to all users and user groups you select. In other words, both new and existing rule as-

signments are merged across those rules. If you do not change rule assignments, existing rule

assignments are unchanged. To fine-tune rule assignments, select one rule at a time and click

Edit. [WEM-420]

• When you select multiple rules and then use Edit, the Permissions option defaults to “Allow,”

even if some or all the selected rules are set to deny. In the rule list, permissions are correctly

reported in the Action column. [WEM-421]

Fixed in Workspace Environment Management 4.4

• If you run the Workspace Environment Management administration console as a standard Win-

dows user, and you attempt to start the Modeling Wizard, the wizard does not start. [WEM-187]

• When you attempt to add a user group, which is in a dierent AD domain to the infrastructure

server, as a processed group in the Citrix User Profile Management tab in the administration

console, the exception *IndexOutOfRangeException is raised, and the group is not processed.

[WEM-210]

• Links in “This PC” in Windows 10 do not reflect folder redirection, and still point to local folders.

[WEM-234]

• The Agent Host waits about 5 minutes before starting if Workspace Environment Management

is installed on Windows version 8, or Server 2012, and a language pack is installed. [WEM-244]

• If you launch or refresh a UI session agent when it is not bound to a configuration set, keyboard

and mouse locks which are active during the agent refresh are not released. [WEM-321]

Page is loading ...

Citrix Workspace Environment Management 1811 User manual

Citrix Workspace Environment Management 1811 User manual

Related papers

Other documents