Badges

gestaltitbadge

follow-me-twitter

Subscribe to me on FriendFeed

Comments / DISQUS
Feedjit.com

Free vCenter 4 Pre-Upgrade Utility To Help Check Patch Readiness For vSphere

vCenter 4 agent pre-upgrade check

VMware made upgrading to vSphere 4 easy enough, but there are still a few things that can go wrong. One example is that admins must consider the patch and version levels of VirtualCenter and ESX  to begin. After the vCenter upgrade specific  compatibilities between vCenter 4 and ESX 3.x must be understood if a mixed mode environment will exist during the span of the upgrade.

vCenter 4 Pre-Upgrade Check

Although the Agent Pre-Upgrade Check Utility was introduced last Fall when VMware released vCenter 4 Update 1, I had not come across a situation where using the tool identified problems with ESX upgrades. Judging by several other blog posts that demonstrated the utility on the web already, most all of these bloggers showed “pass” scenarios as well. For me that was the same result until this week. In fact, the vCenter Pre-Upgrade Check proved it’s worth to me in a huge way.

For those not familiar how to use the Pre-Upgrade Utility, just start the autorun.exe in the vCenter 4 U1 .zip file or from the install DVD. At the bottom of the vCenter Installer menu is the option to start the pre-upgrade check. See the image to the right of this post.

Once the tool starts point it at the VirtualCenter 2.5 server. After less than 5 minutes

the “Agentupgradechecker” results are displayed for all hosts managed by VirtualCenter and whether they are patched to a compatible level for the upgrade to continue. The tool is helpful in that it links to actual VMware KB articles for the patches required as well being savable as .html files for future use. Here’s some more screen shots to help explain:

 agentupgradechecker results agentupgradechecker results host 16

From this point it’s a matter of following the link to the KB article and applying the patches. VMware Update Manager can help with this, or do it manually if necessary.

Related Posts

  • Administrator

    Wierd thing this is. We have Vsphere 4.0U1 running. It tests the hosts, and returns them as VMware ESX Server 3.5.0 build-176894. Ok, they are upgraded once, but they are definitly not 3.5 now.

Get My Podcast On iTunes!
Support VM /ETC
Support VMETC.com

Support VMETC.com

Free Business and Tech Magazines and eBooks
@rbrambley tweets
VMTN Roundtable Podcasts
Subscribe



Add to Google Reader or Homepage
Subscribe in NewsGator Online
Add to netvibes
Add to Plusmo