Maybe similar to <@ULLRRKZ8E> I'm setting up a bra...
# citrix-wem
m
Maybe similar to @Paul Brown I'm setting up a brand new environment for a customer: • Windows Server 2025 • Golden Image through MDT for MCS • Citrix VDA 2507 • WEM Agent 2507 I install WEM with
'/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)_:
Copy code
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.
And this is from the
Citrix WEM Agent Host Service Debug.log
debug log:
Copy code
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: False
p
I don't see in your note where you set "*Override Agent Deployment Type"* to "On-Premises deployment"
❤️ 1
c
❤️ 1
r
Yes gpo or dont install w vda install as a separate package w cmd parameters
m
@Paul Brown Wait what? Is it now mandatory to activate broker mode via GPO???
@Corey Tracey Will try!
@Rob Zylowski It is not installed with VDA. It’s installed separately.
FML after setting the GPO the agent registers..
p
glad you got a result.
m
My commandline is in my OG post:
'/quiet Cloud=0 InfrastructureServer=citrix-wem.customer.loc'
And normaly I only do:
'/quiet Cloud=0'
I've only added the FQDN for troubleshooting
But after setting Override Agent Deployment Type in the GPO it started working immediately.
p
They should take the word "optionally" out of the documentation.
r
For onprem if your not using gpos to define the ports you need them in the cmdline. For cloud you dont
p
For cloud you do also. I had to do the exact same for it to flip out from basic mode to cloud mode.
m
@Rob Zylowski I do also have to set the ports in the GPO?
r
Just need one or the other. Gpo is fine to use
m
I now set the ports and the Deployment Type via GPO, Thank you so much guys! I wasn't aware there was a change, this environment is running since WEM 18xx and stopped at updating at 2305 and I now did a big jump to 2507 giving me a headache.