Enrollment: Google Play account creation failed

Hi all, Since a while we encounter problems when enrolling devices.

For some reason, when enrolling a device, the MobiControl agent reports: Google Play account: Account activation failed.

So i've already found similar cases (Empty token), they mention to remove the current Enterprise google play binding.
But this is being used in so many rules and profiles => Is there another workaround?

Issue encountred with CAT S41/42 (Android 8/11) - Datalogic MEMOR10 (Android 8.1) - Galaxy A52 G5 (Android 11)

Mobicontrol version: 15.4.2.1020

3 years ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
3 years ago

Have you confirmed that your other devices previously enrolled with the old Google Enterprise account are still under full control (e..g.  deployment/removal of app from Managed Google Play store)?

Is it possible to create a new Google Enterprise account binding on your MobiControl server?  If so, have you successfully enrol any new device onto your server with this new binding?

OA
Ozan Acikalin
3 years ago

There was once a bug when you change the registration code of mobicontrol you lose the enterprise bind. There was the solution to remove the enterprise account and to add it again.

Like Raymond already asked.. are your other devices still working?

Have you bind more than one enterprise account to mobicontrol? If yes, then maybe you
are enrolling devices by using a rule with the old (not active) enterprise account.

You can check the enterprise account on the google play site if it's still connected to your
mobicontrol server. You can check that under play.google.com/work in the settings.

Can you still create app policies with your enterprise account?

K
KAS001
3 years ago

Issue was a closed network port to activate the profile. We where externally connected. Once connected on-prem, the issue disappeared.

D
DJMOD@SOTI
3 years ago

Hi KAS001,

Thanks for requesting a response from SOTI Support Staff, Thank you Raymond and Ozan for providing some insights of your experience. 
As KAS001 suggested, it was network issue. Could you please change the status of this case to resolved, It may help some users in the future facing similar issue.

M
mdm001
3 years ago

I am having the same issue. May I ask which port you had to open to get this to work?

Incoming Open ports are as follows:

    TCP 5494, 2195 (Apple), 2196 (Apple), 6443 (SSL)

Outgoing:

    No Restrictions

Thanks.