Tag Archives: vSphere 6

How to update VMware vSphere Update Manager 6

I could not find an article on how to update VMware vSphere Update Manager. There are many articles on how to do a fresh install. I found these articles from VMwareAndMe and vladan to be clear and informative. There is also a good set of tips from one of my favourite source, Notes from Michael White, which you can find here.

The update does not show the version number as 6.0 Update 1. Instead, it’s showing as 6.0.027278. The Update Manager for vSphere 6.0 build no is

To start, download the Windows ISO. It is not a separate install. It is part of the vCenter. Once downloaded, mount the ISO image from the Windows VM where your Update Manager is installed.

Stop the Update Manager service from Windows services. I’m using Windows 2008 here.


Do not tick the box for the Embedded Database Option, as you already have a database. Click Install button.


Don’t worry that it does not the Upgrade option. It will detect that you have existing instance, as you can see below.


It will inform you that it will update the current version to build 27278. It does not say Update Manager 6.0 Update 1.


[8 April 2016 update: The same case with vSphere 6 Update 2. It will only say build 29963]

You get the usual prompt that it was installed successfully. The main installation window was not closed automatically, as you may want to install other thing.

It does not start the service in my case, so I just started it manually. No need to reboot Windows. Close your Update Manager VM server. You’re done with this VM 🙂

Go to your Admin Clien. Update the vSphere C# client plug-in. It should detect that you have the latest version. This time around, the installer shows you Update 1.


And that’s it! Login to your Web Client, and you should see all your Update Managers. I have 2 Update Managers, and both are listed. Interestingly, one was shown as the IP address.


To use the new UI, head over to this blog.

BTW, if you are using HP Proliant Server, and wants to integrate HP add-ons, head to a good write up here.

Happy updating!

Redirect vCenter 6 Appliance to a new Platform Services Controller

I need to redirect my vCenter. There is a good KB article here, so I will only add complimentary info.

The first step is to enable the BASH Shell and SSH.

0 enable SSH

Once done, you’re ready to login remotely. I use Putty as my favourite SSH tool. From the Command>, simply type shell.

That will take you to BASH Shell, which you have enabled earlier.

The first step is to change the setting. You issue the command:

/usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name --server-name localhost --dc-name name_of_second_PSC

I used the FQDN name. Here it is in my case:

/usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name --server-name localhost --dc-name core-platform-sc-1.core.lab

As you can see below, there was no feedback. So I’m not sure if it’s successful or not. I guess it is as it’s a simple change of a property.


The next thing is to essentially reboot. You can do it via GUI, or just from the CLI as I did above. The good thing about the CLI is it shows more details. As you can see below, it’s a long list of services.


After a good few minutes, it finished, and you get the shell again.


The next is to start the services. That’s all you are supposed to do. Your story should end here. MIne did not 🙂

After that, I could not login to my vCenter using my AD credential. I tried both the C# client and Web Client. I also saw that the Web Server is initializing, as you can see below. I waited for it to complete. After it was settled down, I still could not login. I could login to the new PSC, but I do not see any vCenter.

21 web client takes time to initialize

I found out that I needed to register my PSC to AD. I thought this step was taken care off when I deployed the new PSC, as I deployed it to the same Domain and Site. I checked and it was joined. As you can see from the following screenshot, it was blank. Luckily, to register to domain is pretty simple.


You need to reboot. Once done, it should look something like this.

31 all good

That’s all it took to redirect a vCenter to a new PSC. Happy redirecting!

vSphere 6 Update 1 Appliance installation error

I encountered an issue while deploying a new vSphere 6 Update 1 Appliance. It is not an update, so I was merely deploying a new one. The installation is the same, except that we can now specify a vCenter instead of ESXi as the target deployment.

Everything started well, with the usual mounting of the ISO file into my dedicated Admin Client (a Windows 7 machine). I’ve used the Admin Client for years, so it has everything configured properly. I’ve also deployed and vSphere 6.0 from it, so I know it works.

Then I hit a problem below. It’s a blank error message, so I could not google it.

I tried different combination:

  • Using vCenter or ESXi.
  • Using root or other administrator.
  • Using IP or FQDN.
  • Using different Windows account. I had issue with my roaming profile, which causes my VM to have HA event.

Nothing worked. Still the same error message.


Perhaps it’s the ISO. I tried with the vSphere 6.0 (not the U1) as I still have them. It worked!

Then it dawned upon me that maybe it’s the Client Integration Plugin. I had version 6.0, but perhaps it needed version 6 Update 1. So I went to the vcsa folder. Apparently the version has gone up too. I opened the version file and it’s now version build 3018521


I installed the Client Integration plugin. I then launch the installation process again. From the screenshot below, you can see that you can specify vCenter instead.


Voila, the installation is happy! In the screenshot below, you can see I’ve passed that Step 2.


One more thing. I’m joining into an existing PSC Domain and Site. This could be the reason why it’s not allowing me to specify a different appliance size.


After a couple of minutes, it’s all done!