VMTools 'not running' status under VC 2.5 U3

[MetallicWood]

I've got a bizzare issue occuring regularly with VM's and their VMTools appearing as 'not running' under the Virtual Center despite being install correctly.

If I log onto the VM through a console the tool status comes alive in Virtual Center. The same can be achieved by doing a remote restart of the VMTools service.

Does anyone know why this is occuring? - a bug in VC 2.5 U3 with ESX 3.5 U3 maybe?

Also, should I be updating the VMTools agents on every Guest OS with every VC update release?

Comments appreciated.

[MetallicWood]

Logged a call with VMWare - they inform me that this issue is/has been fixed in ESX 3.5 Update 4 due out in third week of March 09.

[Cooldude09]

Hi, Try upgrading to VC 2.5 U4 and see if it helps. Also check if the VMware tools are properly working in the guest OS or not.

Regards

Anil

Save the planet, Go Green

if you found my answer to be useful, feel free to mark it as Helpful or Correct.

[MBrownHenn]

We are struggling with the same problem. We upgraded 24 ESX hosts from 3.0.2 to 3.5 U3 and VC 2.0.2 U4 to 2. U3. We upgraded more than 200 VM's and are only seeing this on one three node cluster and only on certain VM's on that cluster. If this truly was a VC 2.5 U3 problem then wouldn't I see this accross the farm? We'll be going with VC 2.5 U4, but I don't like fixing a specific problem with a sledge hammer update. Sorry to be negative, I do have an open ticket on this that has been escalated to the "Engineers" at VMware. I'm waiting for a call back. Once i have an offical response and fix I will report that here.