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 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.
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.
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.
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.
Workspace Environment Management documentation is updated to reflect current product behavior.
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]
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]
Click here to see depreciated features.
Thanks for reading,