HOW TO IDENTIFY WHICH PLUGIN IS INSTALLED WHEN REQUEST TO INSTALL DEVICE PLUGIN
I guessed it was onde of Zebra 220.127.116.11 apk, by verifying the remote control version that matches its release.
Then I have created a package with the apk as marked to run after install, but it fails the installation.
Not sure it it is due the wrong apk or due the package creation that should include any special scripts for install plugin.
The plugins are already hosted on SOTI's website in PCG form. You do not have to create the package yourself from the APK.
Thank you for your post, please follow steps mentioned below -
To install an Android Enterprise plugin on your Android Enterprise device:
- In your browser, go to the SOTI MobiControl Device Agent Downloads page.
- Select Android Enterprise Agent and Plugins and then select the appropriate manufacturer for your device from the Manufacturer dropdown list.
- Select Download to download a SOTI MobiControl package file (.pcg) to your computer.
- Upload the .pcg file to your SOTI MobiControl instance.
- Distribute the Android Enterprise plugin package to your Android Enterprise devices using a profile.
Let me know if that works for you.
Technical Support | SOTI Inc. |1.905.624.9828 | firstname.lastname@example.org | www.soti.net |
Is this not what is supossed to happen "automatically" as part of the enrollment process if you tick the "Device plugin setup" - "Deploy latest plugin to enrolled device. Device plugin will be installed on your MobiControl instance before it’s deployed to the device. This will trigger a device agent restart after device enrollment."
under the "Device setup" tab for the enrollment rule?
We have the same problem where we have to do this manually, after enrollment, even though we have the above option enabled.
I could see a interesting behavior on this.
If the "add device rules" is properly set to a valid Google account, it will work as mentioned. If not, the device will have no google account assigned on it. Due this no account assigned, the plugin will be considered as from unknown source and be blocked.
I believe that in MC15 it will flow automatically if the "add rule" is valid and installation being performed by afw#mobicontrol.
If not, you should create a dedicated "add device rule" where you should set a path which has assigned only the profile with the pluggin.
After being updated you move to other group to receive all other profiles.
The automatic install has never reliably worked so we just install the package anyway.
That was also my hope, but unfortunately, even though the devices are enrolled with a valid Google Account it still does not work automatically, even though the server has the newest Plugin available so the 1:1 match between agenst version and plugin version should not be a problem - everything is also fine when we manually click the "Install plugin" button, which is why a script to trigger this would be so useful!. We do not want the extra work of having additional profiles to simply deploy the plugin as MobiControl already has this built-in, just not quite working.