I have some profiles that are stuck in a Pending Install status no matter what I do.

Hello,

We are currently on Mobi version 15.4.2.1020. We use Android tablets and utilize package studio to deploy some APK's that we cannot distribute via the Google Play store. We deploy the same profile to 3,000+ devices. All devices are either a Tab Active2 or Tab Active3. Roughly 60% of the tablets we deploy to will take the update almost immediately and install properly. The other 40% are stuck in a "Pending Install" state. A lot of these are like that because we have been updating via assigning a new profile with the updated apk, then removing the old profile that housed the previous version. Sometimes, when the older profile removes itself from the tablet, it leaves behind the older app version. We used to be able to just manually remove the old apk from the tablet and repush the new profile installation. For whatever reason, now when we perform the above steps, the new profile will not install and stays in a Pending status. I have tried:

Unassigning the new profile completely, check - in right after, and then reassigning the new profile to the tablet. I will wait 10 minutes or so and then perform another check in. It just won't download no matter what I try. Our DS queue is sitting at 0 so it's not bogged down. Does anyone have any ideas of where I could look? Any idea why the same tablet models accepting the exact same profile would only be successful on 60% of our tablets? 

2 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
2 years ago

Having the same hardware does not guarantee same behaviour.

Are the problematic devices running both the same firmware version (same build number of the same release date) and the same Soti device agent version as those that worked fine?

Also, are they in the same device group with exactly the same SET of MDM policies (e.g. without using special filter/filters to smartly deploy profile to only some devices in the same group)?

RS
Rafael Schäfer
2 years ago

My personal experience says: If you deploy an apk via profile/package use the same to update it otherwise you have a big risk of what you exactly had.

So, why using 2 different profiles?

(And only an optional hint: If you deploy the apk only (no use of any scripting, additional files etc.), you can just upload the pure apk file in the packages section without using the package studio.)

M
MPMOD@SOTI
2 years ago

Hi Eric,

Thank you for posting on SOTI Pulse! 

Are you still having issues with pushing packages to your devices? As Raymond has mentioned, even if the device models are the same, is the firmware also identical? We need to ensure if there are any differences with the working and non working devices. 

As a test have you possibly tried creating a profile with just the package and tried pushing it on the device to see if the configuration will go through?

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net lDiscussion Forum | Log a Case OnlineLinkedIn