Software Package Handling 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.

The screen shot is provided only as 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
Software Package Name Format	Choicelist	Synchronizes the software package using either the Package Name only (default) or the Package Name suffixed with the software package version. Including the version helps ensure each package record is unique.
Include OS as a Software Package	Slider	When enabled, Include OS as a Software Package creates one software package for each unique operating system. It also creates a `cmdb_software_instance` record for each device, linking the ServiceNow computer CI to the corresponding operating system package record in the `cmdb_ci_spkg` table.
Software Install Name Delimiter	String	Defines the delimiter used when composing the software install name. By default, CI Sync uses a hyphen (`-`), but this can be changed to any delimiter. The software install name is composed as Software Package Name + {delimiter} + Asset Name.

After modifying 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.