Moving your Lansweeper installation to a different server

If required, you can migrate your Lansweeper installation from one computer to another. The exact migration procedure you should follow depends on which database server you are using, SQL Compact or SQL Server. If you are unsure which database server you are using, browse to the following section of the web console: Configuration\Your Lansweeper License

checking used database server in order to migrate Lansweeper

Moving your installation if you are using SQL Compact

SQL Compact is no longer supported as a Lansweeper database provider. The latest Lansweeper version that supports SQL Compact is version 7.2.107.4. Before moving your installation, we recommend migrating your SQL Compact installation to SQL Server or SQL LocalDB.

Moving your installation if you are using SQL Server or SQL Server LocalDB

To move your installation to another computer if your database server is SQL Server or SQL Server LocalDB, do the following:

  1. Make sure your new server has .NET Framework 4.8 or a more recent .NET version installed. This is a Lansweeper installation requirement from Lansweeper 8.2.200 onward.
    Updating your .NET Framework to version 4.8 manually or via the Lansweeper installer often requires a reboot. Whether or not a reboot is required is determined by the Microsoft .NET Framework installer, this process is not Lansweeper-specific.
  2. Create a full backup of your Lansweeper installation by following the steps in this knowledge base article.
  3. Perform an Advanced install of Lansweeper on the computer you want to migrate to and select SQL Server or or SQL Server Local DB as your database server. Installation instructions can be found in this knowledge base article.
  4. Restore your backup over the new Lansweeper installation by following the steps in this knowledge base article.
  5. If necessary, update the Action Path in the Configuration\Asset Pages section of the web console, replacing the old computer name in the path with the new one. Your Action Path determines where Lansweeper will try to locate scripts and executables used by asset and user actions.
    Asset Pages menu
  6. If your Lansweeper license allows for multiple scanning servers and the scanning configuration of the old scanning server should be migrated to the new scanning server, run the following tool on the new server:
    Program Files (x86)\Lansweeper\Tools\DatabaseMaintenance.exe
    running the Lansweeper Database Maintenance tool
  7. If your Lansweeper license allows for multiple scanning servers and the scanning configuration of the old scanning server should be migrated to the new scanning server, execute the script below in the Script Execution tab of the aforementioned tool. You'll need to replace OldServer with the NetBIOS name of the old scanning server and NewServer with the NetBIOS name of the new scanning server, leaving the single quotes in place. The script deletes the new, empty tab that will have been generated for the new scanning server under Scanning\Scanning Targets in the web console and transfers the old scanning server settings to the new server.
    delete from tsysasservers where servername = 'NewServer'
    GO
    update tsysasservers set servername = 'NewServer' where servername = 'OldServer'
    GO
    update tblassets set scanserver = 'NewServer' where scanserver = 'OldServer'
    GO
  8. Restart the Lansweeper Server service in Windows Services

Related Articles

Get Started Right Away

Try Lansweeper for Free