Ivanti Neurons connector

The Ivanti Neurons connector feeds the Portail ZAPP CMDB with the devices managed by Ivanti Neurons, Ivanti's cloud platform. Portail ZAPP queries the Neurons API directly: there is no agent to install. The screens are reserved for administrators; the Ivanti Neurons entry is in the Administration › Connectors and automation menu.

This connector does not replace the Ivanti UEM connector, which reads the older on-premises console (Ivanti EPM) through an Outpost agent.

What is imported

At each collection, the connector reads the Neurons devices and creates or updates, in the CMDB:

• one Computer per device: name, domain, serial number, Brand and Model, operating system, processor, memory, Primary user;
• one Disk per local disk (C:, D:…), with its capacity and free space;
• one Network adapter per card, with its MAC address and IP address;
• the installed software (Add/Remove Programs list), if the option is checked.

Devices without an agent: Neurons also knows devices that were only discovered on the network, with no agent installed. They carry little more than their MAC address, IP address and system name. They are imported only if the Devices discovered without an agent option is checked. Among them, infrastructure devices (switches, routers, printers…) are imported as Network Devices, with their addresses, brand and model, not as computers.

A known computer is not duplicated: if another source (Intune, GLPI, Ivanti UEM…) already imported it, it is matched by its BIOS UUID, serial number, MAC addresses or name, and its fields are completed. Manufacturers' generic serial numbers ("Default string", "To Be Filled By O.E.M."…) are never used for matching.

Primary user: Portail ZAPP looks for the account of the user that Neurons associates with the device, first by their Entra ID email address, then by their domain login (DOMAIN\account), ignoring case and accents. A local account of the device (DEVICE-NAME\account) is never used. If no account matches, or if several accounts match, the field is not changed; the computer is imported anyway. You can link these users yourself, local accounts included: see Reconciling users.

Imported computers can be browsed in the CMDB, type Computer.

Before creating a source

On the Neurons side, an administrator registers an application allowed to read data (Data Services). Neurons gives it:

• the authority URL, in the form https://xxx-sfc.ivanticloud.com/xxx.ivanticloud.com/connect/token;
• the client ID;
• the client secret.

In Portail ZAPP, store the client secret value in the Secrets vault: the source refers to that secret by its name, never by its value.

Creating a source

The Ivanti Neurons sources page lists the sources with their name, slug, the API host called, their schedule and their state. Click + New source and fill in:

• Name and Slug (short identifier; it cannot be changed after creation);
• Authority URL: as given by Neurons, in https://. Portail ZAPP derives the API host and the tenant from it, then shows them on the source page;
• Client ID;
• Secret: pick the secret in the list. If the list is empty, the create one link leads to the secrets vault;
• API host and Tenant: leave them empty unless Ivanti says otherwise;
• Timeout per call: in seconds, from 5 to 300 (60 by default);
• Installed software and Devices discovered without an agent: see above;
• Link CMDB contacts to workstations: see Reconciling users;
• Schedule (cron, optional): the collection frequency, chosen with the assistant. Without a schedule, the source is only collected by Synchronize now.

Click Save. An invalid entry is reported and nothing is saved.

Testing, synchronizing

On the source page:

• Test connection asks Neurons for a token and reads one device; on success, the number of devices announced by Neurons is shown. Nothing is imported.
• Synchronize now starts a collection in the background; reload the page to see its result in the Last collection box (status, devices imported, errors). The button is also in the source list.

Reconciling users

The Reconcile users button on the source page shows the number of users to process: those Portail ZAPP did not link to any account. The Neurons users page lists them (To process tab, or All). Neurons does not give user names: each user is identified by their Entra ID email address, otherwise by their DOMAIN\account. A local account badge marks an account of the device itself. For each one, the page shows the number of workstations, the result of automatic matching and the decision taken.

• Link (per row): pick a Portail ZAPP account in the list (search ignores case and accents). It is the only way to link a local account.
• Create contacts (ticked users): creates a CMDB contact per user, named after their address (otherwise their account) and attached to the chosen third party, then links it to the user.
• Ignore (ticked users): the user is never linked again and leaves the list to process.
• Remove the decision (ticked users): the user goes back through automatic matching.

A decision takes precedence over automatic matching and applies at the next collection; Synchronize now applies it at once. A user linked to a contact or ignored no longer fills the primary user of their workstations. If the source's Link CMDB contacts to workstations option is ticked, their workstations are linked to the contact ("used by").

Enabling, editing, deleting

• The button in the Enabled column (Yes / No) enables or suspends the source and its scheduled collection. A suspended source does not synchronize.
• Edit opens the source page; clearing the schedule removes the scheduled collection.
• The trash can deletes the source and its collection, after confirmation, along with its decisions on users. Computers already imported and contacts created stay in the CMDB.

Error codes

A failed collection, or a refused connection test, shows a code:

A collection that finds no device succeeds, with 0 devices.