Out of Contact Policy is not applying to device

Out of Contact Policy is not applying to device

For some reason, when configuring a Out of Contact policy in my Package Configuration, it won't install to the device.

 

 

See image. This is on SOTI server 14.4.1.1195, agent version 14.3.0.1000, Android 8.1. I've tried revoking the profile and re-installing it, rebooting, factory resetting and re-enrolling, etc. Any ideas? Thanks!

 

  • 21 July 2020
  • SOTI MobiControl
  • 6 Answers
  • 0 Upvote
  • 2 Followers
  • 1.4K Views
    • 6 Answers
    • 0 Upvote
    • 2 Followers

6 Answers

Order By:   Standard | Newest | Votes
DDMOD@SOTI | posted this 21 July 2020

Hi Ian Stuart,

 

Thanks for the post!

Do you mind sharing what actions/scripts have you included in the Out of Contact profile, as the error message says 'Failed to download script files'? This usually happens if the script file name has changed or may not have been applied.

 

Regards,

Technical Support | SOTI Inc. |+1-888-494-SOTI (7684) | support@soti.net | www.soti.net |

  • 0
  • 0
Ian Stuart | posted this 21 July 2020

Hello,

 

Here are the 2 scripts I have in the payload.

 

 

Thanks!

  • 0
  • 0
DDMOD@SOTI | posted this 21 July 2020

Hi Ian,

 

Can you please send the first script 'Show message lost" only to the device and confirm its working?

If it is successfully pushed to the device, then try the same with the second script "Lock/Turn on Kiosk". This will help us to identify which script is actually throwing an error.

Please share the outcome.

 

Regards,

Technical Support | SOTI Inc. |+1-888-494-SOTI (7684) | support@soti.net | www.soti.net |

  • 0
  • 0
Ian Stuart | posted this 22 July 2020

Hello,

 

So I did test both scripts and they both worked as intended, but I removed my "Lock Kiosk" script from the Out of Contact policy and now the profile is showing fully installed. I am not sure why the Lock Kiosk script is not working, but I can probably figure out a work around. Thanks for the help!

  • 1
  • 0
Matt Dermody | posted this 22 July 2020

It looks like you may have configured them for the exact same time frame based on them both saying 168 hours. There is perhaps a conflict in having multiple scripts with the same timer value. You could just put all of the scripting together into one script if your plan is to have it launch at the same time anyway? There really isn't a need to have two different scripts if you are running them together. 

  • 0
  • 0
Ian Stuart | posted this 22 July 2020

Good point, I will try combining them. Thanks for the idea!

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback