[dpeters11]

I upgraded my Pixel to a 2, and cannot get it to activate, around where it says policies received, it errors out. This is on Android 8, UEM server 12.7.1. we use Blackberry Dynamics, but it doesn't get that far. I tried reactivating my old phone, that works fine. Other users activated today with no issue.

Anyone have any suggestions? Everything I see is regarding Knox or hitting the max number of devices.

I also do have a PIN set up for the device.

[sbowlestx]

The device is showing a false positive as being rooted. I created a separate compliance policy and turned off root detection for Android . It activates just fine now. I currently have a ticket open with Blackberry on this.


Different device but it is the same issue.

http://support.blackberry.com/kb/art...mber=000046236

[dpeters11]

Thanks, that was really getting to me.

[hrit95]

Hi there !
how did you created an new compliance policy ? since the UEM 12.6 i can only create compatibilty profiles for a reference to the old compliance profiles.
I have same problem with two devices.

[hrit95]

Hi there !
how did you created an new compliance policy ? since the UEM 12.6 i can only create compatibilty profiles for a reference to the old compliance profiles.
I have same problem with two devices.

[dpeters11]

Hi there !
how did you created an new compliance policy ? since the UEM 12.6 i can only create compatibilty profiles for a reference to the old compliance profiles.
I have same problem with two devices.

I have 12.7.1, I just made a copy of my current compliance policy, then made the change to that copy and assigned it to myself.

[hrit95]

Sorry for this "stupid" question.. But how can i copy the compliance policy ? There is no copy function.. Running UEM 12.7.1
Do i have to copy the BlackBerry Dynamics compliance profile or the normal compliance profile.

[rpayne_bb]

We are aware of the issue and working on a client side fix.

[Ron Caron]

I was having the same problem and found this post. I went under the BES console, created a new "Compliance" policy called Pixel. You just make sure none of the boxes are checked (or at least the "rooted OS" box is not checked" under the Android tab. Then save it.
Then I went to my User account, and I clicked the plus sign to add a policy, selected Pixel from the drop down that appears, and it overrides whatever compliance policy was there when you select "Pixel" or whatever you named it. In the end you should see your User overview with all of you policies (email, Activation, etc. including Compliance with Pixel instead of "default" or whatever was there before.

[sethyx]

We are aware of the issue and working on a client side fix.

Do you have any ETA for the fixed release? Thanks

[rpayne_bb]

next uem client posting should have it

[sethyx]

Thanks, that's good to hear. What would that mean, to be a bit more exact? In a week, month, year?
Sorry, I'm pretty new to this client.
Just got upgraded from Good, but UEM does not work on Android 8.1, and I can't roll back to Good = no work stuff on my phone.

[dpeters11]

I noticed the 8.1 issue as well, haven't opened a ticket since this is a beta OS and I figured unsupported.

[sethyx]

Did anyone try if 12.31.0.154065 fixes this issue? Or @rpayne_bb can you confirm?

[rpayne_bb]

@sethyx yes it should fix the issue. Another client version is also coming very shortly.