I assume people have had success enrolling Pixel 6 and Android 12 into WS1 after applying the seed script? I'm wondering if my profile problem has anything to do with the fact that the user transferred data from his old pixel to the new one using the cable transfer method. I know with iOS people restoring from backup is a real pain and we have to enterprise wipe their new device and remove the record from WS1 in order to get them to install their phone in MDM. Wonder if it's similar with Android somehow.
The prior script fixed it for my other devices but the new one just posted didn't do anything for the Pixel 6. Well it gets pasts the URL message but not the inability to install Android Enterprise on the device. Though should say that I installed the script prior to testing on my devices, just had the user with the Pixel 6 error out and then tried the script, then I tested my enrollment so who knows.
So I'm running into this for the first time today. Our first Pixel 6 running Build number SD1A.210817.036. Our Workspace One environment is on-prem, 2008. So far we have 13 devices enrolled that are running Android 12, but this is the first Pixel 6. Do we have confirmation from VMware that the DB script linked earlier in this thread actually fixes the issue? Thanks.