NetLock RMMNetLock RMM Docs
IV — Administration

IT Glue

Connect NetLock RMM to IT Glue: devices become configurations of the mapped organization, organizations can be imported as tenants.

IT Glue

Requirements

  • An API key, created by an administrator in IT Glue under Account, Settings, API Keys. Use a dedicated key for NetLock. IT Glue shows a key only once and revokes it after 90 days without use, so a connection that was paused for a long time may need a new one.
  • The address of your data center: https://api.itglue.com, https://api.eu.itglue.com or https://api.au.itglue.com. No other address is accepted, so a stored key cannot go anywhere else.

Setup

  1. In Settings → Integrations, open the IT Glue tile and choose Connect.
  2. Enter the Instance address and the API key.
  3. Under options, switch on Sync devices as assets: without it the connection does nothing. Check whether new configurations affect your IT Glue plan before you switch it on. Choose the Default configuration type, which IT Glue requires on every configuration, and optionally a Configuration status.
  4. Map each tenant to an organization and its locations, or import the organizations. Tenants without a mapping are not included.
  5. Optionally map device classes to configuration types.
  6. Activate the connection.

What goes to the vendor

Device name, operating system, manufacturer, model, serial number, IP address and MAC address of the authorized devices of the mapped tenants.

Asset sync

Every hour NetLock sends the devices that changed since the last run, at most 200 per run; if more devices changed, the next run starts right after. Synchronize now starts a run immediately.

  • A device becomes a configuration of the mapped organization, with NetLock-Device-<id> as asset tag.
  • A device is linked to an existing configuration by its serial number, provided that exactly one configuration of the organization has it, it is not archived, its asset tag is empty and no other device holds it. A configuration that already has a different asset tag is left alone, and the device gets a new configuration. A linked configuration keeps its name and type.
  • Manufacturer, model and operating system are lists in IT Glue. If IT Glue knows the exact name, it is selected. NetLock creates no entries in these lists: an unknown manufacturer or model goes into the notes of a new configuration, and the operating system is always written to Operating system notes.
  • Name, type and status are set when NetLock creates a configuration. An update sends only the values NetLock knows, among them the host name, and never changes name, type, status or notes.
  • A configuration that another system such as a PSA syncs accepts only a few attributes through the API. If IT Glue refuses the update and the configuration shows such a link, NetLock sends only the serial number and, if the field is empty, the asset tag. Any other refusal counts as a failed device.
  • A device that moved to another tenant gets a new configuration in the new organization. The old one stays.
  • A device that fails is named in the history and waits for the next hourly run; the other devices are still processed.

Nothing is deleted in IT Glue. The External systems tab of the device links to its configuration.

Known limits

  • IT Glue answers a wrong or revoked key with status 403, which NetLock treats as a problem of the whole connection: it goes to Error until the key is replaced.
  • IT Glue allows 3000 requests in five minutes. NetLock waits when IT Glue reports the limit.