Hi Jason, When it's a random problem, and you don't have a test device with the problem, it will become harder to troubleshoot. Assuming the above, you are using BYOD devices with ' Android for Work - Work profile' , with Public apps. So only the work ' folder' is being managed on the device. The user probably will be able to download the same public app for the personal profile / Google ID / Play Store, because this is separated from the Work profile / Work Play Store. The ID error message seems to be related to the app download from the Play Store. When you manually perform an installation of a app from the WS ONE console to the device, on the background you are asking the device to contact the Work PlayStore and download / install the application. So the console only asks to perform the installation, but it will not do the installation itself. To download from the Work Play Store, a Managed Work Account is being used. You can check on the device itself if the Google account is added under Accounts.
Can you check if you can see any account in the work profile of the device? See: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1912/Android_Platform/GUID-AWT-AFWDEVICEMODES.ht...
Did you also checked the network which the clients are using? Is there any blocked traffic to the Work Play Store? See: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1912/Android_Platform/GUID-80E36005-09EE-42B7-B3...
And you don't have enabled SAML authentication?
I agree with Wilbert and those questions should guide you in the right direction.
Hi Wilbert,
We are synced to AD and all of our devices are Employee owned BYOD, so they self-enroll. EMM reg looks good. I will check the log files and see if anything sticks out.
The frustrating part of it all is there doesn't seem to be any rhyme or reason. Some devices take the install immediately with no problem, while others fail. Doesn't seem to matter which android OS, which model, it's just random.
Update: I guess I can't pull log files since these are employee owned devices 😞
Hi Jason, When it's a random problem, and you don't have a test device with the problem, it will become harder to troubleshoot. Assuming the above, you are using BYOD devices with ' Android for Work - Work profile' , with Public apps. So only the work ' folder' is being managed on the device. The user probably will be able to download the same public app for the personal profile / Google ID / Play Store, because this is separated from the Work profile / Work Play Store. The ID error message seems to be related to the app download from the Play Store. When you manually perform an installation of a app from the WS ONE console to the device, on the background you are asking the device to contact the Work PlayStore and download / install the application. So the console only asks to perform the installation, but it will not do the installation itself. To download from the Work Play Store, a Managed Work Account is being used. You can check on the device itself if the Google account is added under Accounts.
Can you check if you can see any account in the work profile of the device? See: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1912/Android_Platform/GUID-AWT-AFWDEVICEMODES.ht...
Did you also checked the network which the clients are using? Is there any blocked traffic to the Work Play Store? See: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/1912/Android_Platform/GUID-80E36005-09EE-42B7-B3...
And you don't have enabled SAML authentication?
Funny you should mention that @jwkrock I'm getting the same error on a handful of Android devices today. The vast majority of my devices respond with no issue but have noticed about a dozen of them haven't taken a Hub or Boxer update in quite some time so I tried to manually force it. When I did I saw the error you mentioned on about 7 of the 12 devices that were out of date.