Connector Applicability
|
Applies to Source Connectors |
Lansweeper Cloud |
|---|---|
|
Applies to Destination Connectors |
All |
Assumptions
These instructions assume you have already setup a source connection in CI Sync for Lansweeper Cloud using the CI Sync instructions here: Add Lansweeper Cloud to SaaS Agent.
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 Cloud connection.
-
Click the Update link on the right hand side of the Lansweeper Cloud 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 |
|
Suppress Inserts of non-active records |
Slider |
When enabled, non-active records from Lansweeper will NOT be inserted as new CIs to the CMDB. If not enabled, non-active records from Lansweeper will be inserted as new CIs. |
-
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.