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.
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 As we know, in MobiControl, there's an option to assign both a user from Identity or an LDAP (AzureAD, Okta, etc). For our purposes, we use Okta. We have managed to create an application in Okta to create the SAML for authentication/authorization. This part is fine because we can pull some users from Okta. And that is precisely the problem. We cannot find all of the Okta users when trying to assign a user to a device from the MobiControl Dashboard. Is there any troubleshooting I can do there? In my opinion, the integration is done correctly, otherwise I wouldn't be able to find anyone. Thanks a lot
Hi, I want to give permission to allow customers to create users but not let them see and edit users of other customers, how do I do this? Hope there is a workaround for this problem. Many thanks!
Hi, I have some questions about user decentralization, I hope you can answer it, my English is not good, please excuse my ignorance, thanks. In my case I am an agent (Agent S), there are many different active customers and each customer wants to manage their own account. So how can I configure decentralization of those accounts to work properly? I would like to describe how it works as follows: - There are many different customers, I will create for each client 1 main account-identity account (Company A, Company B ...). From their own account, they can create many sub-accounts by themselves to different decentralization (A1, A2, A3 - ...) - How can I configure it according to the following description? + After creating the account "Company A", the account "Company A" is only allowed to configure add / view / edit / delete the account created by account A (A1, A2, A3 ...) + Account A is not allowed to view / modify / delete the sub-accounts created by other accounts, and vice versa. + Account A is only allowed to view / delete / modify Package packages created by account A, not to view Packages created by other accounts. I am look forward to response from you!Many Thanks!
Hello all, I have a table FZ B2 (android 6.0) with a lock down, all works fine but the security service has find a gap ... It's possible to change user, and of course, delete the lock down ...the lock down disapear when you change the user ... I've try to delete ALL USERS under settings ...but it's not possible ... On lock down, i have checked => disable status bar expansion / disable settings change / hide status bar How to reproduce this : tablet sleep, touch on ...touch several time the user (blue icon) and you obtain this screen. After click a other icon represent a user or + , and the lock down switch off ... How i can resolve this ? thanks
Hi all, is there any possibility to select inactive local users which are not connected to MC for 90 days? Afterwards it would be fine to delete these users automatically. Our MC-Version is 13.3.0.3851 Best regards, Marcel
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
