LsClient was a scanning tool for Windows computers. From Lansweeper version 6.0.100 onward, LsClient is no longer supported and no longer works. It is no longer included in new Lansweeper installations either. Use of old versions of the tool in combination with new Lansweeper installations will result in a "connection to server failed" error. LsClient has been discontinued in favor of the more powerful and more secure LsAgent and LsPush scanning agents.
Although the name would suggest otherwise, LsClient was not a true client or scanning agent. It was an executable that, when run on a Windows client machine with specific parameters, would send a request to your Lansweeper scanning server to scan the client machine. The scanning server would then scan the client machine. LsClient itself did none of the scanning. By deploying it using a logon (not startup) script or group policy, LsClient could be used to trigger scans of multiple Windows computers.
Below is an overview of parameters LsClient accepted when it was still supported. If you attempted to run LsClient.exe without parameters, the resulting popup would list available parameters and sample commands as well.
- <IP address or name of your Lansweeper scanning server>
A required parameter that would tell LsClient which scanning server to send its scan request to. This scanning server would then scan the client machine.
A parameter that would tell LsClient to contact your scanning server on a specific port. Inclusion of this parameter was optional if default port 9524 was used.
An optional parameter that would cause the scanning server to connect to the client machine's IP address instead of its name during scanning. Using this parameter was useful in cases where DNS resolution of the client machine's name failed.
An optional parameter used for testing and troubleshooting purposes, which would return visual feedback as to whether the connection to the scanning server succeeded.