Marco Hofmann
09/16/2025, 6:42 PM'/quiet Cloud=0 InfrastructureServer=citrix-wem.customer.loc'
AND have set the regkey via GPO _(I set both for troubleshooting. The current 2016 env with WEM 2305 has only the GPO value set)_:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Norskale\Agent Host]
"AllowWEMUseCvadConnectors"=dword:00000000
"BrokerSvcName"="citrix-wem.customer.loc"
And regardless of what I do, the WEM agent always launches in basic/stand-alone mode and never connects to the broker/db and therefore doesn't do it's job.
This is one of my last blockers and I'm clueless. This feels like a bug to me at the moment.Marco Hofmann
09/16/2025, 6:43 PMCitrix WEM Agent Host Service Debug.log debug log:
Agent Deployment Type: Basic
Agent Broker Server:
Agent Broker Port: 8286
Cached Data Sync Port: 8288
Agent Last Known Site Id: 1
Agent Last Known Site Name: Default Site
Agent Path: C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\
RDS Host: True
Enable user centric intelligent optimization: True
Use Non Persistent Compliant History: FalsePaul Brown
09/16/2025, 6:52 PMCorey Tracey
09/16/2025, 6:54 PMRob Zylowski
09/16/2025, 8:01 PMMarco Hofmann
09/16/2025, 8:14 PMMarco Hofmann
09/16/2025, 8:15 PMMarco Hofmann
09/16/2025, 8:16 PMMarco Hofmann
09/16/2025, 8:23 PMPaul Brown
09/16/2025, 8:24 PMRob Zylowski
09/16/2025, 8:25 PMMarco Hofmann
09/16/2025, 8:26 PM'/quiet Cloud=0 InfrastructureServer=citrix-wem.customer.loc'
And normaly I only do: '/quiet Cloud=0'
I've only added the FQDN for troubleshootingMarco Hofmann
09/16/2025, 8:26 PMPaul Brown
09/16/2025, 8:27 PMRob Zylowski
09/16/2025, 8:27 PMPaul Brown
09/16/2025, 8:27 PMMarco Hofmann
09/16/2025, 8:29 PMRob Zylowski
09/16/2025, 8:32 PMMarco Hofmann
09/16/2025, 8:36 PM