I have an SR with VMware about this issue.
The Tech told me that it is a known issue with 6.7u1 , and that the fix will be released by end of Q1 2019 in Vcenter 6.7U2
I have an SR with VMware about this issue.
The Tech told me that it is a known issue with 6.7u1 , and that the fix will be released by end of Q1 2019 in Vcenter 6.7U2