This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enroll mobile device through afw#sophos

Hello,

normally i'll add a mobile device through the afw#sophos method, however this method is deprecated since last week. Whatever I try the phone will go to work mode (this isn't as much of a problem) the problem itself is that barely any system apps are available when I did give permission to use these. How can I fix this?

I've looked into deployment through QR code however this isn't ideal since our users have to sign in for the self service portal. We don't want them to do that. Is there any way I could configure this without the user having to sign in the ssp?

Regards,

Vincent 



This thread was automatically locked due to age.

Top Replies

  • Hi All,

    This is an update about the said issue.

    We have started the staged release of the client resolving this issue.
    Within Stage 1 of the release users located in Austria, Hungary, and United Arab Emirates will receive the update.

    The new client has version 9.7.3767

    To make the System apps appear again customers can use the following process:

    - Update the client on the affected devices
    - After the client is updated, make any change in the applied Android Enterprise policy
    - Save the change
    - Open the Sophos Mobile Control app and synchronize
    - After a few seconds the System Apps should appear on the device

    It is planned to continue with the next staged rollout beginning of next week.
    Jump to answer
Parents Reply
  • This isn't an answer.

    #1 add device is broken. Doesn't work anymore. We had a task bundle which installed some custom apps and that was it. Everything looked the same as when you wouldn't install SMC. ALL apps were available. Since the last update this is broken and we can only have a very few select apps like the camera. Not even the gallery is available. To clarify, we didn't edit the task bundle at all. This is since your last update. It looks like a work profile and this is exactly what we don't want.

    #2 self service isn't an option because we don't want our users logging in and registering themselves. We want total control of this and want to get rid of the situation we have to know their passwords

    #3 QR code enrollment would be great but we still need our users to login. Like I mentioned in #2 we don't want this

Children