Learn about product name changes here.
Citrix Cloud Connector. This must be installed on at least one machine in every resource location you are using before you install the Workspace Environment Management service agent. See Cloud Connector Installation.
.NET Framework 4.5.2 or later. This is required by the Workspace Environment Management service agent. If not already installed, it is automatically installed during agent installation.
Microsoft SQL Server Compact 3.5 SP2. SQL Server Compact is used by Workspace Environment Management to cache settings, primarily for use in offline mode. It must be installed on all agent environments to let the agent cache settings and run when it is in offline mode. If not already installed, it is automatically installed during agent installation.
Microsoft Sync Framework 2.1. This is required by the Workspace Environment Management service agent. If not already installed, it is automatically installed during agent installation.
Microsoft Active Directory: Workspace Environment Management service requires read access to your Active Directory to push configured settings out to users. Administrative access is required to configure the agent.
Citrix Virtual Apps and Desktops. Any supported version of Citrix Virtual Apps or Citrix Virtual Desktops is required for this release of Workspace Environment Management.
Citrix Workspace app for Windows. To connect to Citrix StoreFront store resources that have been configured from the Workspace Environment Management service administration console, Citrix Workspace app for Windows must be installed on the agent host machine. The following versions are supported:
- Citrix Receiver for Windows versions: 4.4 LTSR CU5, 4.7, 4.9, 4.9 LTSR CU1, and 4.10
- Citrix Workspace app 1808 for Windows and later
For Transformer kiosk-enabled machines, Citrix Workspace app for Windows must be installed with single sign on enabled, and configured for pass-through authentication. For more information, see Citrix Workspace app.
Operating system prerequisites
Agent. The Workspace Environment Management agent is supported on the following operating systems:
- Windows 7 SP1 Professional, Enterprise, and Ultimate editions, 32- and 64-bit
- Windows 8.1 Professional and Enterprise editions, 32- and 64-bit
- Windows 10 version 1607 and newer, 32- and 64-bit
- Windows Server 2008 R2 SP1 Standard, Enterprise, and Datacenter editions*
- Windows Server 2012 Standard and Datacenter editions*
- Windows Server 2012 R2 Standard and Datacenter editions*
- Windows Server 2016 Standard and Datacenter editions*
- Windows Server 2019 Standard and Datacenter editions*
* The Transformer feature is not supported on server operating systems.
Workspace Environment Management service agents running on server operating systems cannot operate correctly when Microsoft’s Dynamic Fair Share Scheduling (DFSS) is enabled. For information about how to disable DFSS, see CTX127135.
Agent: average RAM consumption is 10 MB, but we recommend that you provide 20 MB to be safe. 40 MB of available disk space (100 MB during installation).
For the WEM service agent to operate, you must configure your firewall and proxy server to allow outbound connections. For more information, see Internet connectivity requirements.
In enterprise networks, the WEM service also requires the Cloud Connector to communicate with the WEM service agent. Therefore, check your firewall settings to ensure that the WEM service agent port is configured correctly. For more information, see Port information.
Netlogon. The agent service (“Norskale Agent Host service”) is added to the Netlogon Dependencies list to ensure that the agent service is running before logons can be made.
The Workspace Environment Management service agent is installed in the following default directory:
C:\Program Files (x86)\Norskale\Norskale Agent Host (on 64-bit OS)
C:\Program Files\Norskale\Norskale Agent Host (on 32-bit OS)
On-access scanning must be disabled for the entire “Norskale” installation directory for the Workspace Environment Management agent. When this is not possible, the following processes must be excluded from on-access scanning:
- Norskale Agent Host Service.exe
- Agent Log Parser.exe