Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2064
  • Last Modified:

Updates showing as conflicts in VMWare Update Manager

Hello Experts,
I am in the process of attempting to update our ESX 4.0 host systems using vSphere Update Manager.  After scanning the host with the default baselines, there are 49 applicable patches.  Five of these patches are shown as being in conflict in the Compliance column.  Should I deselect these five patches when I go to stage and remediate the host, or if I leave them selected, will the patch process not attempt to install them due to the fact they are in conflict?  Then, after proceeding with the remediation process, should I then scan the system again to see if these five can then be installed?  Am I still relatively new to this process and need some guidance in how to proceed in general.  Thanks in advance for your help.
Russ  screen shot of conflicting patches
0
rdillion
Asked:
rdillion
  • 4
  • 4
2 Solutions
 
Danny McDanielClinical Systems AnalystCommented:
if you click on each one, in that view that you posted, it should say what it is in conflict with.  That will help determine if you should ignore it or not.
0
 
rdillionSystems AdministratorAuthor Commented:
Hey danm66,
Thank you very much for your help!  I had not noted that before, but in looking at the five patches with conflicts, they all indicate the conflicts are with patches for the Cisco Nexus 1000V switch appliance, which I do not have installed.  Futher, they all have detail information similar to the following:

The selected Update conflicts with following Updates in VMware vCenter Update Manager patch repository:
VEM400-200904001-BG, VEM400-200906002-BG, VEM400-200907001-BG, VEM400-200909001-BG, VEM400-200911014-BG, VEM400-200912001-BG, VEM400-200912016-BG, VEM400-201002001-BG, VEM400-201002011-BG, VEM400-201003001-BG, VEM400-201003011-BG, VEM400-201005001-BG, VEM400-201005011-BG, VEM400-201005021-BG, VEM400-200904001-BG, VEM400-200906002-BG, VEM400-200907001-BG, VEM400-200909001-BG, VEM400-200911014-BG, VEM400-200912001-BG, VEM400-200912016-BG, VEM400-201002001-BG, VEM400-201002011-BG, VEM400-201003001-BG, VEM400-201003011-BG, VEM400-201005001-BG, VEM400-201005011-BG, VEM400-201005021-BG.

These patch repository conflicts will NOT affect stage and remediation unless the conflicting Updates are contained in the baseline(s) 'Critical Host Patches', 'Non-Critical Host Patches'.

When I look at the Compliance column for the patches related to the Nexus switch, some say Not Applicable, but most say New Module.  However, when I then go to the staging screen that shows the individual patches that are selected for staging, none of the Nexus patches are listed.  I am assuming that I can therefore procede with the staging and remediation process of these patches as none of the Nexus patches are selected to be included in the process?  Just want to be sure I am not missing anything.
Thanks again,
Russ Cisco Nexus V1000 patches in list
0
 
Danny McDanielClinical Systems AnalystCommented:
Yeah, you can ignore them or do a custom baseline that doesn't involve any cisco patches.  see http://kb.vmware.com/kb/1013068 

What version is your vCenter server?  I thought they worked on this conflict messaging to make it less disconcerting when this came up???  If your VC isn't at 4.0 U2 or 4.1 U1, you should probably upgrade it.
0
NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

 
rdillionSystems AdministratorAuthor Commented:
Thanks again for all of your help danm66!  I'll take a look at that article and see if I can get this taken care of.  My vCenter Server is at 4.0.0.  The local consulting group that helped me set up our environment has pretty much left me high and dry with regard to ongoing support, so I am trying to get up to speed on as much as I can. I'll see if I can find any links etc. on upgrading our vCenter Server and put that on the list.  
0
 
Danny McDanielClinical Systems AnalystCommented:
http://www.vmware.com/support/pubs/vs_pages/vsp_pubs_esx41_vc41.html has an upgrade guide under the 'Guides' tab.  The main thing is that VC4.1 requires a 64-bit OS, but there is a migration tool to move your database to the new server.
0
 
rdillionSystems AdministratorAuthor Commented:
Thanks for the link, I took a quick look and will get into it more tomorrow.  My hosts are all ESX 4.0 and I know that I will need to upgrade them to 4.1 as well.  I downloaded a video from the VMWare site on that process on Monday and it looked fairly straight forward.  In that scenario, should I upgrade the hosts first and then upgrade the vCenter server install, or do the vCenter server first then the hosts, or does it matter?  I currently have vCenter server installed on a Windows 2008 Server 64 bit guest system, so I am hoping that I will be able to do an "in place" upgrade on the same system.
Thanks again danm66, I really appreciate all of your help on this!
Russ
0
 
Danny McDanielClinical Systems AnalystCommented:
Always upgrade the vc first.

Yeah, you can do an inplace upgrade of your vc.  Just run the setup routine which will bring up a menu and click on each component to run through its wizard.  Backup the vm/db first and you should be good to go.
0
 
rdillionSystems AdministratorAuthor Commented:
Cool, thanks again very much!!  Have a good rest of week and weekend!!  :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

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.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now