vSAN Storage Policy: Content Library
I received an interesting question from one of my customers about the behaviour of vSAN with regards to policy changes to a policy which is applied to a content library and then especially the templates that reside within it. The customer told me that when they changed the Default vSAN Policy that was attached to a content library, the OVF-templates inside that content library, were not updated to comply with the changes made to the policy. So I tried that…