No Matches Found!
Try with a different search term
Hi all,
I am trying to enroll my samsung device but I run into some issues.
From factory reset the device is setup with the afw#mobicontrol hashtag.
When trying to enroll the device with an enrollment ID I get the error "Provisioning failed. Please contact your administrator".
I read something about the use of Knox Mobile Enrollment, but is this mandatory?
Thank you!
Kind regards,
Is there any other devices of different brand/model/Android version already enrolled as Android-Enterprise on your MobiControl server?
First narrow down if the problem is specific ONLY to your current device model (Galaxy Tab S6Lite) or if it applies to many/all other devices too. For the latter case, the cause can be related to your MobiControl server, network/firewall, your device enrollment policy, etc.
Hi Raymond,
Thank you for your response.
This is the first time I'm trying to enroll a samsung device.
We do have about 1000 other devices enrolled, these are TC70/72, enrolled as android classic and enterprise devices.
TC70 are on android 5, TC72 are on android 8. The samsung device is on android 12.
We enroll our devices from a wired network in the same subnet as the server so it does not pass a firewall.
I tried enrolling a samsung tab A8 but this gives the same error.
Any thoughts?
Thanks!
.png)
Hi Hubo,
I hope this finds you well, thank you for contacting SOTI Pulse.
Have you had a chance to try the QR Code enrollment or the latest agent to see if you could reproduce this issue using those methods?
Have a great weekend.
Regards,
Technical Support | SOTI Inc. |1.905.624.9828 | Log a Case Webform | SOTI.net | Facebook | LinkedIn | Twitter
See you in Munich.
We have had the same issue enrolling Samsung devices using afw#mobicontrol.
There is something wrong with the new agent (updated 8 Mar 2023) in the playstore.
Support gave us a QR code so that we can download an older agent during the enrolment process. The issue was forwarded to their dev team but waiting for the play store agent to be fixed before we can return to the normal enrollment process.
There is a new client (15.3.4.113) in the play store. It looks like it has fixed the enrolment issues introduced in the previous client.