Many device models do support both the Classic Android+ platform with an OEM-/model-specific device agent, and the Android-Enterprise platform with a generic device agent.  Besides,some devices can be enrolled to any of the three supported modes (i.e. managed-device, COPE, and BYOD) with the same device agent but different enrollment procedures/enrollment-configurations.  Please also note that AE device platform (except for the BYOD mode) requires the device be factory-reset.  

For my own customers, I would  generally recommend them to use the generic AE device agent rather than the classic Android+ device agent if there is a choice, unless there is/are some critical MDM policies that are supported in the former platform is not available in the latter. The stability/compatibility of the device firmware on the newer AE platform should of course be considered.

So, there is no such thing as the WRONG agent installed.  It all depends on what is done to do the enrollment after testing and deciding which agent to use.

It is the MDM administrator responsibility to thoroughly test if the device agent and enrollment mode used is stable enough the the device and fulfill the use-case requirements primarily in terms of MDM policies supported.  I don't have your hardware nor test its compatibility/feature set, and thus cannot say if there is any hidden problem in your current deployed device.  If possible,  I recommend you to do required tests on that (or similar) hardware to confirm.

Hello Steve,

Thank you for posting on SOTI Central!
I am glad to see that Raymond's response helped to answer your question and provided more clarity.

Thank you for marking this post as solutioned and please feel free to reach out to us if you have any questions in the future.

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