05-23-2023 10:38 PM - edited 06-14-2023 09:33 PM
The Lansweeper architecture consists of several components:
The Lansweeper on-premise database stores configuration and the scanned data. There are many different types of database systems, but Lansweeper, specifically, is always hosted on a Microsoft SQL Server. Supported SQL editions include:
The database is always hosted on the client’s server, meaning you must have a Windows resource to host the database instance.
The scanning server is the workhorse and the real engine of the scanning process. It is steered by the database, as it will constantly ask the database “what do I have to do” before scanning. Lansweeper is configured using the web console, which stores configuration data (scanning targets, server options, roles and permissions, etc.) in the database. The scanning server’s configuration is stored and retrieved from the database. There can be multiple scanning servers available per on-premises installation of Lansweeper (see licensing restrictions), but only one database. The scanning service is a .NET application that will always require a Windows resource in your environment.
The on-premises web console (Lansweeper Classic) displays the data and allows you to set up the configuration. The web console uses a variety of IIS (Internet Information Services), either IIS Express or a full IIS application, installed on a Windows machine in the customer’s environment. Every installation of Lansweeper can only hold one local web console.
Lansweeper Sites are the accelerating layer on top, synced with one or more local, on-premises installations of Lansweeper. The platform drives the data collected from the installations to provide actionable insights and actions to take through integrations. your Lansweeper Sites is hosted by Lansweeper in AWS, eliminating the need for you to host Lansweeper in a private cloud yourselves.
Lansweeper Sites have their own database model, as well: MongoDB. This means that the underlying data model is different from the on-premises data model. The advantage of using MongoDB is that it allows for data to be retrieved from multiple installations and bundled into a single database.
Supported Server Types |
Windows
|
Uses:
|
Supported Database |
Microsoft SQL
|
You can find the complete list of requirements here.
Deciding on a plan and which one is right for you may be a difficult decision and it can be that architecture is a driving factor in choosing a plan. Every package has a number of installations that can be used. With each environment being different, each Lansweeper installation is a little different. If you need help deciding which plan is best for you, work with your Lansweeper partner or contact us at Contact Sales & Customer Service - Lansweeper. You can also look at our top useful use case.
How many installations do you need? Do you have an isolated DMZ or other networks that cannot be reached from a central network location? Examples:
|
Do you have different regions/locations in your company? Approximately how many assets are there per location?
|
Do you want some admins in your Lansweeper installation to only see a subset of scanned assets? (e.g. for complex environments with different ownership for each region.)
|
Lansweeper has a very flexible implementation with many installation options, depending on how your network is set up. For example, you may have a single Lansweeper instance or installation and multiple scanning servers, or you may have multiple installations or instances that cover different regions. If you are in a larger company, you often use a combination of all of the above.
The diagrams below illustrate multiple ways to install Lansweeper, from the most basic to more complex installations.
This is the most basic view of a Lansweeper installation, and it shows what an “easy” installation looks like. All local components (the database, scan server and web console) are hosted on a single machine in a single network.
This is an example of a single Lansweeper instance/installation where the components are spread out across multiple Windows resources (machines A, B, C, D) and spread out across multiple subnets.
Below, an example of different instances/installations of Lansweeper that are all federated to different Lansweeper Sites, to provide a unified overview of the data.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try NowExperience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now