Your MobiControl root certificate and deployment server certiicates are length-1024 bit SHA1 certificates in MobiControl v13.4.

This is likely the major cause of your enrollment problem for Android 10 devices.

ok, and what is your suggestions to solved this ?

Hi,

yes what Raymond wrote is a Possibility too.

What i remind is that Android 10 is in an Later MobiControl Version Supported...

It can happen that in your Setting the Restricted Enrolment Activated ?

Or the Server Certificate is not Imprted then you will get the "SSL..." Error during enrollment.

Have you tried to Enroll Zebra Devices With Stage Now? You can set there Wifi and many other Settings ?

They are then set to full work managed Devices ;)

Hi Jean-Francois,

Thank you for posting on SOTI Central.

I agree with Raymond; if you are looking to enroll Android 10 devices you will need to consider upgrading your MobiControl server to support a SHA-2 Root Certificate. This article should give you the information you require in order to proceed: Android 10 SHA-1 Deprecation (soti.net).

Kind regards,

Hi Jean,

Upgrading your MobiControl server seems to be needed.   However, depending on the target version you choose, there might be extra cost  related to upgrading your MS Windows server and/or  MS SQL server  required.  You might also need paid professional services and lot of time if your system currently has many devices of different device platform(s) enrolled.   Making sure all those devices remain under full control after the upgrade is not a trivial task.  There can be many variations possible.

Hello,

Following up on this thread, were you able to use the above suggestions to find a solution? If yes, please share the steps you took and/or mark the relevant comment as 'Solution' to help others find the answer.

Kind regards,

Beyond upgrading the MC server to support A10 I also would recommend against using afw#mobicontrol for enrollment on Zebra Android devices given the number of manual steps involved and also the fact that important system apps like DataWedge could end up disabled post enrollment. StageNow based AEDO enrollment is the recommended approach for Zebra Android devices with SOTI. 

We have the same problem with the certificate. We have support from Soti but this complicates the steps a lot.
Matt, do you suggest preparing a profile with StageNow that will set up enrollment with Soti?
I'm surprising that I have to use other software to configure a device to Soti.

You dont have to use StageNow for Zebra device enrollment in SOTI. You're welcome to try the other default AEDO enrollment methods like DPC Identifier, QR, ZTE, or NFC. You'll find however of all those options, StageNow is the most streamlined and fastest if you're using Zebra devices and SOTI. 

Here is "Zero Touch" Enrollment for example on a Wifi only Zebra device. 14 taps minimum, even more for each letter of the password you have to type. Zero Touch is an absolute misnomer. It usually just means Zero Touch for the IT admin as it just puts the enrollment effort into someone else's hands. 

Here is the StageNow equivalent. I don't know about you but I'd take Scan+Scan over 14+ taps