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.
This knowledge base article explains which architectural components are involved in linking a Lansweeper installation with Cloud, which components are required and how they interact. It also includes diagrams of example Lansweeper setups.
Cloud installation components
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.
- Database: Your local database stores scanned and custom data, reports and settings. It can be hosted in SQL LocalDB or Microsoft SQL Server.
- Scan server: A scan server is a machine that has the Lansweeper Server service installed. This service is the beating heart of your Lansweeper installation. It scans data, runs deployments, performs database cleanups and sends emails. A scan server is in constant communication with the database to send data and retrieve settings. A Lansweeper installation has at least one scan server, but it can also have multiple.
- Web console: Your local web console displays data and settings stored in your database. It also allows you to make changes to them. The web console can be hosted in IIS Express or IIS. The console communicates with the database to retrieve data and send setting changes. Linking a Lansweeper installation with Cloud starts from the Configuration > Link With Cloud Site menu of the local web console.
Interaction with Cloud
- Sync server: When you link a local Lansweeper installation with Cloud, one scan server becomes the so-called "sync server". A sync server is a regular scan server, but one that is responsible for syncing all of the installation's data with Cloud. If your installation only has one scan server, that server is automatically made the sync server. If your installation has multiple scan servers, you are asked to pick one as your sync server when you link with Cloud. It doesn't matter which server you choose as long as that server meets the requirements for linking with Cloud.
- Cloud site: A Cloud site is a collection of one or more Cloud-linked Lansweeper installations, which you give a specific name. You can create as many sites as you want in Cloud. When you link a Lansweeper installation with Cloud, you are asked to pick a site to link with. A Lansweeper installation can only be actively linked with 1 site at a time, but multiple installations can be linked with the same site. The Cloud interface lets you select the site you want to view, by clicking the site icon in the upper left corner of the interface.
Cloud setup examples
Basic network with a single subnet
If you have a simple network with a single subnet, consider setting up your Cloud connection as shown in the diagram below.
- Possible use case: a single, small home or company network
Larger network with multiple subnets
If you have a large network with multiple subnets, consider setting up your Cloud connection as shown in the diagram below.
- Possible use case: a medium to large company network where locally all asset data is managed by a single team
- Having one scan server per subnet, though not strictly required for scanning, improves asset detection and recognition.
- Having one central, local database simplifies database backup, cleanup and other operations.
- Only one scan server must be linked with Cloud, so only one scan server must meet the Cloud requirements.
- Each scanned asset is only sent to Cloud once, optimizing Cloud traffic and reducing the risk of duplicates.
- In Cloud, asset access can be managed using scopes.
- This setup only works if all scan servers can communicate with the local, central database.
- In the local Lansweeper web console, any user with asset access can see all assets.
Multiple isolated networks with one or more subnets, same company
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.
- Possible use case: a large company network where locally asset data is managed by multiple teams
- The local company networks don't need to be able to communicate with each other.
- Each Lansweeper installation can locally only access its own data.
- In Cloud, asset access across the various installations can be managed using scopes.
- Each local Lansweeper installation must be linked with Cloud, so each installation must meet the Cloud requirements.
- If multiple local installations do scan the same assets, these assets may be sent to Cloud multiple times, generating unnecessary traffic and increasing the risk of duplicates.
Multiple isolated networks with one or more subnets, multiple companies
If you are managing data of multiple unrelated companies, consider setting up your Cloud connections as shown in the diagram below.
- Possible use case: a Managed Service Provider (MSP) that manages data from multiple companies
- Data from different companies can be completely separated in Cloud using sites. Each site can represent one company.
- Within each company site, asset access can be managed further using scopes.
- Reports cannot be run across multiple sites at once.
Was this post helpful? Leave a Kudo!
Did you have a similar issue and a different solution? Share your work in the comments below and help your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions or Community Forum.
If you can't find what you're looking for, create a post in our Community Forum.