Script command is not supported by device (__knoxlicense)

Solved
MM
Miguel Machado
CodeOne - MSP

Hi, I enroll one Samsung SM-T540 in SOTI but my profile is not installed.

Already try with different profiles, but it always Pending Install.

I check the logs and see these messages:

I have another two devices from same model and OS version and everything works fine.

Already try to reset device and configure again, but the problem persists.

Anyone know how can I fix this?

Thanks, Miguel Machado

a year ago
SOTI MobiControl
ANSWERS
MM
Miguel Machado
a year ago

Hi all,

I found a solution.

I'm using agent version 15.1.5.1049 and the profiles never install.

I upgrade to latest version(2024.1.4.1149) and everything works fine.

Solution
RC
Raymond Chan Diamond Contributor
a year ago

Do the three devices has firmware of the same version as well as same build numbers?

What about the version and build numbers of the device agents?

Do you find the active MDM API's reported for the three devices exactly the same?

MM
Miguel Machado
a year ago

Hi Raymond,

Yes,the three devices has the smae OEM Version and agent version.
Supported MDM is also the same.

The only difference I can see is ELM Status. This new device is n/a and previous device is Active

RC
Raymond Chan Diamond Contributor
a year ago

The problem should send be related to difference(s) in

1. steps taken to enroll the two devices

2. changes in  server implementation (e.g. firewall /MobiControl settings related to access to Samsung ELM license server(s), MobiControl server version/patch,  settings in the enrollment policy used, license,  etc.) within the 12 days.

If I were you, the first test I would do is to  unenroll/delete one of the enrolled devices, and see if it can be  re-enrolled back without problem.   If so,  I would unenroll/delete the device again, and try to use exactly the same procedure to try enrolling the currently problematic device.  This can likely help to pin-point whether the issue is likely specific to the problematic device only, or to the server/license side that affects more than 1 device.

MM
Miguel Machado
a year ago

Hi Raymond,

Sorry for the late reply.

I tryed to delete one of the previous enrolled devices and after reenrollment I have the same problem that I have with the "new" device.

P
PMMOD@SOTI
a year ago

Hi Miguel Machado,

Thank you for your post on SOTI Pulse

Please share the below information:-

  1. Method of Enrollment
  2. MobiControl Instance Version
  3. How many devices were affected by this issue

Please let us know after re-enrolling the device you are facing the same issue? Is the device previously enrolled with SOTI?

Have you followed the steps suggested in the above post?

Please share the above information so we can proceed further accordingly.