No Matches Found!
Try with a different search term
We are experiencing issues with enrolment failing when trying to use a mobile data connection, devices are all Samsung, using Android Enterprise client.
Enrolment works when connected to ANY WiFi, internal to our network or external, but always fails when connected to mobile data.
Has anyone experience this previously? Servers are running 15.3.3 software and servers are On-Premise, not Cloud.
Is there anything that could cause this behaviour?
How do you enroll? Do you use Zero-Touch or afw# or anything else like a QR-Code?
We had this issue (using Zero-Touch) in the past and had to change/add something in the DPC-Extras but because i don't know how you enroll, i can't say if this would help you (fully managed):
{
"android.app.extra.PROVISIONING_USE_MOBILE_DATA":true, "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE":
{"enrollmentId":"YOUR_ENROLLMENT_ID","PROVISIONING_MODE":"FULLY_MANAGED_DEVICE"}
}
We also noticed sometimes you have to ensure to put the SIM in Slot 1 and that is strange because this shouldn't happen using Zero-Touch and we had this only on few devices and very random (related to manufacturer/model).
Thanks for the advice - will give this a try - I have the same failure when using the Samsung KME zero touch and also the Android Enterprise method of enrolling
Is your On-Premise server publicly accessible from the open internet? It sounds like it might be based on the usage of an external network but I would question that. If you're using an open cellular data connection on the device with no VPN access or proxy to the on premise server then I don't think the device would have external access to it behind your firewalled private network.
Please provide more details:
- Is there any related warning/error message showing on the device screen or web-console/server log files?
- What are the target mode of your devices ( Android Enterprise DO/WP/COPE, etc.?) and the approach you used to do the enrollment?
- Are you using FQDN or public IP address or local IP address for the device-management address parameter (in MCadmin utility) of your on-premises MobiControl server.?
- Is there any special data-plan arrangement (e.g. corporate APN with firewall/access restrictions) with cellular operator?
You likely need to check the traffic logs and firewall rules configured.
In addition to what Rafael said, if you are using Knox Mobile Enrollment (KME), you have to add the following lines in the "Custom JSON" field:
For COBO devices:
{"enrollmentId":"XXXXXXXX","PROVISIONING_MODE":"FULLY_MANAGED_DEVICE"}
For COPE devices:
{"enrollmentId":"XXXXXXXX","PROVISIONING_MODE":"MANAGED_PROFILE"}
This allowed us to enroll our devices over cellular data.