This message was deleted.

Anything useful in the FSLogix logs on the servers with issues?

Hard to say. Most of the machines are non-persistent VDIs, so the logs disappear after reboot. And getting the logs weren't really a priority either.0 We hade the same issue about 9 months ago, and as far as I can remember now nothing useful was logged then. I was mostly hoping someone knew a little about how FSlogix actually detects that a repository is down, that could help us avoid similar issues in the future.

I haven't worked with Cloud Cache for a while, but from what I can see in the release notes, Microsoft has fixed a lot of issues with Cloud Cache and the failover feature should work just fine. Back in the day I have seen failover issues when multi-session access was configured, however that issue should have been fixed in one of the later versions

Yes, but this is VDI. not multisession access. The profile is only accessed from one VDI at a time. One of our other current issues is the if the VDI don't thet a clean shutdown for any reason, the lock file is left behind and has to be deleted manually before the user can log back in again. These VDIs are pooled, so the users getsa random VDI each they log in. This is not an issue for the persistent VDIs we have, since they are assigned to a specific user for their use only. As long as the VDI name matches the name written in the lock-file there's no problem.