OU filter as a user-defined filter

You can filter by configured asset information of the devices to assign the matching devices to the appropriate OUs.

Filter rules wit OU filter text

eLux devices send an OU filter text field containing their device information to the Scout Server. You can use the OU filter text field in the Scout Report Generator and for the user-defined OU filter. It includes the following information:

Host name, OS name, OS version, serial number, supplier, device type, UEFI/BIOS, CPU speed, model, kernel version, flash type, flash size, RAM size, graphics, IDF name, MAC address.

Examples filter rules:

ELUX_OSNAME=eLux RP AND ELUX_OSVERSION=6.2302.1
ELUX_DEVICETYPE=D3314-A1 OR ELUX_DEVICETYPE=ZQ Class

Setting up a user-defined OU filter

  1. Click Options > Advanced options > Devices.
  2. Under New devices, select the Assign OU depending on OU filter option. If required, click to open the OU assignment dialog.

  3. Under Filter type, select User-defined filter (configured asset information).

  4. Create a new filter rule. Edit the following fields:

    Option Description
    Filter rule Create a filter rule consisting of one or more filter criteria, see above.
    Destination OU To browse the OU list, click and select the OU you want the specified devices to go.

  5. Click Add.

    The filter rule is displayed in the field below.

  6. If required, add more filter rules and configure them. For further information, see Options for OU filter rules.

  7. From the list Non-matching devices, select where you want to keep the non-matching devices.

    If you select assigned to the default OU, all non-matching devices and even devices already assigned to other OUs are reassigned to the default OU.

  8. Review all active filter rules thoroughly to avoid unintentional assignments.
  9. Confirm with OK..

All active filter rules are processed in the specified order. On the next restart the matching devices are assigned to the OUs as defined by the OU user-defined filter. Any additionally defined subnet filter rules will not be taken into account.