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.
How do I set up SSL on a mobicontrol on-premise server? I've tried setting up SSL on IIS but it doesn't work.
Hello there, I'm trying to upgrade MobiControl from 2024.1.0 to 2025.0.0 and experiencing an issue at the end of the installer, at this step: "Upgrading Web Console: Finalizing" Error encountered: [2024-12-16 15:14:30.706] INFO [Install] (.NET TP Worker): Finalizing Installation[2024-12-16 15:14:30.811] INFO [BtnNext_ClickAsync] (1): Load Install failed window[2024-12-16 15:14:30.815] ERROR [BtnNext_ClickAsync] (1): Installation failed while installing - Web Console[2024-12-16 15:14:30.822] ERROR [BtnNext_ClickAsync] (1): ****************************************************************************************************************************************************************************************************************************************************** Exception: Error occurred while executing: powershell. Exception message: An error occurred trying to start process 'powershell' with working directory 'C:\Users\xxxxxxx\AppData\Local\Temp\{BBD91520-FB19-4034-8475-60D59DBFDD5D}'. Acces refused. * Has a kind soul experienced this error and found a solution that could be shared with me please? Thanks! Best regards,
Hello, We have over 1K+ Zebra TCxx devices in use at our warehouses. All devices are deployed with a locked screen, granting access only to the apps necessary for their tasks. Occasionally, a device gets lost or damaged. While this can happen, we'd like to see if we can reduce such incidents by requiring users to log in before they can access applications. We tried the shared device feature, but encountered a few issues: When Soti Identity is down (FE: when there is an update), users cannot log in, which means the scanners are unusable. The default shared device login screen includes a link to the terms and conditions. Through this link, users can access various other websites (possibly something we could block). It seems likely that other companies are facing similar issues. So, here’s our question 😊 Has anyone found an ideal solution to this problem? If so, could you share some details about it? Thanks very much in advance! Best regards,Robbert
Hi, How to install PFX certificate automatically from MobiControl on Windows Classic.
Hi! We use an Android app (Aims Manager) which launches a browser window for sign-in. When configuring the device with Lockdown mode and adding this app only, the pop-up browser gets blocked unless I add the sign-in URL as a Home Screen Item. Is there a way to grant access to this sign-in URL without creating a dummy Home Screen Item?
Hi. Is there any way how to send custom data from SOTI to app or can I at least determine the profile, which device is enrolled in? The use case is that I need to show some information in app according to which profile device is enrolled in. I found only one way so far, which is to assign a config file to device from profile and then read it in app, but it doesn't seem like the easiest and cleanest way to do it, and besides, app need read permissions. MobiControl version: 15.0.1.1181
Hello, we have some Zebra devices (TC57, TC57X, TC58) with Android 10 and Android 13 that when you use the remote control, do not appear any notification to de user. But recently we have deployed a TC27 Android 13 device that allways show notification of remote control. Is ther any way to avoid it?
Good morning, i have a brand new Zebra MC9400 that i am trying to enroll in soti mobicontrol, but i can't figure out how to make the unattended remote control to work. I followed the guide here: Enable SOTI MobiControl Remote Control for Android Enterprise Device Owner (AEDO) Mode (zebra.com) that says that this new models doesn't furhter need the Zebra soti plugin Zebra_Legacy_RC_AE_1.16.10.121.pcg. Without this package in the profile, i can only connect to the device (on the device screen is also prompted to accept the screen casts request) but i can't interact with the device, that is mandatory for our enterprise requirements. I also tried to add the package Zebra_Legacy_RC_AE_1.16.10.121.pcg in the profile (it was working with MC9300) but with no luck , it won't install in the device. My question is, why is the remote interaction not working ? Our mobi control server version is 14.2.0.2894 (cloud appliance) Many thanks, regards
Hello everyone, I would like to know if it is possible to automatically approve the authorizations that MobiControl requests using OEMConfig. In my case it is about Zebra and Samsung devices. Have any of you had any experience with this?
Hi all, Is there a possibility to send a script or something else, to log out the user thats using a device. F.E. condition: when you put a scanner on a charge docking ( isCharging is True) action: log out the user from this scanner. Via the device actions its possible but i can't select this action in the signal actions. Thank you in advance. Kind regards, Robbert
Hi all, We have a question about making use of intents. We want to create a button that calls an intent that starts the Log In screen from Soti. we have scanners in a lock screen and now they need to press and hold the back button and press login: what we want is that we create a login button so they will directly go to this page. (so instead of press and hold the back button and press login) when we check the activity (via identify_activity) we see the following: net.soti.mobicontrol.androidwork/net.soti.mobicontrol.shareddevice.SharedDeviceActivity now the question :) how can we open this screen via an intent? We checked the intent manual but we can't get it work. hopefully someone over here can help us. thank you in advance!!
HI, How do I push a pfx certificate so that it can enter the current user, I tried pushing it via the modern Windows profile but the certificate goes to the local machine.
I have an issue that my device is not showing up in the WebConsole of MobiControl. The devices does enroll correctly. The devices does register to my company account. The devices shows that it was added in the global console but not in the standar web console. When searching on the WebConsole the device name it's not showing up. Additional to this, when I trigger a change of one of my devices it doesn't reflect on the WebConsole but it does reclect on the device itself (Example change the name).
Hello, I need to rename several devices and have seen that this should be possible through CA. I want to use the macro %AUTONUM%. CA has been followed as per following links: https://discussions.soti.net/articles/000002293 and https://discussions.soti.net/thread/bulk-device-rename I have created a CSV file with the correct content, and the CA is populated at Device Details, which is also visible there. The problem is that the device is named exactly "Model Name %AUTONUM%", that is, the macro does not work correctly. I've also seen that you can send a script (included in the previously referenced links), but it makes no difference. Should this work or not?
Hi all. Just wondering how to effectively to carry out the above? I can't remember what was done to grant TLS connectivity via mobicontrol admin or the server and the majority if not all devices that used TLS 1.0 have been deprecated so we no longer want enrolment/deployment to be able to carry out on TLS 1.0 going forward and certainly want to block TLS 1.0 Is it as simple as just removing / disabling the correct SHA1 certificate from admin? Will that throw up any warnings on the dashboard or is there some functionality required from TLS 1.0 we aren't aware of? Is there any specific ports we may have opened that use TLS 1.0 that can be safely removed? Mobicontrol server 15.5.1.1010 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.
