Rule 9a - Standard Location Determination Rules for Assets Discovered by Lansweeper Network Discovery and stored in Lansweeper Cloud

Rule Synopsis

These are the rule/s that control how CI Sync deduce the Location value of a given Lansweeper Cloud Asset (scanned by Lansweepers Network Discovery scanner) using several standard data elements within Lansweeper.

Rule Details and Default

• By default, CI Sync does not persist any form of Location against each CMDB CI record.

Override Options

Context

Customers may consider overriding the default rules so that CI Sync does set a Location against the target CI record.

CI Sync supports several standard Lansweeper data elements to deduce the Asset location.  See the page details below for the standard override options.

If the standard Lansweeper data elements are not suitable, Syncfish can implement Custom Asset Location Determination rules (See Rule 4 – Custom Asset Location Determination Rules).

Options

1. This Data Sync Rule can be overridden so that CI Sync does persist an automatically determined Location against each CMDB CI record.  The persisted value with be a sys_id reference between the CI record and the corresponding record in the cmn_location table.

If customers enable the above override (so CI Sync persists a determined location value) there are three Lansweeper location data elements that can be selected for use by CI Sync to determine the location of each Asset/CI:

1. Standard CI Sync Location Rule Override 1: Use Lansweeper On-Prem’s IP Location records as the way CI Sync determines the Location of assets that were scanned by Lansweepers newer Network Discovery Tool (i.e. the new scanner that does not store data in Lansweeper On-Prem).

2. Standard CI Sync Location Rule Override 2: Asset Locations (relationship based locations)

3. Standard CI Sync Location Rule Override 3: Custom Location (or manual Asset Location) attribute.

See Additional Information below on how Lansweeper implements the above options and the operation of CI Sync’s Standard Location Determination rules.

Overriding via Connection Settings

Customers can perform the override using a “Connection Setting” via the CI Sync User Interface (i.e. customers can perform the overrides themselves). Additional information for this is available via the following documentation:

1. For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.

2. For the specific CI Sync Connection Setting/s related to the rule described on this page please read:

   1. Location Data Handling for Lansweeper On-Prem

   2. Location Data Handling for Lansweeper Cloud

For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.

Additional Information

Standard Location Rule Override 1: Use Lansweeper On-Prem’s IP Location records for CI Sync to determine the Location of Network Discovery assets in Lansweeper Cloud

Firstly, Lansweeper context

1. The Lansweeper Network Discovery tool, for IT and OT assets, does NOT automatically set the Location attribute in Lansweeper Cloud. That is, Network Discovery with Lansweeper Cloud does NOT use the concept of IP Locations in same way as the traditional Lansweeper Scanner and Lansweeper On-Prem.

2. The above situation means the Location attribute is not automatically set in Lansweeper Cloud for IT and OT assets.

3. Customers have three options to deal with this situation:

   1. Wait for Lansweeper to address the limitation (i.e. wait for Lansweeper to introduce IP Locations in the Network Discovery tool and Lansweeper Cloud). Lansweeper have suggested the solution is coming in H1 2026.

   2. Use the Lansweeper Custom Location attribute in Lansweeper Cloud (see Rule Override 2 further below).

   3. Use the Syncfish provided solution describe below (i.e. this Rule Override 1 approach).

Next, How CI Sync Handles Lansweeper IP Locations

Customers can use two CI Sync Connection Settings to drive the behaviour described below.

1. See the CI Sync Connection Setting called “Enable Synchronization of IP Location Master Data“ defined on the Lansweeper On-Prem source connection in the CI Sync SaaS UI.

2. See the CI Sync Connection Setting called “Set Locations from IP Networks“ defined on the Lansweeper Cloud source connection in the CI Sync SaaS UI.

Here’s how it works…

• CI Sync reads the IP Location definitions from Lansweeper On-Prem SQL and sync’s these into the IP Networks table in ServiceNow (into cmdb_ci_ip_network_list).

• Then, when CI Sync reads each asset from Lansweeper Cloud, CI Sync compares the IP Address of the asset against the Lansweeper On-Prem IP Location definitions (now available in the cmdb_ci_ip_network_list). When CI Sync finds a match between the IP Address of the asset and the subnet range of the IP Location, CI Sync then “knows” the Location of the asset.

• Finally, CI Sync attempts to match the now known IP Location value against an existing record in the cmn_location using the cmn_location.name attribute.

  • If CI Sync matches an incoming IP Location value to a record in the cmn_location table, CI Sync sets a foreign key reference between the location attribute on the CI record itself and the matching record in cmn_location table.

  • If CI Sync does not match an incoming IP Location value against the cmn_location table, then CI Sync will do one of the following:

    • Either insert/create a new cmn_location record (and set a foreign key reference between the CI and the newly created location record)

    • Or, not insert/create a new cmn_location record (and obviously not set a foreign key reference, so the location attribute on the CI will be nul).

  • Note 1: The above behaviour (to insert/create new cmn_locations records or not) is controlled by Rule 8 - Automatic Creation of new Location Master Data Records in ServiceNow for Lansweeper Cloud. 

  • Note 2: If there are multiple IP Locations in Lansweeper with the same name (such as two subnets in an IP Location), then these will be set in ServiceNow to the same cmn_location value (i.e. CI Sync does not create duplicate locations with the same name).

Standard Location Rule Override 2: Asset Locations (relationship based locations)

Firstly, Lansweeper context

• In Lansweeper Cloud these “Asset Location” records are treated as an Asset (i.e. an “asset” record is created in Lansweeper to represent a physical “Location”.

• See the screen shot below from Lansweeper Cloud showing “Locations” as a type of “asset”.

• In Lansweeper Cloud, the assocation of Assets to Locations is treated as a relationship.

• The Asset Location of each asset is shown on the asset form down in the Relationships section within Lansweeper Cloud (see below).

Standard Location Rule Override 3: Custom Location (or manual Asset Location) attribute

Firstly, Lansweeper Cloud context

1. Lanswepeer Cloud includes an out-of-the box also the Asset Location attribute. This is a manually maintained in Lansweeper Cloud.

2. This Custom/Manual Location attribute is shown on the asset form in Lansweeper Cloud (see below).

 Next, How CI Sync Handles the Lansweeper Location Attribute

• CI Sync reads the value of the Location attribute from each incoming Lansweeper Asset.

• CI Sync attempts to match the Location value against an existing record in the cmn_location table using the cmn_location.name attribute.

  • If CI Sync matches the Location to a record in the cmn_location table, CI Sync sets a foreign key reference between the location attribute on the CI record itself and the matching record in cmn_location table.

  • If CI Sync does not match the Location to a record in the cmn_location table, then CI Sync will do one of the following:

    • Either insert/create a new cmn_location record (and set a foreign key reference between the CI and the newly created location record)

    • Or, not insert/create a new cmn_location record (and obviously not set a foreign key reference, so the location attribute on the CI will be nul).

  • Note: The above behaviour (to insert/create new cmn_locations records or not) is controlled by Rule 8 - Automatic Creation of new Location Master Data Records in ServiceNow for Lansweeper Cloud 

Related Rules

• Rule 8 - Automatic Creation of new Location Master Data Records in ServiceNow for Lansweeper Cloud

• Rule 9 - Standard Location Determination Rules for Assets Discovered by the Traditional Lansweeper Scanner and replicated from On-Prem SQL to Lansweeper Cloud

• Rule 4 – Custom Asset Location Determination Rules

Support Model for Rule Overrides

Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?

Answer: Yes (via self-service in the CI Sync UI)

Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule

Answer: Either a Bronze Plan, Silver Plan or Gold Plan (for customers wanting Syncfish assistance to perform overrides of this rule)