Known issues in previous releases

Workspace Environment Management service 1812.1.0.1

  • Instances of Adobe Reader installed on Windows Server 2012 R2 prevent 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]

  • Agent host machine names listed in the WEM service administration console Active Directory Objects tab do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again. [WEM-1549]

  • In the administration console Active Directory Objects tab, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.) [WEM-1620]

  • After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent. [WEM-2396]

  • 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 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 the 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 using a publisher condition, the rule does not work. This issue occurs because WEM resolves the file name incorrectly. [WEM-3582]

  • If you click Add OU on the administration console, WEM might not display anything on the Organizational Units window. The issue occurs when a forest (current or trusted) contains a large number of OUs. As a workaround, you might need to click Cancel and then click Add OU multiple times. [WEM-3818, UCOHELP-1211]

  • 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 service 1812.0.0.1

  • Instances of Adobe Reader installed on Windows Server 2012 R2 prevent 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]

  • Agent host machine names listed in the WEM service administration console Active Directory Objects tab do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again. [WEM-1549]

  • In the administration console Active Directory Objects tab, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.) [WEM-1620]

  • After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent. [WEM-2396]

  • 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 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 the 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 using a publisher condition, the rule does not work. This issue occurs because WEM resolves the file name incorrectly. [WEM-3582]

  • Attempts to map a network drive to users fail if you select the character # as the drive letter for that network drive in the Assign Filter & Drive Letter window. This issue occurs because WEM currently does not support assigning a random letter to a network drive by using “#.” [WEM-3752, LD1014]

  • Attempts to migrate your WEM database into the WEM service can fail. The issue occurs when the entries in the VUEMTasksHistory table of your on-premises WEM database contain special characters. As a workaround, delete those entries from your on-premises WEM database, and then restart the migration process. [WEM-3817, UCOHELP-1567]

  • If you click Add OU on the administration console, WEM might not display anything on the Organizational Units window. The issue occurs when a forest (current or trusted) contains a large number of OUs. As a workaround, you might need to click Cancel and then click Add OU multiple times. [WEM-3818, UCOHELP-1211]

  • 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 service 1811

Workspace Environment Management service contains the following issues:

  • Instances of Adobe Reader installed on Windows Server 2012 R2 prevent 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]

  • If you open the Workspace Environment Management service administration console using Internet Explorer 11 (IE11) or Microsoft Edge, and open the Developer Tools pane (F12), when you close the Developer Tools pane again the administration console does not redraw to full size. If this happens, refresh the browser window to redraw the administration console correctly. [WEM-1377]

  • Agent host machine names listed in the WEM service administration console Active Directory Objects tab do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, and then add the machine again. [WEM-1549]

  • In the administration console Active Directory Objects tab, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.) [WEM-1620]

  • After you migrate your on-premises WEM database to the WEM service, you must reinstall the WEM service agent even if the latest version is installed on your machine. This is necessary because the agent cache cannot synchronize with the WEM service database unless you reinstall the WEM service agent. [WEM-2396]

  • Attempts to access the administration console from the Workspace Environment Management service Manage tab fail. As a workaround, refresh your browser window and try again. [WEM-2401]

  • Attempts to run the UpmConfigCheck script on Windows 7 Service Pack 1, Windows 2008 R2 Service Pack 1, or Windows Server 2008 Service Pack 2 fail. To run the script on those operating systems, you must manually install Windows Management Framework 3.0. If the UpmConfigCheck still does not work after you install Windows Management Framework 3.0, restart your WEM agent host service (Norskale Agent Host Service). [WEM-2717]

Workspace Environment Management service 1807

Workspace Environment Management service 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]

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

  • If multiple session support is enabled on a Windows server OS machine, application security rules of previously logged on users are replaced by rules of more recently logged on users. For example, if a rule is assigned to user1 but not to user2, when user2 logs on the rule is deleted from local AppLocker rules. Thus the rule cannot be enforced for user1 as well. [WEM-1070]

  • If you open the Workspace Environment Management service administration console using Internet Explorer 11 (IE11) or Microsoft Edge, and open the Developer Tools pane (F12), when you close the Developer Tools pane again the administration console does not redraw to full size. If this happens, refresh the browser window to redraw the administration console correctly. [WEM-1377]

  • Agent host machine names listed in the WEM service administration console Active Directory Objects tab do not update automatically to reflect changes to machine names. To display the new name of a machine in the Machines list, you must manually delete the machine from the Machines list, then add the machine again. [WEM-1549]

  • The on-premises version of Workspace Environment Management (WEM) allows you to use Active Directory security groups as containers for WEM agents. However, the WEM service does not support using Active Directory security groups as agent containers. The on-premises infrastructure service also supports using direct and indirect OUs as agent containers. However, the WEM service does not support indirect OUs. For example, suppose WEM agent AGENT1 belongs to OU2, and OU2 belongs to OU1 (OU1>OU2>AGENT1). The on-premises infrastructure service recognizes AGENT1 as a member of both OU1 and OU2, but the WEM service only recognizes AGENT1 as a member of OU2. [WEM-1619]

  • In the administration console Active Directory Objects tab, using Add Object and Check Name to search and add objects allows only one object to be added at a time. You must close and then reopen the Select Computers or Groups dialog to add another object. (The on-premises version of Workspace Environment Management allows multiple objects to be identified and added without closing the dialog each time.) [WEM-1620]