Agent not compatible after Enroll

Agent not compatible after Enroll

Hello everyone!

 

I'm having problems enrolling devices in my MobiControl server, the kind of devices I'm enrolling is:

  • Android Plus.
  • Without Google Account.
  • Models are: Samsung G532M, G532MT, J320M.

 

After they are enrolled to the server, they're agent are not compatible with my actual version of MobiControl, even after I checked the version that has been configured with the device add rule.

How can I fix this?

Matheus Grossi

6 Answers

Order By:   Standard | Newest | Votes
JVMOD@SOTI | posted this 12 February 2020

Hello Matheus Grossi,

 

Thank you for your post, please provide agent version and MobiControl version

 

Regards,

 

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
Ozan Acikalin | posted this 13 February 2020

Hey Matheus,

 

when you are running MC Version 14.2.xxx or higher you are able to update the android agents & plugins.

You can find this feature under "Global Settings" -> "Manage Android Agents and Plugins".

All you need is to find the manufactor "Samsung" and click "Update" and then
"Update Compatibility".

Hope this fix your problem.

  • 0
  • 0
Raymond Chan | posted this 13 February 2020

Your Samsung models are J2 or J3 running Android 5 or Android 6.  You might need to use an not so recent Samsung ELM device agent.    What are the version number, build number and actve MDM API's reported in the conifguration tab of the device agent on your "enrolled" devices?

 

You should also provide the version and build numbers of your MobiControl server.  Not all device agent versions are compatbile with any server binary.   If your server is used to manage  other device brands/models, there might be a need to make tradeoff on either the server or the device agents or the devices to be managed.

   

 

 

  • 0
  • 0
Matheus Grossi | posted this 13 February 2020

Not updated agent version:  14.0.0.1579

Updated agent: 14.1.4.1010

MobiControl version: 14.4.4.1045

 

Matheus Grossi

  • 0
  • 0
Matheus Grossi | posted this 13 February 2020

Hello Ozan!

I tried this, and it did not worked for me.

Even creating a new device add rule with the same configuration as the older one, but with updated agent, I could not fix this problem.

But thanks for the atention anyway!

Matheus Grossi

  • 0
  • 0
JVMOD@SOTI | posted this 13 February 2020

Hello Matheus,

 

Thank you for your response, please raise ticket with Technical Support team

They might have to look into DB and check if everything is fine

 

Thanks and Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback