Home > VMware, vSphere > Fixing VMware Update Manager After Changing vCenter Server Host Name

Fixing VMware Update Manager After Changing vCenter Server Host Name

Recently I encountered a problem with the VMware Update Manager after I changed the host name of my vCenter Server.  Turns out that some reconfiguration is necessary.  This is the error message that is presented when I started the vSphere Client and it attempts to load the Update Manager plugin:

Okay let’s fix this.  Go to Start, right click My Computer, then in the menu select Management.

On the left open up “Services and Applications” and click the Services branch.  In the right pane right click the VMware Update Manager Service and select Stop.  Keep the Computer Management MMC open for now.

Now open up Wordpad and we need to edit a file.  The file doesn’t open correct with Notepad.  Browse to the following file:

If using 32-bit Windows edit C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml.
If using 64-bit Windows edit C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vci-integrity.xml.

Search the file for this XML tag:


Replace the “Old_vCenter_Server_Name” or IP Address with the new host name.  I used the FQDN and it worked fine.

Switch back to the Computer Management and right Click the VMware Update Manager Service again and select Start.

Now open up the vSphere Client and it should start and load the Update Manager plugin with no errors.  Yes!



Categories: VMware, vSphere Tags: ,
  1. September 30, 2011 at 10:16 am


    A few days ago I changed the domain name on a vCenter Server, and discovered pretty much the same as you… that VMware Update Manager didn’t work as expected.
    However; In addition to the vci-integrity.xml file, I found a few other places which I had to replace the old name with the new one as well.

    – Windows Registry
    – vSphere Client / vCenter Server Settings
    – ADSI Edit

    I have outlined it in more detail on my blog:

  2. Mike
    October 11, 2012 at 11:22 pm

    There is an update manager utility that ships with update manager. That tool makes it easy to make this change. See the vmware doc titled “Reconfiguration of VMware vCenter Update Manger” which explains how to use the utility. Ironically it does not allow changing the name by which update manager is identified on the nework (which would be quite useful for ensuring the identified name matches custom ssl certs), but it does everything else.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: