Hi Bryn
Although it might seem counter-productive, your test and specific-usage policies need to be set higher in the Precedence list.
To prove this if you verify your device in the inventory, go into the device and from Summary top-left, go to History, you will probably see that the policy has been set.
Where testing policies are used (presumably for small numbers of devices) these should be at the 'top of the tree'.
After this you should have your specific use-case policies, followed by your group-assigned policies.
If a device is assigned to a group, but you have followed the previous 2 pointers, this should fix it.
Please remember not to set the higher-precedence policies (non-group) to default or you will have a world of pain happen with most devices!
Finally, if you want to be sure this won't have an impact on devices in an unexpected way, you need to make a list of all policies and device groups and document your precedence before you actually execute on it.
Best
------------------------------
Eamonn O'Mahony
Technical Client Success Manager
IBM Security
Dublin, Ireland
------------------------------
Original Message:
Sent: Tue June 15, 2021 01:48 PM
From: Bryn Abbott
Subject: Kiosk mode dropping off
OK so, I'm beginning to think this to do with Policy precedence but it's never been an issue for me before.
In the Groups section I have this handset under Enterprise devices and have applied the new kiosk to it, but MaaS keeps forcing a Dynamic Group Assignment and knocking the device back to the wrong policy.
I'm wary of changing policy precedence because 1) I don't know that much about it and 2) I don't want it to adversely affect the 300 devices already out in the field.
Is there a way to stop this Dynamic Group Assignment?
------------------------------
Bryn Abbott
------------------------------