Summary of Data Sync Rules (Self-Service Rule Overrides vs Custom Rules)

Purpose

This page shows which CI Sync Data Sync Rules can be overridden via Self-Service (using the Connection Settings feature within the CI Sync User Interface) versus which rules require custom development by the Syncfish Team.

Click here for the table below showing Data Sync Rules Available for Override using CI Sync Connection Settings
Click here for the table below showing Data Sync Rules that Require Custom Development

Data Sync Rules Available for Override using CI Sync Connection Settings

Key Points

The rules listed below can be amended via the CI Sync User Interface using the Connection Settings feature.
This means customers can perform a self-service change to the default behaviour of CI Sync for the rules described below.
The rules listed below do not require a Syncfish Support Plan because customers can amend the rule themself using a CI Sync Connection Setting. Note: See next bullet point for customers wanting SME-Led assistance.
A Syncfish Bronze Support Plan is required for customers wanting a Syncfish SME conduct a familiarisation call on this topic (i.e. assistance beyond the published documentation about the Default Rules and using Connection Settings to modify the behaviour of those rules).
A Syncfish Silver or Gold Support Plan is required for customers wanting a Syncfish SME to discuss their data/business requirements and make the Connection Setting changes on their behalf.
Please visit the Support page at https://www.syncfish.com.au/support to learn more about Syncfish Support Plan inclusions and any limits on the quantity of calls/changes per subscription year.

Rule Name	Link to the related Default Rule Page Each page explains the rule in details, including the default behaviour and override options	Link to the related Connection Setting Guide Each guide explains how to override the rule using a CI Sync Connection Setting via the CI Sync UI
ServiceNow Specific Rules
ServiceNow Manufacturer Related Rules
Synchronization of Manufacturer, Carries and Vendors on a Parent CI	Click here	Click here
Synchronization of various Manufacturer types on Child / Subordinate Records of the Parent CI	Click here	Click here
Whether CI creates (or not) Manufacturer Master Data records in ServiceNow’s core_company table	Click here	Click here
Whether CI deletes (or not) Manufacturer Master Data records in ServiceNow’s core_company table	Click here	Click here
ServiceNow Hardware Model Related Rules
Synchronization of Hardware Model on a Parent CI	Click here	Click here
Synchronization of Disk Model on Child / Subordinate Records of the Parent CI	Click here	Click here
To determine of which Model Master Data table is being used in ServiceNow	Click here	Click here
Whether CI creates (or not) Model Master Data records in ServiceNow’s model table (using the above “determination” rule)	Click here	Click here
Whether CI deletes (or not) Model Master Data records in ServiceNow’s model table (using the above “determination” rule)	Click here	Click here
Various Other ServiceNow Rules
Whether CI Sync suppresses (or not) updating the multiple ServiceNow Status Value attributes on CIs (and Assets) in the CMDB during CI Update operations	Click here	Click here
How CI Sync interoperates with ServiceNow Field Normalisation Plug-in for Manufacturer values	Click here	Click here
Whether CI Sync overwrites the Discovery Source and Correlation ID attributes in ServiceNow during CI Update operations	Click here	Click here
Whether CI Sync updates the First Seen attribute in ServiceNow during CI Update operations	Click here	Click here
Whether CI Sync uses non-unique MAC Addresses when attempting to match (correlate) existing CIs	Click here	Click here
To inform CI Sync of a Custom Field name when using User Synchronization from a Source System	N/A	Click here
Lansweeper On-Prem Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Whether CI Sync reads the Last Logged On User to set the Assigned_To attribute on CIs	Click here	Coming Soon
Whether CI Sync calculates the most regularly logging on user to set the Most_Frequent_User attribute on CIs	Click here	Coming Soon
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Click here
How CI Sync deduces the Location value of a given Lansweeper Asset to set the Location attribute on CIs	Click here	Click here
Whether CI creates (or not) Location Master Data records in ServiceNow’s cmn_location table	Click here	Click here
Whether CI creates (or not) Software Product Model Master Data records in ServiceNow’s cmdb_software_product_model table	Click here	Click here
Whether CI Sync creates (or not) CIs for Assets that are Non-Active	Click here	Click here
Whether CI Sync create relationships between Lansweeper Assets and Application Service records in ServiceNow (including which data element contains the Service ID)	Click here	Click here
Whether CI Sync filters (i.e. ignores) Assets and therefore does not create/update the corresponding CIs	Click here	Click here
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 that exhibit the same value in a key field (e.g. the same serial number).	Click here	Click here
Whether CI Sync treats Monitors/Displays as Hardware Assets or as peripherals of a Parent CI (which impacts whether monitors/displays are deleted (or not) when no longer detected by Lansweeper)	Click here	Click here
To inform CI Sync if ServiceNow SAM Pro has ever been installed so CI Sync can interoperate correctly with the alm_licence table (This is only applicable for customers syncing Windows Device Software Licence Keys from Lansweeper On-Prem)	Click here	Click here
Whether CI Sync automatically creates/inserts new CMDB Group Records (or not) into the ServiceNow cmdb_group) table	Click here	Click here
Lansweeper Cloud Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Whether CI Sync either passes through or transforms the format of the Windows OS Version attribute/value for Windows CIs created from Lansweeper Cloud	Click here	Click here
Whether CI Sync reads the Windows last logged on user to set the Assigned_To attribute on CIs	Click here	Coming Soon
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Click here
How CI Sync deduces the Location value of a given Lansweeper Asset to set the Location attribute on CIs (specifically for Assets discovered by the traditional Lansweeper scanner and replicated from On-Prem to Lansweeper Cloud)	Click here	Click here
How CI Sync deduces the Location value of a given Lansweeper Asset to set the Location attribute on CIs (specifically for Assets discovered by the Lansweeper Network Discovery scanner and stored only in Lansweeper Cloud)	Click here	Click here
Whether CI creates (or not) Location Master Data records in ServiceNow’s cmn_location table	Click here	Click here
Whether CI creates (or not) Software Product Model Master Data records in ServiceNow’s cmdb_software_product_model table	Click here	Click here
Whether CI Sync creates (or not) CIs for Assets that are Non-Active	Click here	Click here
Whether CI Sync create relationships between Lansweeper Assets and Application Service records in ServiceNow (including which Lansweeper data element contains the Service ID)	Click here	Coming Soon
Whether CI Sync filters (i.e. ignores) Assets and therefore does not create/update the corresponding CIs	Coming Soon	Coming Soon
Whether Digital Certificates (for Windows Servers and Windows PCs) can be selected when creating a synchronization job, and if so, whether the Digital Certificates are filtered (or not) during a sync job. (In the above rule summary, “filtering” means to include/exclude certificates that match certain criteria)	Click here	Click here
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 that exhibit the same value in a key field (e.g. the same serial number).	Coming Soon	Coming Soon
Whether CI Sync treats Monitors/Displays as Hardware Assets or as peripherals of a Parent CI (which impacts whether monitors/displays are deleted (or not) when no longer detected by Lansweeper)	Coming Soon	Coming Soon
Whether CI Sync ignores (or includes) certain system databases when synchronizing instances of MS SQL Server	Click here	Click here
Whether CI Sync synchronizes (or not) Lansweeper Assets that contain a Lansweeper Scan Error.	Click here	Click here
InTune Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Click here
To inform CI Sync which attribute/value from InTune is used by CI Sync to populate the Asset Tag attribute on CIs in the CMDB.	Click here	Click here
Whether CI Sync reads the InTune Primary User to set the Assigned_To attribute on CIs	Click here	Click here
To inform CI Sync which CI Class should be used for Corporate vs Personal Devices	Click here	Click here
Whether CI Sync separates VOIP handsets (based up on the Manufacturer of the handset) from other types of Android devices (such as mobile phones, tablets).	Click here	Click here
Whether CI Sync suppresses (or not) the Device Name and Phone Number for mobile devices (iPad, iPhone, Android) when persisting those values against CIs	Click here	Click here
Whether CI Sync either passes through or transforms the Windows OS Version and Windows OS Name when persisting those values against CIs	Click here	Click here
Whether CI sync will (or not) create CIs if the Serial Number is empty in InTune	Click here	Click here
Omnissa Workspace ONE Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Whether CI Sync reads the Workspace ONE user to set the Assigned_To attribute on CIs	Click here	Coming Soon
Whether CI Sync suppresses (or not) the Device Name and Phone Number for mobile devices (iPad, iPhone, Android) when persisting those values against CIs	Click here	Click here
Jamf Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Whether CI Sync reads the Jamf user to set the Assigned_To attribute on CIs	Click here	Coming Soon
Whether CI Sync suppresses (or not) the Device Name and Phone Number for mobile devices (iPad, iPhone, Android) when persisting those values against CIs	Click here	Click here
VMware vSphere Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Coming Soon
To inform CI Sync which type of CI-to-CI Relationship is used between Virtual Machine Instance CIs and Computer CIs	Click here	Click here
Whether CI Sync create relationships between VMware Resources and Application Service records in ServiceNow (including which data element contains the Service ID)	Click here	Coming Soon
Nutanix Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Coming Soon
ExtremeCloud IQ On-Prem Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
SolarWinds vSphere Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Cisco Meraki Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Microsoft Defender for Endpoint Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Whether CI Sync enriches the Defender for Endpoint CI data with attribute data from Entra ID (to compensate from the lack of manufacturer, model, and Operating System version information from Defender)	Click here	Click here
To inform CI Sync which CVEs should (and therefore should not) be syncrhonized to ServiceNow based on the CVE severity rating using a minimum CVSS threshold.	Click here	Click here
How CI Sync maps and transforms MS Defender for Endpoint Status values into the four CMDB CI Status values	Click here	Click here
SentinelOne Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
How CI Sync deduces the Location value of a given Cloud Resource to set the Location attribute on CIs	Click here	Click here
Whether CI creates (or not) Location Master Data records in ServiceNow’s cmn_location table	Click here	Click here
Whether CI Sync either passes through or transforms the Windows OS Version when persisting this values against CIs	Click here	Click here
To inform CI Sync which CVEs should (and therefore should not) be syncrhonized to ServiceNow based on the CVE severity rating using a minimum CVSS threshold.	Click here	Click here
Microsoft Defender for Cloud Apps Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
To inform CI Sync which Cloud Applications should (and therefore should not) be synchronized to ServiceNow based on the Risk Score ratings in Defender	Click here	Click here
To inform CI Sync of the duration (in days) to query/retrieve data from Defender for Cloud Apps	Click here	Click here
Microsoft 365 Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
Azure Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Click here
How CI Sync deduces the Location value of a given Cloud Resource to set the Location attribute on CIs	Click here	Click here
Whether CI creates (or not) Location Master Data records in ServiceNow’s cmn_location table	Click here	Click here
Whether CI Sync create relationships between Cloud Resources and Application Service records in ServiceNow (including which data element contains the Service ID)	Click here	Click here
What value CI Sync uses for the vendor name attribute on CIs	Click here	Click here
Whether CI Sync synchronizes Cloud Tags, and if so how to match the content of each tag to master data in ServiceNow	Click here	Tag rules as for each of the following Assigned To: Coming Soon Assigned Group: Coming Soon Business Unit: Coming Soon Change Control: Coming Soon Company: Coming Soon Cost Centre: Click here Department: Coming Soon Environment Tag: Click here Managed By: Coming Soon Managed By Group: Coming Soon Owned By Tag: Click here Supported By Tag: Click here Supported By Group: Coming Soon
AWS Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Click here
How CI Sync deduces the Location value of a given Cloud Resource to set the Location attribute on CIs	N/A	N/A
Whether CI creates (or not) Location Master Data records in ServiceNow’s cmn_location table	N/A	N/A
Whether CI Sync create relationships between Cloud Resources and Application Service records in ServiceNow (including which data element contains the Service ID)	Click here	Click here
What value CI Sync uses for the vendor name attribute on CIs	Click here	Click here
Whether CI Sync synchronizes Cloud Tags, and if so how to match the content of each tag to master data in ServiceNow	Click here	Tag rules as for each of the following Assigned To: Coming Soon Assigned Group: Coming Soon Business Unit: Coming Soon Change Control: Coming Soon Company: Coming Soon Cost Centre: Click here Department: Coming Soon Environment: Click here Managed By: Coming Soon Managed By Group: Coming Soon Owned By: Click here Supported By: Click here Supported By Group: Coming Soon
GCP Specific Rules
What value CI Sync uses for the Discovery Source attribute on CIs	Click here	Click here
What value CI Sync uses as a prefix for the Correlation ID attribute on CIs	Click here	Click here
How CI Sync determines if an incoming record (e.g. a physical device or a virtual resource) is virtual or physical and as a result sets the related attribute on the CMDB CI record.	Click here	Click here
How CI Sync deduces the Location value of a given Cloud Resource to set the Location attribute on CIs	N/A	N/A
Whether CI creates (or not) Location Master Data records in ServiceNow’s cmn_location table	N/A	N/A
Whether CI Sync create relationships between Cloud Resources and Application Service records in ServiceNow (including which data element contains the Service ID)	Coming Soon	Coming Soon
What value CI Sync uses for the vendor name attribute on CIs	Click here	Click here
Whether CI Sync synchronizes Cloud Tags, and if so how to match the content of each tag to master data in ServiceNow	Click here	Tag rules as for each of the following Assigned To: Coming Soon Assigned Group: Coming Soon Business Unit: Coming Soon Change Control: Coming Soon Company: Coming Soon Cost Centre: Click here Department: Coming Soon Environment: Click here Managed By: Coming Soon Managed By Group: Coming Soon Owned By: Click here Supported By: Coming Soon Supported By Group: Coming Soon

Data Sync Rules that Require Custom Development

Key Points

The rules listed below cannot be amended via the CI Sync User Interface using the Connection Settings feature.
This means customers cannot perform a self-service change to the default behaviour of CI Sync for the rules described below.
The rules listed below do require a Syncfish Support Plan because customers cannot amend amend the rule themself.
A Syncfish Silver or Gold Support Plan is required for customers wanting changes to these rules. Syncfish SMEs work with customers, including via MS Teams, to understand the data/business requirements and then implement the custom rules to modify the behaviour of the data as it passes through to ServiceNow.
Please visit the Support page at https://www.syncfish.com.au/support to learn more about Syncfish Support Plan inclusions and any limits on the quantity of calls/changes per subscription year.

Data Sync Rule Overview	Links to the default rule details for several source systems
For changes to the rules that govern the default set of Assets or Resources (including the associated Child Records of the Asset/Resource) available to sync from a given source system.	For Lansweeper On-Prem: Click here For InTune: Click here For Azure: Click here … etc (see next point) For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included Record Sets.
For changes to the rules that govern the default set of CI-to-CI Relationships (sometimes called CI Dependencies) available to sync from a given source system.	For Lansweeper On-Prem: Click here For Azure: Click here For AWS: Click here … etc (see next point) For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included CI-to-CI Dependencies.
For changes to the rules that define the mapping between Assets or Resources from a given source system and the default table/CI Class CI Sync targets when (a) searching for existing CIs and (b) inserting new CIs that don’t currently exist in the CMDB.	For Lansweeper On-Prem: Click here For InTune: Click here For VWware: Click here … etc (see next point) For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included Asset/Resource type to CI Class Mappings.
For changes to the rule/s that govern the default set of attributes available to sync from a given source system, and how they are mapped to CMDB CI attributes.	For Lansweeper On-Prem: Click here For InTune: Click here For Jamf: Click here … etc (see next point) For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included Attribute/Field Mappings per CI Class.
For changes to the Split Transformation Rules (i.e. to deliver different record or attribute behaviour between a CI Insert Operation vs a CI Update Operation).	For ServiceNow (relative to each individual source system): Click here
For changes to the way CI Status values are determined and set on CIs (including Install Status, Operational Status, Hardware Status and Hardware Sub-Status). To implement suppression of CI Status values (on CI Insert or CI Update) also requires Custom Data Sync Rule development.	For Lansweeper On-Prem: Click here and Click here For Lansweeper Cloud: Click here and Click here For ServiceNow: Click here … etc (see next point) For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included Status Value Maps.
For changes to the way CI Category and Sub-Category values are determined and set on CIs.	For Lansweeper On-Prem: Click here For VMware: Click here For Azure: Click here For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included Category and Sub-Category Value Maps.
To disable the default behaviour of CI Sync dynamically inserting new Choice Values in ServiceNow.	For Lansweeper On-Prem: Click here For Nutanix: Click here For Azure: Click here For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included Choice Records.
For implementation of any custom Location Determination Rules beyond what is available via self-service using the Connection Settings feature.	Click here
For changes to the synchronization behaviour for Cloud Tags or other sources systems that use Custom Fields beyond what is available via self-service using the Connection Settings feature.	For Azure: Click here For AWS: Click here For GCP: Click here For VWware: Coming Soon For all other source systems, navigate to the Default Configuration Guides page tree here (in the Syncfish Support Portal), then expand the pages related to a given source system, and finally view the Rule “n” page that describes the included Tag Synchronization.
For changes to the default behaviour of excluding assets/resources from a given source system if the incoming asset/resource contains scan errors.	For Lansweeper On-Prem: Click here
To define a custom list of Windows Services to be included in synchronization jobs for Windows Servers or Windows PCs.	For Lansweeper On-Prem: Click here For Lansweeper Cloud: Click here
To determine a suitable value for the Business Owner attribute using a custom field in a given source system.	For Lansweeper On-Prem: Click here For Lansweeper Cloud: Click here
To change the default way CI Sync interacts with the following data elements in ServiceNow: How CI Sync interacts at a record level with the cmdb_ci_spkg table How CI Sync interacts at a record level with the cmdb_software_instance table How CI Sync interacts at a attribute level, specifically the “Install Count” attribute on the cmdb_ci_spkg table.	For ServiceNow: Click here
To change the default master data tables used by CI Sync for Defender for Endpoint for the follow record sets: Software Packages CVE Definitions (a custom table) CVE Instances (a custom table)	For Defender for Endpoint: Click here
To change the default data source used by CI Sync to read from Defender for Cloud Apps	For Defender for Cloud Apps: Click here
For any other data synchronization behaviours/rules not covered by a Connection Setting or the above examples.

Purpose

Data Sync Rules Available for Override using CI Sync Connection Settings

ServiceNow Specific Rules

ServiceNow Manufacturer Related Rules

ServiceNow Hardware Model Related Rules

Various Other ServiceNow Rules

Lansweeper On-Prem Specific Rules

Lansweeper Cloud Specific Rules

InTune Specific Rules

Omnissa Workspace ONE Specific Rules

Jamf Specific Rules

VMware vSphere Specific Rules

Nutanix Specific Rules

ExtremeCloud IQ On-Prem Specific Rules

SolarWinds vSphere Specific Rules

Cisco Meraki Specific Rules

Microsoft Defender for Endpoint Specific Rules

SentinelOne Specific Rules

Microsoft Defender for Cloud Apps Specific Rules

Microsoft 365 Specific Rules

Azure Specific Rules

AWS Specific Rules

GCP Specific Rules

Data Sync Rules that Require Custom Development