You are right. There are discussions in other sites regarding this behavior as a bug in 5.1 vsphere. Considering that the fix is there in latest build of vsphere 5.1, I can find that you are in latest version already. Please let me know if I am wrong.
↧