Hi Van

The empty token error is because the add devices rule has a managed google play account associated with it (MGPA) but the the correct ports are not opened for your server to actually get the account during enrollment.

This can be solved by either removing the MGPA from the add devices rule and select "skip google account during enrollment"

or by opening up the ports for the managed google play account.

The path you are on now is with the old API set from Google, (Device administrator, instead for Device Owner) A device enrolled with DA cannot connect to the Managed Google play Store at all, this is device owner only.

If the agent is injected into your database you do not need to inject it for all your devices, now you can enroll all your CT60 with the same agent and the same add devices rule.

Aloha Fredrik,

Mahalo (thank you) for the feedback. You gave me the immediate answer I needed:  "If the agent is injected into your database you do not need to inject it for all your devices, now you can enroll all your CT60 with the same agent and the same add devices rule"

As for the Empty token, I had SOTI's support check our servers and they found all the ports is open correctly. We skipped the Google account during enrolment and still was unsuccessful. They could not figure it out every attempt "Empty Token" error. At the time of this enrollment I just needed remote access, lock down and my staff to access blue tooth settings. The SOTI tech went with injecting the enrolment agent.

Could you share the difference between this path I'm on vs the path I should be on? Android + vs Android, Device administrator vs Device owner? I'm would like to know what features am I losing out on? Mahalo again for your kokua (help). Aloha and have an awesome weekend!  

Good afternoon

I am in the exact same boat but with a Honeywell ct40 model, did you find a solution Sir ???

Aloha Seb777,

Has SOTI helped you with this? Or were you able resolve your problem? Sorry for the late response found this in my junk mail. With my concern, it was how to move forward with new devices. If SOTI has "injected" the agent into your server than all you need to do is install the special APK file from SOTI HoneywellMobicontrol1350NewGen. Please check with SOTI not sure if the APK file is the same for you, im not sure if its compatible to CT 40.

If you are stuck trying to enroll and you are having the "Empty Token" error please contact SOTI and explain to them your situation. You may than share this thread. That's exactly what I did I found it here about "injecting" and SOTI support understood and took action. Hope this helps. Sorry for the late response. Aloha and have a great day.

Hey Van ! Yeah I spoke with 3 different people at soti and been sitting with their DEV team for a while now..  Last tech I spoke with was Neha Senior level tech, she was great and knowledgeable but the end result is the same..sent "dev team" ha ha   but for the record all of my android test devices have the same problem.  5 different models we are currently testing Honeywell & Zebra..