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.
Good morning, I need to install a specific plugin on some devices, here the details: Manufacturer: Emdoor Android version: 10 Enrollment type: Work Managed Device Agent version: 15.1.5.1049 MobiControl instance version: 15.5.0.1021 I had some issues to access the internal memory (I spoke about this issue in another topic) and because of that SOTI support released a new plugin which should fix the issue. The issue that I have now is that I'm not able to install the updated plugin because MobiControl installs a wrong one. If I click on "Install Device Plugin": MobiControl installs this plugin: Which is wrong, because the correct one is this: My question is: how can I delete the unwanted plugins in order to force MobiControl to install the correct one? I can't find any delete option even if I'm MobiControl administrator. Thank you, best regards.
We have a number of devices that are running with the lockdown kiosk enabled but we need to be able to use Teamviewer QS for troubleshooting/configuration of the 1 specific APK that is used on the devices. Teamviewer QS works like it should when the kiosk is disabled but as soon as we re-enable kiosk mode the Teamviewer remote session only displays a black screen. What do I need to configure/set up to allow for a teamviwer QS session to be run properly with kiosk mode enabled?
Hi, has anyone experienced difficulties in enrolling a device such that it becomes "Non-Compliant"? This is a Zebra TC21, running Android 10, MX 10.4. Enrollment fails, the device DOES end up in the device list however, but cannot be controlled via Soti at all. The enrollment process on the device gives an error. We've tried to enroll on the latest version of the Soti Mobicontrol server, as well as on 15.4. Regards,Daníel
Hello guys, I have a little question. We are enrolling old MC92 with WinCE to a MobiControl 15.5 server on premise. Everything works fine but lately we got one device which doesn´t connect to the server. I got the following logs: Can somebody explain to me what this line means: 2022-07-08 10:26:23,939 (0x00001f48) [ERROR] No Device found with device Id: 73E65B7606490108000A-08C074620600Thanks for your help!
Can anyone provide any insight into where SOTI is with OEMConfig Feedback Channel support, specifically Zebra? I'd like to be able to effectively troubleshoot OEMConfig settings or maybe someone has a better way.
Hey there, I am currently enrolling MX3300x's to our environment and everything seems to be fine but we are getting a message at the bottom of the screen of our kiosk mode saying the following: server policies restricts the use of feature auto_time" then it disappears. I don't know if these will interrupt our users from their tasks but I would like to get rid of the message altogether. It seems to be enrolling at the current time. Not sure where the issue lies.
We have pushed Google Maps out to our Android enterprise enrolled devices (Samsung A7 lite). Google Maps opens and works fine, however when one of our users tries to sign into Maps with their account, we get a message that says "Action not allowed". Am I missing something in the configuration or feature control of the app? we would like to let our users log in with their accounts so they can have all their pins and favorites.
Hi, Is there a possibility to enroll a Samsung device via KME or otherwise with WiFi 802.1X EAP association mode?
Since there is no documentation on how to do this, I thought I’d share it with everyone. You should add Azure Directory first. See this guide: https://discussions.soti.net/thread/how-to-connect-mobicontrol-with-azure-ad In MobiControl – Global Settings – Services – Identity Provider Download the MobiControl Metadata File Go to Azure AD Portal Enterprise Applications New Application Search for and add MobiControl Set up single sign on – SAML Upload metadata file – upload the MobiControl Metadata File you downloaded from MobiControl Basic SAML Configuration should be like this: Identifier (Entity ID) - https://%DOMAIN%/mobicontrol Reply URL - https://%DOMAIN%/mobicontrol/sso/sp/handlelogon Sign On URL – https://%DOMAIN%/mobicontrol Logout Url - https://%DOMAIN%/MobiControl/sso/sp/handlelogout Example: Identifier (Entity ID) - https://s123456.mobicontrolcloud.com/mobicontrol Reply URL - https://s123456.mobicontrolcloud.com/mobicontrol/sso/sp/handlelogon Sign On URL - https://s123456.mobicontrolcloud.com/mobicontrol Logout Url - https://s123456.mobicontrolcloud.com/MobiControl/sso/sp/handlelogout SAML Signing Certificate Signing Options – Sign SAML response and assertion Signing Algorithm – SHA-256 Go to Azure AD Portal App Registrations Find MobiControl – if you do not see it, check under All Applications Manifest Search for “Group Membership Claims” – the value should be “1” with the “ Go to Azure AD Portal Enterprise Applications MobiControl Set up Single Sign On SAML Signing Certificate Download Federation Metadata XML Go to MobiControl Global settings – Services – Identity Provider Select + Name – can be anything Idp Metadata File – upload the Metadata XML you just downloaded Group Settings – Group From – Directory – add you directory Save Testing: Create a new iOS Enrolment User Enrolment Accounts Federated by Microsoft Azure AD – select the directory you just created Based on group membership Select the Azure Idp and search for a group. If you find it, your good to go.
Since there is absolutely no documentation on this I thought I’d share this with everyone. Log into Azure AD and create a group and add a user Enterprise Applications – New Application Search for and add MobiControl Go to the MobiControl application – Users and Groups Add the group you just created Go back to the Azure portal – App registrations Select MobiControl – if you can’t find it, check under «All applications» Certificate & Secrets New client secret Copy «Value» - this is the client secret and will only be shown once API permissions – add the following – note the difference between Application and Delegated ReadWrite.All > ApplicationDirectory.ReadWrite.All > ApplicationDirectory.Read.All > ApplicationGroup.Read.All > DelegatedUser.Read.All > DelegatedDirectory.ReadWrite.All > Delegated Click on «Grant admin consent for…» Go to MobiControl – Global Settings – Services – Directory Select + on Azure Directories Name – can be anything Microsoft Graph API Address – https://graph.microsoft.com Select + on Azure Tenant ID Name – can be anything Azure Tenant Name – this is the primary domain you see in the Azure AD Overview Azure Tenant ID – Tenant ID in the Azure AD Overview Metadata Endpoint Address – you’ll find this under App Registrations – Endpoints – Federation metadata document Select + on Application Name Application name – can be anything Client ID – you’ll find this under Enterprise Applications – MobiControl – Application ID Client secret – the value you copied on step 9 a Save To test, do the following: In MobiControl – Users and Permissions - Groups - + Search for the group you added earlier – if you find it, it works Search for additional groups in Azure to verify connection Troubleshooting: To troubleshoot, check MS log and search for the Client ID. There will most likely be an understandable error message.
I'm looking for a way to view, whether it be through the device name or in the details pane/overview table, what user logs into a modern Windows device. Our users authenticate through Azure AD and we do not utilize an LDAP, so I can't assign users to these devices. We also don't use shared devices, each user is assigned a device for their sole use. Other users are still capable of logging into any of our Windows devices, but the only time that ever occurs is if I need to log in to run and admin task. I also looked into available variables for device name/hostname, but there didn't appear to be a variable available to get the user information I need. Does anyone have any suggestions for how I can best view which O365 user has logged into/is using a modern Windows device?
Hello MobiControl: 15.5.1 iOS: 15.5 2. attempt at creating a post since it is not possible to edit after posting. iOS device has been enrolled as unsupervised, device enrolment with user authentication. App policy installs Outlook and other necessary apps, Conditional Access authorizes access. Customer has trouble synchronising contacts between Outlook on Windows, Outlook on their iPhone and their personal contacts in the Contacts-app. When they go to the Contacts-app on the phone, they only see contacts created on their phone, not contacts from Office 365 or contacts they have created in Outlook on their computer. They want everything to synchronise between each other, like it did before they enrolled their iPhone. I contacted SOTI Support, they had no idea how to fix this. Which is strange since it should be a pretty widespread problem. I have tried with Outlook Managed App Config. I manage to get everything working, except the keys in bold. I have tried different formats like true/ and true, but no success. Like always, little or no documentation is available from SOTI. I have also thought about Exchange Active Sync. Maybe this could synchronise contacts only, while Outlook takes care of emails and calendars. <dict><key>com.microsoft.outlook.EmailProfile.EmailAccountName</key><string>Office 365</string><key>com.microsoft.outlook.EmailProfile.EmailAddress</key><string>%ENROLLEDUSER_EMAIL%</string><key>com.microsoft.outlook.EmailProfile.EmailUPN</key><string>%ENROLLEDUSER_USERNAME%</string><key>com.microsoft.outlook.EmailProfile.ServerAuthentication</key><string>Username and Password</string><key>com.microsoft.outlook.EmailProfile.AccountDomain</key><string>%DOMAIN%</string><key>com.microsoft.outlook.EmailProfile.ServerHostName</key><string>outlook.office365.com</string><key>com.microsoft.outlook.EmailProfile.AccountType</key><string>ModernAuth</string><key>IntuneMAMAllowedAccountsOnly</key><string>Disabled</string><key>IntuneMAMUPN</key><string>%ENROLLEDUSER_USERNAME%</string><key>com.microsoft.outlook.Contacts.LocalSyncEnabled</key><true/><key>com.microsoft.outlook.Contacts.LocalSyncEnabled.UserChangeAllowed</key><true/></dict>
I have been testing a new EDA52 I have and have noticed when enrolling on my 15.2.2.1080 Mobicontrol server I have no Remote/View icons available. The list of supported APIs is also not shown on the device dashboard. No combination of plugins/agent versions or scripts have worked ie . _resetfailedrcdetectionflag restartagent retryrcdetection I have enrolled this same device as a test on to my 15.5.1.1010 server and sure enough Remote control works on this one! As far as I can see I'm using the same agent version/plugins on both servers Agent version 15.2.0.1025 Plugin version 1.19.2.118 The supported APIs shown on the new server are below but as I said this section is missing on the older server. Supported APIs RC Virtual Display, Work Managed Device, Advanced Android Plus 1.18, 1402, 1500 Does anyone have any ideas or have come across this before? Many thanks
Since the initial launch of Soti Discussion forum some 3 years ago, newest posts are always ordered in chronological order in the main pane, allowing anyone to check the latest posts easily with virtually no effort. It is a misfortune the UI has been redesigned such that the posts are based on the initial date of the discussion thread rather. Any number of followed up posts will be hidden under the thread. Hence, a follow-up post sent today on a thread started 2 years ago will be hidden under the discussion thread entry hundreds of row down. Who on earth has the time to go down to each past disccussion thread to see if there is/are any follow-up post(s)? None of the ten Soti Moderators responds to my brought-up concern posted twice in the last two plus weeks. Should I mail directly to the CEO to tell him about this nonsense UI design and inaction of his staff?
Assuming Managed Google play has already been assigned to MC and some applications from the wider public google play are present in an app policy. In the case where we have private applications, does anyone have an opinions/best practise/know of difference/limitations between deploying these applications via Enterprise App deployment vs Adding them as a Private application to Managed google play. Thanks in advance Adam
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.
