NetLock RMMNetLock RMM Docs
IV — Administration

Hudu

Connect NetLock RMM to Hudu: devices become assets in a layout of their own, companies can be imported as tenants.

Hudu

Requirements

  • An API key, created in the admin area of Hudu under API Keys. Use a dedicated key for NetLock, without password access and without delete rights. If NetLock should create the layout, the key needs the right to write asset layouts.
  • The address of your instance.

Setup

  1. In Settings → Integrations, open the Hudu tile and choose Connect.
  2. Enter the Instance address and the API key. Allow unencrypted http is for an instance on an internal network only.
  3. The test of the connection shows the version of Hudu and what will happen with the layout.
  4. Under options, switch on Sync devices as assets: without it the connection does nothing, and nothing is created in Hudu. Choose the Asset layout: NetLock Device, or a layout that already exists in Hudu.
  5. Map each tenant to a company, or import the companies. Tenants without a mapping are not included.
  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.

  • NetLock Device is created on the first run if it does not exist, with the text fields NetLock Device Id, Operating System, IP Address and MAC Address. Manufacturer, model and serial number go into the primary fields of the asset.
  • A custom layout receives only the fields with these labels. Without a field NetLock Device Id, NetLock finds a device by its serial number or, if there is none, by its name.
  • A device is linked to an existing asset of the same company and layout by its serial number, or by its name if neither has a serial number, provided that exactly one such asset exists, it is not archived and neither another device nor another NetLock Device Id holds it.
  • An update sends the existing fields of the asset with the values NetLock knows filled in, so what you entered is kept. An asset of a custom layout whose fields NetLock cannot read counts as failed and is not changed.
  • A device that moved to another tenant gets a new asset in the new company. 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 Hudu. The External systems tab of the device links to its asset.

Known limits

  • NetLock writes a field under its label in lower case with spaces as underscores (NetLock Device Id becomes netlock_device_id).
  • A location in NetLock has no counterpart in Hudu; assets belong to the company.