on 05-23-2023 10:47 PM - edited 2 weeks ago by Tim_N
Lansweeper was initially developed to automatically gather asset details from a local area network (or LAN). As the lives of the average Lansweeper user have evolved to be more Internet-based and cloud-centric, Lansweeper has grown its product to provide scanning beyond the LAN.
As the Lansweeper roadmap continued to move towards a world-class SaaS solution through multiple iterations, the Lansweeper Cloud Console (or simply, “Lansweeper Sites”) was launched.
To use Lansweeper Sites, all of Lansweeper’s system components must be installed locally (physically or virtually) in the customer’s environment, much like the process for Lansweeper Classic.
Your Lansweeper Site then takes the on-premises Lansweeper SQL database and synchronizes a (substantial) subset of data to a MongoDB at Lansweeper’s AWS instance in Dublin, Ireland. There is a continuous 2-way sync of asset data between the on-prem SQL database and the Lansweeper Site MongoDB. This allows you to keep an accurate view of your asset data wherever you make the changes: in Lansweeper Classic or the Lansweeper Sites.
Once the components are in place, one of the on-premises scanning servers becomes the Sync Server and the conduit for data transfer between Lansweeper Classic (on-premises) and Lansweeper Sites (in the Cloud).
Begin your journey with Lansweeper Sites using this Getting Started Guide.
There are numerous benefits to adopting Lansweeper Sites:
A full comparison between Lansweeper Sites and Lansweeper Classic is available here.
Access to specific Lansweeper Sites features is determined by the level of annual subscription plan you select: Starter, Professional or Enterprise.
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