Product Documentation

Known issues

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]
  • In 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 only allows 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]

Known issues

In this article