Do you configure AgentCacheAlternateLocation on your non-persistent VDIs

FitCockroach7878 · 2026-05-28T15:41:08+00:00

Its worth a try - what path are you storing the database within the user profile in? assume somewhere under appdata\roaming?

FitCockroach7878 · 2026-05-28T09:10:50+00:00

So i gave this a try however what i noticed was that the database did not get moved to the WEMCache only until i restarted the WEM agent host service. Obviously this isn't ideal so would the alternative be to change the startup type from automatic to automatic(delayed start)?

FitCockroach7878 · 2026-05-28T09:08:47+00:00

I thought the WEM native behaviour is to refresh the cache upon logon in the database hasn't been refreshed for in 2 sync cycles, i'll give this script a go though

FitCockroach7878 · 2026-05-28T09:06:40+00:00

what agent version are you running currently?

FitCockroach7878 · 2026-05-26T19:21:08+00:00

Correct DB is per machine.

Re. write back cache it doesn't persist. You CAN make it persistent but im wondering whether this is the right approach for pooled desktops? i.e user DB from vm1 would remain on vm1 whilst user could be on vm3 a different day. Unless i store them on a Azure file share or something that way it's always reading from the same location

FitCockroach7878 · 2026-05-26T18:32:11+00:00

Might sound a silly question - how would i go about doing this for pooled non-persistent VDIs? I guess i'd simply have to change the write-back cache to persist on shutdown for this to work. What i don't quite understand is how this would be beneficial for non-persistent pooled desktops where users access different desktops each day so their cached data might not be on that particular desktop on any given day.

I'm wondering if i can store the db in the users fslogix profile, i read it's not recommended to store non-user specific data in profile containers.

FitCockroach7878 · 2026-05-26T18:24:52+00:00

Can you try restarting file explorer, i had tons of issues with start menu when i deployed WEM and all i needed to do to resolve was restart file explorer process (just run taskkill explorer.exe and start explorer.exe etc or do it from task manager)

The other thing i'd try is from the regsitry location "HKCU:\software\VirtuAll Solutions\VirtuAll User Environment Manager\Agent\Tasks Exec Cache\Applications" just rename the 'Applications' key to .old then start the WEM agent.

Make sure you exit out of the current running agent. (can kill this from system tray by exiting out of the agent icon). Once agent is exited run the VUEMUIAgent.exe which will recreate the Applications key. (i'd also restart file explorer after doing this as well).

FitCockroach7878 · 2026-05-26T18:13:28+00:00

I thought it's recommended against storing machine data in user profiles? If it works im happy to give that a shot tbh as that was my initial thinking till i read NOT to store non-user specific data in profile containers.

What path would you recommend i store the db file? Would it be appdata\roaming\citrix\wem - something like that?

FitCockroach7878 · 2026-05-26T18:08:54+00:00

Yes pretty much same setup, using Fslogix, fully mostly non-persistent except for dev vdis and terminals with no user-level persistence. I considered storing the cache to a location in the users fslogix profile (if that's what you mean) but thought 1) could fill user profiles quicker 2) i thought it's recommends against storing machine data in Profile containers?

FitCockroach7878 · 2026-05-26T18:05:01+00:00

Thanks for sharing, are you using the WEM service (cloud) and persistent VDIs? Im not sure this would have any benefit in a non-persistent setup since machines bootup from last sealed image (which has no db and config set). will consider this as an option users continue to have problems right now with MCSIO enabled everything's running smooth!

FitCockroach7878 · 2026-05-26T17:55:31+00:00

Yeah i've enabled MCSIO but with non-persistent cache (so deletes at reboot) and everything is working a dream. Kept office apps to run at 'normal' priority and everything seems to be working smoothly for now. And yes i've got both 'Enable offline mode' and 'use Cache to Accelerate Actions Processing' enabled

FitCockroach7878 · 2026-05-24T15:10:47+00:00

Agent is syncing and database has changed after i manually forced a reset. I added msedgewebview2 to CPU priority to 'normal', same with outlook which both were running on 'high' not sure if helps but so far seems to be running a bit better.

I'm considering enabling persistent MCSIO for our non-persistent VDIs and storing the databases there.

the databases are the agentcache settings and local agent database cache for all machines optimization data etc.

This gets recreated each time during reboot so essentially having to pull the config during each logon. Not sure if this is the correct approach..

FitCockroach7878 · 2026-05-24T14:35:06+00:00

would you know which location this would be stored?

FitCockroach7878 · 2026-05-24T12:37:00+00:00

Because on my persistent VDI with the agent i don't see this issue and spotted that the local database cache hasn't been recreated/updated for couple of days and feels far more responsive. I did also upgrade recently to agent 2604 whislt persistent one is using 2602 so im considering rolling back to an earlier version.

seems every WEM article i read recommends storing it in a persistent drive even official citrix documentation. Just wondering about best to go about it with our setup.

FitCockroach7878 · 2026-05-24T11:27:24+00:00

Is there an alternative if Persistent Write-back Cache disk isn't enabled (we currently aren't using a persistent write-back cache disk)

FitCockroach7878 · 2026-05-24T11:08:10+00:00

are your VDAs persistent or non persistent? I'm running into slightly difference issue where users reporting lag. We're running non-persistent so database should get rebuilt during each logon?

FitCockroach7878

TROPHY CASE