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.
When MobiControl connects to the CLA, it invokes the GetCertificate method to communicate with the Agent. At present, this method generates a COM-based Certificate Request and submits it to the Certificate Authority for certificate issuance. Because Certificate Request objects are created on the CLA side, the CLA encounters performance bottlenecks. To address this, the flow will be updated so that the Certificate Request is created only on the MobiControl side and then passed to the CLA as a parameter in the GetCertificate method. The CLA will simply reuse this object, reducing its processing load. Customer Impact: For customers who have applied security policies on the Certificate Authority side that validate the request based on the process name, an update will be required. With this change, the process name may appear as one of the following: Soti.Cloudlink.GrpcServer.exe MCDeplSvr.exe
One of the features that was brought up by SOTI during our POC was the app catalog. It was billed as similar to the app store in Intune. However, now that we are trying to set it up, it appears that the only people that can use it are those with admin rights on the local machine. If they have admin rights then they can install whatever they want, something that we are trying to get rid of. So, question is, am I reading the documentation correctly, is the regular user unable to install from the App Catalog?
We’re running into an issue with our Zebra VC8300 devices on Android 14 where DataWedge configurations are not importing. Our current process works fine on Android 13 — the .db file is stored on the device in /sdcard/, and we push it via SOTI MobiControl using the DataWedgeMgr XML. <wap-provisioningdoc> <characteristic version="9.2" type="DataWedgeMgr"> <parm name="ConfigurationFile" value="/sdcard/UlineMX/datawedge.db"/> <parm name="AutoImporting" value="1"/> </characteristic></wap-provisioningdoc> On Android 14, the same .db file will not import — even if I go into the DataWedge app on the device and attempt to import it manually. No errors appear; it simply doesn’t apply the configuration. I also tried creating a new StageNow Profile with a higher MX but that did not solve the problem. Has anyone run into this with Android 14? Did the import location change? Is there a new permission requirement for DataWedge to access files? Is .db importing deprecated in favor of another method? Any insight or workaround would be appreciated.
We have disabled the GMS services on our devices, which worked perfectly under Android 11, 12, and 13. Now, under Android 14, the Google Play services are still being queried. Is there a way to disable this? If so, where? We haven't found a solution for this yet
We are currently facing an issue where no phone calls go through when we activate the lockdown. The phone itself is enabled on the lockdown and works, but incoming calls are not displayed. We Use Zebra TC77 and TC78 with Android 14 SOTI MobiControl 2025.1 We've also tried everything and attempted to read and release the activity, but always without success. Does anyone have an idea?
Hi All I can see lots of posts regarding remote control stays black on Android 13 and 14 Samsung devices and generally the advice is to start your RC session, once connected to the device it will show a black screen, use Page Up on your keyboard, followed by the PIN (you won't see it on screen) followed by enter and you will then be able to see the screen. This method works fine for android 12 and 15 devices, but not for android 13 and 14. The android 13 and 14 devices just can't be woken remotely - has anyone got any extra tips or know if an agent is available to support this function. In the past we've just been told this is just the way android 13 and 14 are, but since it is still in support and these are still supported devices (the OS can't be upgraded) then has there been any fixes or workarounds? The test device in question is SM-G780F (max OS is 13) We have Samsung on android 12 and typing the PIN on black screen is fine We have Samsung on android 14 and it has the same issue as android 13 - can't get past the black screen even after typing PIn in blind. We have Samsungs on android 15 and no issues. Any advice appreciated, but please note what I have already tried above and the comparison between android 12 and 15 above. Many Thanks
Hi All, I hope you can help me with this. The Calculator app in Kiosk Lockdown is showing a “Package not Found” error after we upgraded TC57 devices from Android 8.1 to Android 13. However, on TC57 devices that are still running Android 8.1, the package appears and works normally in Kiosk mode. Thanks in Advance
Does anyone have a working example for this? How to get the downloadOptionsReferenceID in specific.
Hell all, We have soti mobicontrol on version v15.5.1.1010 with a server who run windows 2016. The IT infrastructure wants to migrate the server to windows 2022. Someone can tell me, if Mobicontrol will continue to run with a windows server 2022 ? thanks for all
hello, i have there an Zebra TC21 running OEMversion: 14-26-08.00-UG-U00-STD-HEL-04. On the device was set an PinLock using Soti Script : " resetpassword 1234 -bypass_secure_startup". Now the owner live and i need to remove the Passkey. The problem is that the device is connectet to the correct network but didnt show up online in the Mobicontrol console (2024.1.2). Enrolled as Enterprise device. Any idea ? Kind regards Günter
This is on A13 devices, i do not have this issue on A11 devices. I have an app that connects to a paried BT printer. The nearby permissions is being "blocked by admin" but i have another app that i push in the same way that that permisison is allowed. does the developer need to requrest the BT related permissions in a different way for SOTI to auto approve?
We are doing a proof of concept on managing our engineering laptops that live on our manufacturing networks, which are air gapped. Currently all of the install files are on a file share insdide the network and installed from there. The question that has come up, is it possible to use the App Catalouge from SOTI to manage them. Not all devcies will need the same software so giving them the choice on what to install would be nice. I only see one option that is not msi(x).
I would appreciate your support regarding the following topics: We are using Galaxy XCover Pro devices running Android 13. The devices support dual SIM, but only one SIM card is inserted. Is it possible to determine through SOTI which SIM slot (SIM 1 or SIM 2) the active SIM card is using? Can we monitor the monthly mobile data usage of the devices via SOTI? Is it possible to enable Multi-Factor Authentication (MFA) on the SOTI MobiControl login screen for administrator access?
We are adding Windows 10 laptops, the device name in SOTI matches the Active Directory rules, however the name on the device remains the default. I cannot find anywhere in Mobicontrol where i can see what the device name is on the computer, am I missing it somewhere. How can I change the device name on the machine during enrollment to match the generated device name in Mobicontrol? Thanks.
Hi all.Need some advice and perhaps looking at this completely incorrectly.Our on-prem instance of Mobicontrol is running version 2024.1.0.1052.Samsung Tablets ranging from Android 9, through to Android 14.Android agents 2024.0.1 through to 2025.1.3, enrolled as Android Classic.It's to my understanding that the legacy Content Library policies were depracated and that the UI on newer versions of the server software could no longer access that element of the system, in favour of Soti Hub.I am trying to experiment whether a transition to Soti Hub would impact our field workers, because they are contractors they do not have access to any cloud based corporate accounts as its not a requirement nor allowed, yet when I install Soti Hub and try to run it on a test device, only an error message is displayed with a Login button to say to contact an Administrator. I am entirely unsure why I assume its because we are still using the original Content Library policy and that there is a missing configuration somewhere (such as where the documents are located, I did add a configuration to the profile along with the package but kept its default settings).My questions are as follows: Can we upload documentation via Hub but have the users continue to access the newly uploaded documents via the Content Library section of the agent on the device? If not, is there any way we can set up hub to not require the user login with credentials? Can the documents be uploaded to the server they're sat on, in the same way as the deprecated Content Library policy? Without the need for the documents to sit on the cloud. If they can be, how would one go about this? As currently on a test device, I just get an error message and the Hub is inaccessible and I have no way to test beyond this to see how any of this can be achieved without disrupting our field workers. There is really no clear indication about this deprecation of the Content Library policy, and what we would like to avoid when updating is creating further problems for ourselves. We have hundreds of documents being accessed daily and due to the nature of this and the number of users, we'd like to keep the system this way. Any assistance regarding this is appreciated as it feels unless I have missed it somewhere that any instructions to transition isn't well documented.Thanks
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.
