→ 🚀What's New? Join Us for the Fall Product Launch! Register Now !
‎08-23-2017 09:02 AM
Solved! Go to Solution.
‎08-23-2017 07:57 PM - last edited on ‎02-09-2024 11:49 AM by Mercedes_O
Unfortunately we've officially retired the usage of LsClient.exe in Lansweeper version 6.0.100 as indicated here and here, since Lansweeper version 6.0, LsClient was already a legacy tool as its usage was no longer required to direct scans for your Lansweeper server. In Lansweeper version 6.0.100 we made a change to the listen port of the Lansweeper server, directing all traffic to its listen port over https, which is incompatible with LsClient.
Scans can be set up directly under Scanning\Scanning Targets. For computers that aren't scannable by your Lansweeper server due to firewall issues, LsPush.exe can be used. For tracking more accurate logon information, LsPush can be used as well. For more information on LsPush.exe you can consult this knowledge base article.
‎08-23-2017 07:57 PM - last edited on ‎02-09-2024 11:49 AM by Mercedes_O
Unfortunately we've officially retired the usage of LsClient.exe in Lansweeper version 6.0.100 as indicated here and here, since Lansweeper version 6.0, LsClient was already a legacy tool as its usage was no longer required to direct scans for your Lansweeper server. In Lansweeper version 6.0.100 we made a change to the listen port of the Lansweeper server, directing all traffic to its listen port over https, which is incompatible with LsClient.
Scans can be set up directly under Scanning\Scanning Targets. For computers that aren't scannable by your Lansweeper server due to firewall issues, LsPush.exe can be used. For tracking more accurate logon information, LsPush can be used as well. For more information on LsPush.exe you can consult this knowledge base article.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now