Citrix Workspace Environment Management with PVS – Synchronization State “Unknown”

This week I wanted to test the the Workspace Environment Management Suite which is included in the XenApp/XenDesktop Enterprise edition. I don’t want to write an article about how to install the software. For a detailed installation guide you can refer to Carl Stalhoods website.

Update – 20191211
With the latest Citrix WEM Release the folder name under Program Files changed from “C:\Program Files (x86)\Norskale\Norskale Agent Host” to “C:\Program Files (x86)\Citrix\Workspace Environment Management Agent”. Updated the post with the correct folder locations.

Install parameters when using PVS (silent):

Its important to redirect the cache to a persistent drive otherwise information about the process history will be lost after a reboot.

After installing the WEM Agent into the vDisk and configuring the needed GPO settings I  powered on my XenApp worker for testing purpose. A short view in the WEM Admin console was telling me, that there was an issue with the “Synchronization State” under “Administration –> Agents”.

wes_unknown

In the eventlog you only could find the information that the agent couldnt connect the broker machine because of a connection timeout.

wes_eventlog

First of all I was thinking maybe its a firwall problem but the specific ports used by the WEM Agent have been accessible. The following ports are used:

  • Agent Broker – 8286
  • Agent Sync – 8285

After reading the product documentation I found a command how to force the agent to synchronize against the WEM server.

Sounds promising 🙂  Lets check the agent status in the WEM Admin console.

wes_sync_ok

Now the synchronization was working but after rebooting the provisioned system the problem with the unknown sync state occured again.

Fix: You need to create a scheduled task which is refreshing the WEM cache on every startup of the system. The task should be run by the user “NT AUTHORITY\SYSTEM”.

 

  1. Hi Julien

    not realy sure what you mean with the task aobve.do i make a script where i shutdown the norskale service, make a cache refresh, and then start the norskale and netlogon service?
    or is it ok, to just refresh cache at startup?

    1. Hello Thorsten. Exaclty you need to create a batch file which will be triggered at the system startup.
      1.) Force the Norskale service to stop
      2.) Start the Norskale + Netlogon service
      3.) Refresh the cache.

      I couldnt get the agent synchronized without all the mentioned steps.

      1. thx 4 the fast replay
        i will try it first without and then double check with the script.
        what about the gpo setting „vuemappcmd extra sync delay“ extra launch delay = 1000
        thats what we setup.
        we have a running test with 2008r2 on xenserver with pvs, now i just setup a pilot with 2016 on hpe moonshot m710x cartridges.
        have a nice evening
        Thorsten

  2. Thanks for this blog Julien really helped me alot understanding its behaviour. Im keen to find out if the Sync Delay actually works. Thorsten you set this to „1000“ and the GPO mentions only a delay of between 100 – 200ms. Is this a typo? How did you get on? I tested a delay of 150ms but i still had to go on and force a refresh as Julien mentions doing so i might have to implement the scheduled task regardless.

    1. Julian,

      I thought a “upgraded installation of the WEM agent will result in partial changes to your environment:
      The new Service name is: Citrix WEM Agent Host Service
      The new process name is: Wem.Agent.Service.exe
      The path on the file system will not be altered and will remain as it was: %ProgramFiles%\Norskale\Norskale Agent Host”

      You have
      net stop “Norskale Agent Host Service” /y

      net start “Norskale Agent Host Service”

      net start “Netlogon”

      “C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\AgentCacheUtility.exe” -refreshcache

      Should it reflect the new service if it’s upgraded?

  3. Thank you!
    My mistake was not to use the system account, the scheduled task wouldn’t run with an admin account.
    Everything is OK now 🙂

    1. Working with WEM 1903 in a current project and I still need to refresh the cache for the PVS targets on each reboot. If you are using BISF the cache refresh action will already be included in the startup task and you don’t need to worry about anything 🙂

Leave a Reply to Thorsten Cancel reply

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