Another companies device Agent...
I would factory reset the device rather than just trying to manually delete files.
Thank you for your question.
For windows, Factory reset the device and after rebooting the device look for McSetup.ini and Pdb.ini files. If they still exist please make sure that they are deleted before you enroll with your new agent.
Sometimes in variation of the device behavior, Even after doing a factory reset the files wont be deleted or will reappear in the device. So, you will have to make sure that the those files are not in the device during the time of enrollment.
After deleting those files and factory resetting the device successfully, the device will be able to communicate to the server and enroll the device.
Technical Support | SOTI Inc. |1.905.624.9828 | email@example.com | www.soti.net |
I/We figured this out.
Soti support realized that since were using windows/CE devices, they only communicate with sha-1. Our deployserver didn't contain that cert. They put that cert on our server and I rebuilt a new device deploy rule and also checked the 'Force SHA-1 client certificate distribution' in the rule.
factory resetting would have not resolved this issue. In face, zebra agent was still on some devices and they are working fine for me now.
Thanks all who chimed in! :)