Hi Remy,

when you are going to use more samsung devices than just "few" ones then i recommend to make use of
the samsung knox platform. There you can use the free solution Samsung Knox Mobile Enrollment (KME).

It helps you to mass enroll your devices directly into MobiControl. Its almost the same like the Stage Programmer.

You can:

• Enroll devices as android legacy (only for android 10 or lower)
• Enroll devices as android enterprise
• Disable system apps
• Create a qr-code which contains wifi information (open, WPE, WPA/WPA2)
• Add json data: you can add the enrollment id for auto enrollment
  (with the json config it will automatically re-enroll the device into mobicontrol when someone tries
  to unenroll the device)

Samsung also recommends to enroll the devices as android enterprise for soti.

Hello Remi

Greetings

Thanks for requesting an answer from SOTI!!

• Kindly confirm your Samsung device OS and firmware version and Your Mobicontrol version
• Secondly , if your  do not want to enroll your devices as android enterprise devices than you can also test by  enrolling your device in Android plus method by  trying to Download the device agent from  SOTI MobiControl Device Agents Downloads page under Android classic -oem specific agent after selecting manufacturer.
• For assistance with android oem enrollment , you can follow this link too  https://www.youtube.com/watch?v=7-t89RLW_FE
• In last , you mentioned that Android enterprise enrollment as work manage device gives you remote view option only so to check with that issue also , you can try to send following scripts to test with remote view issue.

Reset_elm_license       

#perform device check in after above mentioned script and try to see if you are able to remote control.

Here are some other scripts to reset flags for remote control which you can test.

_resetfailedrcdetectionflag 

restartagent

Also, if this post has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others may benefit from this information.

 Regard

Hi Ankmod,

Here are the requested information:

OEM Version: QP1A.190711.020.T540XXS3BUD1
OS Version: 10
Android Security Patch Level: 2021-03-01
-----------------------------------------
Mobicontrol version: 15.1.3.1021

-----------------------------------------

Unfortunately the scripts did not worked I don't get the "right" API's but also the ELM Status is "Activation Failed".

I've tried using the KME platform listening Ozan's advice and "for a short time" I've had these API's: SamsungMdmV57, Samsung RC v1, Samsung KNOX v3,3, Work Managed Device instead of the "standard" Remote View and of course Work Managed Device. I think the "ELM status" was trigger for a "roll-back".

Our environment is a "pretty" closed one so now I have some questions to rise:

1. Do I need an additional key in Mobicontrol to be able to get the ELM "activated" status?

2. If not it is enough only for the server to have access to the *samsung destinations or also the device?

3. Is this feature "free" up to a certain point?

Thanks for your help!

Hi Ozan,

Thanks for your feedback. It helped me move forward a bit but I'm still not where I want to be.

Probably we will enroll more Samsung devices in the near future so a good solution is mandatory to have.

What do you know about KME direct. I've discovered that and Enterprise security option for the WLAN exist and it fits us better but the generated qr-code is "rejected" by the device via a "KNOX enrollment" and I don't know way.
Maybe you've already met something similar...

Thanks for your help!