This is a known issue affecting vSphere 5.0 and is scheduled to be resolved in a future update.
For More Info Check this KB Article:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008877
For More Info Check this KB Article:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008877
No comments:
Post a Comment