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.
Is there a posibility to start Soti Surf from a lockdown shortcut directly in Downloads screen? I'm using Surf for one of our internal web apps, and endusers are downloading pdf documents and photos. I'm looking for a way to give endusers access to that downloaded files (without access to other files, so shortcut for myfiles or other file explorers is a no go) Tried to check the activity for the Downloads screen in SOTI. Current activity name: net.soti.surf/.ui.activities.DownloadContentActivity Are there some sendintent scripts that could work? MC Version: 15.6.3.1018 Devices used: Zebra with Android 10/11/13 Thanks in advance
Hi, I added a file sync configuration on our device, before updating to the latest version, I can see the file sync results in the servers menu -> file system manager. However, after updating to the latest version we can't find that menu, how do I see the file sync results?
I am looking for a way to delete the lockdown template file from a device. Revoking the profile has left the lockdown file on the device, and now it has become impossible to install new lockdown profiles on the device. Is there any way, either manually or using a script, to remove the lockdown file from a device?
Hello, My PDAs DT50 go into black screen from time to time. I have to restart them to return to kiosk mode Do you have an idea ? Version du serveur : 15.6.3.1018 Model : DT50 Manufacturer : Urovo Agent version : 2024.0.2.1131 OS 11 black screen :
I have one TC77, rencently updated to Android 11 which is failing to install the packages, all returning the error Package "XXX" version X failed to install. Incompatible platform / processor / OS. I've same profiles installed in multiple others TC77 with A11 on it. Comparing the devices, the only difference I see is the Agent Version, this faulty device has version 14.1.4.1010 still.I've tried multiple ways updating the agent on the device, but it just won't due it. The same with the plugin, it is not installing anything to the device. I even had someone, at the site, manually run the agent APK. The installation when thru, but once the device rebooted, it was still with version 14. I'm having the device shipped to office to try a factory reset and see if things work from there. But until I have it in hands, anyone has a suggestion of what else I could look into? We have MobiControl on-premise, v14.4.4.1045 (hopefully next year we move to latest version).
Hi everyone :) I have a question about my Zebra TC52 with Android 8.1 at the moment. When I created the packages with MC Studio, the Android max version was Android 10.Now I'd like to upgrade those TC52 to Android 11. I tried with one TC52 and it seems working even with those old packages, but will I have some issues ? What should I do, create new packages ? Thank you !
Hello, It is possible to change device personalized name?
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
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.
