This message was deleted.

My recommendation is atleast SSD or higher. For the cloud cache side it writes to the drive(stored locally) and some move it to presistent drive. But some don’t. There was a thread recently where someone moved the cloud cache. Cloud cache by default is here C:\ProgramData\FSLogix\Cache. There is a GPO/reg file to move it. Cache Directory/WriteCacheDirectory. @Matthias Eckerle had some issues in an older thread above. https://worldofeuc.slack.com/archives/CKBVDG48H/p1666290400931929

dumb question, why would you move cloud cache to another drive? is it for non-peristent VDIs?

From my experience yea. PVS and MCS multi session will hammer the write cache on those provisioning mechanisms

so you move it on the PVS target device so it doesn't drain the pvs write cache file?

Well let’s say you have a 2019 image that’s Xenapp(multi session) and Using cloud cache Fslogix . The more users that login will belt the PVS write cache. So I personally move it to the PVS Target persistent drive. For single session it’s not as much as a concern as they are one to one. Then you need to make sure the persistent drive has adequate space as well if moved. The Fslogix cloud cache is flush frequently, but I can’t remember how fast it’s flushed. But you’ll need to test to confirm No performance issues occur. Many will have other opinions as well

Cloud Cache is too buggy in my opinion. We had a discussion here --> https://worldofeuc.slack.com/archives/CKBVDG48H/p1668448438233999. But yeah, SSD is highly recommended

@Balint Oberrauch has a solid point. It’s had some issues.

Follow Ray's recommendation and use atleast SSD 🙂

@Balint Oberrauch i am not implementing anything. the client asked me for my opinion, but doesn cloud cache have HA built into it. you can specify 4 different locations to replicate the VHD(X) files.

it provides real-time replication based from the cloud cache it stores local, to the smb destinations.