MDF1's Posts

Re: di you verRe: Android enrollment issues with Workspace One/Airwatch?

by Contributor in Workspace ONE Discussions
‎12-06-2022 03:09 PM
2 Kudos
‎12-06-2022 03:09 PM
2 Kudos
Not sure if you are still having the problem today but one solution is to change the URL in Knox to Workspace ONE. Instead of using the Airwatch hosted URL it will grab it from the Play Store URL ins... See more...
Not sure if you are still having the problem today but one solution is to change the URL in Knox to Workspace ONE. Instead of using the Airwatch hosted URL it will grab it from the Play Store URL instead. It automatically fills out the https://play.google.com/managed/downloadManagingApp?identifier=hub URL. I think older deployments still have that "awmdm" URL above in their Knox. 

Re: Android App Configs not working on new deploys? (UEM)

by Contributor in Workspace ONE Discussions
‎11-14-2022 10:12 AM
‎11-14-2022 10:12 AM
Thanks gjohal. I also got the update from the VMWare team last week that the issue may have been resolved on Google's end.  I haven't done tons of tests yet, but was able to get 3 successful app con... See more...
Thanks gjohal. I also got the update from the VMWare team last week that the issue may have been resolved on Google's end.  I haven't done tons of tests yet, but was able to get 3 successful app configs in a row for one Android 9 phone and two for another Android 12 phone. I think it may be OK, but would be more comfortable with more enrollments to verify. Anyways, if others are seeing this as well then hopefully this one has been resolved. Thanks. 

Re: Android App Configs not working on new deploys? (UEM)

by Contributor in Workspace ONE Discussions
‎10-12-2022 02:36 PM
‎10-12-2022 02:36 PM
I just tried it again. Still having the issue after the 2209 update. 

Re: Android App Configs not working on new deploys? (UEM)

by Contributor in Workspace ONE Discussions
‎09-26-2022 07:32 AM
‎09-26-2022 07:32 AM
Well good to know we're not the only ones experiencing this. VMWare tech support also finally responded to me on Friday: "We have opened a ticket with Google for this issue as we have other customer... See more...
Well good to know we're not the only ones experiencing this. VMWare tech support also finally responded to me on Friday: "We have opened a ticket with Google for this issue as we have other customers experiencing similar behavior" Not sure if this will help out, but when this first happened it was for 100% of new deployments that we would be missing configs. Now, it's more like 50/50 - we might get the config, might not. (There have been three minor patches to our SaaS environment since Aug 9 when we first experienced this problem. Not sure if this is related).  In addition to reinstalling the app there is another option of using the "Send Config" button from the Application's page in WS1, which seems to work (not very useful when setting up a brand new phone mind you). Or, opening the app's deployment page and choosing "Save and Publish" seems to do the same thing.   

Android App Configs not working on new deploys? (UEM)

by Contributor in Workspace ONE Discussions
‎08-09-2022 10:02 AM
‎08-09-2022 10:02 AM
Hi all, wondering if this is something with just our environment or if others are experiencing this too. Everything with our apps with App Configs had been working for years until this Monday. As it ... See more...
Hi all, wondering if this is something with just our environment or if others are experiencing this too. Everything with our apps with App Configs had been working for years until this Monday. As it happens our SaaS environment was updated to  22.6.0.0 (2206).  We are having an issue with app configs on newly deployed Android phones (currently testing with Android 9 and 12, all devices Corporate - Dedicated). (the App Configuration settings are in the Apps section, under App> Assign > Add Assignment > Application Configuration > Send Configuration > fill out the list of fields). At least two separate apps we are using with app configs do not seem to be getting the configs from WS1 UEM when a new phone is setup.  We have been able to get around it by reinstalling the app from the App Catalog which usually helps (throwing in a reboot sometimes does the job). Not sure if the "Send Configuration" button would help, but I'm hesitant to push the whole config every time a device is added.  Under the user's device in Devices > Details View > (User's Device) > Apps > (click on App with App Config) it looks like it has the right assignment even when it's not working.  But I'm wondering what happened as this is inconvenient and if anyone else is seeing this. 

Re: Android enrollment issues with Workspace One/Airwatch?

by Contributor in Workspace ONE Discussions
‎07-07-2022 01:33 PM
‎07-07-2022 01:33 PM
Thanks! Yes, I seem to be able to enroll now through Knox.  

Re: Android enrollment issues with Workspace One/Airwatch?

by Contributor in Workspace ONE Discussions
‎07-07-2022 12:45 PM
‎07-07-2022 12:45 PM
Thanks for the info. We do have a ticket open and got a response... they said "I think I've seen a few other customers today submit cases with similar behavior, so I am going to check with my team th... See more...
Thanks for the info. We do have a ticket open and got a response... they said "I think I've seen a few other customers today submit cases with similar behavior, so I am going to check with my team this afternoon to see if there is some ongoing issue or not as well." For what it's worth the QR code enrollment inside Workspace ONE directly seems to work OK (but doesn't play nicely with a Knox enrolled device). 

Android enrollment issues with Workspace One/Airwatch?

by Contributor in Workspace ONE Discussions
‎07-07-2022 10:58 AM
‎07-07-2022 10:58 AM
Wondering if anyone else is having this issue or if it's just me. Just this morning for our Android device enrollments using Samsung Knox we are getting an error (this happens after the Airwatch enro... See more...
Wondering if anyone else is having this issue or if it's just me. Just this morning for our Android device enrollments using Samsung Knox we are getting an error (this happens after the Airwatch enrollment process starts, but before login credentials are requested): "Can't setup the device Can't use the admin app. It's missing components or is corrupted. For help, contact your admin. " During the enrollment workflow Knox seems to successfully send the device to Airwatch, but then we get the above error message. This may be irrelevant and tied to my lack of understanding of APK files... but I tried downloading the management APK file referenced in the the Knox setup just to see. https://discovery.awmdm.com/mobileenrollment/airwatchagent.apk It downloads a file, but I couldn't open the archive (normally for APK files I can open them in tools like 7zip).