Alloy Discovery Synchronization

On this page

Alloy Discovery Synchronization imports the inventory of an Alloy Discovery database into Alloy Navigator. The connector reads the Alloy Discovery database on SQL Server directly. Its work is done by Alloy Discovery Synchronization jobs. The Automation Server starts each enabled job on its schedule.

One job reads one Alloy Discovery database. Importing from several Alloy Discovery databases, on one SQL Server or on several, takes one job per database.

How an audited device is matched to an existing computer, and how audit conflicts are resolved, is described in Audit Conflict Policy and Inventory Data and Audit Conflicts. You manage the jobs in the Settings App and in the Admin Center; see Admin Center and Settings App.

Before you begin

  • For a job to be executed, the Automation Server must be set up and running.
  • You need the Alloy Discovery Integration permission, in the Services Configuration Management group of the role's permissions. It opens the Alloy Discovery Integration branch in the Settings App and the Alloy Discovery Integration page in the Admin Center. In the Admin Center, Administrative Access and Basic Administrative Access also open the page. See Permissions Reference.

Alloy Discovery Synchronization in the Settings App

In the Settings App, Alloy Discovery jobs are managed under Services > Alloy Discovery Integration, which has three nodes: Conflict Resolution, Synchronization, and Logs. Conflict Resolution holds the conflict resolution rules and the conflict list; see Audit Conflict Policy.

Open the job list

Select Services > Alloy Discovery Integration > Synchronization. The same jobs are also listed, and can be run, under Services > Automation Server > Job List.

The toolbar holds Open, New, Delete, Run, Terminate, and Refresh. The right-click menu holds New, Run, Terminate, Enable, Disable, Copy Job ID (GUID) to Clipboard, and Export Selected Settings….

Refresh, or F5, reloads the list and reads the Automation Server status again. While the list is on screen, it also reloads changed rows on its own, every ten seconds by default.

Create or edit a job

  1. In the Synchronization list, click New to open the Alloy Discovery Synchronization dialog for a new job. To edit a job, select it and click Open, or double-click it; its dialog opens on the Settings tab, with the job's name in brackets in the caption.
  2. On the Settings tab, set the name, the Alloy Discovery database, and the schedule.
  3. On the Processing tab, choose the service actions and the processing options.
  4. Click OK.

The dialog has three tabs: Settings, Processing, and Sessions.

Settings tab

The dialog has no Windows account setting: the job connects to the Alloy Discovery database as its Alloy Discovery database group sets.

  • Name and Enabled. A new job is named "Alloy Discovery Connector". When a job of this type already has that name, the dialog takes the first of "Alloy Discovery Connector (1)", "Alloy Discovery Connector (2)", and so on that no job of this type has, ignoring case. A new job starts enabled, with a schedule of every 60 minutes.
  • The Alloy Discovery database group:
    • Connect to the Alloy Discovery Database using: offers The Automation Server database connection and This access key:.
    • With The Automation Server database connection, SQL Server shows the SQL Server of the Automation Server's connection, and the job uses the Automation Server's own database connection. This choice reaches only an Alloy Discovery database on that SQL Server instance.
    • With This access key:, click Import Key... to import a key. The job then reads the SQL Server that the key names. Import Key... is enabled only with this choice. Importing a key replaces the held key and refreshes Key name and SQL Server, but leaves Database as it is.
    • Key name shows the name of the held key, or "N/A" when no key is held. SQL Server is read-only.
    • Clicking either connection choice clears the Database list and its text. Choosing The Automation Server database connection discards a held key.
    • Database is a drop-down list. It fills the first time you open it while it is empty, with the databases on the shown SQL Server that have a compatible Alloy Discovery version. When the job has no database yet, as with a new job, the box is filled in with the database remembered for your user account; a job with a stored database shows that database.
    • Test Connection is enabled with The Automation Server database connection, or once a key is held.
  • The Schedule group shows the schedule as text. Change opens the Schedule window, which you close with OK or Cancel:
    • Occurs is Daily, Weekly, Monthly, or Yearly: every n days; every n weeks on chosen weekdays, Mon to Sun; on a day of the month or on a relative weekday of every n months; or, under Months:, in chosen months on days of the month (Days:) or on ordered weekdays (On:). A relative weekday is First through Fourth, or Last, of a named day, Day, Weekday, or Weekend Day.
    • Daily frequency is Occurs once at: a set time, or Occurs every: n Minute(s) or Hour(s) between Starting at: and Ending at:. A window whose end time is earlier than its start time runs past midnight.
    • Duration holds Start date: and End date:, or No end date, for the first and last date of the schedule. With No end date, the schedule has no last date. Once the next run would fall after the end date, the schedule expires and the Automation Server no longer starts the job on it. Editing the schedule, or enabling the job again, clears the expired state and has the next run calculated afresh.
    • The shortest Occurs every: interval is 1 minute on premises. In Alloy Navigator Cloud, it is 15 minutes: the scheduler raises a lower value to 15.

When a run fell due while the Automation Server was not running, the job runs once as soon as the service is active again, and the run's log records it. A run that takes longer than the interval builds no backlog: the next run is calculated again after it.

While the Automation Server is not running, the tab shows "Warning. For this job to be executed, the Automation Server must be set up and running."

Processing tab

The Workflow group holds seven service-action pickers:

Picker Prompt
Create Computers For new computers:
Update Computers For existing computers:
Create Persons For computer users that can't be matched to a Person:
Update Hardware For existing hardware:
Create Hardware For new hardware:
Update Chromebooks
Create Chromebooks

Processing Options: holds Create Organizations and Create Locations. Both are selected in a new job. They are passed as values to the computer, Chromebook, and Person service actions, and those actions decide what to do with them. The hardware actions do not receive them.

The Other tasks group sets what happens to the Alloy Discovery record of a retired device: Keep its original record in Alloy Discovery or Delete its original record from Alloy Discovery; see Retired devices. A new job starts with Delete its original record from Alloy Discovery.

Sessions tab

The Sessions tab is the job's own log. It is disabled for a new job that has not been saved yet. See Review synchronization results.

When you click OK

  • OK is enabled only when the job has a name, a schedule, and a database name.
  • The dialog refuses an empty job name, an empty database, and This access key: with no key held.
  • When the connection has changed, the dialog offers to test the connection first.
  • When all six computer, Chromebook, and hardware pickers are empty, the dialog asks you to confirm. The Create Persons picker is not counted.

Run a job now

  1. In the Synchronization list, select exactly one job.
  2. Click Run on the toolbar or on the right-click menu.

Run is enabled only while exactly one job is selected and the Automation Server status, as last read, is running. The status is read again when you click Refresh or press F5, and the main window reads it again every minute, so a Run that stays unavailable after the service has started returns after F5 or within a minute.

When the Settings App hands the request to the Automation Server directly, the Automation Server starts the job at once, whether the job is enabled or not, unless the job is already executing or locked, or the Automation Server is not active. A disabled job therefore runs once on Run and stays out of the schedule.

When the Settings App cannot hand the request to the Automation Server directly, it queues the request for the Automation Server and shows a message that, the Settings App and the Automation Server being on separate computers, it may take some time, and that you check the session log once the job has completed. Any other failure shows "Cannot send request to the Automation Server. Make sure the Automation Server is configured and started."

Enable, disable, or delete jobs

  • To enable or disable jobs, select one or more jobs, right-click, and choose Enable or Disable. The Automation Server starts only enabled jobs on their schedule.
  • To delete jobs, select them, click Delete, and confirm "Are you sure you want to delete the selected item?". Delete acts on every selected job.

Review synchronization results

The results of the runs are in the connector's log. The Settings App shows it in three places:

  • Services > Alloy Discovery Integration > Logs. This node is available to users with the Alloy Discovery Integration permission, also without Log Management > Browse.
  • Logs > Discovery Synchronization. This node requires Log Management > Browse.
  • The job's Sessions tab, which shows only that job's runs.

See Permissions Reference.

The log lists each run with Run Date, Job Name, Comments, Duration, and four counts:

Column What it counts
Created Computers Computers created by the run, Chromebooks included
Created Hardware Hardware created by the run
Created Conflicts Audit conflicts raised by the run
Errors Errors of the run

The two created counts rise only when a computer, Chromebook, or hardware record is created, not when one is updated.

In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), the connector's log and the job's Sessions tab offer the views All Time, Last 7 days, Errors, and by Job Name. Each lists the newest run first, so the top row of the Sessions tab is the job's most recent run; by Job Name also groups the runs by job name. These views are supplied content: an administrator can edit or remove them like any other view.

  • View Log, Enter, or a double-click on a row opens the text of the session in the application that Windows uses for .log files.
  • Delete removes the selected session rows. It asks "Are you sure you want to delete the selected record?", or, for several rows, "Are you sure you want to delete n selected records?", and then reports "n records have been deleted."
  • Clear All deletes all sessions of the connector, or, on a job's Sessions tab, all sessions of that job. It first asks "You are about to delete all entries from the Service Log. Are you sure you want to proceed?".
  • On the log nodes, Delete and Clear All are shown only to users with Log Management > Manage. Without it, the log there is read-only.
  • Settings... sets how many days the connector's log records are kept. It is not shown while the log is read-only, or on a job's Sessions tab. It requires Log Management > Manage; without it, Settings... answers "You do not have enough permissions to use this function." The value applies to this connector's log only; while it is not set, the general log retention applies, which is 30 days by default. In Alloy Navigator Cloud, the retention settings are read-only. The Automation Server removes older records once a day.
  • The log loads the last 1,000 records at most, and says how many it has loaded. When loading the log times out, it shows the number of rows in the log and leaves Clear All available.
  • To export session rows, right-click the grid and choose View > Export Rows > Export All or Export Selected, in MS Excel Format, HTML Web Page, XML Format, or ASCII Text File Format. The same View menu also offers Analyze with MS Excel.
  • Refresh, or F5, reloads the log. While the log is on screen, it also reloads on its own, like the job list.

Point jobs at another Alloy Discovery database

A job's source is stored in the Alloy Navigator database. A pilot database made from a copy of production therefore starts with the production jobs:

  • A job with an access key keeps reading the stored database on the key's SQL Server, which is the production Alloy Discovery database.
  • A job without a key reads the stored database name on the SQL Server of the pilot's own Automation Server connection. That is the production Alloy Discovery database only when that server hosts it.

To repoint a job:

  1. Open the job from its Synchronization list.
  2. On the Settings tab, in the Alloy Discovery database group, set the Connect to the Alloy Discovery Database using: choice, click Import Key... for a key, choose the Database, and click Test Connection.
  3. Select Enabled if the job should run on its schedule, and click OK to save the connection settings.
  4. Select the saved job in the list and click Run to try it. Check the session log when the run finishes.

Pointing the jobs back at production after the pilot is the same edit.

Alloy Discovery Synchronization in the Admin Center

In the Admin Center, open Alloy Discovery Integration in the Services and Integrations section of the sidebar. The page requires the Alloy Discovery Integration permission, Administrative Access, or Basic Administrative Access; see Permissions Reference. It has four tabs: Conflict Policy, Conflict List, Synchronization, and Logs, and opens on Conflict Policy. Conflict Policy and Conflict List hold the conflict rules and the conflicts; see Audit Conflict Policy.

Create a job

  1. On the Synchronization tab, click New. A panel titled "New Synchronization" opens on its Settings tab.
  2. On the Settings tab, check the name, choose how to connect to the Alloy Discovery database, set the Database, and set the schedule.
  3. Complete the Processing tab.
  4. Save the job.

The panel of a new job has two tabs, Settings and Processing. On the Settings tab:

  • Name is filled in with "Alloy Discovery Connector", or, when that name is taken, with "Alloy Discovery Connector (1)", "Alloy Discovery Connector (2)", and so on. Enabled is selected.
  • The Alloy Discovery database group holds Connect to the Alloy Discovery Database using:, with The Automation Server database connection, selected in a new job, and This access key:; then SQL Server, Database, and Test Connection.
  • Name and Database are required.
  • The Schedule group holds the job's schedule.

Manage jobs

The Synchronization tab lists the Alloy Discovery jobs. Its toolbar holds New, Edit, Delete, Enable, Disable, Run, and Terminate, followed by a refresh button without a label.

  • To open a job, double-click its row, click its name, or select it and click Edit. Edit is available with one job selected. The job opens in a panel on its Settings tab, which includes the schedule, followed by the Processing and Sessions tabs. The Sessions tab is shown once the job exists; a new job, titled "New Synchronization", has no Sessions tab.
  • Enable and Disable act on the selected jobs.
  • Run requires one selected job and an active Automation Server.
  • Terminate also requires that the job's last run status is executing.
  • The actions are disabled while the list is loading.

Run queues the job and shows "Your job will be started as soon as possible, typically within a few minutes. Please check the job status later." The Automation Server starts the job when it next checks for queued requests, whether the job is enabled or not.

Running a job that is already queued to run shows "Please wait until the job has completed, and then check the session log to make sure that it runs as expected." and refreshes the list instead of queuing the job again. Terminating a job that is already being terminated shows "Please wait, the job will be terminated soon." and refreshes the list.

The Next Run column shows whether a job is waiting to run as soon as possible, being terminated, disabled, or not yet started, before it shows a date.

In Alloy Navigator Cloud, the schedule field offers no interval shorter than 15 minutes for an Alloy Discovery job, and when the job is saved, a schedule of every n minutes below 15 is raised to 15 minutes; see Administering Alloy Navigator Cloud.

An Alloy Discovery job opened from the Admin Center's Automation Server page opens in its own job editor.

Review the connector's log

The connector's log is also one of the logs on the Admin Center's Logs page, as Discovery Synchronization; see Logs. On that page:

  • The log is one table with a search box, sorted by run date with the newest run first. It offers no choice of views.
  • View log is available with exactly one row selected. A double-click on a row does the same.
  • Clear all, Delete, and the Settings link are shown only to users with the permission to manage logs. Clear all asks for confirmation first.
  • In Alloy Navigator Cloud, the log settings keep the log for 30 days: the retention control is disabled, and 30 days is applied again when the settings are saved.
  • Delete asks for confirmation, with the number of rows when several are selected, and shows no result message afterwards.

What a synchronization run does

A run works in this order:

  1. It loads the conflict resolution rules.
  2. It synchronizes the software catalog from the Alloy Discovery database.
  3. It handles the Alloy Discovery link of devices retired in Alloy Navigator, as the job's Other tasks setting says.
  4. It imports computers, then Chromebooks, then hardware.
  5. It removes unused software products.

The software catalog step can be skipped when nothing in the Alloy Discovery database has changed since the last catalog synchronization and no conflict is scheduled, that is, no conflict has a resolution chosen by an administrator that the next run must apply.

If any audit conflict is raised during the run, the connector writes one entry to the system log saying that an audit conflict was detected. See Logs.

A Chromebook is imported as a Computer record, not as a class of its own, and is counted under Created Computers.

Retired devices

When a Computer or Hardware record in the Retired status still carries its link to an Alloy Discovery record, the job's Other tasks setting decides what the run does:

  • Delete its original record from Alloy Discovery: the run deletes the matching record in the Alloy Discovery database and removes the link in Alloy Navigator.
  • Keep its original record in Alloy Discovery: the run skips the step, and the link stays too.

Once the link is gone, a later audit of the same machine is no longer recognized through that link; the other matching steps decide whether it counts as new.

Computer users and Persons

For each computer it creates or updates, the connector looks for the computer's user among the existing Persons. Chromebooks and hardware are not included. The user's full name, first, last, and middle name, primary login, and primary e-mail are taken from the Alloy Discovery columns that the job's Create Persons action maps to those Person fields, or from a built-in mapping when the job has no such action.

  • A login written as DOMAIN\user is split into the domain and the login.
  • A user whose full name is SYSTEM is neither matched nor created.
  • A user with no name, login, or e-mail is skipped with the warning "Skip empty user".

The other users go to the shared person matching; see Person Matching Reference. For this connector, a full-name match alone is enough, and the full-name match is not limited to Persons without a directory identity. The highest-scoring active Person wins; on a tie, the oldest one. The result of the match is written to the session log.

Only when no Person matches and the job has a Create Persons action does the connector run that action, logging Adding new user "<name>" (<e-mail>). The matched or created Person is passed to the computer's service action as the computer's user.