View 7.1 and vSAN 6.6.1 interop – nice fix

Last week, I was rolling out Horizon View v7.1 on my new vSAN 6.6.1 all-flash configuration in the lab. Now, one of the pet peeves a few of us have had with this configuration was that a warning was always reported around read cache reservations on all-flash vSAN. Of course, read cache is irrelevant to all-flash (AF) configurations as it does not use a read cache; this is only applicable to hybrid vSAN configurations. This is why it was such as annoyance.

To address this warning in the health check, vSAN customers had to manually edit the storage policies associated with Horizon View disks, and remove any reference to the read cache requirement, which was a bit of an annoyance/pain. So I was pleased to see that we have now addressed this in Horizon View 7.1. Just to show you a few screenshots from View 7 on vSAN 6.6.1, you can see the automatically created policies for View on vSAN, and also the fact that the policy for the replica is still using Read Cache Reservations (since this would still be beneficial for View desktops deployed on hybrid configurations):


But the good thing now is that there is an understanding that read cache reservation is not relevant to AF-vSAN, so we do not flag any errors or warning about this in the health check anymore. Good news indeed.