VMware Workspace ONE Community
anonymousmigrat
Enthusiast
Enthusiast

After upgrade - cannot move devices from the Global OG

Hi all,


I just finished an upgrade, one where alot of issues occurred to slow me down, most notably an older instance of AWCM which didn't uninstall and blocked the upgrade (I had to forcibly remove the service before I upgraded) and I just ran into a new issue I am having trouble finding the cause for.


Upgrade was from version 8.4 and to the latest 1811


The issue is that all the devices I enroll after upgrading get placed in the Global OG, and I cannot move them to their assigned groups. The user group assignment rule also doesn't do it's job. Android devices behave like the enrollment worked as planned, but they do not get their assigned profiles since it's legacy assignment and base on the OG. iOS devices don't finish their enrollment. They appear on the console, and I am able to sync then and see their status. The Device Manager profile is in the device settings, but when enrolling it stops after installing the profile, and is stuck intil it says; ' An unexpected error occurred.'  If I open Hub(Agent) again, it just asks for e-mail/server again. If I try to move the devices from the Global OG to the group they should be in, they wont move at all.


Anyone had any similar issues and can share how it went?

Labels (1)
Reply
0 Kudos
4 Replies
KonstantinosLei
Contributor
Contributor

Hey Gunnar. Did you perform incremental DB upgrades from 8.4 to 9.3 and then to 1811 or did you go straight from 8.4 to 1811?
Reply
0 Kudos
anonymousmigrat
Enthusiast
Enthusiast

I did perform the incremental upgrades.

I've got a feeling the problem was some pre-existing underlying problem that hadn't ' surfaced'  yet.
Reply
0 Kudos
KonstantinosLei
Contributor
Contributor

Could be. Did you engage AirWatch support? Was the issue fixed eventually?
Reply
0 Kudos
anonymousmigrat
Enthusiast
Enthusiast

I did engage them, but they were unable to find the issue before I managed to create a workaround. My feeling was that something in the upgrades made a mess of that OG in the database. A second OG created with the exact same settings didn't have the issues. Sorry I cannot provide further information as to the cause, but it was never resolved.
Reply
0 Kudos