vCenter VMWare inventory doesn't work with Discovery and Inventory Rules

[andreidrexler]

Hi Flexera community,

I have this situation with a client, where the Discovery and Inventory Rule doesn't discover and inventory VMWare devices for two IPs. 1988 device inventoried, 4 skipped and 1984 failed (see SS1).

Meanwhile, if I run the ESXQuery.exe on the beacon for both IPs, I inventory about 44 devices, 22 from each IP.

For now I've set up a script that queries the ESXQuery for the two Ips, then copies the files into the Incoming folder, so it gets upload into FNMS. But I would like to make the Rule work by itself.

The rule configuration can be found in SS2

As for Targets, the only two IPS are added, with their respective subnets. 
Also subnets assigned to the right beacon.

Pingsweep -ps registry key also added on beacons.

Service account works, clearly, because ESXQuery uses that same account.

Service account added on the Inventory Beacon App, with filtered IPs

Am I missing something here?
Thank you

[kiransuthar]

Hello Flexera, 

Even i could face a similar issue, where we have 10 vcentres and vmware inventory happening only for 5 and for remaining 5 those not at all exists but overall it shows completed with error and no clear picture on error one's ? 

[mschwach]

Hi,

we have the same issue here and also tried to modify the Registry on the Beacon according to Flexera advices. But newly added vCenters are not discovered by the standard rule-settings in FNMS, even though there are already existing vCenter connections and these are working properly.

We also opened a Case for this missbehaviour.

What Level of FNMS you are driving? We are on "on-prem" 2023R2.