Deferred Profile assignment?

Deferred Profile assignment?

I have a question and a suggestion for the Soti "feature request" folks.

Is anyone trying to manage apk updates that will not conflict with a running app?  If so, how are you doing it?  We have a couple of applications that it is paramount that we not update if the app is running.  The normal android app store knows how to do this, ie, not update an apk if it is being used.  Our devices are all COSU and are kiosk locked so there is no "self serve" option. 

The profile model is maddening.  It has TONS of options to cover the "IF" a profile should apply but precious few to cover the "WHEN" it should be applied.  It has Network Connectivity, specific time, and battery level.  I need to be able to check if a specific app is running and if so, defer the assignment until the next check-in.  I could even work with "charging/not charging" as a proxy for app use but that isn't an option either.  Coupled with the fact that the Android script engine has no conditional processing I am unable to figure out a way to meet this very reasonable customer demand.  At this point it appears we will have to erect a secondary server infrastructure and a device side agent to call the MC API to assign profiles on demand, which is exasperating since that is basically what we purchases MobiControl to do.

Anyone see something obvious I'm missing?

5 Answers

Order By:   Standard | Newest | Votes
Matt Dermody | posted this 26 September 2018

I have the exact same request and a couple of additional suggestions, check out my post here:

https://discussions.soti.net/thread/install-android-apk-when-previous-version-not-in-use/

 

 

  • 0
  • 0
Matt Dermody | posted this 26 September 2018

Actually, it looks like you may have already found it!

  • 0
  • 0
Scott | posted this 28 September 2018

Yeah, just thought I would send up one more flare in case anyone had come up with something recently...
Thanks

  • 0
  • 0
Matt Dermody | posted this 25 October 2018

Check out the possibility of a deferred APK update via a install script set to launch at startup:

 

https://discussions.soti.net/thread/copy-apk-in-mcstudio/

 

  • 0
  • 0
Scott | posted this 25 October 2018

That would potentially work for install on boot, we just need more than that.  I have been using that method to install apps already using mx to get around the permissions issue.  I do a copy/rename then call mx to install the app.

Since a device can't be in more than one group and you can't apply profiles to virtual groups...

Currently, we are creating a custom attribute for each application. The profiles have a filter criteria to match a version string in the custom attribute.  We create and maintain device lists, device groups and custom attributes in an external database. We have to build version logic in to our applications that on logoff, the version is checked and if not current, triggers a back-end process to use the REST API to update the custom attribute for the device and then trigger a check-in, which then causes the previous profile to be removed and the new profile to be assigned at that point.

A PITA to be sure but currently the only workable mechanism available to us.

 

  • 1
  • 0

Give us your feedback
Give us your feedback
Feedback