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-help command with the -examples, -detailed, or -full switch instead. [WEM-694]

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

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

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