Hi All,

Thanks for helping me out. 

The issue has been already fixed. What I've tried was I generated a new certificate for deployment and management server from Mobicontrol admin utility. I think the cause is due to changes in Deployment/management server address in MCadmin utility.

So my assumption is everytime you'll change server addresses, you'll need to also generate a new cert.

You failed to include your photo in your post.

Did you get the device on-line to have google play services updated?

Hi Raymond,

On my end, i could see the photo I attached. Yes the mobile phone do have connection to public internet.

I can see your photos now.

What are the version and build numbers of your MobiControl server and device agent?

What is the brand/model of your device? And the Android firmware version and build numbers?

Have you created your managed google play account on Google's portal via MobiControl web-console?  If so, was the created Enterprise associated with your Add-Devices rule?

I've seen this before. In my case, this happens until the device updates google play services, which is automatic if there is connectivity. This could take some minutes.

Please make sure the device has connectivity to Google Play.

Hi Raymond,


Yes, i already did android binding via MC platform. And it 's associated with the rule I created


Kindly see requested details:
MC version: 14.1.4.1693
Agent version: 13.5.6.1577
Manufacturer: OPPO
Model: A37fw
OS Version: 5.1.1


Hi Edgar,

I have checked playstore app and checked google play services, all services from google were updated. Still pending.

Have you tired and succeeded in enrolling device of other brand/model on the same server?

I haven't encountered Oppo device in the past, and the Android version (5.1.1) is a bit old, considering the continuous changes in Android Enterprise platform in the last 6-12 months.  If I were you, I would first test with the bigger brand(s)  to confirm that you server, MGPA account and MDM policies are properly set up.    

Hi Benedict,

From a previous case, I have had a customer re-bind/create a new Android Enterprise binding and it worked for them.

You can do this by going to your Android Enterprise Bindings from Global Settings, click on the wrench icon and Delete your current binding. You will need to remove the binding from any associated Add Device rules beforehand.

To add it again, you need to log in with your account to https://play.google.com/work
Go to Admin Settings. Under Organization information, click the 3 dots and select Delete Organization.

This will allow you to go back and create a binding again in Android Enterprise Bindings using the same account.

However, I would also suggest you try Raymond's recommendation above to confirm if your current Android Enterprise Binding is working or not first - if it is working before and you have configurations already then you may lose your existing settings if you delete the binding. 

As he had stated, Oppo is not as common as other brands and documentation on Android 5.1.1 is scarce.
For instance, here is a response from Google Support that states that Android Enterprise is supported on Android 5.0+ but it also states "that have work profile support" so it is not clear if all devices have support:

https://support.google.com/work/android/answer/6174145?hl=en

The device catalog also only state devices that are Android 6.0 and above:

https://www.android.com/enterprise/device-catalog/

And the currently recommended "minimum" version of Android for use is 7.0:

https://www.android.com/intl/en_ca/enterprise/recommended/requirements/

As stated in the second link, support may also differ from carrier to carrier and country to country so contacting the OEM for certification information is the best option.

There's a chance that this may also be network-related since one case had the customer notice that certain Google activity were blocked but there isn't any additional details so that may or may not be related.

Regards,

~G

I am having this issue with multiple customers running everything from v13.4.x to v14.2.x and no solution appears to work all the time. I think this needs to be investigated further by SOTI as asking a customer to delete something and then recreate it is not a valid answer... What happens to devices already deployed with that MGPA if you delete the binding? What happens to add device rules that contain that MGPA? I can tell you my customers would not accept this as an answer.

I agree with Fisch, the cause of the problem has to be found to offer a proper solution. We faced the same issue with Android 8. Connectivity with Google Play is OK, certificates are properly configured and we can see how Google Play Libraries get updated in the devices. In our case the solution is restarting the agent so it seems a bug in the agent.

Hi Fisch and Victor, 

We always appreciate the feedback regarding burning issues affecting our customers but this thread dates back to June of 2018 which is some time ago. The responses and solutions posted here may no longer be applicable since the implementations of Google's Android OS, Google Play and MobiControl may have experienced considerable changes over time.

What appears to be the same errors on the console may be actually be a different issue altogether once we investigate the logs. It is always advised for users to open new support cases to confirm if the issue stems from the same cause. It may also be helpful to start a new discussion here and post the relevant portions of logs so that we may look at them at a glance and compare them with the experiences of others. Please also be mindful because there may be some revealing information about the server and your devices if you choose the latter option

Since this thread had been marked with a "Solution" and because the solution was relevant to original poster, this thread will be considered closed.

Thank you again for your sharing your experiences and hope that you will follow up with support and/or on a separate thread.

Regards,
~G