had a similar issue pop up with a random vm (one of hundreds) running on esx 4.1 as part of vsphere environment.
updating vmtools non-interactively did the trick.
had a similar issue pop up with a random vm (one of hundreds) running on esx 4.1 as part of vsphere environment.
updating vmtools non-interactively did the trick.