Latest Android Enterprise Agent is not enrolling properly for newer Samsung Devices.
Thank you for posting in SOTI Central.
As a word of caution, you shouldn't be modifying your database in this manner as that potentially voids your Support for future issues. I recommend you revert back the change and utilize the workaround found within your linked discussion. You're correct in that the problem originates due to an API issue on the 14.4.1 agent. And that is through the new 840 APIID for Samsung KNOX 3.4.
I suggest that you raise a Support Case so that you can be kept informed on the progression of the fix. Or alternatively, I will endeavor to update the linked post when possible.
Technical Support | SOTI Inc. |1.905.624.9828 | email@example.com | www.soti.net |
We have the same problems on our side, we use the KME for enrollment of our Samsung devices.
We have had to revert to version 188.8.131.528 for the moment.
I hope SOTI will provide a new version of agent that fixes this.
I just want to add that I found another issue with this agent, this time with custom data
Samsung with Android 10 and agent ver. 184.108.40.2064.
Is working in relocation rule;
Are not visible in device detail;
Are not working anymore with our scripts for changing background and changing name.
Everything works fine with older agent or Nokia mobiles or OS versions.
The v220.127.116.114 AE device agent doesn't seem to have any problem with MobiControl v14.5.3 or v14.5.5 server in my tests, but do have some problems on the same Samsung test device when enrolled onto a v15.2.x server.
I tested an enrollment with the new version published today 18.104.22.1689 we have no more problem with installation of profiles AE.