No Matches Found!
Try with a different search term
I have two groups
One has a set of apps assigned through an app policy, the other has no app policy.
I have set up a signal configuration so if a sim is changed in the phone then it moves the phone to the group which has no apps assigned.
When I change the sim on the phone it correctly moves the phones to the other group, but it doesn't remove the apps from the previous app policy.
How do I get it to remove them?
Hi Steve,
I just tested on my side an app policy with only Enterprise applications and an app policy with a mixture of enterprise apps and managed google play applications.
The above tested on Android enterprise, fully managed, agent version 15.3.2.1042
Unassigning the profle didn't remove the applications for me, but in both cases above, moving the device to a group where those policies are not assigned removed all applications automatically.
Is it possible that your app policy is accidentally assigned via inheritence through a parent group?
Hi Adam,
Thanks for you help, but no, there are no App policies on this group at all.
The idea is to stop engineers swapping Sims. So if they do, their apps are removed.
I wonder what I am doing wrong?
Cheers
Steve
I cannot think of a reason why they wouldn't remove. App policies are a bit of a pain (or at least to me they are) because you cannot force apply them like you can revoke/reapply a profile.
If you need this implemented in the short term, while investigating why the applications are not removed. Two (temporary) options that come to mind either:
On the new device group add a lockdown profile (maybe with a background which says stop removing your sim card!!)
Or add a blacklist to the new device group which blacklists all the applications currently in the app policy (though a maintenance burden with this option)
Unlike enterprise app deployed with .pcg package that has well defined option about whether to uninstall the app when the policy is removed, apps from managed google play store has no similar option. The case is further complicated by the new migrated UI and app-policy implemented in recent MobiControl server versions, and possibly some mismatches and/or bugs between MobiControl server and Google app store backend. Hence, this topic deserves further investigation and other discussion threads or articles to cover in more details.
However, regarding your approach of uninstalling apps totally when the SIM card gets changed, I believe there will likely be many complaints from end-users related to application data-loss upon apps uninstallation if they are not aware of the SIM-card change restriction policy. Such data loss is likely unrecoverable after app re-deployment except for the near perfectly designed client-server apps. Also, lots of network bandwidth (even worst for paid traffic) or time will be needed to get the apps re-installed after the intended SIM card is inserted back. Thus, it is much more practical and effective to use application-run-control, lockdown menu, feature control, etc. policies on relocation target device-group to disallow some/all apps from being run when the SIM card change is detected.
.png)
Hi Steve,
Thank you for posting on SOTI Pulse!
Could you please tell if any of the discussion helped you get closer to the solution? If yes, please mark that post as solution and if not, you can create a support case with us to dig deeper into the issue and troubleshoot it.
Kind regards,
Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net l Discussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter