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.
Does anyone know how to locate the APNS certificate in the database? Or an alternate solution to removing the APNS expiry warning every time I log into MobiControl. Thanks
After rebooting device and opening application that uses certificate installed through other profile it asks for credential storage password. If I press cancel, it will ask to allow certificate after some while. If device is rebooted and left alone for a minute or two, it works just fine. Application is using certificates and Authentication profile is set. Everything also works if PIN to unlock is added. It looks like SOTI is starting some process that allows access to keystore (only my guess). Is it possible to enable it manually, startup or through script? One solution was to include a scripted delay when opening app from lockdown, but this seems to not be the best solution, because time it takes to set everything up differs and we would like to achieve the best startup without 3-5 min delay, if possible.
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
Good Afternoon Everyone, I'm currently trying to remove certificates that were installed by our old MDM system via the API as they're causing issues with Exchange Email configuration. I'm getting an error that appears to be from MobiControl rather than a generic Rest API error but I can't find anything about it in any MobiControl documentation. The error is: Invoke-restmethod : {"$type": "ErrorDetails","ErrorCode": 3500,"Message": "Certificate action failed.","Data": [],"HelpLink": null} The script I'm running is: $MCFQDN = "https://SERVERURL/mobicontrol/api/devices/$DeviceId/certificates/$CertificateID/actions" $Body = @{"ActionKind" = "Revoke" } $Header = @{Authorization = "Bearer $token"} try{$response = Invoke-restmethod -Uri $MCFQDN -Method POST -Headers $Header -Body (ConvertTo-Json $Body) -ContentType "application/json"}catch{$($_.Exception.Message)} Does anyone have any idea what the issue might be? I'm tried removing a certificate managed by MobiControl as well and got the same error. Thanks!
Hi, On the SOTI-MobiControl platform, I want to prevent deleting the configuration of an IPAD group, as well as deleting the SOTI certificate. Thanks in advance, BR,
Hey Everyone, When it comes to certificate renewal for CBA is it mobicontrol or exchange that is responsible to send the updated certificate to the devices? I noticed that under our Certificate Template the "Auto renewal" check box is not checked, could that be the issue? Currently when people are having authentication issues we have to revoke the CBA profile and push it again which updates the certificate but this should be done automatically. Regards, Johnathon
I am curious if any has had any issue with a Certificate Profile failing to install and what it may be caused by. In my case, we are installing a Cert to a Zebra Android+ device to run an application. The Cert is in its own profile and the mandatory Auth is in a separate Lockdown profile. (This may be relevant but I have not found it to be yet) At some point after making changes to a completely different profile, the already installed Cert would change to an Install Failed status and the app would no longer operate. To my knowledge, the profile was not reinstalled and the Lockdown(with Auth) was not removed during this issue. I am able to reproduce the failure by revoking and reinstalling the Cert profile on a device (while keeping Lockdown + Auth installed). Once I attempt to reinstall, I get a failure for the Cert profile and have to Factory Reset the device to even get the cert to reinstall. Another note, not to distract from the main topic, is if you have Cert XYZ in Profile A and Profile B, SOTI somehow sees that the cert is the same and does not attempt to reinstall the cert when changing from Profile A to B via folder move or other means. I have a SOTI case open and have sent verbose logs but it's not really getting anywhere and I am apprehensive to move forward with changes I need to make in fear that it will bring down their production devices.
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 get the following message on my device: "The certificate for this Server is invalid". How can I avoid this message / what is the solution?
I have an environment that is completely locked down and any requests for public internet access are being denied? How can I improve the performance of MobiControl in a fully offline environment? I'm available to perform registration successfully offline, but access to other SOTI services like the Remote Control skins repo and the central CA are resulting in a relatively hindered experience. Can you sideload the skins into the environment, bypassing the service? Can you get around the certificate related issues during enrollments and check ins at the device level (Android). Another issue that I'm seeing is that the Enrollment rule creation fails to provide me with a local enrollment url. I would expect the enrollment ID to not be generated given it not having access to the central Enrollment service, but shouldn't a local enrollment url be generated?
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)
