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]

Fixed in previous releases

Fixed in Workspace Environment Management 1903

The following issues have been fixed in the current release:

  • With language packs installed, options in the Start menu > User Account menu might not appear in the language you selected. [WEM-1176, LC8811]

  • You might find that the Norskale Broker Service.exe consumes more than 2GB of RAM several days after you perform frequent Active Directory (AD) operations (for example, specify users, computers, groups, and organizational units). The issue occurs when you have a very large AD because the garbage collection mechanism cannot automatically release the RAM consumed by the System.Threading.Tasks namespace objects that the Norskale Broker Service.exe uses. [WEM-3251, LD1195]

Fixed in Workspace Environment Management 1811

The following issues have been fixed in the current release:

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

  • Attempts to upgrade the WEM database using the command line might fail. [WEM-1410]

  • After you apply a percentage of the CPU’s processing power for a process on the System Optimization > CPU Management > CPU Clamping tab of the administration console for the first time and configure a different percentage for the same process later, the change does not take effect. [WEM-1993, LD0110]

  • When the Citrix WEM agent starts, a Citrix WEM Agent Init file (.log) and a Citrix WEM Agent file (.log) are created separately in the root of the current user’s Users folder. However, while WEM agent switches from the Citrix WEM Agent Init file to the Citrix WEM Agent file, some logs might be missing. [WEM-2233]

  • When a forest (current or trusted) contains a large number of OUs (for example, 10,000), if you click Add OU from the administration console, you might find some OUs to be missing from the Organizational Units window. This issue occurs because the search task times out before the search completes. [WEM-2378, LD0428]

  • The Workspace Environment Management node has been moved from Computer Configuration > Policies > Administrative Templates > Citrix to Computer Configuration > Policies > Administrative Templates > Citrix Components. [WEM-2582]

Fixed in Workspace Environment Management 1808

  • The Workspace Environment Management Agent Host screen capture feature allows end users to take screenshots of error messages in their environment. They can then send the screenshots to the administrator via Microsoft Outlook for support. However, when end users click the Send to Support button, the following error message appears: “Error encountered while sending email.” [WEM-1123]

  • Application Security features are not available if the Workspace Environment Management administration console is installed on Windows 7 SP1 or Windows Server 2008 R2 SP1 (or earlier versions). In the Security tab, none of the Application Security options can be selected. [WEM-1216, LC9023]

  • When the number of connected agents exceeds a certain threshold (for example, 5,000), if you frequently specify users, computers, groups, and organizational units, you might find that the Norskale Broker Service.exe consumes more than 2GB of RAM several days later. The issue occurs because some Microsoft LDAP APIs used by Norskale Broker Service.exe are unable to release the consumed RAM automatically. [WEM-1494, LC9623]

  • When a forest (current or trusted) contains more than 1,000 OUs, if you click Add OU from the administration console, you might find some OUs to be missing from the Organizational Units window. The issues occurs because LDAP API FindAll() returns no more than 1,000 results by default. [WEM-1986, LD0121]

  • After you upgrade the WEM agent to Version 4.7, if you select Enable Intelligent CPU Optimization and/or Enable Intelligent I/O Optimization on the System Optimization > CPU Management > CPU Management Settings tab of the administration console, error messages about Error 87 frequently appear in Windows Event logs. This issue does not affect the user experience, thus you can dismiss these error messages. [WEM-2051]

Fixed in Workspace Environment Management 4.7

  • You can use the Citrix Workspace Environment Management Infrastructure Services Setup.exe to install the Citrix Workspace Environment Management SDK without installing the infrastructure service (by selecting “Custom” installation type and deselecting “Default feature”). However, if you leave the option “Start the Database Management Utility” selected then click “Finish,” an error message about Error 2753 is displayed. You can click OK to dismiss this error dialog, which is benign. [WEM-541]

  • When you are configuring the Workspace Environment Management database, if you use incorrect settings the system may become unresponsive for up to six minutes. The system then displays an error message reporting “A network-related or instance-specific error occurred while establishing a connection to SQL Server. Examples of incorrect settings include incorrect SQL user name and password or invalid database instance. This happens because Workspace Environment Management makes multiple database connection retries with the incorrect settings. [WEM-790]

  • In the administration console Active Directory Objects section Machines tab, when you click Add OU, the Organization Units dialog does not list all the items it should. There are two scenarios to be aware of:
    • When the infrastructure server and administration console are not installed on the parent domain (for example, they are installed on the tree-domain or on a sub-domain), none of the Active Directory structure or OUs (forests, domains, sub-domains, and so on) outside the current forest are shown.
    • When the infrastructure server and administration console are installed on the parent domain, only the parent domain OU is shown. The OUs of sub-domains and tree-domains in different forests are not shown.

    To add machines which are in a different forest, in the Machines tab, click Add Object and select the other forest. [WEM-1069]

  • When end-users access applications via Workspace Environment Management, the CPU usage of NorSkale Agent Host service.exe increases to 20% and remains there for 5 to 60 seconds, thus affecting the user experience. [WEM-1094, LC9230]

  • WEM agents are randomly reported with the following different status under Administration > Agents > Registrations: “Agent <AgentHostName> is bound to multiple configuration sets.” “Agent <AgentHostName> is not be bound to any Configuration Set.” This issue occurs only when using OUs as AD objects in Configuration Sets. It prevents agents registering successfully with infrastructure servers. [WEM-1302, LC9524]

  • The Workspace Environment Management administration console Administration > Agents tab reports the Netscaler Subnet IP address instead of the agent IP address. This prevents the agent cache being refreshed because the Agents tab times out. [WEM-1406, LC9645]

  • When users log on, the Workspace Environment Management session agent reports “processing applications…”, but this never completes. This occurs only when customer assigns multiple applications to the agent and enables multi-functions. [WEM-1740, LC8601]

  • Attempting to add an application of type URL in the Workspace Environment Management administration console fails. The event and broker logs show “AdminBrokerService.CreateVuemApp():Cannot insert the value NULL into column ‘WorkingDirectory’, table ‘CitrixWEM.dbo.VUEMApps’; column does not allow nulls. INSERT fails.” [WEM-1741, LC9551]

Fixed in Workspace Environment Management 4.6

  • When you uninstall the Workspace Environment Management agent, the uninstall process does not delete the Windows Firewall inbound rule “Norskale agent in”. Manually delete this rule in the Windows Firewall with Advanced Security dialog. [WEM-312]
  • When the option “Launch Agent at Reconnect” is selected, the Workspace Environment Management agent executable does not run when reconnecting with published desktops on agent hosts which are running Windows desktop operating systems, via ICA. (RDP sessions are unaffected.) [WEM-322, LC8816]
  • If you attempt to add an agent host machine to a configuration set when the agent host machine is in a different forest to the infrastructure service, it can take several minutes before the agent host is added, depending on the actual AD topology involved. During this time, the administration console displays the message “Please Wait loading…” and further activities are not possible. [WEM-358]
  • Attempts to create or update a WEM database, on an SQL Server instance which uses case-sensitive collation, fails. Ensure that the SQL Server instance uses *case-insensitive *collation before attempting to create or update a WEM database. [WEM-540]
  • The Workspace Environment Management agent randomly crashes after VDAs are upgraded to XenApp and XenDesktop 7.16. [WEM-937, LC8926]
  • In the Workspace Environment Management administration console Citrix Profile Management Settings, the Synchronization tab option “Enable File Mirroring” does not match the Citrix Studio Profile Management policy setting it is derived from. The option should read “Enable File Synchronization” and allow files to be added. [WEM-971, LC9090]
  • When you are adding an Application Security executable rule of type “Publisher”, dragging the Publisher info slider to “File name” or above causes an exception in the Workspace Environment Management administration console. [WEM-1199, LC9255]
  • On laptop machines in transformer mode, the Transformer battery icon does not stay synchronized with the battery percent reported by the OS. When the power cable is connected or disconnected, the transformer battery icon is refreshed with the correct percentage value, but it then continues to show the same fixed value until the next power cable change is detected. [LC9261]
  • The WEM agent installs VUEMRSAV.exe (Workspace Environment Management Resultant Actions Viewer), a utility which allows users to view the WEM configuration defined for them by the administrator. If an administrator assigns an action directly to a specific user, when that user runs VUEMRSAV.exe, the assigned action is missing in the Applied Actions tab. If an administrator assigns an action to a User Group to which the user belongs (for example, ‘Domain Users’), when that user runs VUEMRSAV.exe, the assigned action is visible in the Applied Actions tab, which is the correct behavior. [WEM-1200]

Fixed in Workspace Environment Management 4.5

  • When you examine the properties of rules in the Microsoft Security Policy Editor (secpol.msc), script rules set to “Audit” mode in the Workspace Environment Management Security tab are incorrectly shown as not configured. (PowerShell can be used to confirm that these rules are actually in audit mode.) [WEM-352]
  • In the WEM Infrastructure Server Configuration wizard Advanced tab, if you select the option Use cache even if online, it is not saved when you close the wizard. A workaround is to set the registry key BrokerUseCacheEvenIfOnline = 1 in HKLM\System\CurrentControlSet\Control\Norskale\Infrastructure Services. [WEM-396]
  • While in the Security Tab and switching between Configuration Sets, the side panel may incorrectly display its state, either enabled/disabled. Switching to another tab and back resolves this issue. [WEM-405]
  • When you select multiple rules and click Edit, any changes to rule assignments you make are applied to all users and user groups you select. In other words, both new and existing rule assignments are merged across those rules. If you do not change rule assignments, existing rule assignments are unchanged. To fine-tune rule assignments, select one rule at a time and click Edit. [WEM-420]
  • When you select multiple rules and then use Edit, the Permissions option defaults to “Allow,” even if some or all the selected rules are set to deny. In the rule list, permissions are correctly reported in the Action column. [WEM-421]

Fixed in Workspace Environment Management 4.4

  • If you run the Workspace Environment Management administration console as a standard Windows user, and you attempt to start the Modeling Wizard, the wizard does not start. [WEM-187]

  • When you attempt to add a user group, which is in a different AD domain to the infrastructure server, as a processed group in the Citrix User Profile Management tab in the administration console, the exception *IndexOutOfRangeException is raised, and the group is not processed. [WEM-210]

  • Links in “This PC” in Windows 10 do not reflect folder redirection, and still point to local folders. [WEM-234]

  • The Agent Host waits about 5 minutes before starting if Workspace Environment Management is installed on Windows version 8, or Server 2012, and a language pack is installed. [WEM-244]

  • If you launch or refresh a UI session agent when it is not bound to a configuration set, keyboard and mouse locks which are active during the agent refresh are not released. [WEM-321]

  • If you attempt to add an agent host machine to a configuration set when the agent host machine is in a different domain to the infrastructure service, the machine is not added in the administration console Active Directory Objects tab. This happens regardless of the actual AD topology involved (parent/child domains, multi-forest setups, one- or two-way trust relationships, and so on). [WEM-326, WEM-299]

Fixed in Workspace Environment Management 4.3

  • When the Workspace Environment Management session agent is running in command line mode, User Statistics data is not reported to the WEM infrastructure services. [WEM-41]

  • The Workspace Environment Management session agent interface does not render correctly when a computer display is extended to external displays connected via a dock. This problem, which occurs when extending to multiple displays with different screen resolution settings, results in a portion of the right-hand side of the display not rendering completely. This prevents users seeing the home button or being able to change other native Workspace Environment Management settings. [WEM-90]

  • The Workspace Environment Management session agent causes the mouse to stop working on virtual machines which have the System Center Configuration Manager (SCCM) client installed with Power Management enabled. [WEM-115]

  • When you are using the Transformer feature, the session agent generates an unhandled exception if Wi-Fi is turned off using “ms-settings:network-wifi.” [WEM-133]

  • The Workspace Environment Management session agent causes the mouse to stop working on virtual machines after an interruption to network access is restored. [WEM-159]

Fixed in Workspace Environment Management 4.2

  • File Association actions cannot be processed by the Agent Host on Windows 8, 8.1, Server 2012, Server 2012 R2, and Server 2016 due to registry access issues. [WEM-15]
  • The Agent Host waits about 5 minutes before starting if Workspace Environment Management is installed on Windows version 8, 8.1, 10, Server 2012, Server 2012 R2, or Server 2016 (all branches and builds) and a language pack is installed. [WEM-17]