Cloud platform database requirements

The Lansweeper cloud platform is a feature that is currently in development. You can find more information on it and an early access signup form in the Enterprise menu of Lansweeper 7.1 (or higher) installations. Keep in mind that the information in this knowledge base article does not provide access to the cloud platform. It simply ensures that you meet the database requirements for cloud once you are granted access.

To be able to push data from a local Lansweeper installation into the Lansweeper cloud platform, your Lansweeper database must be hosted in Microsoft SQL LocalDB or Microsoft SQL Server. If your database is currently hosted in the deprecated Microsoft SQL Compact database server, you can convert it to SQL LocalDB or SQL Server.

In addition to the database being hosted in SQL LocalDB or SQL Server, lansweeperuser must also have the dbcreator role in your SQL instance. Lansweeperuser is a SQL login created by the Lansweeper installer during an installation under SQL LocalDB or SQL Server. It connects Lansweeper components to the database. This user requires dbcreator rights for Lansweeper cloud because a backup copy of your database will be created, which will be used to push your data into cloud. Under certain database setups, lansweeperuser does not have dbcreator rights by default and only has rights to the Lansweeper database. This results in the below warning message in the Configuration\Enterprise Options menu of the web console. To give lansweeperuser the necessary dbcreator rights for the Lansweeper cloud platform, follow the steps below.

Lansweeper Enterprise necessary privileges

Step 1: stop the services

Stop the Lansweeper Server service in Windows Services on your Lansweeper server. Stop your web server service in Windows Services as well. Keep in mind that this will log everyone out of your local web console. Your web server service is either IIS Express or World Wide Web Publishing Service (IIS).

stopping the Lansweeper Server service
stopping the web server service

Step 2: log into SQL Server Management Studio

Log into SQL Server Management Studio with a user that has sysadmin rights, a user other than lansweeperuser. If SQL Server Management Studio isn't installed on your Lansweeper server, we recommend downloading it online.

If your database is hosted in SQL LocalDB, the SQL instance name you need to submit in Management Studio is (localdb)\.\LSInstance and you can log in with the Windows user that initially installed Lansweeper. If your database is hosted in SQL Server, you would have configured your SQL instance name and password when you installed SQL Server.

Step 3: configure lansweeperuser

Under Security\Logins in SQL Server Management Studio, right-click lansweeperuser and select Properties. In the Server Roles tab of the resulting popup, tick the dbcreator role and hit OK.

Lansweeperuser is the default and only officially supported SQL user account to connect Lansweeper components to the Lansweeper database. While custom user accounts may technically work as well, they are not supported. Lansweeperuser has a randomized password by default, which you can customize if you want.
lansweeperuser in SQL Server Management Studio
giving dbcreator rights in SQL Server Management Studio

Step 4: restart the services

Restart the Lansweeper and web server services in Windows Services on your Lansweeper server.

starting the Lansweeper Server service

Related Articles