→ Upcoming Keynote Event - Introducing Lansweeper's 2023 Spring Release: 'Duvel' - Learn More

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Lansweeper Tech Support
Lansweeper Tech Support

Moving your Lansweeper server configuration manually from one scanning server to another can be straightforward but results in the old server being removed. This article introduces a more accessible method that achieves the same result by running a database script. The advantage of this script is that the old server will not be removed.

The script copies the configuration (threads, cleanup settings, and active scanning options) from the old source server to the new destination server. For this script to work correctly, the new server's service must have started successfully at least once. 

This process can easily break your installation. We recommend backing up your database before continuing, as explained in this knowledge base article
  1. Open SQL Server Management Studio and connect to the SQL Server instance hosting your Lansweeper database.
  2. Modify the script below with the name of the source server you're copying the config from.
  3. Modify the script below with the name of the destination server you're copying the config to.
  4. Stop the Lansweeper Server service on your destination server.
  5. Execute the following script via a New Query window.


Use Lansweeperdb

 UPDATE tsysASServers


      [Listenport] = existing.listenport,

      [ConcurrentThreads] = existing.[ConcurrentThreads],

      [IPscanThreads] = existing.[IPscanThreads],

      [RMADCOMP] = existing.[RMADCOMP],

      [NAADCOMP] = existing.[NAADCOMP],

      [RMADUSER] = existing.[RMADUSER],

      [MAKEACTIVE] = existing.[MAKEACTIVE],

      [DELHIST] = existing.[DELHIST],

      [DELHISTDAYS] = existing.[DELHISTDAYS],

      [DELCOMP] = existing.[DELCOMP],

      [DELCOMPDAYS] = existing.[DELCOMPDAYS],

      [NACOMP] = existing.[NACOMP],

      [NACOMPDAYS] = existing.[NACOMPDAYS],



      [REFRADCOMP] = existing.[REFRADCOMP],

      [REFRADUSERS] = existing.[REFRADUSERS],

      [RMDIUSER] = existing.[RMDIUSER],

      [RMDICOMP] = existing.[RMDICOMP],

      [NADICOMP] = existing.[NADICOMP],

      [Scanuser] = existing.[Scanuser],

      [EVinfo] = existing.[EVinfo],

      [EVsuccess] = existing.[EVsuccess],

      [DELUptimeDays] = existing.[DELUptimeDays],

      [EVwarning] = existing.[EVwarning],

      [EVfailure] = existing.[EVfailure],


      [renamedComputerDetection] = existing.[renamedComputerDetection],

      [MaxDeploymentThreads] = existing.[MaxDeploymentThreads],


      [ScanHistoryDays] = existing.[ScanHistoryDays],

      [ActiveScanningMaxRescanTime] = existing.[ActiveScanningMaxRescanTime],

      [ActiveScanningMinRescanTime] = existing.[ActiveScanningMinRescanTime],

      [ActiveScanningInterval] = existing.[ActiveScanningInterval],

      [Delconfigurationlogdays] = existing.[Delconfigurationlogdays],

      [Delloginlogdays] = existing.[Delloginlogdays],

      [DoFallbackScanning] = existing.[DoFallbackScanning],

      DelPerformanceCounterDays = existing.[DelPerformanceCounterDays]

FROM tsysasservers

     INNER JOIN tsysasservers existing ON existing.servername = 'sourceserver'

WHERE tsysasservers.servername = 'destinationserver';


If you want to move your entire Lansweeper installation to a different server instead of the configuration, please follow the steps in this knowledge base article
Was this article helpful? Yes No
No ratings

New to Lansweeper?

Try Lansweeper For Free

Test Drive Lansweeper Yourself. Explore our interactive Demo or sign up for free 14-day trial.

Try Now
Knowledge Base Dashboard
Article Dashboard
Version history
Last update:
‎02-08-2023 04:45 PM
Updated by: