Why the profile doesn't get assigned(pushed) to the devices ?

Why the profile doesn't get assigned(pushed) to the devices ?

I connected my android plus devices to the SOTI Mobicontrol and my devices are sowing in the Mobicontroldashboard. I can do some simple actions like "Send a message", "Lock" on my devices using Mobicontrol. 
Now i want to send some configurations like SOTI Surf, Lock Down and some apk files (using package) to the devices. For this i created a profile and set all my configurations and set my package in this profile. But when i try to assign this package to my device , these configurations or packages doesn't get reflected in the devices. Also the dashboard shows that "no devices assigned".
i am getting no error message. Screenshots attached. 
Can you please help me to resolve this issue ? 

PS: I have disabled my firewall to make sure no port is blocking. 

 

9 Answers

Order By:   Standard | Newest | Votes
Raymond Chan | posted this 22 January 2019

What are the active MDM API's reported in your web-console or in the Device Configuration tab of your device agent?

 

Is your profile an Android Plus profile or an Android Enterprise profile?

 

  • 0
  • 0
Sherry, Melukadaval | posted this 22 January 2019

Active MDM API reported on the Device is  -- Work Profile, Remote View (1.11.0.102).
I don't know where the same thing will be displayed in the MobiControl web console. But in MobiControl when clicking on this device, it is showing the Supported APIs as 'Remote View, Work Profile'. 
Profile is an Android Plus profile. 

 

  • 0
  • 0
Raymond Chan | posted this 22 January 2019

Your device is in Android Enterprise Work Profile mode (for BYOD use case), but the profile is for Android Plus device.  That's why your created profile won't be deployed to the device.

 

You have to create a new profile targeted for Android-Enterprise platform i(near the bottom of the "General" tab).  Please also note that Work-Profile mode only supports a small subset of Android Enterprise policies.  If you want to test out the full set, you have to factory reset your device and force it into Managed Device/Device-Owner mode of Android Enterprise platform.

 

  • 3
  • 1
Raymond Chan | posted this 22 January 2019

Your device is in Android Enterprise Work Profile mode (for BYOD use case), but the profile is for Android Plus device.  That's why your created profile won't be deployed to the device.

 

You have to create a new profile targeted for Android-Enterprise platform i(near the bottom of the "General" tab).  Please also note that Work-Profile mode only supports a small subset of Android Enterprise policies.  If you want to test out the full set, you have to factory reset your device and force it into Managed Device/Device-Owner mode of Android Enterprise platform.

 

  • 3
  • 1
Matt Dermody | posted this 22 January 2019

Raymond is right. You first need to understand what sort of management scenario you want to leverage depending on your usecase (BYOD, COPE, COSU, etc and Android+ vs. Android Enterprise). The identified management scenario will then dictate which enrollment process you leverage and then which configurations and management policies are applicable. 

  • 1
  • 1
Sherry, Melukadaval | posted this 23 January 2019

I changed my profile to Android enterprise and it got installed successfully in the device. Thanks Raymond and Matt for helping me out. 
Now i face another issue when i try to push some configurations like Feature Control (Disable Bluetooth), Applications Run Control to restrict the use of Youtube and etc , it shows the profile is installed in the device. But in the device i can still access & manage bluetooth and  play vidoes in youtube, etc  , means those restrictions doesn't get reflected. 
Screesnshots attached. 
Does it need any additional configuration to work ?.

  • 0
  • 0
Raymond Chan | posted this 23 January 2019

As said in earlier post, your device is in work-profile (BYOD) mode, in which only a very small subset of MDM features are supported for your work-profile apps targeting a file/memory space separated from your personal  app/space   E.g. over 90% of Feature-Control options are for "managed-device" mode and won't work in your work-profile mode.  These behaviours are defined by Google and  are the same for any MDM solutions in the market.

 

 

To use what you have set up as shown in your screenshots for the whole device just like for Android+, you have to do the following to get it into Managed-Device mode in Android Enterprise:

 

1. Create a NEW add-devices rule.  In its "Android Management" tab, select a Managed-Google-Play Account (you need to create one if you don't have any integrated earlier. The web console should bring you to the right Google portal to do this). Save and publish the rule  to get an enrollment ID.

 

2. Factory reset your device.  Select language, Wifi, etc as usual.

 

3. Enter afw#mobicontrol as the Google user account name when you are prompted input an "existing" Google account.

 

4. Follow the instructions shown on your device screen.  Keep your device online to get all required software downloaded (usually take a few minutes).  Agree to all terms & conditions.  Input the enrollment ID for the rule created in step (1) with the MobiControl AE device agent automatically downloaded.

 

5. After successful enrollment, you'll find the active MDM API to have an item like "Work Managed device".   Assign your previous profiles to this device and test again.

  • 2
  • 1
Matt Dermody | posted this 23 January 2019

For step 3 you can optionally also use the Mobicontrol Stage Programmer available for download in the Play Store. You could install that app on a staging device of sorts and then use it to stage the devices via QR code or NFC bump if the device supports it. The NFC bump method requires the least amount of manual intervention of those options but does require hardware that supports it. 

  • 1
  • 1
Sherry, Melukadaval | posted this 29 January 2019

Hi Raymond,
Thanks for your support.
I configured my device OS and SOTI profile for Android plus instead of Android enterprise and used the SOTI lock down feature to control the device. It is working as per my requirements. 

@Matt, As you suggested i used the QR code downloading the agent to my other devices and for enrollement as well. Thank you . 

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback