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.
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 |
|
Filter Devices |
Slider |
When enabled, devices will be filtered by CIDRs using the addition settings described below. Filtering causes matching devices to be ignored by CI Sync jobs. NOTE: If you haven’t already, we recommend reading the following Syncfish “How To”. The How To explains this topic in further details. Please read: How-to - Limit record syncing from my Lansweeper database for testing using the connection Device Filter. Once the filter has been applied it will be used for all Lansweeper On-Prem data sync jobs until disabled. |
|
Operator |
Choicelist |
Selected one of the available choicelist values. By default this is set to “Include” which will synchronize only devices that have an IP Address that is within one of the entered CIDR ranges. Changing the Operator to “Exclude” will synchronize only devices that do NOT have an IP Address in any of the entered CIDR ranges. |
|
CIDRs |
String |
Enter one or more comma-separated CIDR values in the CIDR input. The CI Sync data extract query (run by the CI Sync Agent against the Lansweeper On-Prem SQL Database) will only return records with IP Addresses within the specified scope of CIDRs. |
|
Bypass Delete Detection |
Slider |
If enabled, the Bypass Delete Detection option will skip the delete detection step in the data extraction orchestration process. This may be of use if performing a synchronization for a set of assets that fall outside of the usual filter you apply. IMPORTANT: Unless the Bypass Delete Detection is enabled, any devices that have been previously synchronized that do not match the defined CIDR filter will be treated as a deletion by CI Sync (and therefore deactived in the CMDB). Please contact Syncfish for more information if this topic is not understood. |
-
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.