This page explains which architectural components are involved in linking a Lansweeper installation with a cloud site, which components are required and how they interact.
A local Lansweeper installation can be linked with a cloud site. Linking a local installation causes the installation's current data and any subsequent data changes to be sent to Cloud. The cloud interface offers a number of advantages over the local one: centralized access to multiple Lansweeper installations, more granular permissions over assets, a new report builder, a fully integrated API, and more.
To link a Lansweeper installation with Cloud, you must first set up a full Lansweeper installation in your own network. You must install a Lansweeper database, web console and at least one scan server in your own network. Optionally, you can add secondary scan servers as well, though only one scan server will be responsible for syncing all of your installation's data with your Cloud site.
If you have a simple network with a single subnet, consider setting up your Cloud connection as shown in the diagram below.
If you have a large network with multiple subnets, consider setting up your Cloud connection as shown in the diagram below.
If your company has multiple local, isolated networks that can't communicate with each other, consider setting up your Cloud connections as shown in the diagram below.
If you are managing data of multiple unrelated companies, consider setting up your Cloud connections as shown in the diagram below.