SOTI Pulse Logo

Android Everything pending Install

Solved
LC
Leon Callsen
Taneri Consulting GmbH (TCG Global)

Hi Everyone, 

I have several customers with fresh new On-Premise installation which are unable to use MobiControl properly. 
Everyone of them is on 2024.1.0
It doesn't matter if it's Android Enterprise or Android Classic. 
Every device stucks on the profile installation "Pending Install" 
Older devices do not react to an Agent Update. 

With one customer I have the issue like a month ago already. 
Support told me that a new MobiControl Agent release would fix this but it didn't.
Another customer has this issue since yesterday. 
The day before everything was working fine and they didn't changed anything on the system environment. 

Is somebody here which is expieriencing the same behaviour on their environment? 
I don't have this issue in my cloud instances. 

Pending Install Profile Installation android
a year ago
SOTI MobiControl
ANSWERS
RS
Rafael Schäfer
a year ago

We have currently a case running as some profiles stay randomly at pending state.

Often we can solve that by following procedure:
1. revoke the pending profile (on the device details -> configuration view!)
2. Checkin
3. wait for the red dot to appear and press it to refresh the data displayed in the console
4. assign the profile again
5. Checkin
6. wait for the red dot to appear and press it to refresh the data displayed in the console

The profile is then nearly always installed successcully.

But we are still on 15.6.5 but with latest agent (waiting for 2024.1.1 release) and as only some profiles affected randomly not sure if it'S the same issue. I recommend to open a case.

LC
Leon Callsen
a year ago

Hi Rafael, 

in the beginning we thought that this issue only belongs to Android 13 an Zebra. 
We found out that it doesn't matter which device or OS it is. We even tried different Agent Versions. 
I am not even able to revoke a profile. That don't work either. 
The only thing which works sometimes is to reset the agent with "restartagent" and do a soft reset with "reset /s" afterwards.
Sometimes the devices receives their configuration like 2 days later but most of the time nothing happens. 

I am really waiting for 2024.1.1 and hope that this issue is gonna be fixed then. 
Unfortunately I don't know what I can do in the meantime to help the customers.

RS
Rafael Schäfer
a year ago

As said in your case it very sounds like a different issue which highly recommend to get a case on Soti so they take a look into it.

LC
Leon Callsen
a year ago

As I already mentioned in my initial post. 
Both issues are already adressed to the support but they don't know what to do either. 
There is already a development ticket created but I need any kind of workaround to fix the issue with the customers. 

Thanks for your time! 

A
AGMOD@soti
a year ago

Hi Leon Callsen

Thank you for posting on SOTI Pulse. Thanks Rafael for responding to the post!

Has the suggestion or input from Rafael successfully addressed your query?

Since you had mentioned that a development is created for your concern with the assistance from Support team, please let us know if you have any additional questions or concerns to share.

Or if the matter has been resolved, and if any of the posts from Rafael has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others can also benefit from this information.

We're dedicated to providing assistance and support.

Technical Support, SOTI | Call Us | SOTI.net | Discussion Forum | Log a Case Online

LC
Leon Callsen
a year ago

Hi Support Team, 

the issue got fixed by your support. 
Which is interally mentioned under MCMR-37388
This is an exchange of a file on the environment. 
Afterwards everthing is working as expected. 

Your team mentioned that an upgrade to 2024.1.1 is not recommended due to several issues.

Solution

Similar Discussions