Device conflict between inventory sources

[Smitty987]

Hi,

We have a few inventory sources - TADDM, SCCM and the FlexNet agent

There are a small number of devices that, despite having the agent installed and uploading inventory, are not showing Flexera as the inventory source. They are, for some reason, reporting as TADDM being the source.

Flexera is set as the primary inventory data input.

Any ideas?

Thanks

[mfranz]

Hi,

You can try to follow the inventory trace back to the source to find out where they went missing.

1. Try ImportedComputer_MT to see if they were imported from all sources.
2. If the FNMS inventory is missing, then check the Inventory Database, tables Computer_MT and InventoryReport_MT.
3. If they're missing form there, check your Incomming Inventory folder for BadLogs.

Best regards,

Markward

[Smitty987]

Thanks

I have a device which is in ImportedComputer_MT - 3 lines all showing TADDM as inventory agent (strangely 3 different ExternalID, all other details the same)

Is in Computer_MT but not in InventoryReport_MT

Nothing in bad logs - this is checked frequently

[mfranz]

Here's how I see things:

• I have a device which is in ImportedComputer_MT - 3 lines all showing TADDM as inventory agent (strangely 3 different ExternalID, all other details the same)
  • This at least rules out failed inventory matching or something like this.
• Is in Computer_MT but not in InventoryReport_MT
  • The Computer_MT entry can be result of Beaocn AD integration, so that's ok.
  • Missing InventoryReport_MT entry indicates there never has been a FNMS Agent inventory file for this device.
• Nothing in bad logs - this is checked frequently
  • If it's not a bad inventory file, it's likely the inventory is missing completely. I would start checking the FNMS Agent on these devices.

[Smitty987]

[root@xxxxxxxxxxxxxxx ~]# /opt/managesoft/bin/ndschedag -e

Event Next Run Time
Generate Inventory 16/01/21 00:05:00
Update Machine Policy 13/01/21 12:16:00
Update Client Settings 14/01/21 01:05:00
Upload Client Files 14/01/21 00:56:00

[mfranz]

Maybe one of your Beacons "ate" the file/did not upload?

[kclausen]

Look in the TRACKER.LOG file on one of these devices.  Make sure that Inventory is being generated and that the NDI Inventory File is being successfully uploaded to a Beacon.

[Smitty987]

[Wed 13 Jan 2021 00:14:23 GMT (G, 0)] {30636} Connecting to upload location 'http://xxxxxxxxxxxxxxxxxxxx/ManageSoftRL/Logs/'
[Wed 13 Jan 2021 00:14:23 GMT (G, 0)] {30636} Upload username is ''
[Wed 13 Jan 2021 00:14:23 GMT (G, 0)] {30636} Upload proxy is ''
[Wed 13 Jan 2021 00:14:23 GMT (G, 0)] {30636} Uploading file 'xxxxxxxxxxxxx at 20210113T001414_{4F46C2F4-258E-46BA-9238-6B1797ABEC71}.log' to 'http://xxxxxxxxxxxxxxx/ManageSoftRL/Logs/'
[Wed 13 Jan 2021 00:14:23 GMT (G, 0)] {30636} File 'xxxxxxxxxxxxxxxxxxx at 20210113T001414_{4F46C2F4-258E-46BA-9238-6B1797ABEC71}.log' removed from upload directory
[Wed 13 Jan 2021 00:14:23 GMT (G, 0)] {30636} Upload successful
[Wed 13 Jan 2021 00:14:23 GMT (G, 0)] {30636} Uploading finished

[mfranz]

Did you check the Beacon upload location and beacon logs? Has the data been forwarded properly? It has to be somewhere... 

[Smitty987]

I agree but why only some devices affected - getting inventory reported from other devices that are using the same beacon?

[mfranz]

Have you tried searching for serial numbers instead of machine names (in ImportedComputer_MT)? I have seen cases where FNMS might not use the host name. Maybe the data is in there, but just not under the name you would assume.