In general, choosing AE device agent is a better choice because of better support/continuity (due to standardized AE certification requirements for all involved parties as defined by Google), and guaranteed minimum feature sets as defined by Google AE documentations.

OEM specific device agent needs development efforts from both Soti and the OEM developers, which can potentially have longer release delay if there is resource or other constraints.

Without a device to do thorough tests,  it is difficult to come up with an exhaustive and updated list on the differences.  The most obvious advantages of using AE device agent include:

1. the support of app deployment  from managed Google-Play store and dynamic configuration of associated AppConfig compliant app parameters.
2. the support of automated enrollment with Zero-Touch Enrollment (ZTE)

Hi BD

Greetings from SOTI.

Thanks for posting on SOTI Pulse.

Please confirm if you have raised any support ticket for your issue, if not, kindly let me know so that I can proceed with creating ticket for you.

Key Considerations for Agent Selection

1. Agent Types:
   • AE Generic Agent:
     • This is a more universal agent that supports Android Enterprise features across various Android devices.
     • It typically receives more frequent updates because it’s designed to work with a wider range of devices and scenarios.
   • OEM Agent:
     • This is tailored for specific OEM devices (like Honeywell) and may include specific optimizations and features designed for those devices.
     • It might lag in updates if the OEM has not released a new version, which can result in missing functionality or compliance.

Evaluating Your Choice:

1. Using AE Agent:

   • Since you are successfully enrolling Honeywell devices with the Honeywell Provisioner, using the AE Generic Agent is generally fine as long as it meets your organizational needs and security requirements.
   • Ensure that the AE Agent supports all necessary Android Enterprise features you need, as it may differ from the OEM-specific features.

2. Checking OEM Agent:

   • The OEM agent (2025.1.2.1214) being older does not necessarily indicate a wrong choice, but using an outdated agent could mean you are missing new functionality or security enhancements present in later releases.
   • If the specific Honeywell OEM agent provides necessary features or settings that the AE Generic Agent does not, it may be worth investigating whether to switch back, assuming it can optimize your provisioning.

Incase of any further concerns, please don't hesitate to reach out.

Have a great day ahead

Kind Regards

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