Workspace Environment Management (WEM) 2303

Last Modified: May 30, 2023 @ 2:05 pm

539 Comments

Navigation

This post covers Citrix Workspace Environment Management (WEM) versions 2303, 1912, and 4.7 through 4.1.

💡 = Recently Updated

Change Log

Overview

Workspace Environment Management (WEM) is Citrix’s Performance Management and UEM (User Environment Management) tool for all XenApp/XenDesktop Enterprise or Platinum Customers with active Software Maintenance (Subscription Advantage is not sufficient). The WEM Agent is supported on XenApp 6.5, and XenApp/XenDesktop 7.x. Videos:

Note: WEM does not replace Citrix Profile Management. You usually implement both.

Citrix Blog Post User Experience on Steroids: Citrix Workspace Environment Management has a list of Frequently Asked Questions about WEM, including a drawing of the architecture.

From Hal Lange at Database sizing at Citrix Discussions: SQL Always On is fully supported.  In WEM 1909 and older, the ONE caveat is to remove from the Always On Availability Group before upgrading.

Here are the official calculations from the Norskale days on space needed on the SQL Server:

  • Reserve 1GB of RAM per 1,000 users deployed
  • RAM=1.5GB system + (1.5GB SQL + 1 GB per 1,000 users) for that SQL instance
  • Disk = 1GB per 10,000 users per year + 10 MB per WEM site configured

Upgrade WEM

There is no LTSR version of Citrix Workspace Environment Management (WEM), so you should always upgrade to the latest version of WEM.

From Upgrade a deployment at Citrix Docs: In-place upgrades from versions earlier than Workspace Environment Management 4.7 to version 1808 or later are not supported. To upgrade from any of those earlier versions, you need to upgrade to version 4.7 first and then upgrade to the target version.

If you want to upgrade a WEM deployment earlier than 2006 to 2209 or later: To avoid database upgrade failures, upgrade to 2103 first and then to 2209 or later.

CTA Marco Hofmann at CUGC: How-To: Update Citrix Workspace Environment Management (WEM) from 4.x to 4.7 (v4.07.00.00)

To upgrade Citrix WEM:

  1. In-place upgrade the Citrix Licensing Server. No special instructions.
    • Ensure the installed licenses a non-expired Subscription Advantage date.
  2. Before you upgrade, run WEM Infrastructure Service Configuration Utility and record all settings.
  3. In-place upgrade the WEM Server. No special instructions.
  4. Use the Database Maintenance tool to upgrade the WEM database.
    • In WEM 1909 and older, before upgrading the database that’s in a SQL Server Always On availability group, you must remove it from the availability group. This is no longer required in WEM 1912 and newer.
  5. You might have to run the WEM Infrastructure Service Configuration Utility on each Broker to point to the upgraded database. If the settings are still there, then just click Save Configuration.
  6. In-place upgrade the WEM Console. No special instructions.
  7. In-place upgrade the WEM Agents.

Install/Upgrade WEM Server (Broker Service)

There is no LTSR version of Citrix Workspace Environment Management (WEM), so you should always upgrade to the latest version of WEM.

The WEM Broker Service can be installed on one or more servers, including Delivery Controllers. The WEM Agent cannot be installed on the Broker Server.

A WEM Server with 4 vCPU and 8 GB RAM can support up to 3,000 users.

  1. Port 8288 – WEM 1912 and newer have a new port 8288 for WEM Agent Cache Synchronization. You’ll need to add this port to your load balancer and open it in your firewall.
    • Port 8285 is still available for WEM Agents 2012 and older connecting to newer WEM Servers.
    • Old port removed – The Cache synchronization port (8285) was removed from WEM Server 2103 and newer, so make sure your existing agents are a version that supports the newer Cached data synchronization port. WEM Agent 1912 and newer should be sufficient.
    • If your existing WEM Agents don’t support the new port number, then upgrade your WEM Server to version 2012 (or version 1912), upgrade your WEM Agents to the corresponding version, and then upgrade the WEM Server to a newer version.
  2. Download Workspace Environment Management 2303 and extract it.
  3. If you are upgrading, run WEM Infrastructure Service Configuration Utility and record all settings. These settings might be wiped out during the upgrade.
  4. Licenses – make sure your installed CVAD licenses have a CSS date that is later than the date required by your WEM version. The required CSS date is shown at the top of the WEM download page.
  5. Run the downloaded Citrix Workspace Environment Management Infrastructure Services Setup.exe from the 2303-01-00-01 folder.
  6. If you see a prerequisites screen, then click Install to install the prerequisites.
  7. In the Welcome to the InstallShield Wizard for Citrix Workspace Environment Management Infrastructure Services page, click Next.
  8. In the License Agreement page, select I accept the terms, and click Next.
  9. In the Customer Information page, click Next.
  10. In the Setup Type page, click Next.
  11. In the Ready to Install the Program page, click Install.
  12. If you are upgrading, you might be prompted to restart applications.
  13. In the InstallShield Wizard Completed page, click Finish.
  14. Antivirus – C:\Program Files (x86)\Norskale\Norskale Infrastructure Services must be excluded from Antivirus scanning. Or exclude: Norskale Broker Service.exe; Norskale Broker Service Configuration Utility.exe; Norskale Database Management Utility.exe.
  15. If you are upgrading, then make sure your WEM Service Account has Full control permissions on the DBSync folder at C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\DBSync. For new installs, WEM should set this permission correctly once the Infrastructure Services are configured. Note: this folder seems to be missing in newer versions of WEM.
  16. Firewall – Ensure firewall allows the following ports to/from the WEM Broker servers. See Citrix Tech Zone Communication Ports Used by Citrix Technologies.
    • Agent Port – defaults to TCP 8286 – from WEM Agent to WEM Broker
    • AgentSyncPort – defaults to TCP 8285 – from WEM Agent to WEM Broker
    • Cached data synchronization port – defaults to TCP 8288 – from WEM Agent 1912 and newer to WEM Broker
    • AdminPort – defaults to TCP 8284 – from WEM Admin Console to WEM Broker
    • Monitoring Port – defaults to TCP 8287 – from Director to WEM Broker
    • AgentPort – defaults to TCP 49752 – from WEM Broker to WEM Agent
  17. See CTX218965 Error: “Server sent back a fault indicating it is too busy to process the request” and the WEM Agent fails to connect to the Broker Service if you need to throttle the number of connections if you have insufficient resources on the WEM Broker server.

Upgrade WEM Database

Workspace Environment Management 4.5 and newer have PowerShell commands. For details, see Citrix Workspace Environment Management 2103 SDK at Citrix Developer docs.

To upgrade the Workspace Environment Management database using the GUI tool:

  1. If this is a new install, skip to Create WEM Database.
  2. The person running Database Management must be a sysadmin on the SQL Server. Or you can enter a SQL login.
  3. On the WEM server, run Database Management from the Start Menu.
  4. If upgrading, in the ribbon, click Upgrade Database.
  5. In WEM 1906 and newer, the fields might already be filled in. Otherwise:
    1. Enter the SQL Server Name.
    2. Enter the existing WEM Database Name.
    3. Configure the credentials for the WEM service account.
  6. If your account is not a sysadmin on SQL, then enter a SQL account in the Database Credentials fields.
  7. Click Upgrade.
  8. Click Yes when asked to proceed.
  9. Click OK when prompted that database upgraded successfully.
  10. Click Finish to close the Database Upgrade Wizard.
  11. Close the WEM Database Management Utility.
  12. Open services.msc and restart the Norskale Infrastructure Service.

After the database is upgraded, run the WEM Infrastructure Service Configuration Utility.

  1. If the upgrade preserved the settings, then simply click Save Configuration. The service won’t start unless you do this.
  2. In WEM older than version 1906, you might have to re-configure the settings.
    1. On the Licensing tab, configure the licensing server.
    2. On the Database Maintenance tab, consider checking Enable Scheduled Database Maintenance.
    3. On the Advanced Settings tab:
      1. Enter the Infrastructure service account credentials.
      2. Enter the vuemUser SQL user account password.
      3. In WEM 1909 and newer, check the box next to Enable performance tuning and set both of the Minimum threads boxes to the number of concurrent WEM Agents that will be connected to this one WEM server. Maximum value is 3000.
      4. Make a choice regarding Google Analytics.
    4. The Advanced Settings tab will look something like this.
    5. On the Database Settings tab, enter the database server name and database name.
    6. In the ribbon, click Save Configuration.
  3. Click Yes to restart the Broker Service.
  4. If you are upgrading, then make sure your WEM Service Account has Full control permissions on the DBSync folder at C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\DBSync. For new installs, WEM should set this permission correctly once the Infrastructure Services are configured. This folder doesn’t exist in newer versions of WEM.
  5. Skip ahead to upgrade the WEM Administration Console.

Create WEM Database

Workspace Environment Management 4.5 and newer have PowerShell commands. For details, see Citrix Workspace Environment Management 2103 SDK at Citrix Developer docs.

To create the database using the GUI tool:

  1. The person running Database Management must be a sysadmin on the SQL Server. Or you can enter a SQL login.
  2. Make sure SQL Server authentication (mixed mode) is enabled on the SQL server > Properties > Security. Even though the WEM Broker server runs as an AD account that is used login to SQL, WEM Broker also uses a SQL account named vuemUser, which means mixed mode must be enabled. Source = John Long at WEM new install, cannot connect to infrastructure server at Citrix Discussions.

  3. On the WEM server, run WEM Database Management Utility from the Start Menu.
  4. If a new install, in the ribbon, click Create Database.
  5. In the Create database Wizard page, click Next.
  6. In the Database Informations page, enter the SQL server name, and enter a new Database Name.
    1. Only enter an instance name if you have a named SQL instance.
    2. Only enter a port number if your SQL instance is listening on a static port number other than 1433.
    3. From Måns Hurtigh at Problem creating WEM 4.3 Database on SQL Server 2012 at Citrix Discussions: The database name cannot contain a dash.
  7. The paths might not be correct so double check them. Then click Next.
  8. In the Database Server Credentials page, if your account has sysadmin permissions, then leave the box checked. Otherwise, uncheck the box, and enter a SQL login that has sysadmin permissions. Click Next.
  9. In the VUEM Administrators section, click Browse, and select your Citrix Admins group.
  10. In the Database Security page, if you intend to load balance multiple WEM servers, then specify a Windows service account for database access. The Broker Service will run as this account. See the load balancing topic at Install the Citrix Workspace Environment Management Infrastructure Services at Citrix Docs.
  11. The Database Creation Wizard also creates a SQL account called vuemUser with an 8 character alphanumeric password. If you want it more complex, check the box and specify the password.
    • Note: if you intend to implement AlwaysOn Availability Group, then you must specify this password, since you’ll be asked for it again when adding the database to the Availability Group. Also see SQL Server Always On at Citrix Docs.

  12. Click Next.
  13. In the Database Information Summary page, click Create Database.
  14. Click OK when prompted that the database was created successfully.
  15. Click Finish to close the Database Creation Wizard.
  16. Close the WEM Database Management Utility.
  17. There is a log file at “C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\Citrix WEM Database Management Utility Debug Log.log”

WEM Infrastructure Services Configuration

  1. On the WEM Server, run WEM Infrastructure Service Configuration Utility from the Start Menu.
  2. On the Database Settings tab, enter the SQL Server name and database name.
  3. Switch to the Advanced Settings tab.
  4. If you intend to load balance WEM Servers, then Browse to a service account. This service account must have access to the database.

    • The service account must be in the local Administrators group on the WEM servers.
  5. Enter the vuemUser SQL user account password.
  6. In WEM 1909 and newer, check the box next to Enable performance tuning and set both of the Minimum threads boxes to the number of concurrent WEM Agents that will be connected to this one WEM server. Maximum value is 3000.
  7. Make a choice regarding Google Analytics.
  8. The Advanced Settings tab will look something like this.
  9. On the Database Maintenance tab, consider checking Enable Scheduled Database Maintenance.
  10. On the Licensing tab, you can enter a Citrix License Server 11.14.0.1 or newer that has valid licenses. Or you can enter the license server later in the admin console.
  11. Click Save Configuration in the ribbon.
  12. Click Yes when asked to restart the Broker Service.
  13. Close the WEM Infrastructure Service Configuration utility.
  14. If you are upgrading, then make sure your WEM Service Account has Full control permissions on the DBSync folder at C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\DBSync. For new installs, WEM should set this permission correctly once the Infrastructure Services are configured.
  15. If you are load balancing WEM servers, then you must also create a Kerberos SPN, where [accountname] is the service account you are using for the Norskale service.
    setspn -U -S Norskale/BrokerService [accountname]

Install/Upgrade WEM Console

  1. Run Citrix Workspace Environment Management Console Setup.exe from the downloaded WEM 2303 (aka 2303-01-00-01) installation files.
  2. In the Welcome to the InstallShield Wizard for Citrix Workspace Environment Management Console page, click Next.
  3. In the License Agreement page, select I accept the terms, and click Next.
  4. In the Customer Information page, click Next.
  5. In the Setup Type page, click Next.
  6. In the Ready to Install the Program page, click Install.
  7. In the InstallShield Wizard Completed page, click Finish.

WEM Configuration Sets (formerly known as Sites)

In WEM 4.3, Sites was renamed to Configuration Sets.

  1. From the Start Menu, run WEM Administration Console.
  2. In the ribbon, click Connect.
  3. In the Database Broker Information window, enter the WEM Server name, and click Connect.
  4. Some WEM Console settings are global (every agent gets the same setting). So if you want different global settings for different agents, then you create multiple WEM Configuration sets. At the top of the window, in the ribbon, you can create a new WEM Configuration set. 
  5. WEM 1912 and newer can Backup and Restore entire Configuration Sets, which makes it easy to duplicate a Configuration Set.

    • When Restoring a Configuration Set, there’s no need to create a new empty Set. Just run the Restore wizard and WEM will try to use the original Configuration Set name. If the original Configuration Set already exists, then WEM will append _1 to the name, which you can then rename.
  6. Once you have multiple Configuration sets, you can use the drop-down to switch between them.
  7. A WEM Agent can only belong to one WEM Configuration set. Different Agents can belong to different WEM Configuration sets.
  8. In WEM 4.3 and newer, you add agents to the Configuration set at Active Directory Objects (workspace on bottom left) > Machines (node on top left). You can add OUs or individual objects (computers or computer groups).
  9. In WEM 4.2 and older:
    1. The WEM Group Policy template has a GPO setting to specify the WEM Site name that an agent should use.

Import Recommended Settings

If you have multiple WEM configuration sets, this process should be repeated for each new, empty WEM configuration set.

  1. In WEM 4.4 and newer, on the right side of the ribbon, click Restore.

    • In WEM 4.3 and older, on the right side of the ribbon, click Import Settings.
  2. In WEM 4.4 and newer, select Settings, and click Next.
  3. In the Settings Restore wizard, click Next.
  4. In the Restore from folder section, click Browse, and browse to the \Workspace-Environment-Management-v-2303-01-00-01\Configuration Templates\Default Recommended Settings folder that was included in the WEM download.
  5. In the Settings Type Selection section, check all available boxes, and click Next.
  6. In the Restore settings processing window, click Restore Settings.
  7. Click Yes when prompted to replace.
  8. Click Finish.

CTP James Kindon at WEM Hydration Kit has a collection of Applications, File System and Registry Actions that can be imported to WEM. CTP James Kindon recently added Environmental Settings to the Hydration Kit.

WEM 1909 and newer can Migrate your Group Policies to WEM. CTP James Kindon at Migrating GPO settings to WEM explains this feature in detail.

WEM Administrators

  1. In the Administration Console, go to Administration (workspace on bottom left) > Administrators (node on top left).
  2. In the right pane, click Add, and specify an Active Directory group that can administer WEM.
  3. After adding a group or user, right-click the new administrator, and click Edit.
  4. Use the Permissions drop-down to select a role. The roles are detailed at Administrators at Citrix Docs.
  5. Then use the State drop-down to select Enabled. New administrators are initially disabled. Click OK to close the window.

WEM Agent Configuration

For configuration guidance, see CTP James Kindon WEM Advanced Guidance – 2023 at CUGC.

  1. In the WEM Administration Console, in the Advanced Settings workspace (bottom left), there are several tabs for configuring the agent.
  2. On the bottom of each tab is an Apply button. Click this button periodically to save your configuration to the database.
  3. Setting on these tabs are mostly self-explanatory. Feel free to change any as desired.
  4. On the Main Configuration tab, one option you might want to enable is Launch Agent for admins.
  5. Also consider enabling Launch Agent at Reconnect.
  6. In the right pane, on the Reconnection Actions tab, you can select which modules should be refreshed on reconnect.
  7. The Agent Options tab defaults to processing printers and drives asynchronously.
  8. If WEM in Citrix Cloud, consider enabling Offline Mode and Use Cache to Accelerate Actions Processing. More info at Citrix Blog Post Workspace Environment Management agent caching explained.
  9. The Service Options tab has a setting for Bypass ie4uinit Check. Enabling this might eliminate a 2 minute delay before WEM Agent starts.
  10. On the top left, in the Advanced Settings workspace, there’s a UI Agent Personalization node.
  11. In the right pane, in the UI Agent Options tab, you can change the Agent skin, and Preview it.
  12. Other settings on this page let you hide the splash screen.
  13. The Helpdesk Options tab lets you enable Screen Capture.

System Optimization

  1. The System Optimization workspace (bottom left) lets you configure the various optimizations.
  2. On the top left, click the CPU Management node.
  3. CPU Spikes Protection gives processes equal access to the CPU.
    • WEM 1909 and newer have an option for Auto Prevent CPU Spikes.
    • From Hal Lange: “CPU Usage Limit should never be set to higher a percentage than one CPU. This will keep a single threaded application from thrashing a CPU.  Example: if 2 CPU’s are available, the CPU setting should not be set above 49%, if 4 CPU’s are available, the CPU setting should not be set above 24%”
    • Hal Lange demonstrates Citrix WEM Performance Optimizations in a YouTube video.
  4. Other tabs on the right let you manually specify CPU priority and/or clamping.

    • CTX230843 WEM protection and Skype for Business + Real Time Optimization Pack has a list of processes that should be excluded from WEM CPU Spikes protection.
    • From CTA Chris Schrameyer WEM – CPU LOGGING: WEM does not provide any built-in logs to determine when a CPU Spikes Protection action is taken. It would be nice to know what processes are often limited, so we can then add them to a CPU Clamping policy or identify why they are using so much CPU.
  5. On the top left, click the Memory Management node. In the right pane, you can enable Optimize Memory Usage for Idle Processes to periodically reclaim memory from running processes. This feature tells processes to flush their memory to disk. In other words, you’re trading memory for disk.

    1. WEM 2206 adds an option for Do Not Optimize When Total Available Memory Exceeds (MB). In other words, WEM does not optimize memory until available memory drops below this value.
    2. WEM 2206 adds a Memory Usage Limit for Specific Processes. Dynamic means the process memory is not limited until available memory is low.
  6. On the top left, click the I/O Management node. On the right, you can prioritize process IO.
  7. On the top left, click the Fast Logoff node. In the right pane, enabling Fast Logoff disconnects a session immediately, and runs logoff processes in the background.
  8. WEM 2003 and newer have a Citrix Optimizer feature. If you enable it, then the WEM Agents will disable services and scheduled tasks according to the settings in the template. WEM comes with built-in templates, or you can add your own. Only one template can be assigned to an operating system version.
    • WEM 2012 and newer have an option to Automatically select Templates to Use.
    • Newer versions of WEM have newer templates.
    • The Administration > Agents section adds a Process Citrix Optimizer action to each agent.
  9. WEM 2112 and newer have a Multi-session Optimization feature that lowers the priority of processes running in disconnected sessions.

Security

  1. Click the Security workspace.
  2. On the top left, click the Process Management node.
  3. In the right pane, in the Processes Management tab, enable Process Management. The other tabs are grayed out until you check this box.

    • You can BlackList processes. There’s also a WhiteList, but once something is added to the WhiteList, then all other processes are blocked.
  4. On the top left, click Application Security.
  5. You can use the top-left sub-nodes to configure AppLocker. See Application Security at Citrix Docs.

    1. If you click the Executable Rules sub-node, on the bottom right is a button to Add Default Rules.
    2. If you edit a rule…
    3. You can assign the rule to a user group.
    4. The list of user groups comes from Active Directory Objects (workspace on bottom left) > Users.
    5. On top of the right pane, set Rule enforcement to On or Audit.
    6. In the ribbon is a button to Import AppLocker Rules that were exported from a group policy.
    7. The other sub-nodes follow the same configuration pattern.
  6. WEM 2112 and newer have a Privilege Elevation feature under the Security workspace. You might have to scroll down to find it. On the right, check the box for Process Privilege Elevation Settings. Notice the setting for Do Not Apply to Windows Server OSs.

    1. On the left, click Executable Rules under Privilege Elevation. Then on the bottom right click Add Rule.
    2. Give the rule a name and select an assignment.
    3. There are options to restrict the elevation to specific parameters. For example, you can restrict cmd.exe so it can only elevate specific scripts. Click Next.
    4. Browse to the executable file and click Create.
    5. CTP David Wilkinson has more details on this feature.
  7. WEM 2203 adds a Self-elevation feature that lets users manually run processes elevated. See Citrix Docs for details.

  8. WEM 2006 adds Process Hierarchy Control, which lets you restrict or allow a parent process from launching specific child processes. See Citrix Docs for configuration details.

    1. On the agent side, you must enable Process Hierarchy Control by running elevated AppInfoViewer.exe from C:\Program Files (x86)\Citrix\Workspace Environment Management.
    2. Click Enable Process Hierarchy Control.
    3. Acknowledge that a restart is required.
  9. WEM has an audit log of the security features at Administration workspace > Logging node > Agent tab.

Policies and Profiles

  1. The Policies and Profiles workspace (bottom left) has four nodes on the top left.
  2. In the Environmental Settings node (top left), in the right pane, you can enable Environmental Settings, and configure restrictions that are usually configured in group policy. Peruse the various tabs on the right. Administrators can be excluded from these restrictions.
  3. The Environmental Settings within the WEM Administration Console are per-machine, not per-user. This means that, by default, all the settings configured inside of a Configuration Set apply to every non-admin user that logs into that particular Agent machine. In order to have different Environmental Settings apply to different users/user groups, they would need to be applied to a separate WEM Agent machine, and all the settings would need to be configured inside a separate Configuration Set to which the WEM Agent Machine is bound. Source = CTX226487 Guidance on configuring WEM settings per user/user groups.
  4. If you switch to the Citrix Profile Management Settings node, you can use WEM to configure Citrix Profile Management. See the Citrix Profile Management post for details on a recommended configuration.

    • Newer Profile Management features requires newer Virtual Delivery Agents (VDA).
    • WEM 2106 and newer with UPM 2106 and newer have the Accelerate Folder Mirroring setting on the Synchronization tab.
    • WEM 2103 and newer with UPM 2103 and newer have Streamed User Profiles > Enable Profile Streaming for Folders, which should speed up logons.
    • WEM 2103 and newer with UPM 2103 and newer have Advanced Settings > Enable multi-session write-back for profile containers, which applies to both UPM Profile Containers and Microsoft FSLogix Profile Containers. WEM 2209 adds OneDrive container.
    • WEM 2103 and newer with UPM 2103 and newer have Profile Container Settings > Enable Local Cache for Profile Container.
    • WEM 2009 and newer have the Profile Container Settings tab that lets you store the entire profile in the container.
    • WEM 2003 and newer can configure the multi-session write-back for FSLogix Profile Container feature in VDA 2003 and newer.
    • WEM 1909 and newer can configure UPM 1909 features, including Migrate user store.
    • WEM 1906 and newer can configure UPM 1903 features, including Enable Profile Container on the Synchronization tab.
    • WEM 1808 and newer can configure UPM 1808 features, including Outlook Search Index Roaming on the Advanced Settings tab.
    • WEM 4.4 and newer can configure UPM 5.8 and 7.15 features, including Enable Logon Exclusion Check.
    • WEM 4.2 and newer can configure UPM 5.5 and 5.6 features, including: Active Write Back Registry, NTUSER.DAT Backup, and Default Exclusion Lists.
  5. If you use WEM to configure UPM settings, but the settings are not applying to the WEM Agent, then see Citrix CTX219086 Some UPM or WEM Agent parameters may not be applied by the agent after switching from GPO settings to Workspace Environment Management settings.
  6. In the right pane, the File System tab has a useful Profile Cleansing button to remove excluded folders from an existing UPM profile share. This function might not be necessary if you enable Logon Exclusion Check.

    • Adjust the Profiles Root Folder, click Scan Profiles Folder, and then click Cleanse Profile(s).
  7. To configure folder redirection, on the top left, click Microsoft USV Settings.
  8. On the right, on the Roaming Profiles Configuration tab, check the box to Process User State Virtualization Configuration.
  9. Then switch to the Folder Redirection tabs, and configure them as desired.

WEM Agent Group Policy

  1. In the WEM Download, go to the \Workspace-Environment-Management-v-2303-01-00-01\Agent Group Policies\ADMX folder.
  2. Copy the .admx file, and the en-US folder to the clipboard.
    • In WEM 4,3, 4.4, and 4.5, the .admx file is suffixed with “v4.3”.
    • In WEM 1808, the .admx file is suffixed with “v1808”.
    • WEM 4.6, WEM 4.7, WEM 1903 and newer do not include the version number in the .admx file name.
  3. Go \\MyADDomain.com\sysvol\MyADDomain.com\Policies.
  4. If you have a PolicyDefinitions folder here, then paste the .admx file and folder.

    • If you don’t have PolicyDefinitions in Sysvol, then instead go to C:\Windows\PolicyDefinitions, and paste the .admx file and folder there.
  5. Look for older versions of the .admx and .adml files (in the en-us subfolder), and delete them.
    • In WEM 4.6, WEM 4.7, WEM 1903 and newer, the .admx and .adml files no longer have a version designation, so remove any .admx and .adml files that have a version number.
    • The WEM 1808 .admx and .admx files have v1808 in their names, so remove any .admx and .adml files that don’t have a version number.



  6. Edit a GPO that applies to the VDAs that will run the WEM Agent.
  7. In WEM 1906 and newer, go to Computer Configuration | Policies | Administrative Templates | Citrix Components | Workspace Environment Management | Agent Host Configuration.
    • In WEM 1903 and older, go to Computer Configuration | Policies | Administrative Templates | Citrix | Workspace Environment Management | Agent Host Configuration.
  8. On the right, double-click Infrastructure server.
  9. Enable the setting, enter the FQDN of the WEM server (or load balanced name), and click OK. Note: It must be FQDN.
  10. In WEM 4.3 and newer, assign Agents to a Configuration Set (formerly known as Site). In the WEM Administration Console, go to Active Directory Objects workspace (bottom left) > Machines node (top left), and in the right pane, add an OU or individual machines.
  11. It’s possible that an Agent might register with multiple Configuration sets. You can review the registrations at Administration workspace (bottom left) > Agents node (top left) > Registrations tab (right pane).
  12. It also might show you Agents not registered with any Configuration Set. Add the Agent to Active Directory Objects > Machines.
  13. If WEM 4.2 or older:
    1. You can configure the WEM Agents to connect to a non-default WEM site by editing the Site Name GPO setting.

Install/Upgrade WEM Agent

For command line unattended installation of WEM Agent 1909, see Alain Assaf at Citrix Discussions.

  1. If App Layering, Citrix recommends installing the WEM Agent in the Platform Layer.
    • If you are installing the WEM Agent in a App Layer, see George Spiers to workaround an issue with the Netlogon service in a Platform Layer that has the Provisioning Services Target Device software installed.
  2. Use registry editor to confirm that the WEM GPO has applied. Look for HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Norskale\Agent Host\BrokerSvcName.
  3. In VDA 2012 and newer, the WEM Agent is included with the VDA installer; however, this install method has been deprecated. You can instead install it separately as detailed in the next step.

  4. On a VDA Master machine, run Citrix Workspace Environment Management Agent.exe from the downloaded WEM 2303 (aka 2303-01-00-01) installation files.
  5. In the Citrix Workspace Environment Management Agent window, check the box next to I agree to the license terms and click Install.
  6. In the Welcome to the Citrix Workspace Environment Management Agent Setup Wizard page, click Next.
  7. In the Destination Folder page, click Next.
  8. In the Deployment Type page, select On-premises Deployment and click Next.
  9. In the Infrastructure Service Configuration page, change the selection to Skip Configuration since you’ve already configured the group policy. Click Next. Note: In WEM 1912 and newer, the cache synchronization port changes from 8285 to 8288.
  10. In the Advanced Settings page, if this machine will be used with Citrix Provisioning and has a Provisioning cache disk, then you can optionally move the WEM Cache to the Provisioning cache disk. Click Next. WEM Agent 2012 and newer have some enhancements for non-persistent machines. See Prerequisites and recommendations and Agent startup behaviors at Citrix Docs.
  11. In the Ready to install Citrix Workspace Environment Management Agent page, click Install.
  12. In the Completed the Citrix Workspace Environment Management Agent Setup Wizard page, click Finish.
  13. In the Installation Successfully Completed window, click Close.

WEM Agent Cache

  1. After installation, check the registry under HKLM\System\CurrentControlSet\Control\Norskale\Agent Host to verify your command line switches applied correctly.

  2. WEM Agent 2012 and newer have some enhancements for non-persistent machines. See Prerequisites and recommendations and Agent startup behaviors at Citrix Docs.
  3. In WEM Agent 1909 and newer, the WEM Agent installation path is now C:\Program Files (x86)\Citrix\Workspace Environment Management Agent instead of C:\Program Files (x86)\Norskale\Norskale Agent Host and you might have to modify your WEM Agent Cache Refresh scripts with the new path. See CTP James Kindon Citrix WEM Updated Start-Up Scripts for more details.
  4. Citrix CTX219839 How to Enable Debug Logging on Workspace Environment Management Agent manually, if no connectivity to Broker exists. Set AgentDebugModeLocalOverride and AgentServiceDebugModeLocalOverride to 1. The Norskale Agent Host Service Debug.log file will be written to %ProgramFiles(x86)%\Norskale\Norskale Agent Host. The Agent Log file will be written to the User Profile (i.e. under %UserProfile%).
  5. Srinivasan Shanmugam at WEM Agent v4.5 Upgrade Issues at CUGC mentioned that you might have to delete the upgraded Agent’s local database.
  6. Optionally, you can pre-build the Agent Cache by running AgentCacheUtility.exe, which is located in C:\Program Files (x86)\Citrix\Workspace Environment Management Agent (fresh WEM Agent 1909 and newer) or in C:\Program Files (x86)\Norskale\Norskale Agent Host.

  7. It needs the following switches:
    -refreshcache -brokername:MyWEMServer
  8. From Hal Lange: “AgentCacheUtility does except short values (Eg AgentCacheUtility -r -b:)  the broker name should always be in FQDN since this does use Kerberos for the authentication.”

  9. You can also use the WEM Administration Console at Administration workspace (bottom left), Agents node (top left), to refresh the cache. The Synchronization column indicates if the cache is up to date or not. It takes a few minutes to update.
  10. From Hal Lange: “Need to optimize the client by running ngen for .NET optimizations in the x64 and x86 directories. These commands will help optimize ANY .NET application installed on the system 
    C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
ngen.exe update
ngen.exe eqi 1
ngen.exe eqi 3
  11. Antivirus – C:\Program Files (x86)\Citrix\Workspace Environment Management Agent or C:\Program Files (x86)\Norskale\Norskale Agent Host must be excluded from Antivirus scanning. Or exclude Citrix.Wem.Agent.Service.exe; Norskale Agent Host Service.exe; VUEMUIAgent.exe; Agent Log Parser.exe; AgentCacheUtility.exe; AppsMgmtUtil.exe; PrnsMgmtUtil.exe; VUEMAppCmd.exe; VUEMAppCmdDbg.exe; VUEMAppHide.exe; VUEMCmdAgent.exe; VUEMMaintMsg.exe; VUEMRSAV.exe.
  12. After Agents are installed, the Administration workspace (bottom left), Agents node (top left), shows the list of Agents, allowing you to perform actions against an Agent. For example, if UPM settings are not applying to your Agents, you can right-click the Agent, and click Reset Profile Management Settings. WEM 1912 and newer let you Reset Actions. You might have to click the Refresh button on the bottom right. See Workspace Environment Manager UPM at Citrix Discussions.
  13. If you use WEM to configure UPM settings, but the settings are not applying to the WEM Agent, then see Citrix CTX219086 Some UPM or WEM Agent parameters may not be applied by the agent after switching from GPO settings to Workspace Environment Management settings.  Delete the machine cache, which is at the following registry location: 
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Norskale\Agent Host\UsvMachineConfigurationSettings
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Norskale\Agent Host\UpmConfigurationSettings

    This will force WEM to re-apply the per-machine settings (Microsoft USV or Citrix UPM settings, respectively).

  14. WEM Cache tends to break often. See CTP James Kindon Citrix WEM Cache Problems…. Again for a script to reset the cache periodically.
  15. CTP James Kindon describes the WEM Client Side Tools including: Log Parser, Resultant Actions Viewer, VUEMAppCMD, Manage Printers, Manage Applications, and Help Desk Tools.

WEM Agent on Citrix Provisioning Target Device

From Citrix Discussions: create a computer startup script that deletes the WEM cache and refreshes it:

net stop "Citrix WEM Agent Host Service" /y
net stop "Norskale Agent Host Service" /y
del D:\WEMCache\ /S /F /q
net start "Citrix WEM Agent Host Service"
net start "Norskale Agent Host Service"
net start "Netlogon"
timeout /T 45 /nobreak
"C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\AgentCacheUtility.exe" -refreshcache -brokername:XXXX
"C:\Program Files (x86)\Norskale\Norskale Agent Host\AgentCacheUtility.exe" -refreshCache -brokerName:XXXX

From Julian Mooren Citrix Workspace Environment Management with PVS – Synchronization State “Unknown”: For Citrix Provisioning, schedule a task to run the following commands at Target Device boot (Trigger = At Startup).

"C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\AgentCacheUtility.exe" -refreshcache
"C:\Program Files (x86)\Norskale\Norskale Agent Host\AgentCacheUtility.exe" -refreshcache

From CTA David Ott at Using Citrix Workspace Environment Management to Redirect Folders via Symbolic Links – Speed Up Logon: before shutting down your maintenance/private mode vdisk to re-seal, kill the Citrix WEM Agent Host Service or Norskale Agent Host Service. For whatever reason if you don’t do this it can cause your vms in standard mode to take an obscenely long time to shutdown.

Base Image Script Framework (BIS-F) automates many image sealing tasks, including tasks for Workspace Environment Management. The script is configurable using Group Policy.

Monitoring

  1. In the WEM Administration Console, the Monitoring workspace (bottom left) lets you see Logon Time and Boot Time reports.
  2. Double-click a category to see more info.

  3. Configuration node (top left) lets you configure Work Days Filtering for Login/Boot Time Reports.
  4. WEM 2203 adds a Profile Container Insights report for both FSLogix and UPM Profile Containers.
  5. When you make changes in the console, if agents are already installed, you can right-click the agent icon (by the clock), and Refresh.
  6. You can also go to the Administration workspace (bottom left) > Agents node (top left). In the right pane, right-click one or more Agents, and click the Refresh options.
  7. WEM 1811 and newer periodically run UPMConfigCheck every day, or whenever the Norskale Agent Service restarts. The Administration > Agents node in the WEM Console has a visual indicator of the UPMConfigCheck results. For status details, check the file C:\Windows\Temp\UPMConfigCheckOutput.xml on each WEM Agent Machine.

WEM Actions Configuration

WEM Actions are similar to Group Policy Preferences.

The general process is as follows:

  • Create the Actions
  • Optionally create Action Groups (WEM 1906 and newer)
  • Add AD user groups to the WEM Console.
  • Assign Actions or Action Groups to user groups. Use Conditions and Rules to perform the Action (or Action Group) for only a subset of machines or users in the user group.

Create Actions

  1. In the WEM Console, use the Actions workspace to map drives, map printers, create shortcuts (Applications), set registry keys, etc. Each Action type is a separate node.
  2. WEM 1909 and newer can Migrate or Import your Group Policies to WEM. CTP James Kindon at Migrating GPO settings to WEM explains this feature in detail.
    1. In Group Policy Management Console, back up the GPOs that you want to import to WEM.
    2. Go to the GPO Backup folder and zip everything.
    3. In WEM Console, go to Actions > Group Policy Settings and click Import.
    4. WEM 2209 and newer let you Import Registry File.
    5. WEM 2012 and newer let you edit the imported group policies.
    6. It seems to be a registry editor that doesn’t use ADMX templates.
  3. On the left, select an Action Type. In the right pane, click the Add button to add actions. These Actions are self explanatory.
  4. Some Actions, on the Options tab, have a Self-Healing option. To optimize performance, WEM only applies an action once. The Self Healing option causes it reapply at every logon.
  5. Network Drives have no field for selecting a drive letter. Instead, you configure the drive letter later when assigning the action as detailed below.
  6. External Tasks are scripts that are triggered at user logon, reconnect or other triggers. WEM 2203 adds triggers for Process start and Process end. WEM 2009 adds triggers for Disconnect, Lock, and Unlock.
  7. Applications (shortcuts)
    1. In the Actions pane, Applications have no option for placing a shortcut on the Desktop. Instead, you configure shortcut placement later when assigning the action as detailed below.
    2. WEM 4.6 and newer let you pull icons from a StoreFront store.

    3. Arjan Mensch at Powershell Module for Citrix WEM – Part 3 – EnvironmentalSettings and MicrosoftUsvSettings from GPO and much, much more provides a PowerShell Module that can do several things to help setup WEM, including reading a bunch of shortcuts (e.g. from Start Menu), and converting them to an .xml file that can be imported into WEM. This simplifies Applications configuration.
    4. To prevent applications (shortcuts) from being created if the application isn’t installed, go to Advanced Settings > Configuration > Agent Options, and check the box next to Check Application Existence in the Extra Features section.
    5. To clean up extra shortcuts, go to Advanced Settings > Configuration > Cleanup Actions, and check the boxes in the Shortcuts deletion at startup section. Also see CTP James Kindon Citrix WEM, Modern Start Menus and Tiles.
    6. After you create Applications (Shortcuts), and assign them, on the agent, there’s a Manage Applications tool that lets users control where shortcuts are created, including pinning to Taskbar and Start Menu.

    7. Applications can be placed in Maintenance Mode. Edit an Application, and find the Maintenance Mode setting on the Options tab.
    8. This causes the icon to change, and a maintenance message to be displayed to the user.

    9. The Applications node has a Start Menu View tab on the right.
  8. For the Printers Action, in the ribbon, there’s a Import Network Print Server button.

  9. For the Registry Entries Action, in the ribbon, there’s an Import Registry File button.

    • If Registry Actions are not applying, delete HKEY_CURRENT_USER\Software\VirtuAll Solutions\VirtuAll User Environment Manager\Agent\. (Source = Registry Entries not applied to users at Citrix Discussions)
  10. For File System Operations, each Action has an Options tab that lets you set the Type of Action.
  11. For File Associations, “Command” is just the parameters without the executable.
  12. CTP James Kindon at File Type Association with WEM and SetUserFTA explains how to use WEM to run Christoph Kolbicz’s SetUserFTA utility to reliably set file type associations on Windows 2012 and newer.
  13. For variables that can be used in the Actions configurations, see CTP James Kindon WEM Variables, Dynamic Tokens, Hashtags and Strings.
  14. The WEM Cloud Service has native support for importing group policies and converting them to WEM Actions and other WEM configurations. See CTP James Kindon Migrating GPO settings to WEM.
  15. WEM 1906 and newer let you combine multiple Actions into an Action Group. Then you can later assign the entire Action Group to a user.

    1. Create an Action Group and name it.
    2. Double-click the Action Group to show the actions on the bottom.
    3. On the bottom, move Actions from the Available box to the Configured box.
    4. For more info, see Action Groups at Citrix Docs.

Create Conditions and Rules

  1. Once the Actions and Action Groups are created, you then need to decide under what conditions the Actions are performed. Go to the Filters workspace (bottom left).
  2. On the top left, switch to the Conditions node.
  3. In the right pane, create Conditions. One or more Conditions are later combined into a Rule.
  4. One of the interesting Conditions is User SBC Resource Type, which lets you run Actions for either Published Desktop or Published Application.

  5. CTP James Kindon at WEM filter conditions on OU and IP Address at Citrix Discussions says that the Active Directory Path Match condition requires a * at the end of the path.
  6. Then switch to the Rules node (top left) and create Rules in the right pane.
  7. If you add (by clicking the right arrow) multiple Conditions to a Rule, all (AND) Conditions must match. There doesn’t appear to be an OR option. The Rules are used later when assigning an Action to a user group.

Add AD Groups to WEM Console

  1. Go to the Active Directory Objects workspace (bottom left).
  2. With the Users node selected on the top left, in the right pane, add groups and/or users that will receive the Action assignments.

Assign Actions to User Groups

  1. Go to the Assignments workspace (bottom left) > Action Assignment node (top left).
  2. In the right pane, initially the bottom half is empty. Double-click a group to show the Actions that are available for assignment. WEM 1808 and newer has a built-in Everyone group.
  3. Move an available Action or Action Group from the left to the right. This assigns the Action (or Action Group) to the user group.
  4. You will be prompted to select a Filter, which contains one or more Conditions.
  5. When you move a Network Drive to the right, you’re prompted to select a drive letter.

    • The list of drive letters is restricted based on the configuration at Advanced Settings workspace (bottom left) > Configuration node (top left) > Console Settings tab (right pane).
  6. Back in the Assignments workspace, on the right, some Actions have additional options that you can right-click. For example, you can create shortcuts on the desktop.

Actions Troubleshooting

WEM caches Actions executions under HKEY_CURRENT_USER\SOFTWARE\VirtuAll Solutions\VirtuAll User Environment Manager\Agent\Tasks Exec Cache. Sometimes clearing these keys and values will fix Actions not applying.

CTP James Kindon at Selective Deletion of the WEM Actions Tracking Cache wrote a PowerShell script to selectively clear these registry keys and values.

Modeling Wizard

  1. In the Assignments workspace, you can use the Modeling Wizard node (top left) to see what Actions apply to a particular user.

Client Side Tools

CTP James Kindon describes the WEM Client Side Tools including: Log Parser, Resultant Actions Viewer, VUEMAppCMD, Manage Printers, Manage Applications, and Help Desk Tools.

Transformer

In WEM 4.1 and newer, you can enable Transformer, which puts the WEM Agent in Kiosk mode. Users can only launch icons (e.g. Citrix icons). Everything else is hidden. This is an alternative to Receiver Desktop Lock. The Transformer interface is customizable. Note: desktops currently will not auto-launch from Transformer.

  1. In the WEM Console, there’s a Transformer Settings workspace (bottom left) with two nodes on the top left: General and Advanced.
  2. Enable Transformer, and point it to your StoreFront URL. Note, this applies to all users and all agents in this WEM configuration set. You should probably have a new Configuration Set just for Kiosk devices.
  3. Other settings on the General Settings tab let you customize the appearance, and specify an unlock password. You probably want to disable the Clock. The Navigation Buttons are browser navigation.
  4. Transformer can be unlocked by pressing Ctrl+Alt+U and entering the unlock password.
  5. On the Site Settings tab, you can add website URLs that can be launched from within Transformer.
  6. At the top of the Transformer window is a Sites icon that lets you go to the sites listed in the WEM Console.
  7. The Advanced node lets you configure Transformer to launch a process other than a browser.
  8. The Advanced & Administration Settings tab lets you hide features from Transformer.
  9. To prevent users from accessing the local system, consider checking Hide Taskbar & Start Button.
  10. You probably want Log Off Screen Redirection to redirect users to the logon page when StoreFront logs off.
  11. The Logon/Logoff & Power Settings tab lets you configure the WEM Agent to autologon as a specific account. Transformer then displays the StoreFront webpage where the user enters his or her credentials.

539 thoughts on “Workspace Environment Management (WEM) 2303”

  1. Hi Carl,
    Do you know how to import GPP that is part of Control Panel Settings like “Regional Options”, “Folder Options” and so on ? Trying to import backup file and migrate option from WEM didn’t give me that functionnality. Unless to find out all the registry key and import them one by one .
    Thanks

    Reply

  2. I have upgraded from 1912 to 2203. I noticed that when I go to Administrator -> Users. The “Clear Expired Records” is greyed-out. Has anyone experienced this?

    Reply

  3. Hi Carl, we recently migrate to Cloud and follow all your recommendations but for some reason seems WEM is not applying settings untill first user connects, hence first user get no settings and profile, had to disconnect and reconnect, next sessions everything seems to run fine, have see anything like this?

    Reply

  4. dead link in this site : Welcome to Citrix Workspace Environment Management (WEM) from CUG is MIA.

    Reply

  5. We use FSLogix for profiles and Id like to pull a report out of WEM for folks where their used profile space is low. I can see it in the WEM console under Profile and Container insights and there is no way to export a report direct from there. Id like to put the user names into a txt document or something to have PS mount the drive and delete some garbage data without having to manually make a list of all of the user names. Anyone know what SQL table or tables I might need to query to get that info?

    Reply

  6. hello Carl, do you know if there is a possibility to add Authenticated Users to AD objects in WEM console? didn’t find a way yet, only Everyone group is set here in default. Thanks R.

    Reply

  7. Hi, I have a question which I didn’t get much help with yet from Citrix support.
    We are using WEM for kiosk devices in meeting rooms, which a user would login to and see their desktops (presented via F5 screen rather than storefront.) The issue I have is that its always asking the user to open/save the ica file, which is already associated.
    Would you know which frame is being used by the Citrix Workspace Environment browser? I believe its IE thats why the Edge GPOs do not take affect.
    WEM 2206.1.0.1
    Thank you

    Reply

    1. Are you using Transformer? It’s a known issue that Citrix never fixed. You could instead buy the original product ThinKiosk.

      Reply

      1. Hi Carl,

        Thanks very much for your response. I am indeed, that’s good to know. I’ll take a look at that.

        Thanks again.

        Reply

  9. Issue Installing Citrix Workspace Environment Management Agent on Provisioning Master Image: 0x900421f7 – Unknown Error

    This while processing “Microsoft Edge WebView2 Runtime” in Setup Progress from WEM-Agent.

    Setup Failed

    Any Idea?

    Reply

  10. Hi Carl,

    Can you advise on the load balancing persistence settings for WEM as per Citrix advice:

    “Session persistence is required for the connection between administration consoles and the infrastructure service. (Session persistence between the agent and the infrastructure service is not required.) We recommend that you directly connect each administration console to an infrastructure service server rather than using the VIP.”

    I cant find any decent suggestions for this.

    Thanks

    Reply

  11. Hello Carl and comment readers,

    first and foremost thank you very much for this detailed information about WEM. Any help is appreciated with the following issue.

    Problem description:
    When executing ‘Upgrade WEM Database’step 8. from https://www.carlstalhood.com/workspace-environment-management/#upgradewem the result is:
    ‘Database Upgrade – Error while Upgrading the specified Database!’

    Log “C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\Citrix WEM Database Management Utility Debug Log.log” says:

    ‘Exception -> DbUpgradeRequestExecutor.Execute() : Violation of PRIMARY KEY constraint ‘PK_VUEMCitrixOptimizerTemplatesHash_ContentId’. Cannot insert duplicate key in object ‘dbo.VUEMCitrixOptimizerTemplatesHash’. The duplicate key value is (1).
    Cannot insert the value NULL into column ‘IdContent’, table ‘CitrixWem.dbo.VUEMCitrixOptimizerTemplatesContent’; column does not allow nulls. INSERT fails.’

    Additional informations:
    System Infos:
    WEM Server OS = Windows Server 2019 Standard version 1809 build 17763
    .3650
    Workspace Environment Management Console version 1912.1.0.1

    Thanks in advance and kind regards
    Bernd

    Reply

      1. I tried upgrading from WEM 1912.1.0.1 to the current version 2209. What intermediate version would you suggest?

        Reply

          1. Thanks for your help. I tried WEM version 2003 , 2005 , 2009 , 2012.

            Same Error and Log “C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\Citrix WEM Database Management Utility Debug Log.log” says:

            Exception -> DbUpgradeRequestExecutor.Execute() : Cannot insert the value NULL into column ‘TaskId’, table ‘CitrixWem.dbo.VUEMSpecialTasks’; column does not allow nulls. INSERT fails.
            The statement has been terminated.

            I will create a ticket with Citrix support.

    2. Hi. I am facing the same issue upgrading af Citrix WEM Database from 1912.1.0.1 to 2209. Did you find a solution for this problem.

      Reply

  12. This may be very elementary. I do not understand by what mechanism the endpoint is locked down to kiosk mode. I assume it is not running the WEM agent, how is WEM aware of it before it connects to a VDA machine that is running the agent? Where am I getting confused? Thanks for any clarification.

    Reply

  13. Hello carl,

    We upgraded from WEM 1912 to 2203 and I have actions that no longer work.
    Example a link to an excel file that has become like this:
    J:\Extraction\Reporting-script\Fiche-renta\Fiche_de_rentabilité.xls

    While in the WEM console it’s fine
    J:\Extraction\Reporting-script\Fiche-renta\Profitability sheet.xls

    To solve the problem from the user session, the only way is to WEM Agent> Manage Application> Find Application> Right click update shortcut and the link is functional again.

    For information, I never note a file name in yyyy_yyyy, either it’s spaces or dashes between the file names

    Why ? or watch?

    Reply

  14. hi, just have an issue with application security(applocker), i have tested it and after that disabled the function, but on the vda the settings were not updated. so program launch is now restricted. but when i start the local gpo applocker is empty and not configured, but still blocking.. any ideas? kind regards

    Reply

  15. Is there anyway to create an application action for an app not installed. The console does not run on my image it is on a jump server and not all apps are installed on this server that are on my image/

    Reply

  16. Hi There,

    short question.
    Should be the workers turned off during the WEM update (2206 ->2209)? Or Workers can be online, and users can be logged in during the update process?
    Thanks!

    Reply

  17. Hello Carl,
    thanks for this article.

    However, I have never understood how to map printers based on clientnames. I consider the instructions with the Printer.XML to be very time-consuming.
    Is there a way to map printers based on the clientname of thin clients that are members of an AD group or listed in a simple CSV file?

    Many Thanks,

    René

    Reply

  18. Hi Carl,

    I’m looking for extra info on the agent cleanup actions. Specifically if the delete desktop shortcuts only apply for WEM created shortcuts or for anything that is already on the desktop (other GPOs created shortcuts or files user put on their desktops)

    Thank you.

    Reply

  19. Hi Carl,

    I have implemented the Citrix WEM in my existing environment where I am using user Personalized Layer. The issue is when users login into VDI the UPL drive is loading as Temp Profile and the login process is very slow. Sometimes the user’s session are getting disconnected while logon.

    Please note that in WEM we are using CPU, Memory, and I/O management only.

    Any help would be appreciated.

    Reply

  20. if you prevent access to cmd, powershell, and registry in a hardening situation in windows. Does this impact WEM external task? Being they run under the user context I am curious how windows treats it while running the action that would need to make registry changes for example or an external task that excites a script. I need to lab it up and test it to know for sure. But I’m curious if anyone has experienced this? Or if there is any docs or warning around hardening an image and the impacts of use WEM

    Reply

  21. The CUGC WEM Advanced Guides are not available anymore as the website did a move 🙁
    “For configuration guidance, see CTP James Kindon and CTA Hal Lange at WEM Advanced Guidance – Part 1 and WEM Advanced Guidance–Part 2: User Interaction at CUGC.”
    Maybe someone has a saved version?

    Reply

  22. Is it possible to assign specific user to a client where we use transformer to restrict clients? We plan to roll-out a Citrix application to multiple clients where we already use WEM transformer but each client would need a specific user.

    Reply

  23. In Citrix Cloud and Using WEM I’m creating configuration sets with AD groups of USERs (based on location of user) and a select group of VDI’s. Unfortunately, it appears I cannot use the same select group of VDI’s in multiple configuration sets. I need to set some registry entries based on user’s location to the same group of VDI’s

    Any suggestions as to best way around this ?

    Reply

    1. WEM Actions have filters. What filter option is missing that requires you to create a new configuration set?

      Reply

      1. That’s all the help I needed Carl. I had to figure out the filtering but can see now how filtering will allow me to avoid multiple config sets. I appreciate your note…

        Reply

      2. Thanks Carl – I figured out the filtering and can see now I don’t need multiple config sets.

        Reply

  24. Hi Carl,

    Do USV config settings apply to the Config Set, like Environmental settings do? I’m having a difficult time trying to find a way to filter which devices get the USV redirection settings within a config set. e.g. we have a config set using an OU to define its members, but we want to change USV settings for a set of servers within the config set, like for a delivery group, but am unable to get a working filter

    Reply

  25. Thank you for your work Carl. The pvs startup script or task should not be necessary starting from WEM 2012. See https://docs.citrix.com/en-us/workspace-environment-management/2012/whats-new.html “To ensure that the agent cache is up to date, the agent automatically recreates the cache in non-persistent environments.” and https://docs.citrix.com/en-us/workspace-environment-management/2012/install-and-configure/agent-host.html#agent-startup-behaviors “If the virtual machine is provisioned and the local database files are from the base image, the database files are automatically purged.”. I have removed my startup script after update to WEM 2103 and the synchronization is working well.

    Reply

  26. Hi Carl,
    I’m confused about VDA 2112 deployment with WEM feature. At configuring WEM Server with “test connection” I get an connection error. Looking at installation log I can see that the WEM server is tried to connect with port 80, but why. I cannot see a port 80 listening at the WEM infrastructure server. Where do I fail?
    Thanks, Stefan

    Reply

  27. Hey Carl, appreciate all your hard work, you are the best in the business.
    have an issue with WEM not allowing local client drive in Citrix session, ie local disk on PC X? enabled via Ctrix policy.. however with WEM enabled i lose this in explorer.
    would love to know if you had this problem, and if its a setting i am not seeing.
    cheers
    jr

    Reply

    1. Did you configure the UNCEnabled registry key to map client drives as drive letters instead of the default UNC? Is WEM configured to hide drive letters?

      Reply

  28. Question,

    Using WEM 2016 we present Microsoft Edge shortcut to the start menu.
    After we manually start Edge (or even pin to start) the shortcut disappears and only comes back after you refresh WEM in the system tray. Other applications work just fine….

    Reply

    1. Did you find a solution for this? We experience the same problem and cannot find a solution…. Drives me crazy.

      Reply

  29. Hi Carl,

    I hope you are well.

    How do we force a Device or OU to pick up a new configuration SET? We have already unlinked from the previous configuration set.

    Reply

  30. Hey Carl,

    I hope you can help us.

    We have changed to a new created configuration set to one of our VMs and we had to roll back to the working one and now it does not see the configuration set.

    Scenario – We changed to a “test_configuration set” – didn’t work as expected and changed back to “Working_configurationset” however it is still linked to the “test_configuration set” – How do I force it to see the “working_configurationset” again?

    Manu thanks!

    Reply

    1. In Active Directory Objects > Machines, remove the computer. Then add it to the other configuration set.

      Maybe the WEM Agent is caching. Try clearing the WEM Agent cache.

      Reply

  31. I have an issue with wem profiles cleansing. It seems that the profiles have too long paths and the cleansing tool fails with “error while scanning profiles!”. If I scan a single profile and remove the files with the longest paths everything works fine. Is there a workaround for this? We are running 1912 ltsr cu2.

    Reply

    1. Sakari, I’ll chime in here because I’ve encountered this a lot. Google Chrome in notorious for these really deep sub-folder trees for its data (with long strings of random characters for a single folder name). I believe the source of the problem is drive mapping and the context of the application. If the user’s profile is on a network drive like y:, mapped to \\servername\something\UPM_Profiles when a different application (like WEM) is trying to access those folders directly by UNC path the length is extended by 40 or more characters. I’m not certain how to solve it, but thought it would be helpful to know how these paths (which are too long to exist) were created.

      Reply

  32. We upgraded to WEM 2012 and the following folder
    “C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\DBSync” doesn’t exists anymore. Do you have any idea if this is normal behavior?

    Reply

    1. I’m guessing they removed this folder when they removed the older agent cache sync technology.

      Reply

  33. Hey Carl, have you seen issues where you disable the WEM splashscreen but it does not work, it still displays the splash screen on login?

    Thanks!

    Reply

    1. Only if the users of the physical desktop are Citrix licensed. Transformer is a feature specifically for physical desktops.

      Reply

  37. Carl, might be worth adding this to your documentation because it tripped me up. For the last few versions (2003 -> 2006 -> 2009 -> 2012) I’ve had to save the Infrastructure Configuration settings after upgrading the broker and DB. I brought it up with the WEM PM team and they said this is expected. I also noticed that neglecting to save the Infrastructure Configuration results in the Norskale service being set to disabled and not running.

    Reply

    1. Thanks for the suggestion. I’ve also seen this but I forgot to document it. It should be there now.

      Reply

      1. I had the same issue after upgrading the DB, I got an error when trying to connect to the console after the upgrade. You have to run the infrastructure configuration utility and just save the configuration again and that fixes it. It’s not in the documentation.

        Reply

  38. Hi Carl,
    I am struggling with applying network drives using WEM. It seems very flaky in that it works and then it stops working. I am using security groups to decide who gets which drives and assigning the drive to the group. I have enabled self-healing on the drives and process network drives is ticked. I had it working last week but for some reason it has stopped mapping them and I can’t figure what has happened. In the logs it says it can’t find a drive but I have definitely assigned the drive to the group. Do you have any suggestions I can try? Any help would be appreciated.

    Thanks.

    Reply

Leave a Reply to Carl Stalhood Cancel reply

Your email address will not be published. Required fields are marked *