- FIrst of all,VMware always recommends to have same host build across sites if IP customization is involved. The reason being VMtools plays a major role in achieving IP customization.
- Second of all,VMtools prior to 10.0 used VIX authentication and post 10.0 It uses different authentication mechanism which is adopted from 6.5 too
In my opinion upgrading your host to 6.5 and upgrading the appropriate VMtools on the servers at prod site should rectify the issue.
Mo-rover from 6.5 any server below 10.0 vmtools fails with the error message "customization is not supported for installed vmtools version" during test recovery.