I have always suspected that this was a result of vCenter Windows leveraging ADAM (Active Directory Application Mode).
Although I have not tested this, vCenter 6 VCSA do not use ADAM, so therefore the issue you have experienced may be resolved.
I have always suspected that this was a result of vCenter Windows leveraging ADAM (Active Directory Application Mode).
Although I have not tested this, vCenter 6 VCSA do not use ADAM, so therefore the issue you have experienced may be resolved.