Failed handshake with server and cannot enroll CK75 devices

AK
Anas kortas
Lisa Dräxlmaier GmbH

After we made an update of our soti version to 2025.0 from the version 15.6 we are not able to re-enroll CK75 devices only . (enrolling CK65 still possible)
Any one know the root cause ? 
PS : for CK75 we are using .Ini file (that contain all information related to the enrollment rule.)

9 months ago
SOTI MobiControl
ANSWERS
MB

Hi Anas, 

do you have installed 2025.0.2 ?

Can you check if you have a SHA1 Certificate for the CK75 for the enrollment.

What i see has the Device Android 6 or WEH 6.5 as OS Running.

AK
Anas kortas
9 months ago

Hello, 
Yes its the version 2025.0.2 and certificate Algo is SHA-256

MB
AK
Anas kortas
9 months ago

Hello, 
It was working fine with certificate SHA-256 with Soti 15.6.
I also pushed a second SH1 certificate but was not solving the issue! 

MB

Hi Anas,

what you mean with pushed?

-> what i remind must be the SHA Certificate bnded to the DS.

-> have you checked if the Device is in an other Group or not correctly removed ?

Sometime the enrollment failed when the device is under specific conditions existing in MobiControl or one time i had it that it was not correct removed in the DB.

When that is not working please have a look intot the DS Logs with the MAC Adress to see an Error.

When that is not helping and the Scanners are in the Same Wifi or Network with workin Scanners i recommand to open a Ticket at Soti Support to have a look.

ZC
Zafer Cigdem
9 months ago

Hi Anas,

What is the OS version of your CK75 devices and which type of Android management you are using, is it Android Enteprise, Work Managed?

During the upgrade did you migrate the server or change the Windows Server OS version or any cipher suite /TLS related changes

I think the current devices keep well after the upgrade even for CK75, but you only have an issue for new device enrollment for CK75 right?

If you don't test yet, please also test to enroll new device (which was not on your Webconsole) and verify whether there is also an issue on this device enrollment as well.

AK
Anas kortas
9 months ago

the last available OS version  is installed into  our CK75 devices (6.0) and we are using, Work Managed rules.

we only upgrade the soti version without a server or change  or any cipher suite /TLS related changes

The already enrolled devices still working fine but we are not able to enroll/Re-enroll new CK75 devices.
Its not the same issue with all other types that are still working fine with that process.

ZC
Zafer Cigdem
9 months ago

Hi Anas,

I did not use CK75 earlier but looks like there are both Android and Windows version of it. If your device is Android for your case then AFAIK, AE OS6 is end of life (EOL): Android Enterprise Agent Maintenance Releases | SOTI Docs

Since Android agent version 15.4

On your previous server version you mentioned 15.6, how did you enroll this device on 15.6, and how are you trying to enroll now is it via DPC method by using afw#enroll. Thank you

AK
Anas kortas
9 months ago

AK
Anas kortas
9 months ago

Hello , 
There is no mention about Android 6 not supported with the version 2025.0 and yes it was working fine with 15.6.

We are creating enrollment rule and getting the .ini file that we are using to create the provisioning file.

ZC
Zafer Cigdem
9 months ago

Can you share what is your CK75 Agent version that is already enrolled an on your Webconsole, is it higher than 15.4 Agent? 

AK
Anas kortas
9 months ago

HI,

The Agent Version is: 15.2.0.1025 and we also tried the enrollment process with older version but its the same issue . I think its more related to the SOTI version that need to be checked!

  

ZC
Zafer Cigdem
9 months ago

Hi Anas,

How did you test enrolling the device by using 15.2.0.1025 agent version as an Android Enterprise Work Managed for your new MC server version?  and where are you installing this agent by using AE enrollment method?

I've already asked similar question on my 2 post earlier whether you are using afw#mobicontrol method or others, but I don't get any answer yet. 

RC
Raymond Chan Diamond Contributor
9 months ago

From Honeywell online documentations, it seems that CK65 has upgrade available to Android 11, but your problematic CK75 model is just supported up to Android 6.  What is the firmware version of your CK65?

Also do you have any existing CK75 device already enrolled in your system BEFORE the server upgrade to v2025.0?   If so, have you checked if they are still under full control?  What are the version/build numbers of MobiControl device agent/plug-in running on such device(s)?

AK
Anas kortas
9 months ago

Hello,

For CK65 devices the version of android that we have is 9 and higher !

Concerning the CK75 , yes all already enrolled devices with version 15.6 still working fine and under control ! but only enrollment process of new one is not working ! and OEM Version is : 81.01.16-(0139)

P
PMMOD@SOTI
8 months ago

Hello  Anas kortas,

Thank you for your post on SOTI Pulse.  Marcus Breitenthaler, Zafer Cigdem & Raymond Chan thank you for responding to the post your expertise and willingness to help are greatly appreciated!

I understand that you are experiencing issues while enrolling Honeywell CK75 devices. While the already enrolled devices are functioning correctly, new enrollments are failing. You have also attempted enrollment using an older version of Android agents, but the issue persists.

To resolve this, I recommend connecting with our support team for further investigation. They will need to collect logs, analyze the enrollment process, and determine whether a different method is required for successful enrollment. Additionally, they will check if the issue is related to the newer version of MobiControl or if there is a compatibility concern. The team will investigate using your test devices and provide an update accordingly.

I would like you to create a support case (click here) or call the SOTI Support team (click here)  to gain a better understanding of the issue. We can then determine whether to raise a Feature Request or troubleshoot to fix the issue.

Please let us know so we can proceed further accordingly.

Similar Discussions