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, We got different terminals with Android 8 in the factory and they actually only display in the notification bar the icon of the battery but no his %, i try to find how to configure via StageNow or SOTI that parameter to evade configure the terminals one by one but i cannot find how to make it. Someone know how i can do it?
Hey Guys, actually I'm developing a new lockdown Template which listens to json-Files on the Filesystem to show certain Apps in the lockdown or not. Everything is working so far, but I have to serve all the App-Icons to the device manually, even for installed applications.Does anyone knows how to target the App-Icon within the Lockdown as a path, e.g. /system/package/app1/appicon.png ?How does the SOTI-Magic works within the Lockdown? There are only Placeholders like <img src="<MCExeIcon4>" onerror="this.style.display='none'" /> but works as charme. How does the MCExeIcon4 get's converted to the App-Icon? Thank you!
Hi Everyone, I am trying to add an item to the lockdown to launch into the settings>app>storage screen on a Zebra device, TC75x. However, every time I try to run identify_activity, it is showing me: Current activity name: com.android.settings/.SubSettings. That is too generic for the lockdown to navigate to the correct location. All of my devices are in the field so I was wondering if anyone has previously done this and had the package name already. If not, do you know of a script that would clear the cache instead of the data? I have only seen the wipeapplication script. Enrollment Method: Enterprise Model: TC75X OS: 8.1.0 Patch Level: 2019-02-01
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!
Is there a way to send a script down to an Android device to force it to check-in? I tried "connect -f" but I can't really tell if it's doing anything, nothing logs as a device check-in. I would like to send a device check-in script as part of a post installation script in a package after a new software version is installed. This would allow to us to quickly see if the app version incremented successfully as well as some other items. Thanks
Hi All, We are trying to deploy a datawedge profile (dwprofile_MSCA.db) using a package in SOTI on a Zebra MC330x device running Android 10. Deploying it through a package has worked successfully and the dwprofile_MSCA.db file has succesfully imported to the correct folder: /enterprise/device/settings/datawedge/autoimport/dwprofile_MSCA.db Once the file has been pushed to the folder location above using SOTI, we are seeing no change within the Datawedge app in the device. We have tried to reboot as well but not seeing any changes once the device is back online. We have had to click the options menu in datawedge (top right buttons) and manually import the profile from the autoimport folder on each of the devices so far. After doing this we can see the MSCA profile within the menu and it is working fine. I have also tried a script that I found online to push the dwprofile_MSCA.db file once it is on the device but had no joy. The script was the one given on the Zebra website, __chmod 777 /enterprise/device/settings/datawedge/autoimport/dwprofile_MSCA.db Again after executing the script, no changes are seen in the datawedge app until I manually import it. Please advise on the path forward to automate this as we only have another few weeks before we are going to be rolling out the remainder of the devices and this method of manually having to import in the datawedge application is not feasible for such a large amount of devices. Kind Regards, Shane
Hi, We have problem that when we try to sync applications on from any enterprise binding we get 'Internal Server Error'. This happens everytime i try to sync approved applications. If i make new binding it will work for a while (aprox 1day), but stops working after a while. Any ideas how to solve this? We are running version 15.2.2.1080 Thanks in advance! /Jaakko
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
I have a problem when I re-enroll Android devices that have been sent to Zebra for repair. I re-enroll the device and I can literally watch Mobicontrol and see that the device is re-enrolled with a new name and the name that it previously was using disappears. I then rename the 'new' device back to the name that I want it to have, and put it in the proper folder to pull down the appropriate profile. My issue is that even though Mobicontrol knows it is the same device being re-enrolled it is still claiming a new license. Every time I re-enroll a device, my number of free licenses is dropping by one, when it actually should just be using the same license it was using before. I've started deleting the device to reclaim the license, and then re-enrolling the device again, but my issue is that this has apparently been going on for quite a while and I probably have 50-100 devices that are tying up two licenses each. Is there a way I can clean out these ghost licenses so I can free them up in the system?
We are trying to use SOTI Surf as a web kiosk to allow users access to specific websites and some of these websites are showing "Webpage not available" For example: https://okta.com https://account.microsoft.com These websites are otherwise accessible on the same devices using any other browsers. We currently do not have any restrictions in our SOTI Surf config, only a configured home page. Currently the application should be open. We also found this on SOTI Surf version 13.3 and 15.2
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
Hello, in our Company we are using Zebra TC52 with Android10. Now i want to integrate a Testdevice in our Mobicontrol15 Environment. Somebody know which is the correct Agent? I tried all Zebra Agents in different Versions. After Installation I get the prompt: The Version of SotiMC is not comaptible withe the device". When I install really old Versions I dont get the Error, but the App closes directly after the start.Is here a solution?Thanks in advance!
This might not make sense. The devices we are going to deploy will not be easily physically accessible once they are out in the field. Is it possible to update the MC agent remotely? If so, how is it done? Since we plan on setting up the devices in Kiosk mode, will I have to unlock them all first before I do an upgrade? Is it necessary to upgrade the agent each time there is a new version?
Dear All, we need to preconfigure Datawedge in order to send scanned information into an app. The manual way is the bellow: Go to DataWedge provided app Press on Profile0(default) Scroll until "Intent output" section is found Enable output via intent In intent action write com.euronav_app.ACTION Intent delivery must be set to "Broadcast intent I assume that this could be done with a commant like the bellow: sendintent -b "intent:#Intent;action=com.symbol.datawedge.api.ACTION;S.putExtra= com.euronav_app.ACTION;end" "com.euronav_app" is the application name. Cen anybody advise on thos? Best regards
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
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.
