WEM 1909 UPDATE AVAILABLE

Intro

With every changing season, Citrix releases another version of WEM. This version is 1909. You can download the new version here (requires Platinum licenses and login to Citrix.com). I’ve provided the release notes below.

What’s new in Workspace Environment Management 1909

Workspace Environment Management agent installer

This release provides a new, unified Workspace Environment Management (WEM) agent installer. The installer bundles the WEM on-premises and service agents into a single executable. It eliminates the need to configure the ADMX templates and to edit group policies. You can choose to install the agent interactively or use the command line. For more information, see Agent.

The new WEM agent installer also introduces name and installation path changes. The changes include:

ISWasWhat
Citrix WEM Agent Host ServiceNorskale Agent Host Service Display name of the WEM agent service (WemAgentSvc) that appears in Windows Services.
WEM Agent Service Norskale Agent ServiceLog name that appears in the Windows Event Log.
Citrix.Wem.Agent.Service.exeNorskale Agent Host Service.exeFile name that appears in the agent installation folder.
%ProgramFiles%\Citrix\Workspace Environment Management Agent%ProgramFiles%\Norskale\Norskale Agent HostDefault agent installation path. This change applies only to the default installation path when you perform fresh installation. In case of in-place upgrades, the installation path remains unchanged.

Agent switch

This release introduces the agent switch functionality that lets you switch from the on-premises agent to the service agent. The functionality can be useful in migration use cases where you want to migrate your existing on-premises deployment to the WEM service. It simplifies and expedites the migration process. For more information, see Agent switch.

Infrastructure service

This release includes the following enhancements to the infrastructure service to improve the user experience:

  • The Active Directory (AD) subsystem has been redesigned to improve performance. It can now dynamically blacklist detected dead forests. Dead forests remain in the blacklist unless they are no longer dead two hours later. The infrastructure service does not search for AD objects in forests that are in the blacklist. As a result, some OUs in the blacklisted forests might be missing in the Organizational Units window when you click Add OU from the administration console.
  • The infrastructure service can now cache data related to the configuration set for the agents. As a result, the infrastructure service retrieves data from AD less frequently. This also reduces the time it takes for the agents to retrieve the information from the infrastructure service. Time reduction is particularly noticeable when there are many connected agents.

Infrastructure service configuration

This release introduces the “Enable performance tuning” option on the Advanced Settings tab of the WEM Infrastructure Service Configuration utility. You can now optimize the performance in scenarios where the number of connected agents exceeds a certain threshold (by default, 200). As a result, it takes shorter time for the agent or the administration console to connect to the infrastructure service. This feature is especially useful when the agent or the administration console intermittently disconnects from the infrastructure service. In this scenario, you can set the minimum number of worker threads and asynchronous I/O threads to a greater value. For more information, see Configure the infrastructure service.

Profile Management

Workspace Environment Management now supports all versions of Profile Management through 1909. The following new options are now available on the tabs in the Administration Console > Policies and Profiles > Citrix Profile Management Settings pane:

  • Migrate user store. Available on the Main Citrix Profile Management Settings tab, this option lets you migrate your user store without losing any data.
  • Automatic migration of existing application profiles. Available on the Profile Handling tab, this option lets you automatically migrate existing application profiles.
  • Outlook search index database – backup and restore. Available on the Advanced Settings tab, this option ensures the stability of the Enable search index roaming for Outlook feature.

For more information, see Citrix Profile Management Settings.

Administration console

The user interface of the administration console has changed:

  • An Agent Switch tab is provided in the Advanced Settings > Configuration pane. The tab lets you switch from the on-premises agent to the service agent. For more information, see Agent switch.
  • An “Auto Prevent CPU Spikes” option is provided on the System Optimization > CPU Management > CPU Management Settings tab. You can use this option to automatically reduce the CPU priority of processes that overload your CPU. For more information, see CPU Management.

Support for migrating Group Policy Objects (GPOs)

Starting with this release, you can migrate a zip backup of your GPOs to Workspace Environment Management (WEM) service. To do so, click Migrate in the ribbon of the WEM administration console. The Migrate wizard provides the flexibility to migrate your GPOs. You can select Overwrite mode or Convert mode for your migration. The Overwrite mode overwrites existing WEM settings (GPOs) when there are conflicts. The Convert mode converts your GPOs to XML files. Then you can manually import the XML files to WEM using the Restore wizard. Doing so gives you granular control over settings to be imported. For more information, see Ribbon.

Support for exporting and importing Active Directory (AD) objects

As of this release, Workspace Environment Management service adds support for exporting and importing AD objects using the administration console. To export AD objects, use the Backup wizard, where the Active Directory (AD) objects option is provided on the Select what to back up page. To import AD objects, use the Restore wizard, where the Active Directory (AD) objects option is provided on the Select what to restore page. You can specify which type of AD objects to back up and restore. For more information, see Ribbon.

Fixed Issues

  • Attempts to connect to the WEM administration console might take a long time to complete. The issue occurs when domains to which Active Directory objects (for example, groups and OUs) belong are no longer available. [WEM-3103, LD0725]
  • When you enable the process launcher on the Administration Console > Transformer Settings > Advanced > Process Launcher tab to launch a Windows built-in application (for example, calc.exe) as entered in the process command line field, the agent host might keep opening the application after you refresh Citrix WEM Agent. [WEM-3262]
  • You might experience the following two issues:
    • Attempts to connect to the WEM administration console might take a few minutes to complete.
    • It takes a long time to load WEM configurations on agent hosts. The issue occurs when you have a large Active Directory deployment and there are many connected agents. [WEM-4225]
  • Attempts to map a network drive to users might fail if the assigned drive letter is already in use by an existing network drive. The issue occurs when the existing network drive failed to connect as indicated by a red “X” on the network drive icon. [WEM-4495, LD1552]
  • The agent splash screen can persist for a long time when there is a large amount of data associated with user statistics. [WEM-4674, LD1167]
  • The Workspace Environment Management administration console might unexpectedly exit if you edit the application security rules. The issue occurs when there is a long list of users and user groups present in the Edit Rule window and you scroll down to view them. [WEM-4960, LD1818]
  • You might find that there are two Citrix Components nodes in the left pane of the Group Policy Management Console. [WEM-5012]
  • When you log on to a Workspace Environment Management agent machine, the logon process might take longer to complete. The issue occurs because the Workspace Environment Management agent logon service (Citrix.Wem.Agent.LogonService.exe) delays the logon process for several seconds even though the Endpoint Management group policy processing is disabled. [WEM-5237]

Known Issues

Workspace Environment Management contains the following issues:

  • When you use a configuration object with Workspace Environment Management PowerShell modules SDK cmdlets, all parameters must be specified. If they are not, the command fails with an InvalidOperation error. [WEM-691, WEM-693]
  • In PowerShell, when you use the help command with the -ShowWindow switch to display help in a floating window for a Workspace Environment Management PowerShell cmdlet, the Examples section of the help is unpopulated. To see the examples, use the get-help command with the -examples-detailed, or -full switch instead. [WEM-694]
  • In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off. [WEM-3133]
  • Registry entries might not take effect if you assign them to a user or user group through an action group. However, they do take effect if you assign them directly. The issue occurs when you assign registry entries to be created in one of the following locations:
    • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Policies
    • %ComputerName%\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies [WEM-5253]

Depreciated Features

Click here to see depreciated features.

Thanks for reading,
Alain

Advertisements

WEM 1906 UPDATE AVAILABLE

Intro

Summer is just around the corner and Citrix has released another version of WEM. This version is 1906. You can download the new version here (requires Platinum licenses and login to Citrix.com). I’ve provided the release notes below.

What’s new in Workspace Environment Management 1906

Action Groups

Action Groups functionality has been added to the administration console Actions pane. This functionality lets you configure a group of actions that you want to assign to a user or user group. For more information, see Action Groups.

Administration console

The administration console user interface has changed:

  • In Actions, there is a new Action Groups pane. In the Actions > Action Groups pane, there is a new Action Group List tab for configuring a group of actions that you want to assign to a user or user group.
  • An “Enable Notifications” option is provided on the Advanced Settings > Configuration > Agent Options tab. You can use this option to control whether the agent displays notification messages on the agent host when the connection to the infrastructure service is lost or restored.

Upgrade enhancement

This release includes the following enhancements to improve the user experience with the upgrade of Workspace Environment Management:

  • After upgrading the infrastructure service, the fields on all the tabs of WEM Infrastructure Service Configuration are automatically populated with the data you previously configured. As a result, you no longer need to type the required information manually after you upgrade the infrastructure service.
  • After upgrading the database, the fields in the Database Upgrade Wizard window are automatically populated with the data you previously configured. As a result, you no longer need to type the required information manually after you upgrade the database.

Profile management

Workspace Environment Management now supports all versions of Profile Management through 1903. The following new option is now available on the Administration Console > Policies and Profiles > Citrix Profile Management Settings > Synchronization tab:

  • Enable Profile Container (option for eliminating the need to save a copy of the folders to the local profile)

VMware Persona settings deprecation

Support for VMware Persona settings has been deprecated. All VMware Persona settings content will be removed from the documentation in the next release. For more information, see Deprecation.

Documentation

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

Fixed Issues

Fixed in Workspace Environment Management 1906

  • Attempts to create a WEM database using the WEM Database Management Utility might fail. The issue occurs when the synchronization context creation for the WEM database times out. [WEM-3020, LD0675]
  • When you click Apply Filter or Refresh Report on the Administration Console > Monitoring > User Trends > Devices Types tab, you might not be able to view the report. Instead, you are returned to the Administration Console > Actions > Applications > Application List tab. [WEM-3254]
  • On Windows 10 version 1809 and Windows Server 2019, Workspace Environment Management fails to pin the applications to the task bar. [WEM-3257]
  • After WEM upgrades to the latest version, if you still use earlier versions of the agent, the agent fails to work properly in offline mode. This issue occurs because of the scope changes of the agent local cache file in the latest release. As a workaround, delete the old agent local cache file, and then restart the WEM Agent Host Service (Norskale Agent Host service). [WEM-3281]
  • On the Security tab of the administration console, if you create an AppLocker rule for a file with an .exe or a .dll extension using a file hash condition, the rule does not work. This issue occurs because WEM calculates the hash code of that file incorrectly. [WEM-3580]
  • On the Security tab of the administration console, if you create an AppLocker rule for a file with an .exe extension using a file path condition, the rule does not work. This issue occurs because WEM converts the path for that file incorrectly. For example, suppose you browse to the .exe file in C:\ProgramData folder. Instead of converting the file path to %OSDRIVE%\ProgramData<filename>, WEM converts it to %SYSTEMDRIVE%\ProgramData<filename>. [WEM-3581]
  • On the Security tab of the administration console, if you create an AppLocker rule for a file using a publisher condition, the rule does not work. This issue occurs because WEM resolves the file name incorrectly. [WEM-3582]
  • On the Security tab of the administration console, if you attempt to create an AppLocker rule for a file with a .bat extension, WEM fails to display the .bat file in the Open window after you browse to the folder where the .bat file is located. [WEM-3585]
  • The Enable AutoEndTasks option on the Policies and Profiles > Environmental Settings > SBC / HVD Tuning tab of the administration console does not work. [WEM-3749, LD0876]
  • The Application Security feature does not work on Windows servers that use non-English Windows operating systems. This issue occurs because WEM fails to start the Application Identity service in non-English language environments. [WEM-3957, LD1185]
  • Workspace Environment Management fails to convert a UNC path to a local path. The issue occurs when you use the Administration Console > Actions > Applications > Application List tab to associate an icon located on the network with an application. [WEM-3977]
  • The Windows theme of the agent host might revert to the default if you use GPO to customize your Windows theme. The issue occurs when you enable the WEM agent to process environmental settings without selecting Set Specific Theme File and Set Background Color on the Policies and Profiles > Environmental Settings > Start Menu tab of the administration console. As a result, the WEM agent deletes the registry settings associated with the Windows theme. [WEM-4044, LD1246]
  • The Windows desktop background of the agent host might revert to the default if you use GPO to customize your Windows desktop background. The issue occurs when you enable the WEM agent to process environmental settings without selecting Set Specific Theme File and Set Background Color on the Policies and Profiles > Environmental Settings > Start Menu tab of the administration console. As a result, the WEM agent deletes the registry settings associated with the Windows desktop background. [WEM-4217, LD1408]

Known Issues

Workspace Environment Management contains the following issues:

  • On Windows Server 2012 R2, if Adobe Acrobat Reader is installed, it prevents Workspace Environment Management from associating PDF files with other PDF reader applications. Users are forced to select the PDF reader application each time they open a PDF. [WEM-33]
  • When you use a configuration object with Workspace Environment Management PowerShell modules SDK cmdlets, all parameters must be specified. If they are not, the command fails with an InvalidOperation error. [WEM-691, WEM-693]
  • In PowerShell, when you use the help command with the -ShowWindow switch to display help in a floating window for a Workspace Environment Management PowerShell cmdlet, the Examples section of the help is unpopulated. To see the examples, use the get-helpcommand with the -examples-detailed, or -full switch instead. [WEM-694]
  • In Transformer (kiosk) mode, and with Log Off Screen Redirection enabled, WEM might fail to redirect the user to the logon page after logging off. [WEM-3133]
  • When you enable the process launcher on the Administration Console > Transformer Settings > Advanced > Process Launcher tab to launch a Windows built-in application (for example, calc.exe) as entered in the process command line field, the agent host might keep opening the application after you refresh Citrix WEM Agent. [WEM-3262]
  • You might experience the following two issues:
    • Attempts to connect to the WEM administration console might take a few minutes to complete.
    • It takes a long time to load WEM configurations on agent hosts. The issue occurs when you have a large Active Directory deployment and there are many connected agents. [WEM-4225]
  • Attempts to map a network drive to users might fail if the assigned drive letter is already in use by an existing network drive. The issue occurs when the existing network drive failed to connect as indicated by a red “X” on the network drive icon. [WEM-4495, LD1552]

Depreciated Features

Click here to see depreciated features.

Thanks for reading,
Alain

WEM 1903 UPDATE AVAILABLE

Intro

The first release of WEM for 2019 is out. The version numbering system in now in line with other newly released Citrix products. This version is 1903. You can now download the new version here (requires Platinum licenses and login to Citrix.com). I’ve provided the release notes below.

What’s new in Workspace Environment Management 1903

Workspace Environment Management 1903 does not include any new features. Ths release addresses several issues to improve the user experience. For information about bug fixes, see Fixed issues.

Thanks for reading,
Alain