Solved

VMware Update Manager vSphere 5 to 5.1 Guidance

Posted on 2013-01-10
3
705 Views
Last Modified: 2013-01-10
We are preparing to upgrade from vSphere 5 to vSphere 5.1 and I need a little guidance using Update Manager.

I recently installed Update Manager and the associated plugins. It shows that I have 6 critical and 41 non-critical patches for each of our 3 ESXi hosts. We are currently running ESXi 5.0.0 Build 474610, vSphere Client 5.0.0 Build 455961 and VMware vCenter Server 5.0.0 Build 913577.

I have heard that it is best to first install all incremental patches for 5.0 before performing the 5.1 upgrade. Can anyone confirm this is best practice?

Also, since we obviously did not keep up with patches since there are 47 outstanding how should I go about getting caught up? Can I just put a host into maintenance mode and remediate all 47 patches at one time? Is there anything I should be concerned about or do to prepare for this?

**I have plenty of available resources to evacuate one host at a time so  that isn't a concern for upgrading.

Thank you
0
Comment
Question by:AIC-Admin
  • 2
3 Comments
 
LVL 18

Accepted Solution

by:
xtermie earned 500 total points
ID: 38762823
It is better to actually install all incremental patches before updating.
I found full detailed documentation for the update to 5.1 here:
https://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-51-upgrade-guide.pdf

Whenever I look for such patches I go here, and usually I find them:
https://my.vmware.com/web/vmware/downloads

Hope you have a smooth update!
0
 
LVL 3

Author Comment

by:AIC-Admin
ID: 38762894
Thank you very much for the link to the upgrade PDF and the patch download location.

As for my current incremental updates... do you see any reason why I wouldn't just remediate all 47 patches at one time?

Thank you again!
0
 
LVL 18

Expert Comment

by:xtermie
ID: 38763055
I dont see why not
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question