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.
Hi Everyone, I configured the Shared Device function on a onpremise server with a connection to LDAP. We can see the user group which we want to add. When we try to login into the account we always receives an error and it is also unable to "reset" this error without disableing the shared device function. Do you guys have any idea what is wrong? MobiControl Version is 15.4.0 MobiControl Agent version: 2024.0.2Some screenshots were you can see the error:
Hello guys, I have an LDAP connection setup and working, can connect through it in the webconsole .. I can recover my LDAP groups in the Users/groups directories. If i had a group i'm belonging (or whoever) as adminstrators, then i had Shared Device Configuration to my devices with the group i'm belonging. (samsung S7 FE for example). My device now show the Shared Login screen, and on that screen if i input my username/pwd, it authenticate (success shows in logs). But return a message "Failed to authorize user 'username' because the user is not permitted in the shared device configuration" Agent V15.4.3 Build 1054 Server : 15.3 Any ideas on that ? Thanks !
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
I am attempting to enroll a Windows 10 laptop onto our SOTI MobiControl server (running version 15.2) using LDAP authentication against our on-premise Active Directory. I have set up my rule to include the group with the most permissions in our AD for enrollment purposes I have confirmed that the domain user that I am using is a part of this group and possesses all the necessary permissions However, when on the laptop, I successfully join it to our domain, but nothing ever gets enrolled on the SOTI side. Could someone point me in the right direction for where to troubleshoot or even provide a solution for how to successfully join a laptop to a domain and SOTI simultaneously?
Hi Guys, Is this possible (I am not aware of this option): Is there an option to limit Devices per User, so that one Useraccount e.g. only have two devices registered?We're using authentication within the Add_Device Rule. Is there any change to set up a limit so that one AD-User can only register one Device with his credentials and "block" the authentication for a second or third device? MC-Version: 14.4.9.1034
Hello, i am running MobiControl version 15.1.2.1035 on premise We are using the instance for about 2 months now. We added our ldap for the enrollment andto login on the web console. Out of nowhere some ldap users are not able to login anymore. I checked some users and somecan login and some get the error message "Invalid credentials, please try again!" I tried to delete the ldap user and add him again. But made no difference. Then i tried to restartall services but didn't helped too. Then i tried to create a new ldap user and add him to mobicontrol. Even the new ldap user wasnot able to login. Then i checked the logs. The logs kinda irritated me because it was saying different error messagesbefore and after i restarted the services. At first it was saying that the user is using the wrong credentials and that he should use the correct ldapcredentials to login using domain\username. And later it was saying that there is no access right definedfor that user. That does not make sense because he is part of the admin group in MC with full rights. There were no changes in the ldap database for those users. No one touched the configurations on theserver, ldap server or withing mobicontrol. So has someone an idea how i could fix this? EDIT: requests from the api no longer work either
please, is someone could help me find a solution to this error message that appears on my screen when trying to enroll a laptop with Windows10 professional 1909 os/version : 18363.900 to a Soti-MC cloud instance, knowing that LDAP is already successfully configured on Soti-MC settings, as well as a modern windows rule
Hey Guys, we're testing a Failover this month, where our Primary Domaincontroller gets off for a few hours. My question is: how do you set a failover LDAP-Server in Soti? I only can set up a single server in the Config: Do I have to create a new LDAP-Config similar to the active one and only change the Server-Name? How did you set up the LDAP Configuration with multiple Domain-Controllers? Thank you!
Hi everyone, i have some trouble enrolling my devices with LDAP on MC version 14.3 The server cant find my users or groups. It was working without anyproblems before i updated MC from 14.2 to 14.3. I noticed in the directory service connections the new pane "ID" atgroup attributes and user attributes. This pane seems to be new andit is used for the GUID ( Globally Unique Identifier). But our LDAP dont have this attribute. Do i need the GUID to get myenrollment with LDAP work again? Or has someone else the same issue?
Hi all, Can virtual groups make a dynamic update of the LDAP targets? If i make a virtual group LDAP targets are assigned, later if the user is not member of the LDAP group anymore the device is still there.
Hi, I would like to publish Our Active Directory, in the platform SOTI Mobicontrol Cloud, my goal is to prohibit the direct communication between AD and the platform MobiControl Cloud.Please send me the procedure with the steps to set up the Cloud Link Agentthank you in advance
We keep having issues whereby multiple users are being randomly unassigned from Samsung SM-T365 (Android) devices for no reason whatsoever. Whenever this happens their Exchange profile is removed and we see the below entry in the log file for the device: Device Configuration removed ([EAS Settings] Configuration is being uninstalled) We are then able to re-assign the user and the Exchange profile is automatically re-added, however this is getting quite annoying! We are currently running Soti MobiControl v13.2.0.3247 Has anyone else seen the same issue? Thanks, Stuart
Hello, I made the setup for LDAP server and created the special group in Active directory. I added this group thru the Manage Users MobiControl Security User/Group tab and granted MobiControlAdministrators permission. I added to this group several number of users thru the AD snapin. However, when I try to log in to Soti with AD account - I get the following error: ********************************************************************** Exception: Authorization Server Host: Failed to authenticate user **********************************************************************[BusinessLogicException: Parameter username has invalid value ruuxxxxxx.] at Soti.MobiControl.Providers.Ado.Legacy.SecurityPrincipalProvider.GetByNameDomainLdap(String name, String domain, String ldapConnectionName) at Soti.MobiControl.Providers.Ado.Legacy.SecurityPrincipalProvider.GetByName(String name) at Soti.MobiControl.ManagementService.AuthorizationService.Authenticate(LogOnRequest request, Boolean& isAdUser) at Soti.MobiControl.ManagementService.AuthorizationService.InitialUserSession(LogOnRequest request) at Soti.MobiControl.ManagementService.Security.AuthorizationManager.AuthorizeWithUserCredentials(String userName, String password, String source) at Soti.MobiControl.Security.AuthorizationServer.Controllers.AccountController.<LogOn>d__5.MoveNext() ********************************************************************* Should I make some additional setup ?
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
