Eric Siebert
VMware Communities User Moderator
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-
Check out my website: VMware-land
Read my virtualization blog: SSV Blog
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

I hope there is no Time & Attendance or Industrial Timerelated Application running on ESX and you VM guys can fix
this problem quickly, because I guess the major pain comes from the ESX 3.5-U2 Customer base.

Can a moderator pin this thread as critical for everyone?

Since its good practice so far - most of the vm's synchronize their time with the esx host.And they do this also backwards as someone experienced.

Having wrong time can be disastrous to the whole domain and also to member servers than can get disconnected from the domain.

Solution?

Since the patch will probably need maintenance mode you will have to evacuate all you vm's from the esx. But how should this be possible with the problem. At the end I guess you will have 2 opportunities:

Power off vm's, apply patch, power on. - temporary install a new esx within your cluster with a patch for the problem and use it as a VMotion target for the others.

Regards

Spex

I second the view of vmware really dropping the ball with the 3.5 release of ESX. If this is as big of an issue as it looks I wonder if the stock price will take another hit today in the US?? Probably not because of this, but it certainly doesnt help the situation.

Here's hoping the work experience kid doesn't trip over the power cables in the next 24hrs.

Also -- Has anyone else noticed that Update 2 hosts are showing as non-compliant. They are showing as needing Update 1 to be installed! This only happened in the last few hours as far as i can tell.