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.
I have enrolled the devices, but put the sim card in after enrolling due to swap rounds, this inst showing the number on the system now, is there anyway to fix this? It just says phone number - unknown
Hi, i have a lockdown configured and I want to use a wifi icon to open the available networks. The customer doesn't want to use the soti wifi, he wants to use the android specific. So I was thinking I could to this via a intent, unfortunately I'm unable to fullfil the intent correctly. I want to open the following com.android.settings/.SubSettings sendintent -a "intent://com.android.settings/.SubSettings/#Intent;scheme=content;action=android.intent.action.EDIT;component=com.android.settings/.Subsettings;end" Any ideas or help for me? Thanks,
We have recently upgraded MobiControl from version 13.4 to 15.0.2.1049 as we are now procuring Android 10 devices and version 13 doesn't support SHA2 certificates for enrollment. Since the upgrade, we have come across a number of issues, one of which is mentioned below. We have a support case open with SOTI, but I thought I'd also reach out to the community to see if anyone else can help. Yesterday, we attempted to assign an updated profile to an existing set of devices (around 150) and around 15 of them stayed in an “Installed Partially” state, with the remainder installing successfully. The devices are all Samsung, but different models on different OS versions. On the devices themselves, a message is displayed on a blank screen stating “unable to load application menu please contact your administrator”. We attempted to retry the profile installation, but this did not work. We found that the only remedy for this was to uninstall the agent on the device, re-install it and then re-enrol. Once re-enrolled, the profiles installed correctly. These devices are remote all over the country and in their current state, we can’t remote control them, so are having to recall them back in to be able to re-enrol them. Before we tried to assign an updated profile to them, everything looked fine from the console. The agent had upgraded correctly, the devices were showing online and checking in and all profiles that were installed before the upgrade were still showing as installed correctly. Only once we have tried to assign a new/updated profile to the devices has this issue become apparent. It looks as if the agent has corrupted somehow during the upgrade, but this wasn't visible to us until we tried to assign a new/updated profile. I’m now fearful that we have a larger number of devices in this state within our estate, but we will not know until we try to assign a new/updated profile to them. At which point we’ll then need to manually re-enrol.
I have a profile setup for Soti Surf that enables kiosk mode and does nothing else. Surf kiosk mode ends up hiding the status bar and you have to pull down from the top to make it visible for a few moments. This gets awkward with Surfs pull down to refresh the page function. I've played around with the application settings for Surf but I cannot make the status bar always visible. This happens across multiple devices, CT60, CK75, and Samsung Active Tab 2. Is there a way to make the status bar always visible in Surf's kiosk mode?
Hi, We have Zebra TC55 JB device which we are trying to enroll to SOTI server (DA Mode) using DA Agent version 1300 build 33897. It always gives error -"Enrollment failed please try to contact your administrator" . Console version - 15.0.2.1049 Refer below screenshot Can anybody help if we are missing something? Thanks Raj Zebra Technologies
Hello,We currently use SOTI on our Android Tablets (Samsung Tab Active2 with Android 9).The profile we use is very restrictive, it doesn't allow factory reset, it doesn't allow USB debugging, etc. I mean, almost everything is blocked.We have a tablet which is currently blocked just after it starts :it shows "Mobicontrol - wait - loading" ; with a permanent loop.(the tablet worked a few days and got enrolled by soti).In this state if I press return button I have a tool tip with 2 options:* informations about the application (it does nothing)* close the application (it doesn't work ; the loop continues).I tried to rebot several times, removing battery, etc : same thing.I started in safe mode, in order to unistall sotimobicontrol but it doesn't work: in safe mode, the screen is all black except "mode sécurisé" (safe mode i french) in white at bottom left. Nothing possible to.I tried to do a "wipe data / factory reset"... but it's blocked by soti.it shows "MDM does not allow factoryReset". I also tried to put the firmware of the tablet (downloaded from sammobile.com) into a SD card, but I got errors:/sdcard/update.zipE:mmap (2487630050, R, PRIVATE, 4, 0) failed: Out of memory.E:Map of '/sideload/package.zip' failedE:failed to map file successfully generated dm-verity hash tree.Installation aborted #1. (I tried with T395XXS9CTF5_T395XEF9CTF5_XEF.zip ; T395XXU6CSL1_T395XEF6CSL1_XEF.zip and T395XXU8CTD3_T395XEF8CTD2_XEF.zip, firmwares downloaded from https://www.sammobile.com/samsung/galaxy-tab-active-2/firmware/SM-T395/XEF/ ) Finally, I tried to put the tablet in "odin mode" / "download mode" : it doesn't work with the tablet (and with all tablets running soti ; so we probably blocks it, because with a tablet without soti it works). I can't reach the green "warning message" for Odin mode, so I can't put the firmware through Odin.I don't know what to do now... if you have idea, please help.
Hello, maybe you can help me out here even though i am almost sure its a limitation of mobicontrol / device at this point. i want to set the timeout before the display gets locked to 30 minutes and the powerbutton should only turn of the screen. on an android+ device i found the following with watchsettings so far: Lock Screen After Timeout: Custom log (URI:content://settings/secure SETTING:lock_screen_lock_after_timeout VALUE:1800000) For the powerbutton option i sadly got no result. Using the following script on an aedo device got me no result: writesecuresetting -sec lock_screen_lock_after_timeout 1800000 I then tried to find something with adblogs on the aedo device and found the following settings triggered: security.screenlock.ScreenLockSettings/lock_after_timeout|1800000 security.screenlock.ScreenLockSettings/power_button_instantly_locks|false i tried multiple combinations of the settings with writesecuresetting i.e.: writesecuresetting -sec lock_after_timeout 1800000writesecuresetting -sec power_button_instantly_locks false writesecuresetting -sec lock_screen_lock_after_timeout 1800000writesecuresetting -sec lock_screen_power_button_instantly_locks false None of them worked. Any Ideas would be appreciated.
Dear all, We have an issue with the https://url command in the lockdown menu. 1. We can open the https website of the local webserver in the chrome app. 2. Using the command https://url in the lockdown menu, the scanner stay in the menu and does not open the page. 3. On the other side opening a the google address via https in the lockdown menu is working. Cert info: All required certificates are installed on android trusted certificates in the user area. System Info: TC52, android 9, mobi control 14.2, Does anybody know, what the https command in the lockdown menu is doing in the background or why it is not opening the webpage? Thanks a lot in advance. BR, Jens
Hi, just as a notice the on premise installer is crashing and or corrupting services afterwards. Running on latest updates for Windows Server 2016 and MSSQL17.
We recently upgraded the Cloud Instance of our Mobicontrol v15.1.1 However, we are experiencing issues with the Cloud Link Agent 2.0 (CLA) on our locally hosted Windows Server 2012 R2 box. We cannot get the LDAP and ADCS boxes to get checked/enabled as seen in screenshot below: I spun up test VMs running Windows Server 2012 R2 on my home lab, same issue. Is there any way to get CLA 2.0 to work on this OS? Can you provide us a version of the CLA that works with this OS and is compatible with Mobi 15.1.1? Our VM fulfills the minimum requirements as posted on the SOTI help page. SOTI minimum requirements for CLA 2.0: https://www.soti.net/mc/help/v15.1/en/cloudlink/configure/system_requirements.html CLA 2.0 download: http://download.soti.net/tools/CloudLinkAgentInstaller_v2.0.msi
I have created a user in "Manage users" and authorization Mobicontrol Administrators but I can't use the initialized user information to login SOTI MobiControl. Sorry I'm not good at English Thanks all! https://i.imgur.com/7ZyuY98.png https://i.imgur.com/diXOtex.png
Good Evening. I am running Samsung Tab A 8.0. All are Android+ ELM enrollments. Now we had and issue with a ROOT cert because some of these upgraded to OS10 and the server was running SHA1 and not SHA256. So we got SOTI on the phone really quick they got that all straightened up. Then.. We started hearing whispers that something done today broke the script: writesecureprofstring DeviceFeature DisableLockScreenShortcuts 1 apply featurecontrol Now if I rerun on a TAB running 8.1.0 the script will do as it is expected to do. However if I send that same script to a TAB running OS9 then I got a return of: DisableLockScreenShortcuts unsupported. Did the command change from 8.1 to 9?
Hi all, I’m having some issues with the SOTI API that I’m hoping the community can help out with because the documentation is not being very helpful. The goal we’re trying to accomplish is using the API to move a set of 6 devices from each of our facility locations to a different folder. Per the documentation the API method we should be using is POST /devicegroups/{path}/members. I've tried a few different ways but it almost always returns 403 Forbidden error with "Message": "Unauthorized access or invalid reference to specified object" or a 404 Not Found. I am able to run some basic commands like getting folder details or device details: GET <instanceID>.mobicontrolcloud.com/MobiControl/api/devicegroups/referenceIds:reference_id GET <instanceID>.mobicontrolcloud.com/MobiControl/api/devices/device_id From that, I assume I should be doing the following to move the device to the reference_id below but it's not working for me. POST <instanceID>.mobicontrolcloud.com/MobiControl/api/devicegroups/referenceIds:reference_id/<device_id(s)> I’ve also tried it with and without the /members/ in between the new path and device IDs as well as the following in the body as JSON: POST <instanceID>.mobicontrolcloud.com/MobiControl/api/devicegroups/referenceIds:reference_id/<device_id(s)> { "path": "referenceIds:reference_id", "deviceIds": ["device_id"] } I get the following error when using the body method: { "$type": "ErrorDetails", "ErrorCode": 0, "Message": "Contract validation failed", "Data": [ "deviceGroup.Name: Name is a required field." ], "HelpLink": null } Can anyone tell me what I’m doing wrong? Am I misunderstanding the documentation?
Hi,has anyone encountered an issue where when other app is trying to access SOTi issued user certificate and android is asking to set pin or password to access credential storage? Android 7 enrolled as Android + worked, but after upgrading device to android 8 and enrolling as Android Enterprise this issue appeared. Is it fault in new security settings in android 8 or soti app permissions? Would it be possible for SOTI to allow access to credential storage without PIN for some apps? Device TC51 running 02-32-04.00-OG-U01-STD OS 8.1.0Agent 14.3.0.1000A+ Service for Zebra - 1.6.0.102 SOTI Version: 14.3.4.1087
Hi All, Has anyone managed to create a Azure logic App custom creator with SotiMobicontrol? From MS's documentation I should be able to test the API in Postman and then export from Postman in to Azure. Postman connects without any issues and posts back the data we're calling. If someone has done it, could they give me a helping hand? 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.
