Connector Applicability
|
Applies to Source Connectors |
Lansweeper On-Prem |
|---|---|
|
Applies to Destination Connectors |
All |
Assumptions
These instructions assume you have already setup a source connection in CI Sync for Lansweeper On-Prem using the CI Sync instructions here: Add Lansweeper On-Prem.
Pre-Read
Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.
-
Rule 8 - Automatic Creation of new Location Master Data Records in ServiceNow for Lansweeper On-Prem
-
Rule 9 - Standard Asset Location Determination Rules for Lansweeper On-Prem
Locating and Amending the Connection Setting in the CI Sync UI
-
Navigate to the Settings page
-
Under the Source Connections heading (list), locate your Lansweeper On-Prem connection.
-
Click the Update link on the right hand side of the Lansweeper On-Prem connection.
-
Scroll down and locate the Section Heading and view the Individual Settings.
The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.
-
Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.
|
Setting |
Type |
Additional Notes |
|
Synchronize Locations |
Slider |
When enabled, the Location attribute will be set on each CI as a sys_id reference to the ServiceNow cmn_location table. If not enabled, the Location attribute will not be set on each CI. |
|
Synchronize Master Data |
Slider |
When enabled, unique Location values read from Lansweeper (using the Location Data Source described in the next setting) will be inserted to the Servicenow cmn_location table (i.e. the cmn_location table will be extended with new values read from Lansweeper). If not enabled, the cmn_location table will not be extended with new Location values read from Lansweeper. |
|
Location Data Source |
Choicelist |
This setting, which is only available if the above settings are in use, informs CI Sync which method/record sets in Lansweeper will be used to determine the Locations values for the above two rules. Three options are available:
Please read Rule 9 - Standard Asset Location Determination Rules for Lansweeper On-Prem to understand the details and complexity of Lansweeper Location handling and CI Sync works for each of the above options. If in doubt, please contact Syncfish Support as there is some complexity in this topic. |
|
Enable Synchronization of IP Location Master Data |
Slider |
This setting is specifically designed for customers using the new Lansweeper Network Discovery Tool which only persists data to Lansweeper Cloud. The setting is only applicable to the IP Location data source. Enabling this setting causes 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. Please read Rule 9a - Standard Location Determination Rules for Assets Discovered by Lansweeper Network Discovery and stored in Lansweeper Cloud to understand the details and complexity of Lansweeper IP Location handling in Lansweeper Cloud with the Lansweeper Network Discovery Tool. If in doubt, please contact Syncfish Support as there is some complexity in this topic. |
-
After modify the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.
-
You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.
Importantly
Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).
For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.
Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.