If you are changing the hostname of a scanning server, you will need to consider several factors. When you change the hostname, you will need to run a database script; otherwise, you will have a duplicate scanning server. Scanning servers are identified by their hostname and added to your database upon successful connection.
We recommend doing the following steps:
- Stop the Lansweeper Server service (the scanning service) in the Windows Services on your server.
- Execute the script below in the Script Execution tab of the database maintenance tool (Program Files (x86)\Lansweeper\Tools\DatabaseMaintenance.exe). Replace newserver with the new NetBIOS name of your server and oldserver with the old NetBIOS name.
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
- If necessary, update the Action Path in the Configuration\Asset Pages section of the on-prem Lansweeper web console. Your Action Path determines where Lansweeper will attempt to locate scripts and executables used by the actions displayed on individual asset pages.
- Restart the Lansweeper Server service.