Showing results for 
Show  only  | Search instead for 
Did you mean: 
Engaged Sweeper
I have a couple of assets reporting in via LSAgent.

It seems however to take a considerable amount of time until the following fields are visible on the assets page:

  • OU:
  • Enabled in AD:

Understandibly Lansweeper is attempting to scan these machines however it isn't possible as they aren't on a network which Lansweeper can scan hence the use of LSAgent.

Is there something that triggers adding this information?

I've tried adding Active Directory Computer Path and Active Directory Domain for the particular OU these computers are located in, however it seems all this is doing is grabbing the list of computer objects from the specified OU in AD then adding to the scanning queue which eventually fails due to the machine not being on the network. Hence again the use of LSAgent.

Eventually these fields do appear but not sure what makes that happen as I though it could be linked to Active Directory Domain scanning options (applies to all domains) - which is set to 15 minutes but after 15 minutes of the asset appearing via LSAgent they still don't show this information.

Anyone else come across this one before?