SOTI Pulse Logo

Cannot Create Work Profile - SOTI Stage Programmer

JW
Joe Walker
Onecom

HI,

We've come across an issue with configuring some out of the box Samsung X Cover 4's using the SOTI Stage Programmer tool and wondered if anyone had any ideas.

Essentially up to the tool has worked well for us auto provisioning the devices VIA NFC adding the Wi-fi, downloading and installing the enterprise agent and then enrolling the device. However with the latest batch of phones we're getting the following error which we haven't seen before.

"Cannot create work profile, the security policy prevents the creation of managed device because a custom OS is or has been installed on this device"

We factory reset some which worked for around 5 but not for others, any ideas?

7 years ago
Android
ANSWERS
K
KMod@SOTI
7 years ago

Hi Joe,

The devices that you are receiving this error on, are they fresh out of the box or have these devices been previously used?

The majority of the time when this error message appears, it is due to the fact that the device has been rooted. Is this happening with all of your devices that you received in your latest batch?

If these devices are fresh out of the box, are you able to enroll one as Android Enterprise manually?

Regards,

JW
Joe Walker
7 years ago

HI,

They're fresh out of the Box Brand new devices from O2. The only thing that appears to be different from previous ones is that these are now being shipped with Android 8.1.

SS
Support Staff Account
5 years ago

Hello Joe, 

Thank you for requesting a response from SOTI Support staff.

To be honest I experienced this for the first time on Friday last week with a Samsung  - SM-T350 (TAB A).  My device isn't new but definitely has not been rooted as I'm sure your new devices aren't either.  Interestingly enough I was able to bypass this by turning the device off and on.    When the device returned from the restart it had the work profiles on it and continued to work as if the message had not appeared. 

Perhaps you were quick to factory reset the device as mine didn't need a hard reset to recover from this error.   Nonetheless, I would create a support ticket @support@soti.net as my device is 7.1.1 and that means it may happen on various OS versions.  

What Android Enterprise Agent version was on the device when you experienced this error initially?  Are you experiencing this error still?

Regards,

Similar Discussions