Rule Synopsis
Lansweeper may contain two or more asset records (i.e. to tblAsset records) for devices which contain a common key value such as the same serial number.
These are the rule/s that control whether CI Sync synchronizes each likely duplicate asset in Lansweeper as individual CIs, or whether CI Sync only takes the most recent asset from a known set of records exhibit the same value in a key field (e.g. the same serial number).
Rule Details and Default
For existing Syncfish customers up to the end of January 2026
-
By default, CI Sync will synchronize each individual Lansweeper asset record as a separate CI, even if the individual asset records contain the same serial number. That is, CI Sync does not try determine whether the multiple individual asset records are duplicates or not.
For existing Syncfish customers from February 2026 and onwards
-
By default, CI Sync will not synchronize each individual Lansweeper asset record as a separate CI, providing the individual asset records have the same serial number value. Instead, CI Sync the latest seen version of an asset by Serial Number will be synced only (the latest version) - any links or mappings to the previous asset will be released, allowing the newest asset to map to the existing CI in ServiceNow.
Override Options
Context
For existing Syncfish customers up to the end of January 2026
-
Customers may consider overriding this rule if they have assess their Lansweeper data and determined multiple asset records with the same serial number are indeed the same asset (i.e. the are not different assets).
For NEW Syncfish customers from February 2026 and onwards
-
Syncfish generally recommend not overiding this setting to revert to the historical default of creating multiple CIs when Lansweeper has multiple asset records with the same serial number. Customer assessing whether to override the default are encoraged to first discuss this topic with a member of Syncfish team.
Options
For existing Syncfish customers up to the end of January 2026
-
The rule can be amended so that CI Sync will not synchronize each individual Lansweeper asset record as a separate CI, providing the individual asset records have the same serial number value. Instead, CI Sync the latest seen version of an asset by Serial Number will be synced only (the latest version) - any links or mappings to the previous asset will be released, allowing the newest asset to map to the existing CI in ServiceNow.
For NEW Syncfish customers from February 2026 and onwards
-
The rule can be amended so that CI Sync will synchronize each individual Lansweeper asset record as a separate CI, even if the individual asset records contain the same serial number. That is, CI Sync does not try determine whether the multiple individual asset records are duplicates or not.
Syncfish generally recommend not overiding this setting for new customers of CI Sync.
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:
-
For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.
-
For the specific CI Sync Connection Setting/s related to the rule described on this page please read Deduplciate Assets by Serial Number for Lansweeper On-Prem.
For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.
Additional Information
N/A
Related Rules
N/A
Support Model for Rule Overrides
Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?
Answer: No (a plan is needed - see below)
Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule
Answer: Either a Silver Plan or Gold Plan