LSPush.exe Versioning?

[bnelson0523]

Hello

We are considering deploying the LSpush.exe to all our PCs and create a Scheduled Task to run these scans locally.
With putting the LsPush.exe file onto 100's of PCs - what is going to be the impact when we upgrade our LS Servers in the future?
Could there be some compatibility issue with the older versions of LsPush.exe on these PCs?
Is there any plans to create some sort of LsPush.exe automatic upgrade?

Are there any real "gotchas" with using LsPush.exe to obtain info from remote computers/users?

Any comments?

[Bruce_B · Accepted solution]

You would have to replace LsPush every time it receives an update during a Lansweeper update. We don't update LsPush with every update, but we do update it quite frequently. We would recommend using the latest version of LsPush at all times for an optimal scanning experience.

If possible we would recommend calling LsPush.exe from a network location rather than pushing it onto every single computer, this also saves a lot of effort when LsPush gets updated.

You can find information on LsPush and its parameters in this knowledge base article: https://www.lansweeper.com/kb/24/how-to-scan-with-LsPush.html

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. General info on setting up a logon based group policy, not specific to LsPush, can be found here: https://www.petri.com/setting-up-logon-script-through-gpo-windows-server-2008

Set WshShell = CreateObject("Wscript.Shell")
WshShell.run "%logonserver%\netlogon\lspush.exe lansweeperservername",0

[servicedesk]

In my experience having LSPush for some years as scheduled task, set up to be triggered at logon and at new network connection:

- For remote workers that connect via VPN, you have an update of the machine, useful if you need do remote control or just have updated information about security patches, new software installed, etc...

- Old versions of LSPush may affect on the data retrieved. I remember a particular case that lspush wans't scanning my custom setup file scannings.

- LSPush doens't trigger after scanning deployments like the LSClient do.



Regards

[brians]

Anyone at LS that can answer? This is a valid question.
Thanks,