No Matches Found!
Try with a different search term
After scanning the enrollment QR code I get a message (User action pending) after clicking on the notyification I see Google Play account/account creation failed - trying again. It continues to fail. FYI, this is a QR code that I have used successfully on several of the same type of devices. I have not made any changes.
Hi,
Thank you for posting on SOTI Pulse.
This usually means the device side network needs to have port 443 allowed outbound or specific Google FQDN’s, which can be found here: https://support.google.com/work/android/answer/10513641?hl=en.
If the issue persists, there might be a problem on the MobiControl side, and I would recommend you raise a ticket via https://soti.net/services/log-a-case/.
We would likely ask to see the Management Service logs and a debug report from the affected device to help diagnose the issue.
Regards,
Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net
You also could send a reset account command to the devices issuing using the devices drop down menu for that but this is just to get it maybe solved once to those devices not for future ones.
You haven't provided sufficient details (e.g. previous status of your device or server, or what is displayed on the device screen or web-console device view & server log files), so there can be many possible causes of your problem:
If your corporate firewall has recently been configured or replaced, it is possible that there are some missing firewall exceptions as mentioned in previous post by JCMOD.
If important parameter(s) (especially some of those configured in MCAdmin utility) of your Mobicontrol server has recently been modified, it is possible that ALL existing device enrolllment rule will fail. This is easy to check. If this is really the case, a new enrollment rule may need to be created for successful enrollment.
If your problematic device have previously been enrolled in the same server and not deleted, there can be problem in the enrollment due to some configuration conflict(s) {e.g. enterprise binding, mode, etc.] , and the warning/error message may sometimes be misleading. This can be avoided easily by making sure that the device has been deleted before trying re-enrollment.