No Matches Found!
Try with a different search term
Hello everyone!
We’re looking for advice on the best method to update the Soti MobiControl agent and plugin on Android Classic devices.
Ideally, the update process should allow segmentation (by version), for examle:
And be fully automated.
Any guidance or best practices would be greatly appreciated!
Regards.
Assuming the general case that devices having the same old version are in different device groups, then using automatic filter (and/or manual addition for minor tuning) to create three virtual device groups (corresponding to n-3, n-2, n-1 version) may be a systematic approach to consider. Then, use a file-sync policy assigned for these 3 virtual device groups to get the new Android classic device agent/plug-in file(s) deployed to a specific target device directory. There should be a file-sync policy post-script to get the deployed file(s) installed and the device agent restarted with the "install" and "restartagent" legacy script command respectively.
Please verify the flow by first having a handful of test devices of representative device brand/model manually added to the virtual device group(s). After successful verification, automatic filter expression(s) that automatically adding device of the right current n-# version and/or device brand/model can be used for the virtual device groups.
Just to mention here, file sync rule works fine but you can do this also via a package or enterprise app policy.
Positive for file sync: You have the files just somewhere stored and can just exchange the files (naming must be the same ofc) and the filesync will just do the rest. But you must use a post-script to install the apk/update and if needed you can run a pre-script as well.
Positive for package is, you can just upload the apk and have always the version control still visible and freely to choose. So you can choose in the profile which version you want to deploy (so, one "package" in this case: the apk with several versions freely to choose on). You can also use pre- and post-scripts if needed.
Positive for enterprise app policy: You have all apps on one place. You can just switch between app versions in the app policy (requires 2026.x.x or higher). You can also use pre- and post-scripts if needed (requires 2026.x.x or higher).
On 2025 and older the enterprise app policy is not that smooth but as you don't use managed app config on these 2 apps mentioned by you, you would just edit the app policy, removing the old app version, adding the new one and assign it, so not as smooth as the previous ones but still ok.
Hi Rafael,
I understood that App Policy was not designed to deploy applications unattended on Android Classic devices. Instead, we have to use Package + Profile (losing the functionality of AppConfig).
Do you mean that in MobiControl 2026.x.x we will already be able to use App Policy (and AppConfig) to deploy apps on Android Classic devices?
Regards.
Ouh damn, i may have left out the Android Classic part in mentioning the enterprise app policy.
I can only tell that i can choose Enterprise apps when creating an app policy for Android Classic on 2026.0.0 or 2025.0.3 but as we don't use classic, i can't check finally but maybe worth for you asking your contact at Soti about it.
In my understanding (just my opinion, don't meant to be the case) Android Classic is supposed to be obsolete at some point and only Android Enterprise will remain, so not sure if they put development on that part still.
Dear Enric,
Thank you for posting on SOTI Pulse
Thanks Raymond and Rafael for responding to the post, your expertise and willingness to help are greatly appreciated!
Please find the Features and product notes for our 2026 version
https://pulse.soti.net/support/soti-mobicontrol/product-notes/release-notes/
This update introduces a modernized interface for managing Windows Classic enrollment policies directly within the main SOTI MobiControl console. Administrators can now create, edit, and manage these policies without switching to the legacy console, ensuring a consistent and streamlined experience. This enhancement boosts productivity, reduces errors, and simplifies onboarding by centralizing all enrollment workflows.
If you have any additional questions or concerns, please don't hesitate to reach out or you can contact us at support@soti.net
We're dedicated to providing assistance and support
Kind regards,
SOTI
Windows classic wasn't mentioned in his request, he was talking about Android Classic. This post looks very confusing related to this topic.
