Hi,
Any new progress in this effort. This is happening in my infrastructure as well. Is this an occurrence after a specific vSphere upgrade and harmless to ignore?
Thanks.
