Is anyone actually leaving the WEM cache in the default location in their non-persistent image anymore? We're testing MCS NP in Azure, and I'm wondering if it's worth it to create a persistent disk just for this.

You using WEM Service by chance?

Yep

This link https://docs.citrix.com/en-us/workspace-environment-management/service/whats-new.html#wem-agent-support-for-persist[…]che-on-non-persistent-machines

We're not on that build yet, but that feature has been on my watch list

Okay, well then yes I leave it and honestly I go back to either @James Kindon script or still use BIS-F options.

There's also this: https://docs.citrix.com/en-us/workspace-environment-management/service/whats-new.html#wem-agent-support-for-persist[…]che-on-non-persistent-machines

Yea that the 2408 part I linked above.

So for this: Centralized configuration set level agent cache synchronization Where the hell is that configured? There is like no information in this article

Good question.

I never moved the cache from the default location ever. Zero point if you are refreshing it at boot.

We moved back to default location a while ago. Refresh cache at startup with BIS-F. No problems at all.

I leave it in default location with WEM On-Prem 2203 for Server 2022/Windows 10 MCS.

Okay, fuck it, gonna go that route with this build and see how it goes. @James Kindon, you are not still forcing a refresh at boot, right? I mean via script. I wanted to basically have WEM installed as-is with no changes.

Haven’t done it with the latest releases and the associated auto detect changes - not sure I’m a fan of the approach but proof will be in the pudding I guess

Well, I guess we'll see how it goes. I really don't want to go back to the login script method, so I'll test it out with the base install and then move to persistent storage if need be.

I've never moved the WEM cache. Not had any issues with W11 multi-session non-persistent