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.
We are having issues enrolling Samsung A32 devices into Mobicontrol, the process fails on the creating google account part, we have been able to enroll other device models using the same rule, bot running Android 11 but the A32 devices always fail on the account creation, in the logs is a 'Empty Token' error. Has anyone had a similar experience and managed to resolve?
We have received some A32 to be enrolled in our MC 14.4.4.1045. After we set the afw#mobicontrol it starts to download the MC Agent (now it is 14.5.3.....) At this time we receive a message telling the Operational System is not original. (It is not possible to create the work profile. The security policies denies to create a managed work device, because a customized Operational System is or has been installed on this device). The OEM Version of it looks as original (RP1A.200720.012.A325FXXU1AUF2) The mobile is just out of the box. As it is Android 11, we are enforced to grant permissions individually to the Agent, before it goes on (access any file, manage system and so on). If we go forward the Agent install but at the time to create the google account, it hangs on the PlayStore account requesting to recreate account by identity confirmation: (Confirm who yo are. You log off google account , please log in to continue). On the next screen it does not allow to type in any entry. And Click on next, it fails. After hanging in this screen, we have tried to go by download the MC Agent from the server. Then we have proceed by a factory reset and skip google account. Installed the agent by our server. The issue starts as it comes as Android instead of Android Enterprise(the download agent was Enterprise). And again, it does not create the google account, presenting the screen as pending action to create a work profile in the device. (Work Profile Provisioning. Click Here to configure a work profile). It never creates the work profile as the click had no effect. Has anyone had a good installation for Samsung A32 ?
I am trying to enroll a Samsung x cover pro 2 via afw but once I enter my enrollment id into mobicontrol. I will get: Enrollment Failed. Please retry or contact your system administrator. I have tried enterprise and plus with the same result have also tried both google play install and from the website. I believe it has something to do with Knox as I never have this issues with my zebra's only with Samsung's and only every once and a while. Currently on V14.1.8.1064
Can anyone confirm any recent changes to Android Enterprise enrollment for Zebra devices? Maybe I missed something somewhere, but I just AE-enrolled a Zebra TC52 and never got prompted to enable "Modify system settings" or "Notification Access". When I compare devices two devices, one previously enrolled (i.e. months ago) vs today I notice some differences and consequences. Bad Device - New Enrollment Supported APIs Zebra RC Work Managed Device Android Zebra EMDK Plugin Version NOT INSTALLED Prompted on Device to Start Remote Control Session Good Device - Old Enrollment Supported APIs RC Virtual Display Work Managed Device Android Zebra EMDK Android Plus 1.6 Plugin Version 1.6.0.102 Everything else about the devices is identical. Looks like the issue is the plugin is failing to install during enrollment.
So I am trying to setup our device enrollments on an FTP server. Part of the Enrollment is the JSON file that holds the Enrollment ID. With something like the Agent file I can select to use and external source. I store the Agent on an FTP server and enter "ftp-p://USERNAME:PASSWORD@ftp.domain.com:21/Agents/GoogleMobiControl1442_1039.apk" in the external source. I do the same thing with the .bin file for the deployment package. This works great and I love it. Now when I get to the JSON file it only lets me select a file from my PC, I do not get a selection for an external source. So does anyone know how I can do this or a better way of getting the enrollment ID to the device? Thanks!
Hi All im hoping someone may be able to help with the below We Had an issue recently whereby the CA Enrollment certificate had expired without anyone noticing. the certificate was replaced successfully but I would like to be made aware when this cert is due to expire again.the certificate does not seem to exist within the certificate store on the Soti Deployment or management server and is also not mentioned within the administration Utility under certificates (the others are) Can anyone enlighten me as to where I might be able to see this certificate or at least some of its properties?, I also reviewed the logs for an indicator that this problem was apparent but there was nothing seemingly pertinent to an expired certificate Any Help would be much appreciated Kind Regards Richard
Hello, I've got an Erro while Enrolling Android Enterprise Devices. "SSL Handshake Failed". I tested devices of differnt manufacturers. For me it looks like there's a problem with the database? It's on an seperate SQL Server. Anybody knows this problem? Thanks for your help! This is my Error Log from the Soti Server: 2020-12-21 15:34:38,596 (0x00000d9c) [INFO ] < 41> Comm.Client.7: Accepted a new connection from [::ffff:10.150.0.72]:45162.2020-12-21 15:34:38,627 (0x00000d9c) [ERROR] < 41> Comm.Client.7: Error authenticating client [::ffff:10.150.0.72]:45162: System.Security.Authentication.AuthenticationException: Fehler bei SSPI-Aufruf, siehe interne Ausnahme. ---> System.ComponentModel.Win32Exception: Beim Verarbeiten des Zertifikats ist ein unbekannter Fehler aufgetreten --- Ende der internen Ausnahmestapelüberwachung --- bei System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult) bei System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result) bei System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Soti.Comm.Client.<OnReceived>d__48.MoveNext()
Hello together, in the past few weeks I upgraded the SOTI server version from 14.x to 15.1.x. In the time I have not actually installed any new devices. Because of this I have no reference since when the problem exists. But I think that this is a different problem... Devices that were already staged in the system and are only formatted, can be installed again without problems and included in the platform. This error apears on a fresh, new installed device: "Enrollment failed. Please retry or contact your system administrator." The current SSL certificate from SOTI is stored in the server. The device also starts an SSL handshake and asks for a manual confirmation for the trust check of the certificate. I have added the deployment log to the attachment. Here are two errors, which were suspicious: [2020-12-17 07:53:27.538] DEBUG [Management] (DeviceCheckInService): [DeviceCheckInService.WaitUntilNextDeviceCheckIn] Waiting for more device check-ins (max 00:00:20 seconds)[2020-12-17 07:53:36.353] INFO [General] (59): Outgoing response [][2020-12-17 07:53:47.543] DEBUG [Management] (DeviceCheckInService): [DeviceCheckInService.WaitUntilNextDeviceCheckIn] Waiting for more device check-ins (max 00:00:20 seconds)[2020-12-17 07:54:07.553] DEBUG [Management] (DeviceCheckInService): [DeviceCheckInService.WaitUntilNextDeviceCheckIn] Waiting for more device check-ins (max 00:00:20 seconds)[2020-12-17 07:54:08.775] DEBUG [Database] (49): Execute StoredProcedure: [dbo].[GEN_Settings_Get][2020-12-17 07:54:08.775] DEBUG [Database] (49): Parameters: @Name = MaxDeviceStatusReportRequestThroughput[2020-12-17 07:54:27.555] DEBUG [Management] (DeviceCheckInService): [DeviceCheckInService.WaitUntilNextDeviceCheckIn] Waiting for more device check-ins (max 00:00:20 seconds)[2020-12-17 07:54:47.566] DEBUG [Management] (DeviceCheckInService): [DeviceCheckInService.WaitUntilNextDeviceCheckIn] Waiting for more device check-ins (max 00:00:20 seconds)[2020-12-17 07:55:07.568] DEBUG [Management] (DeviceCheckInService): [DeviceCheckInService.WaitUntilNextDeviceCheckIn] Waiting for more device check-ins (max 00:00:20 seconds)[2020-12-17 07:55:08.788] DEBUG [Database] (49): Execute StoredProcedure: [dbo].[GEN_Settings_Get][2020-12-17 07:55:08.788] DEBUG [Database] (49): Parameters: @Name = MaxDeviceStatusReportRequestThroughput[2020-12-17 07:55:12.063] DEBUG [Android RESTful Enrollment] (55): 554cb274-9afb-4783-bd02-7cfcbe25e5c9 CT60 3e2b64be-38f1-4a5f-b0f6-cf891a6866ef Android enroll request { addDeviceRuleId = 1033, addDeviceRuleTag = , deviceNameFromIniFile = , agentUniqueId = 554cb274-9afb-4783-bd02-7cfcbe25e5c9, authenticationToken = , acceptedTermsAndConditionsUrl = , isDeviceGmsCertified = True, isOemAgent = False, androidBuildVersion = 27, deviceIp = 10.114.30.191, deviceFirmwareVersion = , DeviceId = 0c23692c9XXX, BluetoothMac = , WifiMac = 0c23692c9XXX, Mac = 0C23692C9XXX, SerialNumber = , HardwareSerial = 20247D8XXX, Oem = Honeywell, Model = CT60, safetyNetAttestationStatement = , safetyNetAttestationErrorMessage = }[2020-12-17 07:55:12.063] DEBUG [Android RESTful Enrollment] (55): 554cb274-9afb-4783-bd02-7cfcbe25e5c9 CT60 3e2b64be-38f1-4a5f-b0f6-cf891a6866ef CheckForCompatibleAgent begins[2020-12-17 07:55:12.063] DEBUG [Android RESTful Enrollment] (55): 554cb274-9afb-4783-bd02-7cfcbe25e5c9 CT60 3e2b64be-38f1-4a5f-b0f6-cf891a6866ef CheckForAllowedAgent begins { isOemAgent = False, androidBuildVersion = 27 }[2020-12-17 07:55:12.063] DEBUG [Android RESTful Enrollment] (55): 554cb274-9afb-4783-bd02-7cfcbe25e5c9 CT60 3e2b64be-38f1-4a5f-b0f6-cf891a6866ef CheckForAllowedAgent returns - AE Agent[2020-12-17 07:55:12.063] DEBUG [Android RESTful Enrollment] (55): 554cb274-9afb-4783-bd02-7cfcbe25e5c9 CT60 3e2b64be-38f1-4a5f-b0f6-cf891a6866ef SafetyNetAttestation skipped - Enroll on SafetyNet Attestation Failure[2020-12-17 07:55:12.063] DEBUG [Android RESTful Enrollment] (55): 554cb274-9afb-4783-bd02-7cfcbe25e5c9 CT60 3e2b64be-38f1-4a5f-b0f6-cf891a6866ef Target Device Group ID defined. { targetDeviceGroupId = 1074 }[2020-12-17 07:55:12.063] DEBUG [Database] (55): Execute StoredProcedure: [dbo].[Device_GetAndroid_bySerialNumberOrMACOrWifiMACOrBluetoothMAC][2020-12-17 07:55:12.063] DEBUG [Database] (55): Parameters: @SerialNumber = @MAC = 0C23692C9XXX @WifiMAC = 0c23692c9XXX @BluetoothMAC = [2020-12-17 07:55:12.063] ERROR [Android RESTful Enrollment] (55): Unhandled exception on POST https://serveraddress/mc/enrollments/android {"AddDeviceRuleId":1033,"AddDeviceRuleTag":null,"AcceptedTermsAndConditionsUrl":null,"IsDeviceGmsCertified":true,"IsOemAgent":false,"Snapshot":{"DeviceName":null,"Info":{"Uuid":"554cb274-9afb-4783-bd02-7cfcbe25e5c9"},"SafetyNetAttestationResponse":null,"ApiLevel":27,"OSType":800,"DeviceFirmwareVersion":null,"Ip_And_IpType":{"Ip":"10.114.30.191"},"ImsiNumber":"","Esn":"Unavailable","Iccid":"","PhoneNumber":"","Mac":"0C23692C9XXX","SerialNumber":"","Model":"CT60","Oem":"Honeywell","PersonalizedDeviceName":"CT60","LockScreenMessage":null,"Id":"0c23692c9XXX","BluetoothMac":"","WifiMac":"0c23692c9XXX","HardwareSerial":"20247D8XXX","Imei":"Unavailable","SupportedApis":{"ActiveMdmIds":[1040],"RcId":"813"}}}System.InvalidOperationException: Unable to match devices by criteria. at Soti.MobiControl.DeploymentServerExtensions.Android.Resolvers.DefaultEnrollmentLookupResolver.GetClosestDeviceMatch(HardwareCriteriaModel[] devices, AndroidDeviceMatchLookup criteria, IReadOnlyDictionary`2 deviceSnapshot) at Soti.MobiControl.DeploymentServerExtensions.Android.DeviceEnrollmentLookup.GetPreviousDeviceEnrollment(IReadOnlyDictionary`2 deviceSnapshot) at Soti.MobiControl.DeploymentServerExtensions.Android.DeviceReEnrollmentDetectionService.IsReEnrollment(DeviceIdentity deviceIdentity, String& oldDeviceId, String& oldDeviceName, Nullable`1& oldDeviceGroupId) at Soti.MobiControl.Components.Enrollments.Android.Enrollment.EnrollmentService.Enroll(Nullable`1 addDeviceRuleId, String addDeviceRuleTag, String deviceNameFromIniFile, String agentUniqueId, String authenticationToken, String acceptedTermsAndConditionsUrl, SafetyNetAttestation safetyNetAttestation, Boolean isDeviceGmsCertified, Boolean isOemAgent, Int32 androidBuildVersion, DevicePlatform devicePlatform, String deviceIp, String deviceFirmwareVersion, DeviceIdentity deviceIdentity, String imsi, String esn, String imei, String iccid, String phoneNumber, String personalizedDeviceName, String lockScreenMessage, DeviceApi[] supportedActiveMdmIds) at Soti.MobiControl.Components.Enrollments.Android.Enrollment.Web.EnrollmentController.Enroll(EnrollmentRequest enrollmentRequest) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)--- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()[2020-12-17 07:55:13.425] DEBUG [Android RESTful Enrollment] (38): 554cb274-9afb-4783-bd02-7cfcbe25e5c9 CT60 e3189792-fbc2-4acd-8f26-acd633f69f6f Android enroll request { addDeviceRuleId = 1033, addDeviceRuleTag = , deviceNameFromIniFile = , agentUniqueId = 554cb274-9afb-4783-bd02-7cfcbe25e5c9, authenticationToken = , acceptedTermsAndConditionsUrl = , isDeviceGmsCertified = True, isOemAgent = False, androidBuildVersion = 27, deviceIp = 10.114.30.191, deviceFirmwareVersion = , DeviceId = 0c23692c9df6, BluetoothMac = , WifiMac = 0c23692c9df6, Mac = 0C23692C9XXX, SerialNumber = , HardwareSerial = 20247D8XXX, Oem = Honeywell, Model = CT60, safetyNetAttestationStatement = , safetyNetAttestationErrorMessage = }[2020-12-17 07:55:13.425] DEBUG [Android RESTful Enrollment] (38): 554cb274-9afb-4783-bd02-7cfcbe25eXXX CT60 e3189792-fbc2-4acd-8f26-acd633f69f6f CheckForCompatibleAgent begins
I have trouble when enrollment laptop windows 10, I do it based on certificate, not long ago I did it successfully, and it works normally, but now it doesn't work anymore.I hope to receive your support. Many thanks! https://ibb.co/mXNNzL4 https://ibb.co/g4VnPdrhttps://ibb.co/n7Lz2mg
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 forumers I have enrolled more than 300 Android 10 smartphone devices using "Skip google Account Addition during enrollment". Due to customer needs changes I need now to move to "Managed Google Account" for Android Management. Question : is it possible without the need to need to unenroll & reenroll all devices ? If yes how can it be done ? Script command? thx. steve
I am looking for the easiest method to enroll android devices. Please correct me if i am wrong on any of the points below and guide me. I want to use Android Plus mode because 1. it requires the device to be facory reset 2. AP mode supports more functionalities as it is designed specifically for each brand and model sperately where as AE is generic and some functioalities may not be available for some devices. 3 . It is mainly for BYOD work managed devices and doesn't support device admin mode 4 . It requires internet connectivity on the devices as it uses google services So in Android Plus mode, currently i have the option to download the agent from my SOTI server or from SOTI website , but in both cases i have to manually install the agent , also i have to enter the enrollment id manually. Is there any way to hardcode the enrollment ID in the agent and it automatically gets enrolled after the installation ,i.e., without entering the enrollment id manually or scanning ?.Also is there any way to auto install the agent without opening the apk manually ?.I just read about mobicontrol stage, is it a free app comes along with mobicontrol device license Or we have to purchase it seperately ?
Factory resetting Android tablet with afw#mobicontrol and get the "SSL Handshake Failed" error after entering the enrollment ID. "The cert for this server is invalid. You might be connecting to a website that is pretending to be....." We access our deployment server via the cloud. MobiControl v14.1.5.1284 OS v10 Agent v14.4.0.1028
Hi all We are currently testing a Honeywell CT40 for a possible deployment. Is it normal that when we enroll android devices as enterprise managed, there's several system apps that disappear ? (i.e: camera, gallery ...) Now we have to retrieve the exact bundle ID and install the apk Any inputs ? Thanks,
Hi, I have a odd new issue on our MobiControl server related to enrollment. We use version: 13.4.0.4167 The issues is that we cannot enroll new devices as the process does not complete on the client side. We have tried both Android Enterprise (afw#mobicontrol + QR code) and Android Plus. The devices does pop up in mobicontrol, but the install is not completed on the devices - therefore they kind of errors with a re-try option and in the end you come back to the page asking for Enrollment ID. Not sure how to fix this, as it suddently occured this morning. Anyone experienced something similar and what did you do to fix this? /Dan
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.
