Changing date solved it too. But statistics in Infrastruture Client are down.

Regards from France.

Exactly my opinion....:x

/Tobbe

I am still researching where the U2 portion of the updates entered Update Manager.

Perhaps they were only in the non-critical areas, and are "filterable" if I only apply CRITICAL patches.

(I STILL hate that this was anywhere in Update Manager.)

I LIKE that UM can apply this upgrade, but I would have liked to see it in a 3rd update type.
Something other then CRITICAL and NON-CRITICAL, for example, a "release update" level or something like that.

Something that I would have left in an "unchecked" state in Update Manager.

The workaround I was referring to was to set the clock back on the local machine only during the short time window of the licensing verification stage of the boot process. The time can then be set back to normal time before the VM even gets far enough along to notice that it was set in the past. ESX won't stop any machines that are running, it only affects boot and reboot procedures. And as far as the Microsoft product, I wasn't being snarky, competition will only make VMware challenge themselves to be better and cheaper. If they serve your needs better by all means switch. It's not really a solution I think many of us will take, and threatening to take your ball and go home isn't really helpful in expediting a fix. I just think you are being unrealistic about the timeframes for a patch of this magnitude, and frankly wonder why you think Microsoft would be any faster, despite their extensive experience in patching show-stopper bugs. (Okay, that was snark.)

Does anyone know where the "power on" command is in ESX scripts, etc?

I have backdoor idea on how to work around licensing checks at power on, but need to identify the command/script that ESX uses to power on a VM when a user hits the power button and where ESX HA agents power on the VMs.

This would be something that would be a true workaround and avoid everyone "downgrading" to U1, and/or waiting 36 hours.

Anyone?

here

vmware-cmd -s register /vmfs/volumes/<vm path/vmname.vmx

vmware-cmd /vmfs/volumes/<vm path/vmname.vmx start

As far as i know. Microsoft has not released anything so catastrophic like this during the last twenty years that can cause entire systemcenters to go down. Im not a big MS fan in any way but im now an even lesser VmWare fan. The bottom line is, they know the problem.. it shouldnt be to hard to release a quick fix for the dateproblem while they are working on a real fix. Like another guy said... WAKE UP... ITS WAR..

/Tobbe

Quoting ab_lal from this thread for great justice:

---