Inconsistent Naming of VMWare version?

[dmathias]

Flexera On Prem FNMS 2019 R1 and matching agents

Does anyone understand why "Model" attribute in Inventory view of UI reports both "VMware Virtual Platform" and "VMware7,1"?  Why would this not be normalized to a common value?

Thanks,

David Mathias

NTT DATA Services

[kclausen · Accepted solution]

FNMS does not perform any type of normalization for the Manufacturer or Model Number fields.  In effect, we are simply taking in and displaying the raw values received from the Inventory Source (SCCM, Flexera Agent, vCenter SDK, etc.)

[dmathias]

@kclausen - OK, so nothing is broken at our end, then.  If it's important enough for us to have these values normalized, I assume we'll figure out how to do it in back-end tables.

Thanks, David

[gilesogram]

We have some vSphere v8 hosts/vCentre/infrastructure. Why does this show as VMwarev20,1?

[JohnSorensenDK]

@gilesogram 

You may want to investigate the .ndi file generated from this vCenter environment to better understand what is being collected and with which version(s). (20.x versions could indicate that it's some NSX version, but without further details I'm just guessing...)

Thanks,

[gilesogram]

Hi, so we have found that the VMware20,1 seems to be linked with the ESX Compatibly setting of the VM within vCentre. The VMs which are running on vSphere v8 hosts and are set as ESX v8.0 U2 or later (VM version 21) are showing within FNMS as Model VMware20,1

VMs running on the same vSphere v8 hosts but with the ESX Compatibility set to ESX v6.7 and later (VM version 14) are showing as a VMware7,1 Model.

We will check what is being picked up on our Production system, but likely to raise a support case.

[JohnSorensenDK]

@gilesogram 

Yes, please create a support case if you believe that Flexera's content isn't correctly matching the versions.

Thanks,