Compliance Policies

Solved
JK
Jason Klotz
Mediacom Communications Corporation

Morning - I am running V15.5 now and in preps of M365 being fully rolled out I am working on compliance policies that would restrict access to M365 if a device goes non-compliant. Now What I am trying to figure out is how to get the server to run the policy. And the reason I want the server to do it is because if you set the policy to say a device is offline for 2 days or hasnt checked in in 2 days we would want that device to go non compliant and access is then cut off.

Is anyone else running into this or did I miss some easy setting?

3 years ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
3 years ago

If you want devices that have not been on-line or checked in with your MobiControl server for a period (say 2 days), then you can simply use a smart combination of the following:

1. a profile with  out-of-contact payload.  You can associate a script to enable a virtually empty kiosk defined with a previously pushed kiosk profile in which kiosk is turned off every time the device get checked in with your Mobicontrol server.

2. an alert rule with  out-of-contact device event selected as trigger.  The action associated can involve relocating the device to a new device-group (e.g.  a child node, which should by default inherit all existing profile/rule/advanced-configuration policies, unless explicitly added/removed.  If you want to deny access to such out-of-contact device, you may for example add/modify a profile to have a virtually empty kiosk mode and very tight feature-control/restrictions payload options configured.

Solution
K
KCMOD@SOTI
3 years ago

Hello Jason,

Thank you for posting on SOTI Central!

Please kindly let us know if Raymond's advise answered your question?

Regards,
Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net