What platform(s) of devices are you dealing with?

What are the version and build numbers of your MobiControl  server? 

Did you find problem with an old add-devices rule that was functional previously?  Have you tried using a new add-devices rule instead?

We're actually dealing with Android+ and Android Enterprise, but we want to work also with Windows Mobile and iOS devices.

Our server is in version 14.2.0.2894

I tried old and new rules. The device seems to reach the server, shows the certificate (our wild certificate, not the Mobicontrol one) but even if you accept it, fails to enroll.

Hi Samuel,

As long as your wildcard certificate cover the sub-domain you've been using (before and after the certificate change) for your MobiControl server,  there shouldn't be any problem.  This of course assumes that you install everything properly.

Have you run MCadmin.exe to import the new root certificate for your SSL certificate, and update the binding to your new SSL certificate to the relevant services?  If so, did you also run the tests within MCadmin.exe after the binding task?

I imported the signer as Root Certificate, it seems fine, but when i try to import the Wildcard to the Deployment Server, fails with the next error:

So, it seems that you haven't installed things properly.

I'm not sure what you have done from your screenshot.  There can be many possible reason(s) for import problems.  E.g. you might be missing intermediate certificate (between the DigiCert Root CA and your wildcard SSL certificate in the cert. hierarchy) on your system, or the SSL certificate you tried to import does not have private key embedded.

It may not be convenient to go into details on your particular implementation in this open forum.   If you still have problem, I suggest you to open an official support case with Soti support team.

Hello Samuel, 

I would suggest you get in touch with Soti Support and we can take a closer look at this if this is still noticed.