RSS Feed for This PostCurrent Article

VMware Builds, Update 1 Problems, Details, etc.

Hmm, just read a post over at virtualization.info about how the latest VMware VirtualCenter build numbers don’t match the web site. I guess I didn’t notice that the web site says build 84782 but my client reports 84767. Yet another detail that didn’t get attended to. It’s always the details that make life miserable.

I was talking to another VMware customer the other day who was telling me that they were waiting for Update 1 to come out before they migrated from VI 3.0. At the time I thought that was prudent, but with reports of Update 1 problems on top of this build issue I’d advise anybody running a stable VI 3.0 environment just to stay there.

Related Posts

  1. Why This VMware Time Bomb Issue is a Big Deal
  2. VMware vSphere 4 Update 2 Highlights
  3. Ah, Details
  4. Update Manager, VMotion, and Me
  5. ESX 3.5 & VC 2.5 Update 1 Applied

Trackback URL

  1. 2 Comment(s)

  2. By John Troyer on Apr 14, 2008 | Reply

    The build numbers were actually correct. (The installer build number is different than the VC build number — it’s documented, but confusing.) We’re still investigating the other issues.

  3. By Bob Plankers on Apr 14, 2008 | Reply

    Yeah, that is confusing. Thanks for the comment, though, so I can stop keeping an eye out for an update. :-)

Post a Comment

 

Please note that while in principle I don't mind promotion of a non-personal web site or blog in the fields below, any comments that are off-topic, derogatory, or spam-like will likely be removed at my discretion.