Hi All,

Just to close the thread.

I made some further tests regarging this and finally I understood how all of this works.

Essentially the device management in google admin console is not necessary when a third party emm is used (mobicontrol in our case).

It's mobicontrol agent which provide all the rules and settings to the device, even if the device management is off in google admin console.

In our case has been enough to set it to Basic management. From that moment on the device policy app is no more required in the device, the only requirement is mobicontrol agent.

I hope this could be useful for others who had the same issue.

Hi Gavin,

Thanks for requesting an answer from SOTI!

Can you please share the version of your MobiControl?

Is this happening on a particular set of the device or all the devices enrolled in MobiControl?

Hi Gavin,

Your description is a bit confusing.  Correct me if I am wrong.   Are you trying to add a "normal" Google account  (rather than a "managed" Google account, using a Google's app on an Android Enterprise device?  If so, please update the title of your discussion to remove the word "Managed".     If your normal unmanaged account-addition process results in failure, especially when your device is in kiosk mode, you should check:

(1)  Your device has at least one feature-control profile payload deployed to the device, and all such feature-control payload(s) should not have the option restricting 'Google account additon" disabled.

(2)   If item (1) is not a problem, and the failure always occurs when your device is in kiosk/lockdown mode (but is OK if kiosk/lockdown is off), then you have to check if any app/service activities have problem running during the process when kiosk/lockdown is active.  If so, you can try whitelisting the corresponding app activities and see if the problem goes away.

Hi,

We are using Mobicontrol Cloud v14.2.2.1170. The problem happens on a range of devices, with different sets of SOTI profiles. What is curious is the issue occurred with no changes to any build configurations.

Hi Raymond,

We are adding Gsuite Google accounts that are managed by our organization (Enterprise managed), this requires that you accept a Google device policy when you add the account to any device.

Hi,

I have the same issue using Samsung S10 smartphones, Android 10.

MobiControl version: 14.4.4.1045

We started to test our new devices in the first days of march, and initially after the enrollment process, when the agent asked to input the google account to configure in the device, the wizard automatically asked to install the Google Device Policy App. Without this app the google account is unable to sync because in gsuite admin console there is Advanced management enabled by default, and need to be enabled because without it is not possible to use some features such as app catalog.

In the last weeks however the wizard stopped to ask to install Google Device policy app, running instead the mobicontrol agent...

The user needs to install device policy app maunally, without this step the account is not working.

Maybe is something changed in google management api in the last weeks?

Hi Mirko,

You can try out the freshly released v14.2.0 device agent, which provides support for Android 10.  I've briefly tested it on some Samsung Android 10 devices which had problems getting enrolled just 2 days ago with an earlier agent, and the enrollment today seemed seamless with this latest device agent.

Hi Raymond,

I tried it, the enrollment is perfect but the google device policy app is still not installed automatically in the registration process of google account.

Hi Mirko,

Is there any problem deploying  any apps other than "Google Device Policy" app to the enrolled device?

I must admit I overlook the fact that the discussion topic is about enrollment with Managed Google Account rather than Managed Google Play  account.   I tested the former a few years ago when Android-Enterprise (formerly called Android-For-Work) was initially released and there was no Managed-Google-Play account option to choose.  The setup was painful and lengthy.   As soon as MGPA was introduced, I did various tests with positive results, and then started promoting AFW/AE to our big customers for production use in Hong Kong.     I have never recommended any of my corporate customers to use the former in any production server.  Hence, I have not  looked deep into the latest developments, or whether the implementaion is much improved now.

BTW, is there any particular reason you chose to use MG account rather than MGP account?

No problem in deploying any application after the enrollment.

The problem is not the deployment, the problem is that in the google account registration process (triggered by mobicontrol agent after the enrollment) a step is missing. This step is essential to let the google account working, it is about the automatic installation and activation of Google Device Policy app, which enable the account to sync all the data.

It seems this step suddenly disappeared from a day to another without touching any configuration.

This scenario is regarding our company, we are google enterprise customers, so our users are managed in google admin console. That's why we need to enroll our new smartphones using Managed Google Accounts.

With our customers I always use Managed Google Play accounts, they're very easy to setup :) but in this case I cannot use them.

Do someone have update on this?

We are still getting this problem when adding Google accounts, something has changed. Mirko, we were able to workaround the problem by running "Google Apps Device Policy" and sync/re-authenticate the account again.