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.
A catalog rule has been created and assigned to a set of devices, which all of them has been enrolled by the same Add Rule. It means , all of them has its binding to the same company binding. The catalog rule holds some private application as mandatory. Some devices assumes the new application immediately after the cycle request, but some take more then 3 days to receive it. For those devices that are not installing the app, when clicks (in the device) on play store, it shows the application as not been released to the device. But it shows in the device MDM Catalog icone as Free and Mandatory. It looks like the device has not synchronized its account to the company bindings. After 3 or 4 days, it shows as released and may install. I have tried to force google play protect to rescan and also to restart device, but it still has "its own time to synchronize". Turning off the LockDown and set as administrative way, I got into device settings accounts, but the button to synchronize its android work account is disabled. Is there a way to force the synchronization between device and its Google account ?
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
Hi guys, do you know if the version 15.1.2 is running on Windows Server 2019? In the documentation only Windows Server 2016 is mentioned. I wasn't able to get a test installation on a Windows Server 2019, but I'll do that in the future. But maybe someone of you already tried that. The more important part: We encountered some problems after the upgrade from version 14.4.9 to 15.1.0. I hope you have some ideas. The first one isn't that bad, but I find it quite interesting. And maybe the second problem does have the same issue. After the upgrade, the login with the local admin account wasn't possible anymore. I loged in with my AD admin account, the local admin account wasn't locked or inactive. We fixed the issue by resetting the password, after that, login was fine. Did you encounter the same problems after an upgrade? The second issue is with the Android Enterprise bindings. After the upgrade we enrolled one device as Work Managed device with Zero Touch. We used Zebra TC56 and TC57 as testing devices. After connection the device to a WLAN, Zero Touch started. The Soti Enterprise agent got installed, but the device didn't get enrolled automatically. After opening the agent, we had to enter the Enrollment ID manually. After doing that, the device connected to our server, the device got created and is visible in the web console. The problem is the device agent is stuck in the step to get a Google Account. On the server we got the error message: Error message received from device (Managed Google Play Account Status:'EMPTY_TOKEN Got response but there was no token!') In the verbose logs there is this: But the Enterprise binding is present on the server: In our add device rules we are using the BMW Group binding. My first test was to create a new binding, the BMW MDMI and use this binding in a new add device rule to get a new Enrollment ID. So we enrolled a second device and entered the new Enrollment ID manually and the whole process was running without the binding error. Did you encounter some of these problems too after the upgrade or do you have an idea what happend there? Thanks a lot for your help and best regards Stefan
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
