Tic-toc tic-toc…still waiting for the ESX fix
Well, it’s 6 PM PST and no sign of the ESX 3.5 U2 fix. Maybe I should try one of the suggested workarounds?
1. Do not install ESX 3.5 U2 if it has been downloaded from VMware’s website or elsewhere prior to August 12, 2008.
Hmm.. already installed the patch, guess that won’t work.
2. Set the host time to a date prior to August 12, 2008. This workaround has a number of very serious side affects that could impact product environments.
You better believe there are side effects. If you are synchronizing time with the ESX server Kerberos will complain bitterly if you set the clock back. Oh, and another thing, Exchange 2003 won’t even start as it appears to get its initial time from the host hardware clock at boot.
(5 votes, average: 4.2 out of 5)
Loading ...No comments yet. Be the first.
Leave a reply
