Since version 5.19.0, the function of dynamic device groups is available in Relution. This allows you to automatically assign groups already created based on various device properties, and thus equip policies based on those properties.
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.
After clicking on
Start Migration, a message about the upcoming changes will be displayed.
Read it carefully and click on
In the following dialog, you can finally execute the migration.
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
Dynamic are available.
Static groups allow manual linking between devices and policies.
After the group is created, devices and policies can be added. Only policies that have been previously published, can be linked.
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.
The filter specifications
AND as well as
OR are available for configuring the filters.
In the example, a filter has been defined from several properties and filter specifications.
The filter integrates the following devices:
- The linked user must be a member of the
- The device name is not
- The description does not contain
- 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.