I am still concerned about the avilability of this patch.

Currently the servers handling the kb.vmware.com area, is basically so slammed, that it's undergoing a kind of Denial of Service. (it's basically unavailable).

What will happen with the update and patch servers?
When it's available, will these servers be trampled too?

I hope someone has set a few engineers off on a task to beef up the mirror server numbers.

Anyone an idea / procedure how to roll back to U1 (apart from throwing in a CD an do a reinstall)? Will remove certain RPMs work??

__Leo

Just to add to the list...

We coincidentally performed our first upgrade from 3.0.2 to 3.5u2 this morning (Aug 12th, 10am UK time) and I noticed straight away while the upgraded host was still in maintenance mode that the licensing tab within VI client gave the general system error msg. Fortunately, this was only in our test cluster, but obviously, I will leave that host in maintenance until the fix appears.

Hope you guys with production hosts running on update 2 get things sorted quickly.

Hi again,

In my previous post I wasn't clear enough with the workaround I proposed:

When I wrote "restart them elsewhere on 3.5U2" I meant "restart them elsewhere on 3.5U2 where you applied the workaround, i.e moving back the date" if you really can't avoid it.

I strongly suggest that anyone not wanting to wait 36 hours or more for a fix apply the workaround I described because time keeping is really a critical problem for a number of applications (as of now i can think of database, SAP even Kerberos....). A "not so planned" orderly shutdown is far better than data inconsistencies in your environment.

P.S. you can leverge this opportunity to apply Microsoft patches on your VM's (or Red-hat, or...)

Hope this helps, best regards,

Ludovic

LB@SGI:

Maybe their Knowledge Base is hosted on a VM box that suddenly won't boot!

Well, as a matter of fact, we have a big Hyper-v installation at a customers factory and its running like clockwork. So maybe, just maybe if VmWare doesnt fix this really soon you could end up being quite lonely in here. 36 hrs is not acceptable for a fix when a problem of this magnitude arise. So please dont tell me to be calm while we and our customers are loosing thousand of Skr every hour just because they are more interested in licenseprotection stuff than to offer their customers software that will work and is properly tested. The only ones that are having problems with all the "copyprotection" stuff are "we", the ones that are paying for our software. Does that seems right to you. I really think that VmWare is really showing a total lack of respect for their customers when they are "fixing" things like this. I dont think their stocks will be wery high in the nearest future.

/Tobbe

I have the same problem. Changing date solved it, but i hope it's only temporary solution. Still waiting for patch - the one without restart / maintenance mode....

Regards from Poland