Hi,
I can‘t get
After Scanning deployments to run on Windows 10 clients when using LsAgent.
The LsAgent scanning itself works fine, but the deployments are simply not being triggered by/after the scan.
What
does trigger a deployment, for example:
- a manual Rescan asset
- an IP Range scan on the asset‘s IP address
I created a
Scheduled Deployment for a single selected asset with
Execution Plan = After Scanning.
Results:
LsAgent- Client computer starts up
- A few minutes later, I see that the asset‘s Last LsAgent Scan has been updated.
- No deployment is triggered (no entries under Installer Logs or under the asset‘s Deployments tab).
LsPushThere is conflicting information on the forums whether LsPush is supposed to trigger
After Scanning deployments, so I thought I‘d try it as well.
Unfortunately, the results are similar to LsAgent: The asset‘s
Last Lspush Scan is updated, but the deployment doesn‘t happen.
In either case the
Last Execution date for the Scheduled Deployment stays at
Not Executed.
Does anyone have any pointers how to
reliably trigger automatic deployments – either via
After Scanning or through a client-side command?
Thanks in advance!
Lansweeper server 8.1.120.3
LsAgent 7.2.110.18
LsPush 7.2.100.1.