---
title: "Configure Asset Optimization"
slug: "configure-asset-optimization"
updated: 2026-08-27T14:03:41Z
published: 2026-08-27T14:03:41Z
canonical: "documentation.lakesidesoftware.com/configure-asset-optimization"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Asset Optimization

To install and configure the SysTrack Asset Optimization plugin for ServiceNow, complete the steps in the following sections. These steps apply to both SysTrack Cloud and SysTrack On-Premises (except where noted).

## Get the Plugin

Follow these steps to get and install the Asset Optimization plugin:

1. Log in to the ServiceNow Store with a HI permission account and download the [SysTrack Asset Optimization plugin](https://store.servicenow.com/store/app/55a07f261ba46a50a85b16db234bcb4e).

![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image-1778569745624.png)
2. Install the Asset Optimization plugin on the Plugins page in ServiceNow.

## Run the Fix Script

After installation, check if a new discovery source called **SysTrack** is created. If not, run the fix script called **Create SysTrack Discovery source** in the **Global** scope to create the discovery source. The script is included in the SysTrack Asset Optimization package downloaded from ServiceNow.

After running the fix script, confirm that it was successful by verifying that a **SysTrack** entry appears in ServiceNow > **Configuration** > **CI Class Manager** > **Discovery Sources**.

For more information about running fix scripts in ServiceNow, see the official documentation here: [Run fix scripts](https://www.servicenow.com/docs/r/application-development/t_RunFixScripts.html).

## Configure the Plugin

Follow these steps to configure the Asset Optimization plugin:

1. Establish a MID server on a system connected to the SysTrack network. For more information, see the ServiceNow documentation: [MID Server](https://www.servicenow.com/docs/r/xanadu/servicenow-platform/mid-server/mid-server-landing.html).

> [!NOTE]
> **NOTE**: A MID server is required only for SysTrack On-Premises.
2. Open the Properties for SysTrack Asset Optimization.
3. Edit the Properties fields as follows:
  - **HTTP Protocol** is a toggle for whether or not the SysTrack Master uses HTTPS.
  - **Count of systems per request** defines the number of items to be retrieved by a single SysTrack API request. Valid values are 1 to 50,000. The default value is 1,000.
  - **SysTrack master name** is the FQDN or IP of the SysTrack Master for the integration.
  - **SysTrack install type** defines whether the integration targets a SysTrack On-Premises master or a SysTrack Cloud instance.
  - **SysTrack API key** contains the API key used for authentication. This is needed only for SysTrack Cloud instances. If you need to generate a SysTrack API key, refer to the following article: [Generate an API Key](/documentation/docs/manage-api-keys#generate-an-api-key).
  - **MID server name** identifies the intermediary between the ServiceNow and SysTrack environments. This needs to be set up in ServiceNow only for SysTrack On-Premises.
  - **Username for Basic Auth** and **Password for Basic Auth** are the credentials for an account that has access to the SysTrack API for the master. These are needed only for SysTrack On-Premises.

## Set Up Steps for SysTrack On-Premises

The following actions need to be completed only for SysTrack On-Premises. If you are using SysTrack Cloud, you can skip ahead to [Configure a Schedule for Asset Optimization](/documentation/docs/configure-asset-optimization#configure-a-schedule-for-asset-optimization).

### Set Up Basic Authentication for SysTrack API

The following steps show how to set up Basic Authentication for the SysTrack API on the SysTrack Master server.

1. On the SysTrack master system, navigate to the **IIS Manager**.
2. Go to **Sites > Default Web Site > api**.
3. Select **Authentication**.
4. In the Authentication menu, enable **Basic Authentication**, like shown on the below screenshots.

> [!TIP]
> **TIP**: If Basic Authentication isn't visible as an option, you can enable it in Windows feature settings.

![IIS Manager interface displaying application settings and authentication configuration options.](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/API_01.png)

![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/API_02.png)

### Test the Configuration

The following steps show how to test your Asset Optimization configuration.

1. Check the ServiceNow instance's connection to the MID server. Use the Servers menu under the MID Servers heading on the Instance page.
2. Check the MID server's connection to the SysTrack host machine by checking the Services menu. A MID Server service should appear in the list.

## Configure a Schedule for Asset Optimization

After you have installed and configured the Asset Optimization plugin, you can configure the schedule for how often and at what time your ServiceNow CMDB will be updated with fresh data from SysTrack. Follow the below steps to set up the schedule:

1. In ServiceNow, search for **Scheduled Jobs** and locate the SysTrack Import Script.
2. To enable a scheduled import, you need to tick the **Active** box and set a user in the **Run As** field. For a user to appear in the selection box, you need to grant them both the **x_laso_systrack_sy.user** and the **import_set_loader** roles.

> [!WARNING]
> **IMPORTANT**: Both roles are required. Without **import_set_loader**, the import job fails when writing to staging tables or executing transforms. Without **x_laso_systrack_sy.user**, the import job fails due to ACL restrictions on the application's custom tables (staging tables and Import Job Run History).

If no user is selected, the import will run with a user called **system**. The import will be successful but the **Company** field will be empty in the import, since no company is assigned to the **system** user.

> [!NOTE]
> **NOTE:** In domain-separated instances, user data is organized into distinct domains. When the import script runs, it automatically selects the data domain based on the domain of the user specified in the **Run As** setting.
3. Set the schedule to suit your business hours (for example, late evening).

> [!WARNING]
> **IMPORTANT**: The **Run this script** field includes the preconfigured import script. To use the integration, you do not need to edit this script.

## Configure the Identification and Reconciliation Engine (IRE)

> [!WARNING]
> **IMPORTANT**: The new version of the Asset Optimization plugin requires you to set up the Identification and Reconciliation rules to prevent duplicate systems in the import. For more information about the setup, refer to the official ServiceNow documentation here: [Identification rules](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/c_IdentificationRules.html).

### Best Practices for Identification Rules

| **Recommendation** | **Reason** |
| --- | --- |
| Use `serial_number` as primary identifier | Most reliable hardware identifier from SysTrack. |
| Add `fqdn` as a fallback rule | Helps match VMs and devices where serial numbers are missing or inconsistent. |
| Avoid using `ip_address` as the only identifier | IP addresses can change and may create false matches. |
| Test rules with a small chunk first | Set chunk size to 10–50 and run a test import to verify matching behavior. |
| Review Duplicate CIs module after import | Navigate to **CMDB** > **Duplicate CIs** to identify any remaining duplicate records. |

## Uninstalling Asset Optimization

To uninstall the SysTrack Asset Optimization application:

- Go to **Admin** > **Application Manager** > **Installed** or **All** > **Admin Center** > **Application Manager** > **Installed**.
- Select the installed SysTrack Asset Optimization application.
- In the Related Links section, click Uninstall.
- Confirm the uninstall action.

> [!NOTE]
> **NOTE**: Uninstalling the application does not remove the SysTrack discovery source record. An administrator must delete the SysTrack discovery source manually if it is no longer needed.