Breadcrumbs

FAQ - Why are Lansweeper records with a scanning error NOT synchronized?

Question

Why are Lansweeper records with a scanning error NOT synchronized?

This KB applies to:

Applies to Versions

All

Applies to Source Connectors

Lansweeper On-Prem

Applies to Destination Connectors

All

Answer

The Short Answer: CI Sync intentionally does NOT synchronize Lansweeper assets that contain a scan error (i.e. a Lansweeper detected scan error) to maintain correctness of the CMDB. There are one or two exceptions to this rule, but in most cases CI Sync will not sync assets with a scan error.

The Slightly Longer Answer:

Syncfish knows that synchronizing Lansweeper assets containing a scan error will often cause problems in your CMDB. There are two main types of problem:

  1. Duplicate CIs: Sync’ing assets with scan errors can cause duplicates to be created in the CMDB.

  2. Wrongly classified CIs: Sync’ing assets with scan errors can cause CIs to be misclassed in the CMDB (e.g. Lansweeper reports an asset as a web server yet in fact it is an IP Phone, and many other similar variations.).

The above explains why CI Sync’s default behaviour is to NOT synchronize Lansweeper assets that contain a scan error. As mentioned in the short answer above, there are one or two exceptions to this rule:

  1. The Error Config Name is "PRINTERDRIVERS": These errors only relate to printer scanning errors and don’t cause issues to the related CIs in the CMDB.

  2. If the asset has been discovered via the Lansweeper’s LSAgent and the internal error code is either 1, 2 or 4. These errors can occur when LSAgent and the Lansweeper Agentless scanning server both scan the same asset. In this situation, the Lansweeper UI will display a warning symbol to indicate the device in question has a scanning error. Sync’ing assets in this scenario won’t cause issues to the related CIs in the CMDB.

Finally, CI Sync’s default behaviour of not sync’ing assets with a scan error only applies to Insert Operations (i.e. when CI Sync is first creating a new CI from a Lansweeper asset). If CI Sync has previously sync’d an asset (one that didn’t contain a scan error) and a scan error is subsequently detected, CI Sync will perform an Update Operation to the originally sync’d CI.

See also the CI Sync Default Configuration Rules for more information on this topic.

  1. For Lansweeper On-Prem: Rule 17 - Handling of Assets with Scanning Errors in Lansweeper On-Prem

  2. For Lansweeper Cloud: Rule 16 - Handling of Assets with Scanning Errors in Lansweeper Cloud

Control Information

Created

Reviewed

Data Classification

PUBLIC
Classified in accordance with the Syncfish Data Classification Framework