Jump to content
Welcome to our new Citrix community!
  • 0

WEM agent only launches at session reconnect


Greg Reski

Question

As the title states, I'm having an issue where the WEM agent is only launching and applying settings when a Windows 10 desktop is reconnected to.  The agent does not launch at the initial user login.

I have applied CTX226494 as a startup task, and also tried it as a login script, with no success.

 

Environment:

XD 7.15 CU 2

Windows 10 1803 with VDA 7.15 CU3, MCS, non-persistent

Citrix Profile Management

WEM 4.7 (I have also tried with the 1811 WEM agent).

 

 

WEM console "Agent Service Actions" are set to "Launch Agent at Logon", and "Launch Agent at Reconnect".

 

At the initial login, the debug log reads as follows:

 

9:51:46 AM Event -> ConfigurationDataSourcesHelper.CheckBrokerSvcConnection() : Broker Svc Check -> OK
9:51:46 AM Event -> StatisticsUpdater.() : Detected connection security -> Negociated
9:51:47 AM Event -> VuemAgentServiceConfigurationHelper.TryUpdateAgentStatistic() : Agent statistic update (InstanceGuid: d7f350b8-7b9f-439f-b743-e35965e82ec9) -> Success
9:52:00 AM Event -> ConfigurationDataSourcesHelper.CheckBrokerSvcConnection() : Broker Svc Check -> OK
9:52:00 AM Event -> AgentServiceHelper.OpenDataConnection() : Detected connection security -> Negociated
9:52:00 AM Event -> VuemAgentServiceConfigurationHelper.TryUpdateAgentRegistration() : Agent callback info is not updated. Try update...
9:52:00 AM Exception -> VuemAgentServiceConfigurationHelper.TryUpdateAgentRegistration() : The underlying secure session has faulted before the reliable session fully completed. The reliable session was faulted.
9:52:00 AM Event -> VuemAgentServiceConfigurationHelper.DoCentralCfgReport() : Central Configuration Report:  Succeeds to pull report of all of the configurations I have set.

 

At this point, WEM settings have failed to apply to the session.

"C:\Program Files (x86)\Norskale\Norskale Agent Host>AgentCacheUtility.exe -r"  does not successfully cause the agent to launch.

 

If I disconnect from the session, and then reconnect, the debug log then reads as follows:

 

9:52:02 AM Event -> ConfigurationDataSourcesHelper.CheckBrokerSvcConnection() : Broker Svc Check -> OK
9:52:02 AM Event -> StatisticsUpdater.() : Detected connection security -> Negociated
9:52:02 AM Event -> VuemAgentServiceConfigurationHelper.TryUpdateAgentStatistic() : Agent statistic update (InstanceGuid: d7f350b8-7b9f-439f-b743-e35965e82ec9) -> Success
9:55:40 AM Event -> LocalDataUploader.() : Starting local data scheduled upload...
9:55:40 AM Event -> ConfigurationDataSourcesHelper.CheckBrokerSvcConnection() : Broker Svc Check -> OK
9:55:40 AM Event -> LocalDataUploader. () : Detected connection security -> Negociated
9:55:40 AM Event -> LocalDataUploader.() : Starting Agent Statistic Entry entity type processing...
9:55:40 AM Event -> LocalDataUploader.() : Starting User Statistic Entry entity type processing...
9:55:40 AM Event -> LocalDataUploader.() : Starting User Statistic Entry entity type upload...
9:55:41 AM Event -> VuemAgentServiceConfigurationHelper.TryUpdateUserRegistration() : User registration update (UserName: S-1-5-21-349924469-1720938638-1543857936-65325) -> Success
9:55:41 AM Event -> VuemAgentServiceConfigurationHelper.TryUpdateUserStatistic() : User service statistic update (HardwareId: 00505697D12B, UserName: S-1-5-21-349924469-1720938638-1543857936-65325, SessionGuid:6b43304b-1781-452e-989d-d76d2ec26ddb) -> Success
(VuemAgentServiceConfigurationHelper.TryUpdateUserStatistic repeats several times with "Success")
9:55:41 AM Event -> LocalDataUploader.() : Local Data successfully uploaded
9:55:46 AM Event -> ConfigurationDataSourcesHelper.CheckBrokerSyncSvcConnection() : Broker Sync Svc Check -> OK
9:55:46 AM Event -> AgentLocalCacheSync.() : Detected connection security -> Negociated
9:55:47 AM Event -> AgentLocalCacheSync.() : Start Time: 1/6/2019 9:55:46 AM
Total changes downloaded: 0/0
Last successful synchronization: 1/6/2019 9:55:47 AM
9:55:47 AM Event -> ConfigurationDataSourcesHelper.CheckBrokerSvcConnection() : Broker Svc Check -> OK
9:55:47 AM Event -> StatisticsUpdater.() : Detected connection security -> Negociated
9:55:47 AM Event -> VuemAgentServiceConfigurationHelper.TryUpdateAgentStatistic() : Agent statistic update (InstanceGuid: d7f350b8-7b9f-439f-b743-e35965e82ec9) -> Success
 

WEM then proceeds to apply all of my defined settings.

 

Can anyone offer any insight as to why the WEM agent is only starting when I reconnect to a previously established connection?

 

Thanks!

Link to comment

4 answers to this question

Recommended Posts

Finally got this resolved with the help of an excellent Escalation Engineer at Citrix.

 

For installation of the WEM Agent, I had to use the switches below.  This article, from the Norskale days, and this article from Citrix were used to get the switches set correctly.

 

"Citrix WEM Agent Setup.exe" /v"WaitForNetwork=\"1\" SyncForegroundPolicy=\"1\" GpNetworkStartTimeoutPolicyValue=\"90\" ServicesPipeTimeout=\"120000\""

 

On Windows 10 1803, I had to also use the script here (CTX226494) as a scheduled task at startup.

 

On Windows 10 1809, the startup script from CTX226494 had to be modified as seen here in this discussion thread.  I had to take mine a step further and change the timeout to 60 seconds.

@echo off
timeout 60 /nobreak
net stop "Norskale Agent Host Service" /y
net start "Norskale Agent Host Service"
net start "Netlogon"
cd "C:\Program Files (x86)\Norskale\Norskale Agent Host\"
AgentCacheUtility.exe -refreshcache
exit 0

My take away from all this is that WEM is still in it's infancy, and there is still quite a bit of room for improvement on the development side.  That being said, I am not deterred from using WEM, and I am excited to see the product continue to mature.

Link to comment
On 1/15/2019 at 3:24 AM, James Kindon said:

That almost looks like a directory services timeout when trying to get the user info - you could try extending the timeouts for directory services lookups in WEM? (in the admin console under agent options)

 

I tried adjusting up to 20000 ms, but this didn't seem to have any effect.

Should I keep increasing?  Is there a maximum?

 

One other thing I have found is that if I leave the VM (Win10 1803, non-persistent, MCS) idle for about an hour before logging in, the agent launches successfully.

 

I have a case open with support, and will update this post if a solution is found.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...