i am trying to enroll new galaxy tab 2 device and when i get to the google email i enter afw#sophos as instructed but nothing sophos related installs and I end up at the desktop with no enrollment completed.
i cannot click on anything in the play store and it just says Android Enterprise. I have tried on a few different devices all with the same outcome.
can anyone offer any advice?
regards
Lee
We are experiencing the same issue today. When trying to enroll a device, we enter the "afw#sophos" and then it proceeds through the rest of the setup steps without any mention of Sophos, IT managing the device, etc.. Once we get to the home screen of the device after initial setup, Sophos is not installed. When we try to open the play store, we get an authentication error stating that we need to sign back into the google account. When we click the button to "try again" it basically does nothing. Just keeps looping us back to the same screen. Since Sophos is not getting installed, the device is not enrolled, and has no policies or restrictions yet. There is not much we can influence on our side. We have tried on 4 different devices (3 older tablets, and 1 brand new phone). All are acting exactly the same. We have also tried on 3 different networks (1 with our firewall, 2 without any restrictions/security) and all act the same.
Thanks for the response. I am attempting to do the same. I usually dread contacting Sophos Support, as I've not had the best experiences with them in the past. I am hoping they can get us some help this time. I will keep you posted as well if we find a resolution on our side.
i managed to get it done albeit very long exercise using QR code enrollment.
You must configure the settings that are required to create the QR code and to enroll the device.
Prerequisite:
You’ve created a task bundle for QR code enrollment. The task bundle must have an Assign policy task for an Android Enterprise device policy and must not have an Enroll task.
To set up QR code enrollment:
Devices will automatically connect to the Wi-Fi network if it’s available.
The QR code is displayed on the QR code enrollment tab. You can print it out to use it without access to Sophos Mobile Admin.
then
To enroll an Android Enterprise fully managed device with a QR code, you scan the QR code during the initial device setup.
Prerequisites:
To enroll a device:
This opens a QR code reader.
On some devices, you must connect to a Wi-Fi network so that Android can download the QR code reader.
The device enrolls with Sophos Mobile as an Android Enterprise fully managed device.
Depending on the device, the setup procedure might be shorter compared to a manual setup. For example, vendor-specific configuration steps might be skipped.
Same problem here. Enrolling using AFW#Sophos is not working at the moment. (for a couple of days)
When entering the AFW#Sophos and pressing next, an Enterprise account is made, but not SOPHOS Enterprise. This making the phone unable to use the QR code.
I am "ok" right now.. i have 40 phones ready to scan the QR. But i cannot make new ones and we are expecting a rush in new employees soon.
Thanks for the help.
I tried using this method and it seemed to almost work for me. But it was needing a Sophos Central account with the user role to sign in with on the phone during enrollment process (as stated in pre-requisites). I could not figure out which account to use that would make it work. I also found a couple of other items did not match how we want things set up. So this method won't work for us unfortunately.
I spoke with Sophos and they created a ticket. Then the engineer never called back. But instead they emailed me super late in the day and asked for irrelevant info and other questions that I had already provided the answer to. I suppose I will just wait a couple more days and see if this is resolved. Worst case scenario, we are considering switching MDM's soon anyway.
For anyone else that may be reading this, here is the Sophos Knowledge Base article that most closely matches the issue. I am not getting the error message that it states in the article. But the issue seems to likely be caused by the same root.
