Lansweeper Hybrid Solutions

[PatrickOrr]

Hello!

Would a hybrid on-prem with cloud solution work with this configuration:
LS Core - VLAN, communicates with LS Cloud services

LS Scan Server - General Network, direct outbound communication with Core

LS SQL Server - VLAN

LS Web Server - General Network, direct outbound communication with Core

I'm not sure if having a separate web server is possible, or what that web server would need to communicate with (Core & SQL server?)

Thank you.

[DavidPK]

Hi 

Here is a KB article that might help explain more about a Lansweeper installation. 

https://community.lansweeper.com/t5/installation/lansweeper-classic-components-and-architecture/ta-p...

[DavidPK]

Lets try to add a little more context to help explain. 

Classic hybrid you can split the components across servers/VLANs. In Lansweeper terminology there isn’t a “Core” role in Classic; the on‑prem installation consists of:

• Database (Microsoft SQL Server)
• Scanning server(s)
• Web console (IIS)

Cloud sync (hybrid): The on‑prem installation can synchronize its scanned data to Lansweeper Sites (cloud), providing a unified view and additional capabilities

In a hybrid model the on-prem installation is the main workhorse. 

• Practical layout for your proposal:
• SQL Server (VLAN): Host the Lansweeper database; allow inbound from the scan server(s) and the web server.
• Scan Server (General Network): Allow outbound to SQL Server and to your target subnets/devices.
• Web Server (General Network): Allow outbound to SQL Server; publish the site to users. Keep in mind there is only one web console per installation.

“LS Core”: In Classic there’s no distinct “Core” component. If by “Core” you mean “the on‑prem installation that syncs to cloud,” that function is fulfilled by the Classic components above. If you meant the Discovery Hub (Network Discovery), that’s a different deployment model than Classic.

[PatrickOrr]

David,

That makes a lot more sense, thank you for the detailed explanation! I am beginning to understand, and thank you for the guide.
In our case, we won't have a Classic configuration since we don't want the device with cloud access to touch the general network (thus the purpose of the VLAN).

I read into the Discovery Hub a bit, which to my understanding would communicate separately from the on-prem DB.. so maybe having a LS Scan server behind the VLAN which also communicates to the LS Cloud would work, like so:
SQL (VLAN): LS database, inbound from scan server(s) and web server.
Scan Server A (VLAN): LS Scanning Service & the Cloud Uploader, communicates with LS Sites (cloud)
Scan Server B (General Network): Allow outbound to SQL server and target subnets/devices
Web Server (General Network): Allow outbound to SQL server, publish the site to users.

Though if you think the Discovery Hub would be best, please let me know! I'm not sure having an scan server that really only uploads to the cloud & scans the SQL DB would be very efficient, but if it works then that's alright.
Thank you very much.

[DavidPK]

Hi Patrick, 

That's an adequate installation, assuming all necessary communication is open from on-prem to the cloud. You can have the web console on a different server, either by itself or with a scan server. Below is a list of ports scanned or used by Lansweeper.

https://community.lansweeper.com/t5/requirements/ports-scanned-or-used-by-lansweeper/ta-p/64273

[PatrickOrr]

Hi David,

Thank you for the additional information. Just to double check, the Scan server & Web server only need to have an outbound communication with the Core server?

And would this affect Freshservice integration?