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.
Hello; I cant 15.2 to 15.6.6 upgrade. What can i fix the problem?Thx
Hi Everyone, does somebody already have expierience with the new Search Service? I did the upgrade with a customer from MobiControl v15.5 to 2024.0. In the new installer you can select where the Search should be installed. My customer has the Deployment Server in the DMZ and the Management Server in the LAN. Do I have to install Search on both servers? As I did this the "Advanced Search" was not available. Any idea? The new port 5500 is open on both sides. Thank you very much.
Recently, we have started to upgrade our TC57s from Android 8.1 to Android 11. The one problem that we have noticed is that the Calculator app package name is changing. The main issue with this is that it is not consistent among the devices we have upgraded and it ends up being one of the two names below. com.google.android.calculatorcom.android.calculator2 The kiosk profile is setup using com.google.android.calculator so any phone using the other one is not finding the app on the kiosk screen and is giving the error "package not found." The app in the Google Play Store only shows installed if the first package name is used, and when I try installing it when it is named the other way, I get an error. What is the best way to resolve this issue? We have considered using another app from the Google Play Store entirely to avoid this issue, but I don't like the idea of using some random app that could be taken off the store at any moment and cause mass issues.
I searched the forum but not found any info on these two errors. Anyone come across either of these during upgrade? Installation was successful with no errors on DB upgrade but deployment server would not start. First one, nothing has changed on the network. Using same FQDN in the upgrade wizard as the current server, firewall rules are all set per system requirements. Cert is valid. The other main error from the logs is with deployment server extensions not connecting to SQL db. We are using windows creds for this which works fine on 15.2. Testing connection to DB is green in the admin utility. 2022-07-18 23:38:16,755 (0x00001a28) [ERROR] [CDeploymentSrv::InitDeploymentServerExtension] Error initializing Deployment Server Extensions: System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. System info: MC: Server 2016, separate Azure SQL VM instance. Latest Java 11 LTS.
Hi all, I wanted to upgrade my soti mobicontrol program from 15.3 to 15.4.2. So i've updated my java version and excecuted the setup to upgrade.At the end the setup is trying to start de MCDPSRV service and it fails to do so.
Good Morning. I am trying to upgrade the agent on several of our Android Enterprise devices. I have not been able to upgrade using the button. I will select upgrade and upgrade now instead of start on schedule. I will get a message that says "Upgrade Agent Action has been sent to device" The message is a success message. When I go to check the agent version, it remains the same. Is there an extra step I need to do in order to upgrade the agent? Soti Cloud version 14.4.6 Current agent on tablet: 14.1.4.1010 Trying to update to Agent Version 14.5.4.1016 Settings Manager app 15.0.1 requires to have Agent 14.4.7 or higher to use. I have been able to upgrade it using a profile package. But I need to be able to upgrade one specific device. What is the best way to do this?
Hello Soti Forum, we have quite a few Zebra MC33 in use. Previously, these were delivered with Android 8, but in the past there were problems with the connection to Soti. For this reason, a downgrade to Android 7.1.2 was made at that time before installation. In the meantime, the installations with Android 8 have mostly worked again, but we now have 80 devices that still have an Android 7.1.2. Can you tell me what the best method would be to upgrade these devices as stress-free as possible for us and the users? I don't like to send users a list of barcodes where they set the device with to factory settings, etc.At best, they should be aware of the upgrade as little as possible. I just found out, that there is a button for "Migrate to Android Enterprise" + I have found 'This is possible with Zebra Android devices. You'll need to first transfer the firmware files to the device via a Package or a File Sync Rule. install_system_update /sdcard/YOURUPDATE.zip' Sounds not so bad. A best practise solution would be helpful then 🙂 Is there a script that can be sent to the device to install the update and at best not reset everything? I would be very grateful for any tips. Cheers Maik
This is an update to my original problem with upgrading to v15, as the original post has been locked, so I thought I'll share the fix that Soti support gave that fixed our problem as I dont see any other posts about this issue. https://discussions.soti.net/thread/has-anyone-experienced-sql-errors-when-updating-to-15-3-dacpac-dac-message-warning-sql72015 Summary TL;DR So we had a SQL72015 error every time we tried to upgrade to v15.x from v14.5. And was told we had to wait for SQL 2019 support in v15.4, which we did, but unfortunately that still same error and could not upgrade. Logged new ticket with Soti support and after investigating the issue, they gave the following SQL fix that solved our issue. Use the following SQL query at your own risk, this is what was provided to us to fix my issue. This may not work for everyone 1. Take server snapshot and db backup of your Mobicontrol server. 2. Launch SQL server Management studio and login 3. Right click on MobiControlDB and click on 'New Query' 4. Paste the sql query and execute it. 5. Restart MC services (Deployment Server and Management Server) -----code---- DELETE FROM dbo.Container;SET IDENTITY_INSERT dbo.Container ON;INSERT INTO dbo.Container( Id, Name)VALUES( 0, 'No Container'),( 1, 'KNOX Container'),( 2, 'Android Profile Container');SET IDENTITY_INSERT dbo.Container OFF; -----code----
Good afternoon, We have several TC56s that are running Android 7.1.2 and we intend on trying to upgrade them to 8.1. I was testing this process by deploying the Zebra provided ZIP files and was successfully able to update these devices. The only problem is after the update Remote View is the only option when attempting to remote into these devices. The remote view does not work and only shows a black screen. What I have attempted so far: 1. Deploying the MobiControl Device Agent detailed in this article below. I get [Failed to Install (File I/O Error)] as an error. Our devices were enrolled as Work Managed Devices as well. https://discussions.soti.net/thread/why-the-device-is-showing-just-the-option-remote-view/ 2. This other article actually closely resembles the issues I am having but I have the device out of any sort of profile that enforces Kiosk or app permissions. https://discussions.soti.net/thread/android-8-remotecontrol 3. I was testing on devices that I had at a nearby location and the only way I have been able to get them to work is by completely deleting the device out of MobiControl and enrolling from scratch. This allows the devices to work on Remote Control properly. The only problem with this method is we have several devices that are states away so having to completely re-enroll all of them would be incredibly difficult. That is why I am posting here to see if there are any other options. Please let me know if you require any more information regarding this issue and I appreciate any sort of assistance I am given in advance. Thank you! James Pike
Just wondering if anyone has experienced SQL errors when upgrading from v14.3 to 15.3? i get a bunch of these when trying to upgrade and it fails to update 2021-05-24 13:40:55.639: DACPAC: DAC Message: Warning SQL72015: The type for column Id in table [dbo].[Container] is currently INT IDENTITY (1, 1) NOT NULL but is being changed to TINYINT NOT NULL. Data loss could occur.2021-05-24 13:40:55.654: DACPAC: DAC Message: Warning SQL72015: The type for column ContainerId in table [dbo].[DevContainerStatus] is currently INT NOT NULL but is being changed to TINYINT NOT NULL. Data loss could occur.2021-05-24 13:40:55.654: DACPAC: DAC Message: Warning SQL72015: The type for column ContainerId in table [dbo].[DeviceConfigSectionStatus] is currently INT NOT NULL but is being changed to TINYINT NOT NULL. Data loss could occur.2021-05-24 13:40:55.654: DACPAC: DAC Message: Warning SQL72015: The column [dbo].[DeviceInstalledApp].[AppleVPPLicenseId] is being dropped, data loss could occur.2021-05-24 13:40:55.654: DACPAC: DAC Message: Warning SQL72015: The type for column ContainerId in table [dbo].[DeviceInstalledApp] is currently INT NOT NULL but is being changed to TINYINT NOT NULL. Data loss could occur. 2021-05-24 13:40:56.982: DACPAC: DAC Message: Message SQL0: An error occurred while the batch was being executed.2021-05-24 13:40:56.982: DACPAC: Faulted [2]: Updating database2021-05-24 13:40:56.982: DACPAC: DAC Message: Message SQL73036: Updating database (Failed)2021-05-24 13:40:56.982: DACPAC: Faulted [2]: Deploying package to database2021-05-24 13:40:56.998: DACPAC: Faulted [2]: Registering metadata for database2021-05-24 13:40:57.015: DACPAC: FAILURE: DACPAC has failed to deploy: Microsoft.SqlServer.Dac.DacServicesException: Could not deploy package.Warning SQL72015: The type for column Id in table [dbo].[Container] is currently INT IDENTITY (1, 1) NOT NULL but is being changed to TINYINT NOT NULL. Data loss could occur.
Hello everyone. We use V 15.1.2.1035 of mobicontrol and since last week, we encounteer a huge problem. All our devices are Datalogic Memor 10 Since last Thursday , every new enrolled device stay stuck in enrollement answering this error Enrollement Managed Google Play Account Status:'EMPTY_TOKEN I've opened a case to SOTI Yesterday and got contact after multiple Call with someone at English support. This person tried to help, but since i've also got an error on some device saying that Agent can't be updated Invalid device software version (Device is not allowed to upgrade) I've called back this morning, and the person i had on phone said that French support should call me back in 30 min to solve that...it was 3h30 Ago... (We are from Belgium so basically French support seemed to be the most appropriate) Device are stuck and the problem is getting worse every day. Hope someone can Help me here maybe...
I'm planning on upgrading from 13.4 to the newest version of SOTI. Just in case something goes wrong, and I have to revert back to older version, I need installer for that, but I can only find link to download the new one. Can I find older versions somewhere? Our current version of SOTI is 13.4.0.4591. That, or newer version of 13.4. should do.
I would like to Upgrade my enrolled devices with SOTI from Android 7.1.2 to Android 8.1.0 I downloaded the follow files. Full image version: 02-32-04.00 LifeGuard update14 version: ATLAS_DELTA_UPDATE_02-32-04.00-OG-U14-STD How can I manage a zero touch OS update? I need a Work Managed Device with Device Owner enrollment type, because the Remote Control and the default apps are necessary. I think with Android 8 I have to use Enterprise Agent, so if the upgrade done I don't know what gonna be hapen with original Android Classic OEM agent. I'm afraid the device will no longer be available via SOTI. My enrolled device, environment parameters: Zebra MC3300 Android 7.1.2 - FPU_ATLAS_02-07-08.00-NG-U00-STD Enrollment type: Android + MC Web Console version: 15.2.4 MC agent version: GoogleMobicontrol1441_1064 Thanks in advance.
Hello has anyone already upgraded to Mobicontrol 15.3? (on-premise)? There were some issues after installation, but were fixed in MCadmin. Main trouble is some menu items are unavailalble/blank -> e.g Rules,Reports.. its shown just empty window: like the older portal is not available at all (as it was in 15.2.3). Im considering a rollback. thanks Tomas
Hi, my company plans to move from MobiControl Cloud 14.1 to 15.2. We have 250 Android Plus devices: Zebra TC56 running Android v6.0.1 with agent version 13.5 Samsung SM-G390F running Android v7.0 with agent version 13.5 What are the steps to make sure that the transition runs smoothly? Do we need to upgrade the devices agent too? Do we need to upgrade the devices firmware? Do we need to re-enroll the devices? I should note that we anyway plan to upgrade the devices firmware soon, but I see that as a separate project. Thanks in advance for your help and best regards Henry
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
