cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Asset not found

Jump to solution

Our support Analyst send us a list of Laptop they do not find in FNMS but they have been build and so they have been connected to the network at some point. I looked for them also but could not find them.

How can you explain this?

Thank you 

0 Kudos
1 Solution

 

Thank you for your reply, after deeper investigation we found out those asset did not have DSN. All the devices are old/surplus/not talked to SCCM in over 90 days  

 

View solution in original post

0 Kudos

This thread has been automatically locked due to inactivity.

To continue the discussion, please start a new thread.

2 Replies
rmiller1
Level 6 Flexeran
Level 6 Flexeran

Hi Jean,

This could be a number of things. Firstly, lets ensure you are looking in the correct place. Your email indicates that the laptops are built, and connected, so this implies that you are talking about what we would call Inventory Devices. Please don't confuse this for FNSM 'Assets' which are a representation of the purchased asset, and do not come into FNMS via discovery / agents.

If you are looking in All Inventory and still do not find these, you should confirm that the agent (assuming a FNMS agent is deployed) is correctly configured and can 'see' the Beacon server. Sometimes agents are installed in their default config, without a Beacon server address specified - so they don't know where to report to! Then I would look at the last time inventory was processed from the server, this should be nightly (for most organizations) but may take longer, depending on configuration.

This information is explained further in our "Gathering FlexNet Inventory" documentation. Please have a look here as it will provide ALL of the options/info you need to check and confirm where your laptops are.

Hope this helps,

R.Miller
0 Kudos

 

Thank you for your reply, after deeper investigation we found out those asset did not have DSN. All the devices are old/surplus/not talked to SCCM in over 90 days  

 

0 Kudos