Application report not getting collected on Xiaomi mix fold devices
We have couple of users who have the Xiaomi Fold device and in the application report section of status report notifications we are only getting the android device policy app. None of the other applications are getting returned. Is this a known issue? How can we debug the issue? I was not able to see anything obvious in the device logs. We are getting the full application report for the other devices.
Updating the Device Art Generator (Device Frame)
The Device art generator is a great tool for people who don’t want to install Android Studio just to take some framed screenshots for documentation use. There are third-party apps that can do this too (Snapmod), but I was wondering if the developers at Google could give the Device art generator some well-deserved love and update it to include Pixel 10 frames? Thanks. (Google) Device art generator: https://developer.android.com/distribute/marketing-tools/device-art-generator 3rd party option: https://play.google.com/store/apps/details?id=cn.gavinliu.snapmod
Looking for solutions to assist in Bulk Management (Wipe) of Android Enterprise devices
Hi everyone, I'm turning to the community to see if there are any solutions being used out in the wild that assist with bulk wiping Android devices. I suspect that what I'm asking may not be possible - mainly due to the nature of Android Developer Options, USB Debugging etc. - but I've been I've been tasked by our management to investigate and possibly propose a solution. As an example, we currently use several Cambrionix ThunderSync3 16 port devices to DFU both iOS and macOS devices but they don't offer a similar solution for Android. Are there any solutions that can be used either in tandem with docking stations like Cambrionix or some other. Our use case is Work Managed and we use Omnissa Workspace ONE UEM to manage the devices. The devices themselves are Pixels and Samsungs. and each device is loaded into either the Google Zero Touch Portal or the Samsung Knox Portal. The expectation is that when a large number of Androids are returned for whatever reason, we'd like to be able to plug the device into a "station" and programatically wipe them en masse. Personally, I think we need to simplify our returns process and use the MDM in a controlled environment but I have to have asked these questions, due diligence and all that. Thanks in advance for your input.
Google Messages App: SMS to shortcode not able to send
Our Provider (Vodafone Germany) is using a SMS shortcode number to be able to order an upgrade on dataplans by sms. Once the monthly contract plan (e.g. 1 GB) have been used users will receive a sms from 70997 to inform that you can answer the SMS with "1" or "2" to restore your data connectivity. We ran into the issue that the Google Messages app seems to have some sort of bug with sending SMS to this kind of shortcode number as it alway says "Not sent" in red error text. Provider tech support told me that the Google messages app is prefixing the number with "49" resulting in a wrong / unknown number (4970997). They cannot fix that from their side as the issue is within Google messages app and asked me to install a 3rd party messages app.... *ugly* Is this something I can request to investigate from here? I will also create a case with Samsung tech support as we are mainly using Samsung devices as our corp. device fleet. Thank you! Kind Regards DanielManaged Google Play API Error
We manage our mobile device through Intune; we also manage multiple tenants. I didn't know when I did this, but I made the mistake of signing into a new tenant with our Managed Google Play account that we use for our main tenant. Still, unaware of my error, I decided to disconnect the Managed Google Play account from the new tenant and create a new Google Play account for them. The new tenant works fine. I'm able to enroll Android devices and manage apps. However, in our main tenant, under Tenant Administration | Tenant Status for Managed Google Play, it shows a warning: Management Service Error. If I try to go to Android Apps to add an app, I get the following message: "It looks like your tenant has been unbound via the Google Play console. To browse Managed Google Play, your Intune account needs to be connected to your Android Enterprise account." But, in Devices | Android | Android Enrollment | Managed Google Play, it shows the account as Setup (with the green check). I'm also unable to create a new Corporate-Owned, Fully-Managed profile. I get an error. I reached out to Microsoft and they say this is a Google issue. I've tried to find ways to contact Google without success. So, we're kind of stuck in the mud. Is there a way to fix this?
Need explanation for feature validation
I want to validate 1.11. Dedicated device provisioning feature but failed. I have shown a zero touch enrollment for dedicated provisioning and provide below video for demonstration purpose. https://drive.google.com/file/d/1X0YD-kgNIODLPjzDHv-eG_U6s0fB2hi0/view?usp=sharing Anyone can please describe what actually I need to do. Thanks in advancee.
New devices only receive "Enterprise Default Profile" instead of default profile
Hey there, this is my first post here as I could not find a ticket system for Zero Touch. Since a couple of weeks all new devices only getting the "Enterprise Default Profile" automatically assigned which I deleted during zero touch tenant setup in "Configurations". The default profile I created does not get automatically applied anymore. Unfortunately I can change the default assignment profile to whatever I want but newly added devices still are getting the "Enterprise Default Profile". Changing the device profile after the initial upload (including wrong DPC info) to the created target profile works in bulk. Once changed manually the devices apply the correct DPC. Multiple zero touch instances are affected. How to fix the default assignment profile for newly added devices? Any suggestions?Disable random mac address during EMM enrollment
My company is trying to provision tablets via headwind MDM. We have no problem on some of our networks, but the location they are being provisioned at at-scale have a strict no-random-mac address rule on their network. Thus far I have been unable to figure out how to create a QR code that will disable random mac address on the SSID of the network the device connects to when enrolling in our MDM. Is there a field I am missing? Surely there must be a way to overcome this.