LsAgent is a cross-platform, lightweight scanning agent that you can install on Windows, Linux and Mac computers. It automatically collects an inventory from the computer it's installed on and sends the data back to your Lansweeper installation, either directly or through our relay server in the cloud. Data is securely sent to the relay server over HTTPS (TLS 1.2), stored in an encrypted format and deleted once a scanning server has retrieved it. More information on LsAgent can be found in this knowledgebase article.
If you are scanning client machines using LsAgent and migrate your Lansweeper installation, there are some things to keep in mind to ensure your clients continue to successfully scan. This article explains the impact of migrating the Lansweeper server that receives LsAgent scans, both for installations that connect to our LsAgent relay server and installations that receive LsAgent scans directly from client machines.
Migration impact when using the relay server
When you first enabled the use of the relay server in the Scanning > Cloud Relay Configuration menu of your Lansweeper Classic installation, a relay authentication key was generated. This key is one of the properties used to uniquely identify your Lansweeper installation on the relay server. You submitted this key in the LsAgent installer on your client machines as well.
In addition to your relay authentication key, your Lansweeper license key and a unique identifier (GUID) generated during the setup of your Lansweeper installation are also used to uniquely identify your installation on our relay server.
Using these properties, the relay server can match LsAgent scans it receives from client machines to the correct Lansweeper installation. To ensure your LsAgent clients continue sending data over the relay after a migration of your Lansweeper installation, it is crucial that:
- You leave your correct Lansweeper license key applied to your installation after the migration. Ordinarily, if you correctly migrate your installation and Lansweeper database, your license key will automatically be migrated as well.
- You have your migrated installation take over the LsAgent scan retrieval. To do so, click the Override Relay Access option in the Scanning > Cloud Relay Configuration menu of the migrated installation.
By doing the above, your migrated installation will retain your original relay authentication key and no changes are required on your client machines to allow them to continue scanning.
Migration impact when not using the relay server
If your LsAgent clients are sending data directly to your Lansweeper installation, without going to the relay server first, there are still some things to keep in mind when migrating the installation.
When you installed LsAgent on your client machines, you submitted either the name or IP address of your Lansweeper scan server in the LsAgent installer. This is the server the clients are sending their data to. When you migrate your installation, that server name or IP address may change. To ensure your LsAgent clients continue sending data directly to your Lansweeper installation after a migration, keep the following in mind:
- Leave your original Lansweeper installation running while you migrate to your new server.
- Make sure your new server's firewall allows inbound connections over whichever port you configured as your listen port in the Configuration > Server Options section of the Lansweeper Classic web console.
- Check the Server value listed in the LsAgent.ini file of one of your LsAgent installations, found at
Program Files (x86)\LansweeperAgent\LsAgent.ini. This value will either be the name or IP address of your old server. - Either:
- Give your new server the same name or IP address as is listed in your LsAgent.ini files, and update your DNS server to reflect this. That way, no changes are required to your LsAgent installations themselves.
- Link your new server to each LsAgent group in the Scanning > LsAgent Scanning section of the Lansweeper Classic web console, by using the Link Scanserver button in the Configuration tab. Afterward, wait for this configuration change to sync down to your LsAgent clients, which may take up to 24 hours. The clients will start sending scanned data to the new server.
