No Matches Found!
Try with a different search term
Hello Team,
We have an Client Request that if device are not in use they will move them to the Group and it will have lockdown that should show the message as ""The device has been deactivated for security reasons. Please open a support ticket in English by calling the number 23344."
How we can acheive this ?
Hello Rafel,
Thanks for your response, I can put in this way, the application owner restricted to not use those device in the location, if the device went offline but the lockdown remain same, so can i put the the message in side the template that how we use to display the IP address or MAC address on the lockdown screen same way it should display the message in the center of the lockdown screen.
I don't fully understand the scenario but what comes to mind is using a Signal Policy with device side evaluation enabled that changes the value of a Custom Attribute based on an out of contact condition. Then you reference that Custom Attribute as a macro in your Lockdown so that it is displayed to the end user. 
Hello,
There is a feature called "Device Inactivity" since MobiControl version 2025, you can use it for the use-cases of (device online but not in used by anyone for a limited time), please see the screenshots below, otherwise you may prefer device disconnections if you want to monitor and get action when the device offline more than a specific period.
I hope this helps :)
Zafer
Hi Malipatil,
I have delivered solutions to problems similar to yours for my governmental customers in the last ten years. So, what you need is definitely achievable with Soti MobiControl.
The approach mentioned by Matt will not work "seamlessly" in your case because any device-side action (e.g modify custom attribute value) for a signal policy (or alert rule for earlier MobiControl versions) cannot be deployed to the device while it is still OFFLINE as described in your post.
Your mentioned condition of device going off-line (possibly for a specific time threshold) is more in line with device-side OUT-OFCONTACT profile payload policy rather than the DEVICE-INACTIVITY profile payload policy mentioned by Zafer.
In previous solutions for my customers, we had an alert rule/signal policy to relocate device offline exceeding a certain time threshold to a new device group with different policies (e.g. kiosk mode, feature control, etc.) . As said earlier the new policies will not be deployed to the device until the device gets online. Thus, we concurrently deployed a device-side out-of-contact profile policy to the device of interest. The required actions (kiosk/lockdown, feature control, etc.) were all defined in the pre-pushed script to be executed automatically by the device agent when the offline device time threshold has been reached. The actions supported in such OOC script depends VERY MUCH on hardware brand/model, firmware version, MDM-API, enrollment mode, etc. of the device(s) of interest. As my company provides custom-made professional service for such advanced policies design/deployment, I could not reveal too much details here.
.jfif)
Hi D Malipatil,
Thanks for posting on SOTI Pulse, Thanks Rafael, Matt, Zafer and Raymond for responding to the post, your expertise and willingness to help are greatly appreciated!
Have the suggestions provided resolved your query?
If not, or if you have any further questions or concerns, please feel free to reach out. We're here to help and support you.
