When a vm is powered on it gets its time from the esx server. There is no other possibility. Even without vmtools.

Regards Spex

hello vmware...

will this patch be immediatly available via the update plugin when you release it, or am I going to have to download some crazy tar file and install it manually?... I am hoping we can just scan for updates and then remediate to get the patch on there as soon as it's released rather than having to do some kind of manual installation....

we also have this problem arise because someone rebooted a server and it never came back up... I am very critical of the error messages which continue to tell me absolutly nothing about the problems... often I get these unknown errors and have to google stuff for hours to get solutions... it would be good if the unknown errors could instead be a little more verbose so we know kind of where the problem is... for example if it said "expired license" I might have found this thread a little quicker and not spent the past 4 hours trying to work out why the hosts wouldn't start up thanks to my unknown error message....

cheers,,,

Good morning

Switzerland is in the office as well. And we have the same problem.
Be careful with the time change - VM's are affected! This is no workaround for us.
to VMware:

• can we have Trial's for the next 30 days until the issue is fixed?
• can we reset the counter for the initial trial period?
• why do you not proactive inform about this serious issue?

I think you want to be a good product in the enterprise environment, or?

Still waiting that we get any answer to our case.. - Good that the forum is quicker.

Michael

Actually I still believe that ESX should be better than M$ Hypervisor. Although we had purchased the M$ support and M$ would enforce us to change from VMWARE to her hypervisor. (by limiting support level if we use VMWARE at the button.)

Hope that VMWARE will check and test carefully and we didn't want to do patch management for vmware product like M$, to wait for a year for review...

Forgot to let you know that I am from HK. Now waiting for the new release and patches.

KB ID 1006716 seems to be it

its just a real shame that the "bug" has nothing to do with the functioning of ESX... it's all because of licensing and is why I am so critical of this particular error... right now we have critical business systems down because of some expiry date that should never have impacted us in the fist place has lapsed... businesses are losing money right now after paying for all their licenses and in some cases the gold support options as well... to find out we simply can't use our servers because of this is probably the biggest slap it could possibly be....

I imagine VMWare will lose some customers because of this error... no one will suspect that it will be the cause.. I never thought that error was licensing until I read this thread... up until then I thought I had some kind of corruption on the server and I was about to format it and reinstall...

is there a way to uninstall the upgrade, reboot and therefore fix the problem?

perhaps vmware should give us a better work around until they release the patch... as I understand it the current workaround is from a member like us... vmware havn't offered anything as a solution?

Wow gotta say that I am really glad we didnt do the upgrade. That being said I sure hope that VMware gets a patch out for this and quickly. I imagine a great number of VMware's customers are in the US and are only just starting to wake up. It's going to be a crappy day for many system engineers today I fear.

Goodluck to all those effected by this.

I'm so thankful that I waited to update!