I believe you are talking about the OEM specific Android+ device agent (v14.0.0) for Voxter Elite+ from TopSystem( Lydia Voice).

For OEM specific Android+ device agent, use enrollment ID or enrollment URL assoicated with your published Add-Devices rule if your device and server both have access to the internet.

If your MobiControl server and devices are both restricted to your closed corporate network, then your server should likely have used a private IP address for the device-management-address, and you can download mcsetup.ini file to the same device directory as your device agent  apk, and install/run the device agent to get it enrolled automatically with the configurations defined in the mcsetup.ini file.

You haven't given sufficient information related to the certificate error you mentioned.  More recent Android device firmware versions do require stronger certiicate(s).  You won't be able to get from a reputable CA a strong SSL certificate bind to the private IP address of your server.  Besides, older MobiControl server versions use weak length-1024 bit certificate.   So, if you still have problem enrolling using mcsetup.ini, you might need to provide more information on your network and certificates.

Hi Raymond,

Many thanks! Yes the hint to copy mcsetup.ini file was actually the solution. Since the server self does not offer the OEM agent, I took just the file from another vendor with the hope they are identically built. It worked. I have got the Agent from Soti Website with no enrolment ID and yes, we are on restricted corporate network.

Best regards

Michal