There's a new home for Articles. Find Articles on Our Product Support Page.
Good Morning, I am trying to update several of our apps on our devices. I am getting a failure on some apps and it reads "Failed to install i/o error". I have tried repackaging the APK, Finding a different source for the APK and so far no luck. Is there a script available that I could include in my package build? A script to maybe uninstall the previous version of the package? I wonder if i am confusing the device on what it should install.
Hello, everyone, In the factory that I work we have pending to carry out an update of a sw that uses the TC51 / 52 terminals that we have installed. And as a result of how the factory is distributed, the following problem arises, I have to generate a QR code that helps me create an example number: 3, and then from SOTI use a custom data that looks at that number to activate a relocation rule, but I totally don't know how this QR code can be created, I have tried StageNow but I can't. I don't know if anyone has had a similar situation or if they could give me any advice. I am new to this job and my knowledge of this world is limited. Thank you all very much in advance. All the best.
Hey there! I'm trying to integrate MobiControl with ServiceNow. To achieve this I'm trying to get the access token in Servicenow using token POST api. But I'm not able to make successful connection and get the Access Token. I guess I'm making the below mistakes 1. Not converting the Client ID and Client secret to correct RFC2045 MIME Base64 - How do we do this? I'm using notepad++ MIME Tools to convert. Is this correct? or am I doing it wrong? 2. I'm little confuse on how to use the Grant Type? It says follow the below format POST https://server.domain.tld/MobiControl/api/token HTTP/1.1 Host: server.domain.tld Authorization: Basic QXBwbGljYXRpb24xOkFwcGxpY2F0aW9uMVBhc3N3b3Jk Content-Type: application/x-www-form-urlencoded Content-Length: 53 grant_type=password&username=Administrator&password=1Attaching the image how I can do in ServiceNow, not sure it's correct Error I'm getting while calling the API javax.net.ssl.SSLException: Connection reset When I use postman for the same I'm getting "error": "invalid_client" I appreciate any help! thank you in advance.
Hello everybody, I wanted to make the following query about the Android update system through SOTI. We are implementing a system, in which, during several days of the week, the update file would be copied to the various terminals, and on a different day the update would be installed. The problem is, that during the tests we had a mishap, according to the logs of the SOTI rule that is responsible for copying the files to the terminals, this file had been copied correctly in all the terminals, but on the day of execution, We checked that only a certain number of them had been updated, we checked the terminals and to our surprise, they did not have the update file copied but in the rule logs it appeared the opposite. At this point, I thought about using an .xml file to create a custom data, so that it would be downloaded together with the update file, but when redirecting the custom data to the xml information, it did not detect it and in SOTI The field does not appear, the name of the custom data does appear but without information. Has something similar happened to someone else? What update systems do you have implemented for android terminals? Do you have any ideas or suggestions about how I could solve the custom data problem, or any improvement for the update system? My SOTI version is: 14.1.5.1284 and the terminals are mostly TC52 and WT6000. Thank you very much to all.
When we try to access out internal site, we received this warning error "There's a problem with this website security certificate. Proceed anyway" We have a certificate that we can install to fix this error If we access the link to the certificate manually, from the device, we could download the certificate and install it My problem now is, I need to deploy this to multiple devices, so I need this done via a profile or a script I did assigned a profile to keep the certificate in the SD card and tried to import it, but it did not installed properly The script i use to run them is as below, but none of them seems to work certimport -cert "/sdcard/xxxx" -ctype cert certimport -cert "/sdcard/xxx" -ctype certificate_type -itype "install_type" certimport -cert "/sdcard/xxx" -ctype certificate_type -itype "install_type" -storage "storage_type" Certificate is a chain, private root CA and private TLS CA certificate The manual installation will put the certificate here in this location Settings > Security > Trusted Credentials > User When I used the certimport script, it will move my cert from the SD card, but I dont know where it went And the warning will still be there, and the certificate are not in the desired place. Any advise on how I can have these certificate install automatically? Thank you
hi everyone, so recently i enrolled about 80 Samsung A01 devices, and my client push 1 application to the device. The apps is hybrid, and the user of the devices sometimes face blank screen when open the apps. The apps maker ask if SOTI interrupt the process of the apps. Told him already that SOTI has nothing to do with the apps. We tried on 1 devices that not enrolled to SOTI and the issue still happened (blank screen). We (me and my end user) suggest the apps maker to create a mechinism to kill the apps if the apps idle for 1 hour. We suspect that might be the issue. Just wanna ask anyone here experience something like this when do enrollment with SOTI ? I am sure SOTI won't interrupt any apps, but i feels like to share this here in case anyone experienced same kind of issue during SOTI enrollment. Thanks & regards, Randy
Hi, I've created an Advanced Data Formatting rule within DataWedge for a Zebra TC25 that has 27 actions to convert each letter of the alphabet into uppercase when scanning a barcode. The rule works fine, however, I then exported the profile, saved it on our SOTI server and pushed it back out to my device via a SOTI rule (saving it in /enterprise/device/settings/datawedge/autoimport) the rule is created, but none of the actions are present. However, if I copy the file to the device and use the manual import profile function within DataWedge it works fine. Has anyone had similar issues? Regards Steve
Hello everybody, I have the CC6000 tablets from Zebra here. We have a standard for naming devices in our network. Currently they are displayed on the DHCP server with android23ab23ab23ab, for example. But I would like to rename it to ZebraDevice01 for example. Is there a function to do this directly via SOTI or possibly via a script command? I have already tried to do this via the developer options. Unfortunately, this is not possible on the tablets. In addition, given the number of devices, that would be very tedious. Thank you for your help.Pascal
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
Good Morning. I am wondering if there is any way to add features to the Settings Manager. Currently we have a Kiosk on our devices that limit what the user can see/access. One of the things that has came up is needing to print off the android tablet using WiFi-Direct. We are in a specific situation where our DOT truck drivers use tablets connected to a backseat data plan in order to capture driving logs and what not. They are needing to use their tablets to create bills of ladings and print them, all while being connected to the truck's PCG backseat data plan. Unfortunately, we cannot connect a printer or any other devices to that source of WiFi. the solution i have found is to use WiFi Direct via the tablet settings while in admin mode. These settings are not available to the user. I can Connect the printer and put the tablet back in Kiosk mode, but once the internet or printer disconnects, i am needing to go into admin mode and set it all up again. I think it would be easier to have access to Wifi-Direct through the Settings manager. Is this Possible? below is a screenshot of the setting i am needing.
Hi, We have upgraded a few of our CK65 devices to v.9 from v8.1. Afterwards we got a weird issue - it's no longer possible to scroll up/down on the AX website. I have tried with different browsers - same thing. So I guess it something between v9 and the AX IIS config. Any ideas? Worst case, any input to how we downgrade the firmware back to 8.1? BrThomas
Hi, Can you please let us know the Google chrome version of our current SOTI Surf Browser 15.2.1.6 When I used the SOTI Surf browser version 14.4.2, faced the browser compatibility issue and our vendor said that would support their URL access the Google Chrome version 55 above. Before roll out our SOTI Surf new version 15.2.1.6 would like to know which version of google chrome is built.
Does SOTI Local installation and provision package setup need a domain purchase? We do have devices all over Canada. The provisioning package created a few times with Windows and Windows Server 2016, which didn't work. Every day the SOTI employee saying different things, he installed SOTI MobiControl on Windows 10 and tried to create a Provision package, he failed and said Windows Server 2016 needed. I installed Windows Server 2016 and he tried again to create a provisioning package without any success. Now, I am confused about the ability of some tech support people in SOTI. What I need to make SOTI run from local installation, I need a very specific answer. We do have around 350 devices all over Canada.
Hello, Moreso a general management question, curious what others do. We are starting to get from a casual SOTI user to running nearly a thousand devices in the future. We have around 6 or 7 apps we push to devices that regularly require updates. In the past I've been simply using separate kiosk profiles and then a package profile (so 2 per device) with each of our locations having a dedicated package profile. That way, we could test package updates in one location before pushing it out to the rest. However updating 40 locations individually for packages is a pain. So I was thinking of just having a test package profile, and then a production package profile and applying the test to one to an OU while deassigning the prod profile. But removing profiles, adding new ones and switching it around seems risky. Other possibility is having a package profile for each of our apps, and setting the packages to never uninstall upon revocation. Then, for testing, I could just deassign it from all locations and assign it to our testing, then switch it back to all location for prod. Devices with the app shouldn't have it removed, but then again I'm not sure I want to test that on a large scale. TL;DR how do people manage dozens of locations as well as multiple kiosks/packages profiles in SOTI efficiently?
Dears, I am trying to enroll Samsung Mobile A01 Android 10.1, the steps i did is: - Brand new mobile, Start, set the link on google email, AFW#mobicontrol (Android Enterprise) and it install the agent with no issue, and when you go to my SOTI License , you can see that it took a license, and you can run the application and add the enrollment id, until this point everything is fine, but after enrollment id success, the Soti Mobicontrol agent open and it give a msg, Your License is not Activated, this could take until hours sometime foe it to find the license and work and some time it dont. Mobile Samsung Galaxy A01 Version 10.1 Android any support on why its takes long time to work ? and the cure for it.
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.