Infrastructure Navigator – solving vCenter Extension issue

My Infrastucture Navigator setup was broken and I had to deploy another one. I had issue deploying the virtual appliance, as can be seen below, because the old setup was not uninstalled properly. The problem below means there is already an extension registered to vCenter.

error - unable to deploy VIN due to missing provider

I verified with the vCenter Server Extension page and it’s true that the old version is still lingering. Notice the version number is 5.8.0.117. It is registered to vCenter named SDDC-DR-VC. I need to remove this extension.

error - unable to deploy VIN due to missing provider 2

To remove it, I did some google and found the exact answer at William Lam blog. The actual post on how to remove the link is here. He covers it clearly, so please read it first to get familiar. I am adding the Infrastructure Navigator specific info below. William talked about the need to find the key, so here is the key of Infrastructure Navigator. Notice the name is vadm. That stands for VMware Application Dependancy Manager.

error - unable to deploy VIN due to missing provider 3

So I follow William’s post and invoke the method to remove the extension.

error - unable to deploy VIN due to missing provider 4

Execution was fast, and you can see the entry is gone from the screenshot below.

error - unable to deploy VIN due to missing provider 5

Verifying with the vCenter Extension page, you can see it’s gone. So the problem is solved!

error - unable to deploy VIN due to missing provider 6

With the issue solved, I went to deploy a new appliance. A few minutes later, the appliance is up and you can see from the screenshot below that it’s registered. Notice the version is 5.8.3.140. I have 2 entries there as I deployed on 2 vCenter Servers (Prod Site and DR Site).

error - unable to deploy VIN due to missing provider 9

Here is what it looks like after the initial deployment. You need to register it with the vCenter.

error - unable to deploy VIN due to missing provider 7

Registration is simple. In proper production, you should use a service account. It is useful that VIN displays the account used to register.

error - unable to deploy VIN due to missing provider 8

One thought on “Infrastructure Navigator – solving vCenter Extension issue

  1. Pingback: Newsletter: January 4, 2015 | Notes from MWhite

Leave a Reply