IBM Security MaaS360

 View Only
  • 1.  Unable to Configure MaaS360 work profile in New Samsung Tablet A7

    Posted Fri October 30, 2020 01:54 PM
    Hello -
    I purchased a new Samsung Galaxy Tab A7 today.
    Settings -
    Android 10
    Samsung One UI 2.5
    Knox Security 

    I have installed MaaS360, and configured it as per the steps provided in our W3 website.

    When it came to set up the work profile, it is throwing the below message -
    "Can't create work profile
    The security policy prevents the creation of a work profile because a custom OS has been installed on this device."

    Thank You

    ------------------------------
    NILAY DE
    ------------------------------


  • 2.  RE: Unable to Configure MaaS360 work profile in New Samsung Tablet A7

    Posted Mon November 02, 2020 10:09 AM
    I have the exact same issue.  Even tried other DPC identifiers (afw#setup, afw#memdm, etc...) and all have the same issue.  This makes me think it's not necessarily a Maas360 issue.  However, is there a workaround?  Is this a known issue?

    Here's another thread about it: https://r2.community.samsung.com/t5/Tech-Talk/Company-Intune-work-profile-not-getting-created-since-Last/td-p/4265248

    ------------------------------
    Lee Riemer
    ------------------------------



  • 3.  RE: Unable to Configure MaaS360 work profile in New Samsung Tablet A7

    Posted Mon November 02, 2020 11:50 AM

    Thank you both for the information - we have seen intermittent reports of this and (absent any official statement  from Samsung) our internal consensus is that it's one of two issues:

    1) The most likely culprit, since we're seeing multiple reports, is something on the device OS/Firmware side.  It was brought to my attention that this happened in the past and required updates from Samsung.

    2) Another potential cause is used/recycled/resold devices that were once rooted. I have been informed that Samsung works in some sort of failsafe, and, if a device has been rooted, it will "break" certain workflows, including Android Enterprise, even if the device is factory serviced and restored to a "like new" condition.

    We are not able to reproduce on our own internal devices, otherwise I wouldn't ask this, but would one of you be able to get dumpstate logs from an impacted device so that we can open a formal case with Samsung, and maybe get some sort of timeline for a fix if this is a known issue?  You can email them directly to me.



    ------------------------------
    Matt Shaver
    System Architect
    IBM
    mshaver@us.ibm.com
    ------------------------------