Synchronize Displays as Peripherals for Lansweeper On-Prem 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.

CleanShot 2026-02-23 at 12.37.38@2x-20260223-023833.png

The screen shot is provided only as a 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 Displays as Peripherals

Slider

When disabled (which is the default), CI Sync treats Displays as a standalone CI/Asset record rather than as a peripherals.

When enabled, CI Sync treats Displays as a peripheral of the parent/main computer CI/Asset the Display is connected to.

Important Additional Notes

Syncfish amended the default position of this setting in February 2026.
1. For existing customers using CI Sync up to Feb 26, CI Sync treats Displays as a Peripheral of the parent/main computer it is connected to.
2. For new customers using CI Sync after Feb 26, CI Sync now defaults to treating Displays as a standalone asset.
When CI Sync is configured to treat a Display as a peripheral (the historical default), CI Sync will delete the Display CI (and by implication ServiceNow will delete the separate Display Asset) in ServiceNow if either of the following occurs in Lansweeper:
1. If Lansweeper no longer discovers the Display in a Connected To state with a parent/main computer CI/Asset, OR
2. If Lansweeper’s “Last Seen” rules delete a Display.
When CI Sync is configured to treat a Display as a standalone asset (the new default), CI Sync relies solely on Lansweeper’s Status values including Lansweeper’s “Last Seen” behaviour to indicate the status and existence of the Display. If Lansweeper has not “seen” a Display for “n” number of days (where “n” is configured by customers within Lansweeper), then Lansweeper will set the status to Inactive, which in turn causes CI Sync to change the status of the CI/Asset record in ServiceNow to “retired”. This status value behaviour is a standard feature of CI Sync in the way it utilises Lansweeper status values and Lansweeper Last Seen behaviour.

The above topic has several moving parts. For more information and assistance please read the following documentation published by Syncfish:

Or if in doubt, contact the Syncfish support team.

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.