This message was deleted.

Well everytime I go back to use it. It’s alaways something acting up. It’s been a while though since I used it. The CC part of it I mean. I just keep up with everyone’s else experiences and make my choice from their. The main reason is for ability to write to multiple locations and keep them in sync if one smb path failed ect. Long story short.

I dont see any fslogix use without any issues. We have customers using cc. It solves tricky availability problems. I do think there are more issues with it but there are ways to make it more reliable. One i have seen is to have the cache in a persistent disk.

Curious as I have not used either. Why fslogix CC verse azure files with sync?

i have been involved in multiple projects where CC does exactly what it says it should - its not 100% perfect, but what is shrugs.... i think your mileage will vary per version

The scenario i was facing yesterday was a misconfigured GPO was CCSync office containers back to onprem (long story) and it generated 500Mbps of traffic on an express route....it also made logons super slow and log offs even worse.....when i found/disabled the string to point to onprem it all went back to normal. Other clients that used it had similar issues.....maybe its my luck!! i understand the how/why around Cloud Cache i just dont have confidence it is worthwhile using....

muhahah i know exactly what you are talking about... that environment is operating in a fashion that was supposed to be very temporary and they changed the goalposts big time, and their network was not upgraded to support it. So yep, everything you are seeing is 100% expected in that scenario. • If your network can't keep up - don't use it • The lowest performing storage location will dictate logoff speed and logon impacts in some instances • Don't ever use it as the default - it has to have a specific use case - for your scenario it was two active-active datacenters with GOOD network between - Azure was thrown in last minute to cater for a rebuild of one DC - turns out Azure stayed for a loooooong time with a LOT more users than planned - small Express Route to serve a large user base with storage on prem - bup. bow (I did warn of this....) When you tick the boxes it works very well, but one step wrong and it can be a challenge - same as any container deployment really

You are hilarious.....and 100% true on every front haha! I did think of something else while i was reading your reply........if you configure cloud cache instead of VHD location in the other field - does the VDA use the cloudcache driver to process the profile?

CC only turns on if its enabled and the locations are defined - if you define BOTH at the same time VHDLocations and CC Locations with the same path - from memory CC wins out - but that is from memory and i could well be wrong - don't do it either way 😂

Yep that sounds about right, i am looking at reconfiguring the policy to move all the FSL configs from the CC section to the regular section

so no more cloud cache....

@Nick Pylarinos I am using it at a customer and can walk you through a functional config if you want - let me know

Shoot me a message Mike and ill sync up with you