NetLock RMMNetLock RMM Docs
III — How-To Guides

Restrict USB devices on a group

Let new devices learn their keyboard, mouse and dock, then approve further USB devices from the Blocked Devices queue at group scope.

Restrict USB devices on a group

USB access in NetLock RMM is an allowlist: anything not on the whitelist is blocked. A device gets its whitelist in two ways:

  • Learning. When a device is assigned to a policy with learning switched on, it learns the devices connected to it during its learning period, typically its keyboard, mouse, dock and headset. The entries apply to that device only. Other devices on the policy keep blocking unknown devices in the meantime.
  • Approval. A USB device that is blocked appears on the Blocked Devices tab, where an administrator approves it for the device, its group, location, tenant or globally.

This guide sets up a policy for a group of Windows devices, lets the devices learn what is attached to them, and then approves a further USB device for the whole group.

Blocked Devices tab with one pending USB entry selected

Before you start

  • The policy reaches the target group through an automation (see Guide H.4).
  • The devices run agent 3.3.0.11 or later.
  • Required permissions: policies_edit to change the policy; collections_enabled, collections_device_control_enabled and collections_device_control_manage to approve devices; devices_usb_learning to re-learn or end learning on a device.

Steps

Set up the policy and let the devices learn

  1. Open the policy and go to Windows → USB Device Control. Switch on Enabled.
  2. Switch on Learn connected devices on devices newly assigned to this policy and choose the Learning period:
    • 4 hours (the default) or longer when users plug in their docks and headsets over the day.
    • Devices connected when learning starts when only what is attached at that moment should be learned; everything connected later is blocked and can be approved afterwards.
  3. Choose the device type filters and the actions on unknown devices (Eject / disable device, Log device event), then save the policy.
  4. Each device of the group starts its own learning period when it receives the policy. Devices that are already on the policy are not affected.
  5. Follow a device on its USB Devices tab: the status line shows Learning connected devices until …, and the learned devices appear in its whitelist with the author Auto-Whitelist (Agent: <device name>).
  6. Let the period run out, or end it early with End learning now once the device has learned what it needs. From then on, unknown devices are blocked on it.

Tip: For a device that gets a new dock or keyboard later, use Re-learn connected devices on its USB Devices tab. Several devices can re-learn at once from Collections → Device Control (Re-learn connected devices on the Whitelist tab, at most 500 devices).

Approve a further USB device for the group

  1. On one of the devices, plug in the USB device. The agent detects it, disables it and reports it to the Console.
  2. In the Console, open Collections → Device Control and switch to the Blocked Devices tab (route /device-control/blocked).
  3. Find the row for the USB device. The Blocked Devices table shows Count, Date, Reporting Device, the USB metadata (name and manufacturer), the device Type (Mouse / Keyboard / HID / USB / DiskDrive / and so on), the Device ID, the Actions Taken, and a Pending status chip.
  4. Confirm this is the intended device. If more than one pending row looks similar, compare the vendor-id, product-id, and serial encoded in the Device ID.
  5. Open the row's menu and pick Approve for group. The group is the group of the reporting device. The other choices are Approve for this device, Approve for location, Approve for tenant, Approve globally (accounts with access to all tenants) and Dismiss.
  6. The server adds the device to the whitelist scoped to that group, sets the row's status chip to Approved, and requests a sync so the devices in the group pick up the updated whitelist.

Note: Scope is chosen once, at approval time. To widen or narrow a whitelist entry later, delete it from the Whitelist tab and re-approve the blocked-device entry with a different scope.

Verify it worked

  • On the USB Devices tab of a device, the status line reads Connected devices learned on … under policy … once its period is over, and its keyboard and mouse work.
  • On the Whitelist tab (route /device-control/whitelist) a new row appears with the approved USB device's metadata, the group scope chip, and the reporting device's group as Scope Target. Status is on.
  • On any device in the group, the approved USB device connects. On devices outside the group, it continues to be blocked.

Troubleshooting

  • A device does not learn. Check its USB Devices tab. Connected devices have not been learned on this device means it has not received a policy with learning switched on since it was assigned; use Re-learn connected devices. A device that returns to a policy it has already learned under does not learn again by itself.
  • USB device does not appear as blocked. The policy assigned to the device must have USB Device Control turned on. In block mode, at least one whitelist entry must apply to the device or the device must be in its learning period: with an empty rule set nothing is enforced, because every device would otherwise be blocked, including keyboard and mouse.
  • Approved but still blocked. Allow a sync cycle to pass. Once the device has the updated whitelist, the agent enables the device again by itself; re-plugging is not required. If the device was disabled while it was unplugged, it is enabled at the next periodic check after it is plugged in again (5 minutes by default).
  • Multiple similar rows appear. Each failed enumeration is logged as a separate attempt; approve one and delete or dismiss the others.