Hi,

What is pegasus? You would be best served by reading wiki http://en.wikipedia.org/wiki/Web-Based_Enterprise_Management

The pegasus service was still functional before the updates so this fix is not critical at this point.

The changes I made simply correct errors in the install components and will be ultimately what VMware will do to fix the problem.

The real benefit here is the boot process will be about 100 seconds faster.

I've been experiencing the same problem as mentioned by everyone else. We even logged an SR with VMware support and the best they could do was point us at this discussion thread. It's great that Mike.Laspina has posted a fix (thanks Mike), but I would have thought that VMware would have provided a revised package. I have a large number of ESX servers and I really don't want to have perform a work around on every ESX server to get around a flawed update provided by VMware. And yes I could write a script to make the work around alot easier, but once again why should I have do this when VMware should be providing a revised package.

Cheers

Ant

I followed the steps on my one environment, now on a different environment I don't have the 3_files directory. This was a fresh install...what do I do now?

yes, you are correct.

Dear ESX users,

Thanks for your timely feedback regarding upgrading to ESX/ESXi 3.5 Update 1.

As one user correctly pointed out, we use Pegasus to provide system management information, which third-party vendors can incorporate into their management applications.

We have identified the root cause of the issue and will provide fixes in an upcoming patch release. More information can be found in the Knowledge Base article 1004257.

Thanks for your information sharing in the community forum and keeping the discussion lively. We appreciate your support and feedback.

Best regards,

VMware ESX Product Team

This solution worked for me.
Thanks

Thanks A LOT

Carlo