For this, the name of your Lansweeper scanning server must be included in your command.
If the machines you're scanning are in the same network as your Lansweeper installation or have a connection to the installation through for instance a VPN, scanned data can automatically be sent back to Lansweeper. How the scanned data reaches your Lansweeper installation depends on how you are running LsPush and which parameters you are using:
How data scanned by LsPush reaches your Lansweeper installation It can be integrated into logon scripts, group policies, scheduled tasks, custom scripts etc.It generates very little network traffic, only around 40KB for one scanned computer.It can scan computers running a Windows Home edition.It can scan computers of your remote employees, after which the results can be imported back into Lansweeper.It is immune to almost all scanning errors, including access denied and firewall errors.It does not require you to reconfigure your Windows computers' firewalls for scanning.It does not require administrative privileges to be able to scan.
It does not require you to submit scanning credentials.Because it scans locally, it has several advantages over agentless scanning, however: LsPush largely scans the same data as agentless scanning methods. If you have just updated Lansweeper and are scanning with LsPush in a logon script, group policy or scheduled task, copy the up-to-date LsPush to any folder referenced by your script, policy or task. Make sure to use the latest LsPush executable to scan your machines, as scanning with old agents can cause incomplete data to be returned. When you update your Lansweeper installation, the latest version of the LsPush executable is automatically added to the Client folder on your Lansweeper server.
0 kommentar(er)
