There's a new home for Articles. Find Articles on Our Product Support Page.
I have new rule and alert when unenroll device from console and i want to add custom attribute in to email body but i can not what syntax of custom attribute
After update SOTI to version: 2024.0.0.1075 I can't enroll tablet Unitech TB85 (android 8). Error form Diagnostic Deployment Server Extension Log [2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a Android enroll request { AddDeviceRuleId = , EnrollmentPolicyPin = , AddDeviceRuleTag = 3EEB54A4-D9F8-F23C-1831-B2DFDBD9125F, DeviceNameFromIniFile = , AgentUniqueId = e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8, AuthenticationToken = , AcceptedTermsAndConditionsUrl = , IsDeviceGmsCertified = True, IsOemAgent = True, AndroidBuildVersion = 26, DeviceIp = 10.82.136.109, DeviceFirmwareVersion = , DeviceId = 351957100075379, BluetoothMac = 98AAFC23C7DB, WifiMac = 98aafc23c939, Mac = 98AAFC23C939,SerialNumber = 351957100075379, HardwareSerial = 19a1cc96, Oem = k-touch, Model = TB85, safetyNetAttestationStatement = , safetyNetAttestationErrorMessage = , playIntegrityAttestationStatement = , playIntegrityAttestationErrorMessage = }[2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a CheckIfCopeProvisioningRequired begins Android41Enterprise isCope:True BuildVersion:26[2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a CheckForCompatibleAgent begins[2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a CheckForAllowedAgent begins { isOemAgent = True, androidBuildVersion = 26 }[2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a CheckForAllowedAgent { allowedAndroidType = All }[2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a CheckForAllowedAgent returns All[2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a CheckForAllowedAgent begins { isOemAgent = True, enrollmentPolicyKind = AndroidEnterprise }[2023-12-07 14:02:15.721] DEBUG [Android RESTful Enrollment] (177): e974faf7-ff8b-40bb-abdb-f3d87ba2bfd8 TB85 7ce6ee86-743f-4360-b5c9-cfac66cc241a CheckForAllowedAgent enrollment canceled AndroidEnterprise[2023-12-07 14:02:15.721] ERROR [General] (177):***************************************** Exception: Error in the application. *****************************************[DeviceCanNotBeEnrolledWithEnrollmentPolicyException: Error in the application.]at Soti.MobiControl.DeviceEnrollment.Android.Implementation.EnrollmentManagementService.CheckForAllowedAndroidType(Boolean isOemAgent, Boolean isWorkManagedType, EnrollmentPolicyKind enrollmentPolicyKind, String failLog)at Soti.MobiControl.DeviceEnrollment.Android.Implementation.EnrollmentManagementService.ValidateDeviceSnapshot(AndroidDeviceSnapshot deviceSnapshot, AndroidEnrollmentPolicy androidEnrollmentInfo, EnrollmentPolicyKind enrollmentPolicyKind, SafetyNetAttestationResult& safetyNetAttestationResult, PlayIntegrityAttestationResult& playIntegrityAttestationResult, AttestationEventStatus& attestationEventStatus)at Soti.MobiControl.DeviceEnrollment.Android.Implementation.EnrollmentManagementService.Enroll(AndroidDeviceSnapshot deviceSnapshot)at Soti.MobiControl.DeviceEnrollment.Android.Web.Implementation.AndroidAgentEnrollmentController.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()**************************************** Error form Deployment Server Logs Device enrollment failed. Devices can only enroll with the AE Agent. Deployment Type is set up 'OEM Specific for All Android Devices'. TB85 are enorolled with Unitech TB85 agent. Android Enterprise does not work on this device. On TB85 enrolled befor upgrade SOTI I can't upgrade agent. Old agent version 15.0.1.1051. New version 15.4.5.1051. In logs I have 'Invalid device software version'.
Hi, We are having difficulty getting around getting the App to few test users who are using SOTI. Do you have specific procedure How we can setup SOTI enrolled devices can get the apps from Google play test tracks. They dont have issues when the app is on the proper release track. Let me know if you have any news / Ideas/ procedure / Answers on this problem
Hi,I use Soti's lockdown profile with an HTML template on Zebra Android TC72s. the disadvantage is that with this profile, the virtual keyboard appears all the time by default, you always have to click on return to bring it down and see the screen clearly.
We have a web application that our users login to with their Active Directory credentials. When they open the application with Surf and start to enter credentials, their password is displayed in the suggested text field. When using Chrome, the text suggestion area is blank. These devices are running Android 11 and it was the same with Android 10.
Hi, I install TeamViewer app with the Managed Google Play. Once installed, is it possible to launch the app automatically? Thanks,
As title says, I have SOTI setup in the US where it has been used with Android Enterprise fairly flawlessly using an enrollment ID. We have a sister site in Italy using the same enrollment ID, but the system admin there says it keeps kicking out the enrollment with this generic message: the application (SOTI APK) is installed but when I try to Enroll the profile using the ENROLLMENT ID, I receive back every time the same error message: “installation failed, try another time or contact the system administrator” Is there something obvious I'm missing where it works for one site, but not the other? Seems odd that two sites with the same network policies, but in different countries would cause the enrollment ID to stop. Also, even weirder was it USED to work about 3-4 months ago, but when tried recently it just kicks out. I'm sure there's probably a log file I need to check, but as a relatively new person to this site and brand new to SOTI completely, I wasn't sure where to look. Our SOTI is Version: 15.3.2.1072 and we are trying to enroll Honeywell/Intermec CK75 rugged scanners (Yes, I know it's technically deprecated and replaced by the CK65, but we have a bunch on hand and want to keep them working)
Is there any way to use Microsoft Power Apps add to home option to add that app to the Lockdown Screen as an app
Is there a way to enable sound notifications from Microsoft Power Apps when being opened from the lockdown policy? All sound settings are enabled on the device and in settings but still no sounds.
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:
Morning Everyone, I am using FileSync in SOTIMobiControl to upgrade the firmware of my MC93 RF terminal. I would like to use mxconfig /sdard/packages.upl as a script set in FileSync but I am getting the message "OS update has failed to install...." on the device. Running it with install_system_update "/sdcard/11-39-27-00-RG-U02-STD-HEL-04.zip" as script set in Filsync works. But I have to do that for each zip file Is there any other way to run the zip files in one command? Thks in advance
Hello all, We have AD/Azure server intergrated to Soti and we are trying to figure out how to use the log in window feature to be able to have users log in using their AD credentials to avoid them having 2 passwords/Accounts. (Local account/ AD accounts) Has anybody else succesfully been able to get this done after intergrating AD/Azure server ? We have a Support case open but wanted to see if anybody else has done this that can give us details. any info is much appreciated Thank you
I've been using our SOTI instance for about 6 months, and enrolled 100 of the identical tablets. Very minimal issues along the way. Nothing has changed in our environment. Now suddenly, as I'm enrolling the next batch of 30 tablets (same model) having nothing but constant issues when pushing the initial profiles that result in installs. I'm trying to install our LOB application, Settings Manager, and XSight Agent. Sometimes none of these fail but more often than not, I have at least 1 failure - sometimes 1 fails, or 2 fails, or all 3 fail. Always the same error - Failed to install, (File I/O error). Clicking revoke profile and then install profile always fixes it. I saw a previous thread here discussing the same issue. Someone mentioned turning on logging, but it's too late at this point, because if I turn it on, it won't fail again a second time. It's just weird it worked so smoothly for the first 6 months and now a bunch of tablets are having the same problem. It's not the end of the world, since there's a manual workaround, but is slowing down the building process slightly.
We have a GooglePlay Store app called SmarterDriver which we deploy to our android enterprise devices and this has been working perfectly until recently when the app was updated in the play store. Now when you launch the app from the lockdown screen you are unable to get past the applications sign in button. Clicking on the button does nothing. Revoking the lockscreen lets you see what is going on - basically after launching the app you get a sign in button, when you click the sign in button this opens a webpage and then you can sign in. Adding the URL to the lockscreen and then clicking on the shortcut link to the URL does allow you to sign in directly to the website which the app is redirecting to, but this is not ideal in case the vendor updates their URL (I know we could push out the URL) There is no change in behaviour when clicking on the app from the lockscreen despite the URL being present as another entry on the lockscreen. Is the only way to get round this to install the app from the playstore as we are already doing but have no entry to it on the lockscreen and instead just have the URL on the lockscreen? Ideally is there some way to whitelist the website without adding it to the lockscreen and without providing an entry point directly to the URL from the lockscreen
Hello everyone, I have purchased a new Zebra TC58 device (Android 11) and would like to be able to control it via SOTI. It has been staged with Android Plus using an Enrollment ID directly, so the SOTI agent is present right after setting up the device. The remote control function is not working correctly because when I try to remotely control the device, only a white screen appears. However, the device activates the screen as soon as I attempt to access it (indicating that it recognizes my attempt to access), but I can neither see the device in the browser nor control it. This issue persists even after reinstalling the profiles, restarting, or checking in. Initially, I thought it might be due to the OS version, so I updated it to 11-25-02.00, but this did not resolve the problem. Have I missed something? Can someone help me further? Thank you and kind regards.
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.
