/build/static/layout/Breadcrumb_cap_w.png

How to locate workstations with Client Installed but not being inventory

I recently came across a situation where a machine had the client installed and connected to the appliance, but would not inventory nor show up as a device.  It got me wondering, is there a way to locate clients that have not completed the inventory and missing from devices?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Timokirch 1 month ago
5th Degree Black Belt
0

Hey,

have you checked the device quarantine? This is a new security feature. You have to provide a token otherwise the device is untrusted. 

Kind Regards

Timo

Posted by: noviwinger 1 month ago
White Belt
0

Devices are not in quarantine.  In the case the first brought this to my attention, the machine had a problem with the WMI and could never finish the inventory process.  Fixing the WMI wasn't hard, but now I am concerned I may have other machines experiencing a similar problem.  I am trying to figure out a way to recognize these machines to address the issues, rather than waiting to find out they are months behind in updates.

The problem machine was discovered because it was supposed to be part of a smaller group that was supposed to receive an update to an application and it would not, I then discovered it was not even listed in devices. Though the agent on the client side said it was connected with a GOOD status.

I find this very disconcerting! 


Comments:
  • I recently found one as well. kace agent was installed w/token by our MDM as usual but it isnt in inventory. Have not resolved yet but I agree, it would be nice to know if something isnt in inventory. Perhaps we need to setup a discovery scheduled to run on all networks and then somehow compare those found to device inventory. I too am also concerned.. I just happened across the device. I had a tech team member the other day with same issue on a new laptop. I ended up having him run the amptools host= token= from command line to get it to show up. This is odd because again, our MDM sends the agent WITH the token which normally works fine. FWIW we are challenged with this same problem with our anti-virus software.. determining where it isnt running.. and then on top of that, our MDM agent.. this is just part of the ongoing process we deal with... life goes on. - barchetta 3 weeks ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ