Device groups

Introduction

The device group function has been available in Relution since version 5.21.0. This allows devices to be automatically assigned to groups based on various device properties. The device groups can then be used to assign policies that are delivered automatically.

Activation

Currently, the device groups feature must be enabled manually. This can be done via Settings > Device Management > Migration of Device Groups. The associated policy assignment to device groups cannot be undone.

Activate Device Groups

After clicking on Start Migration, a message about the upcoming changes will be displayed. Read it carefully and click on Next.

In the following dialog, you can finally execute the migration.

Activate Device Groups

Device Groups

After the migration has been successfully executed, you will be automatically redirected to the newly appeared menu item Devices > Device Groups. Here, you will find an overview of the automatically created groups and you can create new groups. A device group is a link between devices and policies. This link can be created either manually or automatically based on certain device properties.

If the device groups function is activated, a link between devices and policies can only be created via this function. Direct linking is no longer possible.

Creating new device groups

To create a new device group, click on Add. Assign a name and (optionally) a description for the group. You can also choose the Type of group. Here the options Static and Dynamic are available.

Static groups

Static groups allow manual linking between devices and policies.

Static groups

After the group is created, devices and policies can be added. Only policies that have been previously published, can be linked.

Static groups

Dynamic groups

In dynamic groups, filters must be defined based on which devices are automatically assigned to the group. This happens in the background in real time. There is no direct manual influence on the content of these groups.

Dynamic groups

The filter specifications AND as well as OR are available for configuring the filters.

Dynamic groups

In the example, a filter has been defined from several properties and filter specifications.

Dynamic groups

The filter integrates the following devices:

  • The linked user must be a member of the Appstore User group.

OR

  • The device name is not TEST.

OR

  • The description does not contain New Device.

AND

  • The user is not Admin Support 2.

Alternatively, you could describe the filter like this:

Groups = _SUPPORT2 Appstore User OR Device name NOT TEST.
OR (description does NOT include new device AND user is not Admin Support 2)

The filter specifications behave like ordinary logical functions.

For example, to avoid accidents, you can also add the serial number of a single device as a fixed filter value to really apply the policy only to that device and check if the result is as expected.