Roaming not enabled by Feature-Control

Roaming not enabled by Feature-Control

I have a profile that includes a Feature-Control setting to enable Data Roaming. I have devices picking up this profile, however when I go into the Android settings I can see that roaming is still disabled. Is there another setting that needs to be changed somewhere?

7 Answers

Order By:   Standard | Newest | Votes
Raymond Chan | posted this 09 October 2019

Are you using Android+ or Android Enterprise device agent?

What is the brand/model of the device with probem?  Please note that not all feature-control options shown are supported for all brands/models, especially for the Android+ device agents.

 

  • 0
  • 0
Jake Ward | posted this 09 October 2019

Thanks Raymond, we are using Android Enterprise. 

The device is an Energizer P490S

  • 0
  • 0
Matt Dermody | posted this 09 October 2019

Are the devices Fully Managed under Android Enterprise or are they just enrolled with Work Profile. Unless they're managed with AEDO I do not believe that feature is applicable:

 

  • 0
  • 0
Jake Ward | posted this 10 October 2019

The devices are enrolled at initial setup using afw#mobicontrol. In the add devices rule the Android Management option is set to 'Managed Google Play Accounts'. Is anything else required for these to be fully managed?

  • 0
  • 0
Matt Dermody | posted this 10 October 2019

That is a valid method for achieving AEDO fully managed status, however I would just double check what management state they’re currently in to verify that it got set up correctly. I have seen bugged MobiControl agents that result in Work Profile even if you use the proper enrollment method.

  • 0
  • 0
Jake Ward | posted this 10 October 2019

Thanks Matt, I think these have picked up the correct management state...

  • 0
  • 0
Matt Dermody | posted this 10 October 2019

Yup, that looks right. One other thing you can try is to toggle the opposite value for the setting in Feature Control. I have seen situations where the description for a setting ended up confusing what Enable vs Disable meant. It’s worth trying both values since the default option is to let the user configure. I would also verify that you’ve created an Android Enterprise Profile and not an Android+ Profile. If none of that works your next step is to probably open a case. To RC’s point every setting will not be supported by every manufacturer and a somewhat obscure manufacturer like Energizer probably doesn’t even have an AE plugin.

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback