‎03-08-2017 09:38 PM
Solved! Go to Solution.
‎03-13-2017 11:40 AM
‎07-13-2017 05:06 PM
‎03-13-2017 11:40 AM
‎06-18-2018 06:45 AM
Bruce.B wrote:
LsClient is mostly a legacy executable at this point, which was necessary for the old freeware model. What LsClient does is send a "scan me" request to your Lansweeper server from the local computer, after which your Lansweeper server still needs access over all the required ports to send the scanning queries.
We recommend using the LsPush scanning agent instead. LsPush is a small executable that, when run on a Windows computer, scans the computer locally. The scan results can manually or automatically be forwarded to your Lansweeper server for import. You can find the LsPush executable in the Program Files (x86)\Lansweeper\Client folder on your Lansweeper server. LsPush can easily be deployed in domain environments with a logon script or group policy. A sample VBS script that runs LsPush can be seen below. You will need to replace what we've highlighted with the folder hosting the LsPush executable and the name of your own Lansweeper server. If you deploy this script as part of a logon script or group policy, LsPush will automatically scan your machines when users log into them and send the results directly to your Lansweeper server for import. More info on LsPush and its parameters can be found in this knowledge base article. General info on setting up a logon based group policy, not specific to LsPush, can be found here.
Set WshShell = CreateObject("Wscript.Shell")
WshShell.run "%logonserver%\netlogon\lspush.exe lansweeperservername ",0
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now