You could do wollowing (but maybe there's an easier way):

Just create a filter group matching your 30 days offline filtering, then the devices can stay in their current folders with their profiles.

If you still ned to relocate them, you can assign a profile creating an  ini or xml filter processed by mobicontrol agent as custom data. Based on the custom data you can then relocate the devices by a relocation rule.

Hi,
Depending on your MobiControl version you can use Alert Rule or Signal Policy for this. If you are on more recent version Signal Policy is recommended as Alert Rules is deprecated.

For Signal Policy:
Create policy for "Managed Device" and condition "Device disconnection time duration" and value for how many days.
Then Action "Relocate Device"

For Alert Rule:
Create rule for "Device Event" and event name "Device has not been connected for N (minutes) (Minimum 60)" and add value for how many days.
And then "Relocate Device(s) to" action.

Devices will not be relocated immediately upon rule/policy creation according to my experience but, then when devices reaches this conditions device will be relocated.

Katie,

The Alert Rule/Signal Policy mentioned in Robert's post are the simplest policies for automating what you do manually to relocate devices.

However, the following should be noted:

1. The relocation action in alert/signal policies are scheduled internally in hour interval though the out-of-contact time are configured in minutes. 

2. Even though the device icon has been automatically relocated when the alert/signal rule gets triggered, the new policies for the target device group are all pending installation and the old policies for the old device group are pending uninstallation until the moment when the device actually get connected again to the server.   If both device folders have the same set of policies, then relocating just help you see the list of allegedly "missing" devices easier when viewing the group holding the relocated devices.

However, If some actions actually need to be taken on the device while it is still disconnected (i.e. out-of-contact) with the MobiControl server,  some device platforms support device-side out-of-contact profile payload in which pre-pushed script(s) with required actions (e.g. warniing message, encryption/clean-up of sensitive filles, ARC/kiosk, wipe, ...  etc.) will be executed when corresponding out-of-contact timeout is reached.

If you just want to automatically group those "OOC" device together in a group for easy viewing without having any policy changes, then just add a new "OOC" child group under the current device group (all policies of the child group remain the same due to inheritance) and add an alert rule with the OOC (i.e. "Device has not been connected for N (minutes) (Minimum 60)")  device event trigger and relocation action to the new child group.  This policy has been around for over 10 years and is available for all versions before v2024.

Device-side out-of-contact policy (configuration for Mobicontrol v11- and profile payload for v12+) has also been around for over 10 years.  Details can be found in all versions of MobiControl on-line manuals, e.g.
https://www.soti.net/mc/help/v15.6/en/console/reference/dialogs/profiles/common/profile_outofcontact_eventconfiguration_common.html

Thanks Rafael, Robert and Raymond for responding to the post, your expertise and willingness to help are greatly appreciated!

Have you had an opportunity to test the suggested solutions by Rafael, Robert and Raymond, and has it successfully addressed your query?

If not, or If you have any additional questions or concerns, please don't hesitate to reach out. We're dedicated to providing assistance and support.
 
Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net |www.soti.net
|