The fix for this should be in the next update and release.
For those affected in the mean time, there is a KB article that documents a workaround: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2043311
Thank you for your help and patience,
Nathan