Hi Rafael,

Thank you for posting in SOTI Central.

The initial pictures you've referenced is the Android Agent Delivery Service, this function ultimately serves to efficiently manage your Android Classic agents, which is also known as OEM Specific. Now regarding Android Enterprise, the best practice is to upgrade your agents via a Managed App Catalog.

This firstly requires an Android Enterprise Binding and your device will need to have the binding selected within the Add Device Rule on enrollment. Or alternatively use the "Reset Account" function introduced in MobiControl v15.1 to dynamically assign the enterprise binding to the existing devices.

The Android Enterprise agent found within the "Manage Android Agents & Plugins" is similar to a placeholder and does not serve the function you believe it does. Ultimately upgrade your AE agents via the Managed App Catalog.

If you would like to understand the process further or have any questions, feel free to reach out.

Reference:

https://www.soti.net/mc/help/v15.2/en/index.html

https://docs.soti.net/soti-mobicontrol/release-notes/

Regards,

This is not a problem.

It is possible that a MobiControl server is used to manage more than one device model for a particular brand.  If the models have different optimum (in terms of stability, compatibility or other features) agent versions, it is always the administrator who make the call which agent version to be configured as the default.  The most logical choice is usually the device agent version that is optimal for the majority of devices of that brand.

I'm one of the administrator.s... So is there someway to set the default agent version to "add devices rule"?

And as i posted in screenshots, the agent is the newest one for this brand and for AE.

The default agent version for each OEM device brand/series  is global for the WHOLE server implementation, and NOT configurable on a per add-devices-rule basis. 

So, i don't understand your previous post:

"it is always the administrator who make the call which agent version to be configured as the default."

As you see in the screenshots the newest agent is set as the default (i understand it so) but isn't used. And thats my problem.

What are the version and build numbers of your MobiControl server?  Is it an on-premises or Soti-cloud server?

Have you restarted your MobiControl server after the device agent upgrade on your server?  

Did you check the log files (DS/DSE/MS) for any warning/error messages related to device agent upgrade?

Was the installed v14.3.2.1050 device agent an Android Plus or Android Enterprise agent?   What were the active MDM API reported in the configuration tab of the device agent or in the Device Detail tab in the web-console?  If it was enrolled as an Android Enteprrise device in managed-device mode,  what enrollment method did you use to enrol the device?   It was possible that your other AE enrollment set-up had caused a different AE agent (from the default v14.4.0.1028 device agent on your server) to be installed.

Its a cloud-server hosted by 3rd party.

I haven't restarted the server after that upate and in my opinion it can't be a solution to restart server after each Agent Upgrade.

I saw no error's in the logging.

It's Android Enterprise Agent.

Actual API Level is 27, have to reenroll device to see iwhich level it had before.

We enroll these devices with StageNow barcodes.

Check your StageNow configurations to see if your existing barcode specify a different device agent source and/or agent version.  If so, make proper change(s) to generate a new barcode for enrollment.

Ok, thats new to me, that i hve to add the mobicontrol agent to the app cataogue rule too to get it updated.

The  information in the post you marked as solution is not totally accurate, if not somewhat misleading for some new comers.

It is true since MobiControl v12/13 that the AE device agent of an enrolled device can be upgraded to the agent version availalbe on Managed Google Play store with an app-catalog rule.  However, your problem is related to device agent initially installed upon enrollment.  The limitation of this path is that there is only one active (i.e. the latest) agent version available on MGP store, but older device hardware/firmware sometimes work better with older device agent . 

The "Manage Android Agents and Plugins"  function is nothing more than a simplified GUI to install DEFAULT device agent for a particular brand/series/model (whatever applicable for that plugin), without the need to do manual injection of device agent and configuration in the MS-SQL database tables.   Once an AE enrollment method chosen, and enrollment parameters & add-devices rule are both properly set up to make the device download its agent from your MobiControl server, the corresponding DEFAULT device agent will then be downloaded.  

Ok, thats new to me, that i hve to add the mobicontrol agent to the app cataogue rule too to get it updated.

Hi Rafael,

Can you solution the relevant post that resolved your query?

Regards,