This is a known issue, but it is only a "display" issue. Meaning, even if it states unknown, everything should be working fine, so in practice you should not look at this at all.

If other then that it works fine, I wouldn't worry about it.

Gal

VIN only works on the web client. Where have you tried looking for the VIN options? Under which screens?

You mention that you were able to apply a license key to the web client and get it up and running (so to speak).  Where did the license key come from?  I have been looking all over the portal and we have an Enterprise Plus contract.  However, all that is in the Infrastructure Navigator section is the vApp, and a couple of spreadsheets - no license key.   HELLPPP!!!

vCenter Infrastructure Navigator supports suite licenses for vCenter Server 5.5, 5.5U1, and 5.1U1 as well as vCenter Operations Manager Suite 5.6 or later, and VMware vCloud Advanced and Enterprise Suite 5.1 or later.

That was my thought as well.  However, each time we have attempted to use the license key from the vCOPS for Infrastructure Navigator, the system comes back with an error stating that the key belongs to a different asset.  That's the key which is named "VMware-vcops-5.6.0.0r-ENT-License_Key_for_VC_5.0.txt.  It only works for vCOPS itself.  I have a ticket submitted to VMware now about this, but they seem a bit confused which tells me that this might be an error that no one has picked up on yet.  If you have any suggestions on a 'workaround' or guidance as to what is happening, I would be most grateful.

Hello, we have the same issue but with this environment:

VIN 5.8, vCenter Server + SSO + Web Client 5.1

But we can't see anything. There is not VIN asset in the License area. There is no VIN plugin in the vSphere Client neither in the Web Client.

We have rebooted the vCenter Server and the VIN appliance.

Any help? Thanks.

Hi,

VIN 5.8 does not support VC 5.0 nor the suite license for VC 5.0.

This is why you cannot deploy"VMware-vcops-5.6.0.0r-ENT-License_Key_for_VC_5.0 to the Infrastructure Navigator.

Thanks,

Galit

Hi,

It seems that the VIN extension registration did not succeed.

This might happen because of a communication problem between the VIN appliance to the VC.

Please make sure that the communication between the VC and VIN works, and restart the "vsphere web client" service.

Then a restart to the VIN VA might re-register the VIN extension to the VC.

Thanks,

Galit