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 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...
Hello community, does anyone know the issue that the Google managed account gets no token?In the logs i receive the message: Error message received from device Zebra MC93 (Managed Google Play Account Status:'EMPTY_TOKEN Got response but there was no token!') In the Mobicontrol App i only receive the message that i need to complete the configuration for your Work Profile. I am running MobiControl version 15.3.1.1151 Till now i did the following steps: Deleted the managed Google account and added another Google managed account Created a new rule with a complete new Google managed account Deleted all accounts in SOTI Enterprise Binding Checked if all ports are open: https://support.google.com/work/android/answer/10513641?hl=en&utm_source=google&utm_medium=email&utm_campaign=android_enterprise_april_nl&utm_content=help_center Nothing helped and the support Case (C00480403) has no solution yet. Does anyone has an idea how to solve the issue?
Looking for help with CT 60 Android agent enrollment. We currently have a CT 60, and I worked with SOTI Support to enroll this device. We tried many times, only to receive an “Empty Token” error. After a month of trying, the SOTI support shared there were a few open tickets with the same problem. The SOTI support finally “injected” the agent directly into the device and going through the Android + path. The help I need now is we are planning to purchase more CT 60s with in the next month and I need info on how do I enroll the new devices? Do I need to “inject” each device? Do I use an "add device rule"? Mahalo (thank you) in advance.
Hi, Have an On-prem v14.3 instance that I am using for internal testing, all components (DS/DSE, MS, SQL) are all sat on the same Windows 2008 r2 server. Server sits behind a UTM firewall. Access from outside world to DS for devices is provided by inbound NAT via the firewall, from one of our available public IP addresses. Everything generally speaking works fine but I have found a couple of issues which I am really struggling to get a definitive answer on: - * I can enrol the server for Managed Google Play, this all completes fine. However when I enrol a device (typically as DO) to leverage use of the configured Managed Google Play services, I get the Configuring Google Work Account message in the Pending Actions but it never completes. Looking at the device logs there is an associated Managed Google Play error message showing "EMPTY_TOKEN". The device is therefore not receiving the AfW generic credentials back (I believe from the server but may be wrong...the devices have open access to the internet so should be able to directly communicate with GMS no problem). * Similarly when not using Managed Google Play, but attempting to leverage app deployment rules to deploy Google Play apps none of this works. The Apps never publish to the App catalogue on the device and cant be downloaded. When set as mandatory they equally never find their way onto the device. * Finally when looking at the Configuration Profiles screen within the device agent, this fails to communicate with the server and does not populate any of the information; simply throwing the error "failed to retrieve list of profiles". Have also had access to a cloud version and the above typically worked just fine and experienced no such issues. The firewalling is allowing the devices to communicate with the server inbound on 5494 & 5495, outbound the server is allowed to the internet on any port. I have the feeling that Google services and the device agent themselves are experiencing problems talking back to the server. Does 443 need to be allowed inbound also to allow this all to work? Appreciate any help or thoughts anyone can offer.
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
