Rule 16 - Handling of Assets with Scanning Errors in Lansweeper Cloud

Rule Synopsis

These are the rule/s that control whether CI Sync synchronizes Lansweeper assets that contain a Lansweeper Scan Error.

Rule Details and Default

• By default, CI Sync does not synchronize Lansweeper assets that contain a scan error (i.e. a Lansweeper detected scan error) to maintain correctness of the CMDB.

• 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 CIs to be misclassied 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.).

• There are one or two exceptions to this rule:

  • 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.

  • If the asset has been disovered 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.

Override Options

Context

Syncfish do not recommend override the default rule. Customer’s should discuss this topic with Syncfish before considering any form of override as it can cause data errors in the CMDB.

Options

1. The rule can be amended so that CI Sync allows Lansweeper assets containing a scan error to be sync’d to the CMDB.

Overriding via Connection Settings

N/A

Additional Information

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:

1. For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.

2. For the specific CI Sync Connection Setting/s related to the rule described on this page please read Insert Suppression of Records with Scan Errors in Lansweeper On-Cloud.

For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.

Also, see the CI Sync KB Article for additional information this topic: FAQ - Why are Lansweeper records with a scanning error NOT synchronized?.

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: Yes (via self-service in the CI Sync UI)

Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule

Answer: Either a Bronze Plan, Silver Plan or Gold Plan (for customers wanting Syncfish assistance to perform overrides of this rule)