Workspace Environment Management (WEM) 1909

Last Modified: Nov 23, 2019 @ 9:07 am

Navigation

This post covers Citrix Workspace Environment Management (WEM) versions 1909, 1906, 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.  The ONE caveat is to remove from the Always On Availability Group before upgrading.

Here is 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

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.

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.
    • According to Citrix Docs Upgrade a deployment, before upgrading the database that’s in a SQL Server Always On availability group, you must remove it from the availability group.
  5. You might have to run the WEM Infrastructure Service Configuration Utility on each Broker to point to the upgraded database.
  6. In-place upgrade the WEM Console. No special instructions.
  7. In-place upgrade the WEM Agents.

Install/Upgrade WEM Server (Broker Service)

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 3,000 users.

  1. Download Workspace Environment Management 1909 and extract it.
  2. If you are upgrading, run WEM Infrastructure Service Configuration Utility and record all settings. These settings might be wiped out during the upgrade.
  3. Run the downloaded Citrix Workspace Environment Management Infrastructure Services Setup.exe.
  4. Click Install to install the prerequisites.
  5. In the Welcome to the InstallShield Wizard for Citrix Workspace Environment Management Infrastructure Services page, click Next.
  6. In the License Agreement page, select I accept the terms, and click Next.
  7. In the Customer Information page, click Next.
  8. In the Setup Type page, click Next.
  9. In the Ready to Install the Program page, click Install.
  10. If you are upgrading, you might be prompted to restart applications.
  11. In the InstallShield Wizard Completed page, click Finish.
  12. 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.
  13. Firewall РEnsure firewall allows the following ports to/from the WEM Broker servers. See Citrix CTX101810 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 SQL
    • 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
  14. 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 SDK v4.7 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. According to Citrix Docs Upgrade a deployment, before upgrading the database that’s in a SQL Server Always On availability group, you must remove it from the availability group.
  4. On the WEM server, run Database Management from the Start Menu.
  5. If upgrading, in the ribbon, click Upgrade Database.
  6. 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.
  7. If your account is not a sysadmin on SQL, then enter a SQL account in the Database Credentials fields.
  8. Click Upgrade.
  9. Click Yes when asked to proceed.
  10. Click OK when prompted that database upgraded successfully.
  11. Click Finish to close the Database Upgrade Wizard.
  12. Close the WEM Database Management Utility.
  13. Restart the Norskale Infrastructure Service.

After the database is upgraded, run the WEM Infrastructure Service Configuration Utility to set the database connection settings again. Upgrading seems to wipe out 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 for Windows Communication Framework 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 same Advanced Settings tab, enter the vuemUser SQL password and .
  6. On the Database Settings tab, enter the database server name and database name.
  7. In the ribbon, click Save Configuration.
  8. Click Yes to restart the Broker Service.
  9. 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 SDK v4.7 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 for Windows Communication Framework 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 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 1909 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. Once you have multiple Configuration sets, you can use the drop-down to switch between them.
  6. A WEM Agent can only belong to one WEM Configuration set. Different Agents can belong to different WEM Configuration sets.
  7. 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).
  8. 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 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-1909-00-01-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 and CTA Hal Lange at WEM Advanced Guidance – Part 1¬†and WEM Advanced Guidance‚ÄďPart 2: User Interaction 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. On the Main Configuration tab, one option you might want to enable is Launch Agent for admins.
  4. Also consider enabling Launch Agent at Reconnect.
  5. In the right pane, on the Reconnection Actions tab, you can select which modules should be refreshed on reconnect.
  6. The Agent Options tab defaults to processing printers and drives asynchronously.
  7. Setting on these tabs are mostly self-explanatory. Feel free to change any as desired.
  8. The Service Options tab has a setting for Bypass ie4uinit Check. Enabling this might eliminate a 2 minute delay before WEM Agent starts.
  9. On the top left, in the Advanced Settings workspace, there’s a¬†UI Agent Personalization node.
  10. In the right pane, in the UI Agent Options tab, you can change the Agent skin, and Preview it.
  11. Other settings on this page let you hide the splash screen.
  12. 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.
  6. In the right pane, you can enable¬†Working Set Optimization¬†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.
  7. On the top left, click the I/O Management node.
  8. On the right, you can prioritize process IO.
  9. On the top left, click the Fast Logoff node.
  10. In the right pane, enabling Fast Logoff disconnects a session immediately, and runs logoff processes in the background.

Security

  1. In Workspace Environment Management 4.5 and newer, on the bottom left, click the Security workspace. In older WEM, stay on the Process Optimization 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.

  4. You can BlackList processes. There’s also a WhiteList, but once something is added to the WhiteList, then all other processes are blocked.
  5. In Workspace Environment Management 4.5 and newer, on the top left, click Application Security.
  6. You can use the top-left sub-nodes to configure AppLocker. See Application Security at Citrix Docs.
  7. If you click the Executable Rules sub-node, on the bottom right is a button to Add Default Rules.
  8. If you edit a rule…

    1. You can assign the rule to a user group.
    2. The list of user groups comes from Active Directory Objects (workspace on bottom left) > Users.
  9. On top of the right pane, set Rule enforcement to On or Audit.
  10. In the ribbon is a button to Import AppLocker Rules that were exported from a group policy. See Saadallah Chebaro Configure Citrix Workspace Environment Management Application Security for details.
  11. The other sub-nodes follow the same configuration pattern.

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.

    • 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.
    • WEM 4.4 and newer can configure UPM 5.8 and 7.15 features, including Enable Logon Exclusion Check.
    • WEM 1808 and newer can configure UPM 1808 features, including Outlook Search Index Roaming on the Advanced Settings tab.
    • WEM 1906 and newer can configure UPM 1903 features, including Enable Profile Container on the Synchronization tab.
    • WEM 1909 and newer can configure UPM 1909 features, including¬†Migrate user store.
  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-1909-00-01-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

  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. On a VDA Master machine, run Citrix Workspace Environment Management Agent Setup.exe from the downloaded WEM 1909 installation files.

WEM Agent 1909 or newer

The install instructions for WEM Agent 1909 and newer are different than the instructions for WEM Agent 1906 and older.

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

  1. In the Citrix Workspace Environment Management Agent window, check the box next to I agree to the license terms and click Install.
  2. In the Welcome to the Citrix Workspace Environment Management Agent Setup Wizard page, click Next.
  3. In the Destination Folder page, click Next.
  4. In the Deployment Type page, select On-premises Deployment and click Next.
  5. In the Infrastructure Service Configuration page, change the selection to Skip Configuration since you’ve already configured the group policy. Click Next.
  6. In the Advanced Settings page, if this machine will be used with Citrix Provisioning and have a Provisioning cache disk, then you can optionally move the WEM Cache to the Provisioning cache disk. Click Next.
  7. In the Ready to install Citrix Workspace Environment Management Agent page, click Install.
  8. In the Completed the Citrix Workspace Environment Management Agent Setup Wizard page, click Finish.
  9. In the Installation Successfully Completed window, click Close.
  10. Jump ahead to WEM Agent Common.

WEM Agent 1906 or older

This section is for WEM Agent 1906 and older.

  1. If you are installing the Agent on a Provisioning Services vDisk, there are a couple Agent Installer Switches that let you move the WEM cache file to the PvS cache disk:
    "\\fs01\bin\Citrix\WEM\Workspace-Environment-Management-v-1906-00-01-01\Citrix Workspace Environment Management Agent Setup.exe" /v"AgentCacheAlternateLocation=\"D:\WEMCache\""
  2. You can use the ARPSYSTEMCOMPONENT=1 switch to prevent the Agent from showing up in the Programs and Features list where it can be uninstalled.
  3. Citrix CTX218964 How To Secure a Citrix WEM Agent Installation in Cases Where Users are Local Administrators also details how to configure a group policy to prevent local administrators from stopping the Agent service.
  4. Click Install to install the prerequisites.
  5. In the Welcome to the InstallShield Wizard for Citrix Workspace Environment Management Agent page, click Next.
  6. In the License Agreement page, select I accept the terms, and click Next.
  7. In the Customer Information page, click Next.
  8. In the Setup Type page, click Next.
  9. In the Ready to Install the Program page, click Install.
  10. In the InstallShield Wizard Completed page, click Finish.

WEM Agent Common

  1. CyrillDaeniker at WEM 1906 – Citrix WEM User Logon Service adds 5 seconds to logon time at Citrix Discussions says that Citrix WEM User Logon Service adds 5 seconds to logon time.
  2. After installation, check the registry under HKLM\System\CurrentControlSet\Control\Norskale\Agent Host to verify your command line switches applied correctly.

  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. AntivirusC:\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. 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. 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. When you make changes in the console, if agents are already installed, you can right-click the agent icon (by the clock), and Refresh.
  5. 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.
  6. 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. 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.
  2. 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.
  3. 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. 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.
  7. For the¬†Printers Action, in the ribbon, there’s a Import Network Print Server button.

  8. 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)
  9. For File System Operations, each Action has an Options tab that lets you set the Type of Action.
  10. For File Associations, “Command” is just the parameters without the executable.
  11. 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.
  12. For variables that can be used in the Actions configurations, see CTP James Kindon WEM Variables, Dynamic Tokens, Hashtags and Strings.
  13. 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.
  14. 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.

424 thoughts on “Workspace Environment Management (WEM) 1909”

  1. Excellent article!

    Quick question, have you ever seen the WEM agent loading before the GPOs that assign the cloud connectors configuration? I’ve tried with everything including the latest software, and it still happens. Citrix support wants me to delay the application of the GPOs :/

    I tried to change the startuptype of the services to automatic (delayed) and that does not work.

    If I install the software with the cloud connectors set through the software, it works.

    Thanks!

    1. I usually apply computer-level GPOs to my master image to avoid any timing issues when the non-persistent machines boot.

  2. Carl, Can I run WEM 1808 or 1909 in XA 7.15? I see ambiguous requirements in the release notes about the naming conventions being interchangeable (CVAD or XA/XD) so I’m not sure what they mean by “any supported version of…” are the terms interchangeable, or is 4.7 the latest version that I can install?

    1. XA/XD was renamed to CVAD. Version 7.15 still has the XA/XD name. The latest WEM version should work fine on XA/XD 7.15.

  3. Test user logs in and eventviewer logs following error: “Error while Configuring Registry Security.” No exeptions or warnings in citrix wem agent log. Removed all assgned settings but still the same error. New userprofile same result. Is this a fals positive ? When i assign a regsitry key, it works.

  4. Hello Carl,
    Version 1909 constantly generate this error.” Error while Configuring Registry Security “for the user that logs in. In the citrix wem agent log there is no fault/exceptions.. For test i removed all the registry assigend to domain users and then the error is gone. The registry directly assigned to the test account does not generate an error. Is it a false positive?

  5. Hello, I have a question according the actions in WEM and I’m not able to find the information at the moment.
    I would like to ask in which order actions are applied during logon. For example first applications, second external tasks, etc. Is there any documentation about that?

    Thank you very much.
    Regards Michael

  6. Hi Carl,

    We have Citrix WEM as a cloud service for profile management and all the printers are mapped via WEM – Actions – Printers. But when the user login to the Citrix it is prompting message to “Trust the printer” and asking for admin credentials to install the printer and it gets installed if we supply admin credentials and gets disappeared after logoff. This issue is with out new Citrix cloud environment running VDAs in server 2016.

    We are currently in the process of migrating users from XA6.5 to Citrix cloud and all the printers were working in the XA6.5 environment. Not sure what we are missing in terms of printer mapping. This issue is with US region and we have similar setup for UK region where all the printers get mapped via WEM policies without issues.

    Your help is much appreciated!

    Thanks

      1. Yes it is multi user RDSH and we didn’t install the printer driver on the VDA machine. As I explained above, we have similar setup for UK region where we didn’t install any printer drivers to the VDA machine, but it still maps the printer to the user session.

        1. I think RDSH needs administrator permission to install drivers. Virtual Desktops don’t have that requirement.

          1. Hi carl

            I have tested installing the printers directly to the Server VDA and it is not prompting the admin credentials to install the printer on the user session and works fine. I couldn’t understand how it works in this way. It means I have to install all the printers on all server VDAs manually. Please could you confirm that whether it is right approach and what I am doing is correct.?

            Thanks
            RAV

  7. Hi Carl, we configured Application active setup through External Tasks but it is not working at user first logon but next time on wards it’s working fine. How to fix this ?

  8. Hi carl, we already created a new SQL db for WEM and i have to configure that db in WEM server , so which one(Create or upgrade ) i have to run in WEM Database Management Utility. ??

  9. Hi,

    after updating from stable 4.7 to 1906 a new nightmare is starting. The Management Server are stopping ever 24 hours. Means the norskale service is running but not answering.There are messages like this in the event id.

    ——————————–
    Faulting application name: Norskale Broker Service.exe, version: 4.7.0.0, time stamp: 0x5b3b2f06
    Faulting module name: adsldpc.dll, version: 6.3.9600.17415, time stamp: 0x545053e3
    Exception code: 0xc0000005
    Fault offset: 0x000000000001e554
    Faulting process id: 0x1380
    Faulting application start time: 0x01d4d35b74778845
    Faulting application path: C:\Program Files (x86)\Norskale\Norskale Infrastructure Services\Norskale Broker Service.exe
    Faulting module path: C:\Windows\system32\adsldpc.dll
    Report Id: d350f54c-4299-11e9-80fe-005056ad16f6
    Faulting package full name:
    Faulting package-relative application ID:
    —————————

    The Windows Server (W2K12R2) is fully patched but this doesn`t help :-(. The only thing is to restart the server. Restarting the Norskale Service did not help

    The WEM Client stopped to work, but the service is running. Try to restart with error “Failed to stop service. System.AggregateException: One or more errors occurred. —> Norskale.Common.Data.PortAlreadyInUseException: The requested port 49752 is busy”, but firewall port is definitly open. After downgrade to WEM Client 4.7 everything is good

    Any ideas ? The CITRIX Support is doing ….. nothing ūüôĀ

    Regards Claus-Michael

  10. Hi Carl we have Ivanti Environment Manager with none persistent VDI. The fast log off is not set under Log off tab. But when users log off the log off is fast. Are you aware of any Citrix settings where I can look at to stop this fast log off?

  11. Can WEM be updated directly from v4.6 to 1906 or are there intermediate update levels that need to be applied first?
    e.g.
    A) version 4.6 upgraded to version 1906
    or
    B) something like version 4.6 upgraded to version 1811 then upgraded to version 1906

  12. Thank you Carl for the above article , i would like to know if there any way that we can export the application name and associated Active directory groups from WEM

  13. Hi Carl,

    Just FYI that the latest version of WEM (v1903 as of this post) includes GPO template files that have a typo; Workspace is spelled Worskpace.

    If others like me just copy the contents of the ADMX folder and replace them into the GPO store, you’ll get a prompt to replace files, but really it will create 2 ADMX\ADML files instead.

    Just FYI in case anyone else runs into this.

    Best,
    Moiz Veravalwala

  14. Hi Carl,

    We are using the Citrix cloud service and installed/configured the WEM agent 1903 and pointed to cloud connectors. However, I can’t see the agents are getting registered in the WEM console. Any idea what is blocking?

    Our server VDAs and Cloud connectors are hosted in AWS and configured necessary security groups to allow WEM ports.

    Thanks.

      1. Yes I followed the same. However, I didn’t set any additional arguments as they explained at the end of the article. I just ran the typical installation of the agent and configured the GPO as per this article.

      2. Hi Carl, Thanks for your advise. The issue has been resolved now. It seems the version WEM 1903 agent is not supported in the WEM as a service. I have reinstalled with the WEM agent 1811.1 and now it is appearing in the WEM console.

        Thanks

        1. Just adding to this incase someone is interested… I attempted to use WEM 1903 connected to our Cloud connectors to Cloud WEM. The new agent did not understand the use of cloud connectors instead of the Web broker. I went back to 1811 also.. My motive was to get around consistent problem with WEM applying my UPM settings. It will work at first, then some weeks later users lose their Citrix Profile. All other WEM settings are applied but I’ve finally resorted to Group Policy just for UPM configuration. To clarify this is cloud WEM …

  15. Carl,

    Thanks for the great work !!

    I’m upgrading a customer environment to 1903 versions. The use UPM from WEM and like to use the Profile container option from UPM 1903. Where can I configure that in WEM 1903 ?

    Thanks,

    Mario

  16. Just a note – in the Citrix upgrade docs for 1811, they specify that if you use SQL AlwaysOn HA, you must remove the WEM database from it before perfomring an upgrade:
    “SQL Server Always On availability groups. If your Workspace Environment Management database is deployed in an SQL Server Always On availability group, before upgrading the database you must remove it from the availability group.”

  17. Is this the same setup for Citrix Cloud wem version? I am wanting to set WEM up in Citrix Cloud and point the DB over to Azure. I scanned over the post but didn’t see anything that suggests setup from Citrix Cloud to Azure.

    1. For the Citrix Cloud version of WEM, Citrix handles the servers and the database. You just install the WEM Agent and point in to the Cloud Connector.

      Or are you asking about building your own WEM Servers in Azure without Citrix Cloud?

      1. No, if Citrix cloud supplies it already then no need to move it over to Azure. Thanks for the info. Love the site. Keep up the great work.

  18. Hey Carl, something basic but I think it is worth to mention, if you set a custom password for your vuemUser SQL account during installation you have to specify it in the Advanced Settings when you are first connecting your Management Console to the Infrastructure Broker. Otherwise, you will get errors like:

    “Login failed for user ‘vuemUser’. Reason: Password did not match that for the login provided”

  19. Hello Carl,

    I have to Provide some URLs to our VDIs – is there a way tor provide this links with WEM.
    We are using WEM 4.7

    Thank you

    1. Without WEM, you can Publish Content from XenApp. Otherwise, you should be able to use WEM or Group Policy Preferences to create a Shortcut (aka application) that points to a URL.

  20. Hello Carl,

    thanks for your blog. I am not shure wether to use one or two assignments with lots of filters or lots of assignments with less filter conditions. What would be a best practice soultion?

    Thanks in advance!
    Sebastian

    1. I like to keep assignments generalised to groups, and then use filters and conditions when there is an exemption to that general requirement or you need to only apply something when another condition is true. Less filters, the less complex the processing.

  21. Hey Carl,

    Not to sure if you have ran across this yet, but for step 24 I would amend that if you move your Computer AD objects to a different OU, then you will need to apply that fix. Had a ticket open with Citrix and that fixed the issue with WEM not applying.

    Justin

  22. Carl, Have you guys noticed by chance WEM will not allow Pinned Items to re-appear in the Start menu? I have the “Delete Taskbar Pinned Shortcuts not checked either.

  23. Has anyone seen an oddity using environment variables? I have a script that runs as an external task. It needs to use the clientname variable which isn’t present when WEM runs – no drama, we set a new variable in WEM to point to ##clientname##

    This works fine the first time a user logs on. The clientname is set as expected.

    What isn’t expected – and I may be missing a trick here – is that on subsequent logons, the environment variable isn’t updated. It remains stuck at whatever was set the very first time a user logged on.

    And it gets weirder – if you delete the key in the user registry hive, log off and back on, the value key (or just value – it doesn’t matter which you remove) never returns.

    I notice in the WEM logs, the following, which (again I may be misreading) suggest to me that WEM thinks the value is static/cached:

    08:54:38 Event -> VuemEnvironmentVariableExecutor.CheckExecCacheState() : Environment Variable -> TCName (Id:7) -> Action already processed -> returning true
    08:54:38 Event -> VuemEnvironmentVariableExecutor.CheckExecCacheState() : Environment Variable -> TCName (Id:7) -> Action already processed -> returning true
    08:54:38 Event -> VuemEnvironmentVariableController.ProcessActionRelatedRefresh() : Environment Variable Processing: No Refresh required -> Exiting

    Any ideas? I am sure I am missing a trick here.

      1. Sorry for the delay replying. I’d put a workaround into the script but that check box does the trick, albeit only at logon.

        Thanks for the pointer.

Leave a Reply to Tony Cancel reply