No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hi all, I am testing SOTI Mobicontrol 14.3 and testing enrolment of AE smartphones. When testing LG smartphones (K4/K8/K9), the smartphones are encrypted, factory reset or straight out of the box, they are failing to enrol with the following SOTI Agent message; "Enrollment Failed. This device is not SafetyNet compliant. Please contact your system administrator." I know I can simply tick the box to still enrol the devices but that would defeat the point of the SafetyNet feature. Has anyone else hit this yet? I will check this with SOTI later today. John.
In SOTI MobiControl, it's possible to configure "Prevent unenrollment from Device Agent" for a device group. However, this does not seem to work, as I can still select 'unenroll' in the device agent? Environment = SOTI 14.2.1.4394 Panasonic FZ-N1 enrolled with Android Enterprise SOTI MobiControl Agent (13.6.0.1567), in Work Managed Device mode
Is it possible to setup the Samsung device with Android 8+ OS as Fully managed devices with work profile (COPE) without use of Samsung Knox container? The Google docs writes that should be available on Android 8+ devices. Is it possible to setup it on any Android 8+ device in SOTI? I can't find any information about it in documentation. Thanks for any information. Peter
Hi community and support, I wanted to configure Soti Mobi Contrtol in the way to use the Certificate Authorities to issue an user certificate for WLAN/Wifi access. The field "Enrollment Certificate" is a mandatory field when using the ADCS and PKI configuration. The description of the filed is the following in V13 and V14: "Upload the enrollment agent certificate. The enrollment agent certificate is used to sign certificate requests to the ADCS server and is explicitly trusted to request certificates on behalf of other users, for example, the device owner in MobiControl." My qestion is how to get such an enrollment agent certificate to upload it in the requesting field? All other configuration fields are clear for me. We are currently on version 13.4.0.3985. I have also created an Enrollment Agent with the Device Agent function. Many thanks in advance Regards, Uwe
When I enroll a device into Mobicontrol, is there a way to have it prompt for the device name to use?
Hi, I already have a case for this(C00275940), but just wanted to check if anyone might have a suggestion. Issue: Devices of various (7.0+) Android builds, networks (4G, Wi-Fi) and OEMs cannot enroll (times our when trying to connect to server in MC agent) after a DNS update. Everything is marked green by admin util. and already enrolled devices connect just fine. If I manually enter the enrollment page in a browser, then it is properly displayed and accessible from all devices and networks (available from on internet). The weirdest is however, that when testing alongside support, THEY where able to enroll devices to the environment. None of us have been able to explain this behaviour yet. For now we have fetched ADB-logs which is then to be submitted to development. I however just have a feeling this has to do with the DS certificate. Even though this is mapped to the correct hostname and everything is marked green (And support was able to enroll their test device.). This entry is repeated in the ADB logs during enrollment: 11-01 15:37:18.310 8859 8917 E soti : Caused by: java.security.cert.CertificateException: Certificate with Issuer: 2.5.4.46=#132433323346343431352d304146332d343139392d424430432d363433323331424246454243,CN=MobiControl Root CA and Subj: CN=MobiControl Server is not trusted Brgds, Ole
I am looking for the best way to get an email alert each time a device is enrolled. We have devices returning from depot service from a shared spare pool. This means that I must delete/unenroll my damaged device before sending to depot, because I will not always be getting the same device back from depot. It is possible that a previously used and now repaired device will return from depot at a later time. I tried using the "Add new device" Event from the Alert Rule wizard, which covers the new device (that's never been enrolled with MobiControl) scenario. The problem is this method does not alert me if a device that has been previously enrolled is re-enrolled. I need both to work. As a workaround, we have applied a single profile to devices and are using a "Profile installed" Event to send email alerts to appropriate teams. This is not ideal, as we are sending a useless package just for the sake of an alert rule. Can anyone help me with a more simplified alert process that is triggered every time a device is enrolled?
When we manufacture our Android devices, one of the steps is enrolling the device in the Soti MDM. This enrollment is done via an Ethernet connection. We have recently modified the agent version that is bundled in our OS image from 13.0.0.33835 to 13.5.0.1088 and there appears to be a behaviour change. We are now seeing all devices attempt to enroll with a device id of 00904c112233. If we instead connect the device to Wi-Fi before enrolling, then the device id appears to be unique for each device. Has there been a change in the algorithm that the Android agent uses to generate the device id when enrolling? If so, I have two additional questions: is there any way to ensure unique device ids without connecting to Wi-Fi? is this behaviour the same in more recent versions of the agent (if there are any)? Steve...
Wondering if anyone has deployed multiple deployment servers here and what it takes from a server/resource perspective and how it impacts the Management Console experience. This question is coming from a call I had with SOTI Support last week about CE5 devices that were not able to enroll into 14.1 because 14.1 installs with a SHA2 root cert and CE5 devices can only use SHA1. They also mentioned that If I did want to enroll CE5 (along with SHA2 compatible devices) then I'd have to set up a 2nd deployment server and install a SHA1 cert. I'm going to be doing some digging on my own and may even reopen the previous case but would like to hear your thoughts. Also, @SOTI , if you have any release notes specifically for what version this root cert change was made, I'd like to see that. Though testing, my 13.3 env can enroll CE5 devices and does not have the "Force SHA1" option in the enrollment rule settings so I'm assuming it's using SHA1. If 13.4 uses SHA1 as well then I will just recommend this version until customers upgrade past CE5 devices. Thanks, Ben
Hello, I am having a problem enrolling Huawei Mate 9 Lite devices. First, the problem was that after enrolling 1 device, the next one could not be enrolled because "Device ID already exist". I opened a case on SOTI, where I was told to update to version 13.4.0.4591 (previoulsy, it was 13.4.0.4266). After the update, this is what happened: I enroll Device 1, it enrolls ok with device id 1234. I enroll Device 2, it enrolls ok with device id 1234, and Device 1 dissapear. I unenroll Device 2, it unenrolls ok, and Device 1 appear again. Sometimes, I enroll other device, with no problem at all, and sometimes it keeps saying "duplicate device id". Any idea what is going on? * I tried enrolling using .ini, url, code, etc. * I have no intention of using Android Enterprise. Thanks in advance, Maximiliano.
In a scenario where Windows, Android, and iOS are involved.
I see this feature, but I don't know what it's for!
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.
.jpg)
