Each time a rule is executed on a beacon server, a new logging folder will be created under C:\ProgramData\Flexera Software\Compliance\Logging\InventoryRule.
Under C:\ProgramData\Flexera Software\Compliance\Logging\InventoryRule\<GUID>, in the VMWareInventory.log for the rule execution, you will see a note similar to the following:
[INFO ] Queued virtualization inventory execution on device '<vCenterIP>' using protocol https and port 443
If you have both discovery AND inventory enabled for your vCenter rule, then you'll want to be sure that both the '<datetime>-{<GUID>}.disco' (Discovery) and '<FQDN> at <datetime> (VMWare).ndi' (Inventory) files are both getting uploaded.
You could also check the cluster and host (ESX) inventory date from the "Virtual Devices and Clusters" view. They should be up to date if the process works correctly.
Hello @chirag_sharma2 ,
Each time a rule is executed on a beacon server, a new logging folder will be created under C:\ProgramData\Flexera Software\Compliance\Logging\InventoryRule.
Under C:\ProgramData\Flexera Software\Compliance\Logging\InventoryRule\<GUID>, in the VMWareInventory.log for the rule execution, you will see a note similar to the following:
[INFO ] Queued virtualization inventory execution on device '<vCenterIP>' using protocol https and port 443
HTH,
Joseph
Thanks Joseph,
And How can I check if it is actually discovering and sending inventory files ?
The beacon's uploader.log (C:\Windows\Temp\ManageSoft) would be one way to check.
If you have both discovery AND inventory enabled for your vCenter rule, then you'll want to be sure that both the '<datetime>-{<GUID>}.disco' (Discovery) and '<FQDN> at <datetime> (VMWare).ndi' (Inventory) files are both getting uploaded.
HTH,
JosephHi,
You could also check the cluster and host (ESX) inventory date from the "Virtual Devices and Clusters" view. They should be up to date if the process works correctly.
Best regards,
Markward