I'm running a Citrix Cloud env with VDAs on prem, multi-session, non persistent. MCS through Citrix Cloud and Cloud WEM. I installed the WEM agent on my master image (default installation with DB on C:) and after creating the VDAs from the master image in Cloud, I see that the DB files are updated on the VDAs under C: everytime they restart, however I feel its very unstable because when I log in as a user, sometimes the WEM settings are synced, sometimes not. Especially when I restart the VDAs, the sync is not stable at all. I see the WEM agent icon when I login as the user but start menu is not updated for example. I'm running startmenu through actions in WEM Cloud. Just not sure why this is so unstable, is no one running Cloud WEM nowadays? I can't imagine that this is working for majority. When I tried to put the WEM cache on a separate partition, Citrix Cloud MCS would change the partition letter(Even though I clearly configured it to pick E:) and mix the MCS cache partition with WEM cache partition, it became a mess. I also tried to put the WEM cache on the MCS cache partition but then the WEM cache on C: was taking over and I had two different settings coming from WEM cache on C: and WEM cache on the MCS partition.

startup scripts for cache refresh man - rock solid every time

are there any finished scripts out there for Citrix Cloud? not sure if it works like with onprem or if I have to connect to the Citrix Cloud API to do the refresh

Good to see WEM still has to have this shim in near-2026

Yeah its terrible! I'm now going to try to first restart the WEM service with a script at server restart and see if it makes things more stable which I doubt.. because the service is technically started on each server restart and refreshed, I can see that on the time and date

If my Australian alter ego suggests startup scripts for cache refresh then that is what will work... I'm just commenting on how crappy it is that they still haven't stabilized it past this

Yeah! will add these two as you say step by step and see if things improve.

Can you check on the WEM Console (Monitoring > Administration > Agents) that you dont have transient registration errors. ie Agent "VDI999" not bound to any configuration set.

looks green here and I can refresh the cache from here aswell. But I have seen those error messages in the event viewer on the VDA itself.

https://github.com/JamesKindon/Citrix/blob/master/Citrix%20WEM%20Startup%20Scripts/RestartWEMServices.ps1 oldie but a goodie, all local, no need to talk to APIs etc, did many many wem deployments over the years, this always sorted stability

Double-check here: https://docs.citrix.com/en-us/workspace-environment-management/service/get-started/install-and-configure.html#agent-cache-utility-options Besides the "Citrix WEM Agent Host Service", also restart the "Citrix WEM User Logon Service" After stopping services and before starting the services, delete these del /f "C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\Local Databases\*.sdf" del /f "C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\Local Databases\*.db" also be sure Netlogon is started after the services Check your config in WEM Service too, may need to adjust settings. Our WEM Service environment has been working well.

thanks guys, trying this out right now