tell me if you think it should work.

1st turn off the ntp client on esx 3.5 u2 server i am going to VMotion VM's too

2nd make sure VM's tools do not have time "checked" Time synchronization between the virtual machine and ESX server operation system

3rd change date on ESX server that i am going to vmotion the vm too.

4th vmotion vm's to ESX server with date changed.

5th patch other esx 3.5 u2 server.

6th vmotion vm's to patched ESX 3.5 u2 server

7th patch and change date on other ESX 3.5 u2 server.

what do you think

Stephen

As previously reported, today, VMware ESX/ESXi Update 2 has an issue that causes where virtual machines fail to power on or VMotion successfully as of August 12.

The express patches are now available for download that will resolve the ESX/ESXi 3.5 Update 2 issue which causes the product license to expire as of August 12, 2008.
Please go to http://www.vmware.com/go/esxexpresspatches for more information.

Thank You,

The VMware ESX Product Team

Yes I agre, the message to the console is non-descript and hence why so many of us spent a few hours trying to work out the error before we found this thread... I commented on that in a post on the 4th or 5th page... the message I was referring to is the message in the vmware log.. there are transcripts of it in the first few pages of the thread as well...

So with that, I will take my comments and concede the point.

No need to as again I totally agree, our environment doesn't have as many automated procedures for setting up our ESX's as yours, so for us this is a lengthy process.. we also install agents like the EMC Navisphere (which I know is now bundeled with the latest version anyway) so we can manage our lun mappings from a single place.. there is also some complex scripting we had created for some custom deployments etc.. so the environment is not so in tune with just reinstalling the base ESX product and bringing the VM's online.. I could do it, it just takes time and time I don't really want to spend on this issue given the patch release time was relatively short... If I did this I would have been up for 24 hrs seting everything back up again, only to have the patch released a few hours later...

I don't think it has anything to do with ESXi's free release, which was probably part of u2. I think it's just a bad coincidence.

Sorry I probably didn't word this correctly.. I meant that ESXi had the beta time bomb but ESX didn't... They time bombed ESXi because it was free and they do it on almost all their free betas I have seen that you can freely download... unfortunately because of this it got rolled up into the production ESX code when it shouldn't have.. they rolled the beta code from ESXi into the update patch for ESXi and ESX, so ESX got the benefit of the timebomb as well... great!.. at least that is how I understand it to have occured, I might be worng.....