Deployment After Scan

[sullivane]

Will that work with LSPUSH or just active scanning?

Also, it has Deploy On, so how would that work? One machine is scanned in that group and it scans all or just the one that was scanned?

[Daniel_B]

sullivane wrote:
So the difference is that the client will tell the server to scan the computer, whereas the push will scan the computer and update the server?

Yes, correct.

sullivane wrote:
So if I switch to the client, and have a schedule deployment (to a group that doesn't have java for example) for after scan, will it deploy to the whole group or just the client that was scanned if it's in that group?

"After scanning" always means: After one specific computer has been scanned, the package deployment will be started on this specific machine.

[Daniel_B]

No, LsPush won't trigger a deployment with "After scanning" schedule. As mentioned before, in your case you could replace LsPush.exe with LsClient.exe. LsClient won't locally scan the computer, it only triggers the target machine to be scanned by your Lansweeper server. But LsClient will initiate "After scanning" deployments.

[sullivane]

We use LSPUSH.exe instead of active scanning, because we want a log on who used which computer and when. We are a school and it's VERY useful in labs if something is broken, we have a history of who used it. It's setup to scan at login, so it records the current user.

So if I use "After Scanning", that is ONLY for active scanning? If LSPUSH updates the server, that does not count as a scan and will not trigger it?

[Daniel_B · Accepted solution]

LsPush scans can't be used as trigger for deployments. In general, LsPush is designed to be used if you have issues with firewalls or you can't provide scanning credentials with administrator access on scanned computers. These circumstances make remote deployment impossible. Lansweeper needs to be able to contact remote registry service and task scheduler on target computers for deployment.

If you would like to use an executable on network computers to trigger a scan and a deployment, you could use LsClient.exe (which we normally don't recommend as other agentless scanning methods like Active scanning or IP range scanning are much more flexible).

The deployment target ("Deploy On") can either be an asset group (static or dynamic), a report (all assets currently listed by a specific custom report) or a manual selection of assets. Lansweeper will deploy the packages to the computers listed. The "After scanning" schedule would initiate a deployment on one computer which is listed in the target computer after it has been scanned. It doesn't deploy to all assets of the group, only to the computer which was scanned. Details on how to set up deployment schedules can be found in this KB article.