Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 7 Next »

Step 1: Download the MDM Config File from the Cloud Services Portal

An app-config file is required to update an app’s configuration in MDM. To download the file from the Cloud Services Portal, do the following:

  1. Log in to csp.infoblox.com.
  2. Go to Manage Endpoints > Endpoint Groups.
  3. Select Download MDM Configuration, and click iOS Config File or Android Config File, depending on the type of the device the file is to be used with.



ImageThe Download MDM Configuration drop-down options for handling endpoint configurations within a network. The configuration options include: Android Config File, iOS Config File, and Chrome Config File. 


To assign an endpoint to a specific endpoint group, click  next to the name of the endpoint group and select Download MDM Configuration > Android or iOS Config File



ImageThe download MDM configuration options when applying a configuration option to an existing endpoint group. The configuration options include: Android Config File, iOS Config File, and Chrome Config File.

4. Save the downloaded config file to a directory where it can be located easily.

The MDM app config contains the following parameters:

  • joinToken: The value in the XML file.
  • groupName: In the Cloud Services Portal, the name of the group to which the endpoint will be moved. If the name is not present in the Cloud Services Portal, it will be added to the All BloxOne Endpoints group.
  • userId: The unique name used to identify a mobile device. The configured name is displayed in the Cloud Services Portal, on the Manage Endpoints page.
  • allowServiceControl: By default, this value will be True. To disallow and hide service control, use the toggle switch to change this value to False

In MDM, the app config can be added manually or by uploading the XML file.

Step 2: Register a Mobile Endpoint to the Microsoft Intune Server

  1. Install the Intune Company Portal app from the Google Play store or the Apple App store, according to the device type.
  2. Log in to the Intune Company Portal with the credentials provided by your admin.
  3. Follow the steps in the Intune Company Portal to register the device to the Microsoft Intune server.

Step 3: Add the BloxOne App in the Microsoft Intune Server

For Android:

  1. Go to Home > Apps > Android > + Add > Managed Google Play.
  2. In the Search field, type “BloxOne". Select the app.



Image
: The BloxOne Endpoint application page in the Google Play store. 

3. Find the BloxOne app in the list of apps.



Image: Locating the BloxOne app from among a list of Android applications.  

4. Open the BloxOne app, and add the assignments to the app.

Step 4: Upload and Add the App-config file

  1. Go to Home > Apps > App Configuration policies.
  2. Click +Add > Managed devices
  3. Provide information about the platform (iOS or Android), and select the targeted app.



Image: Creating an app configuration policy. 

For iOS:

Using the downloaded config file obtained from the Cloud Services Portal, add the configuration with the keys and values, and create the policy. Note: You can use the XML file or enter the key/value manually.

Note

BloxOne Endpoint version iOS 2.0.7 and above use the joinToken instead of customerId for authorization. For existing devices with older versions of the app the update to the latest version is automatic. Forr fresh installations on new devices, the joinToken should be updated in the configuration settings.



Image: Configuring an app policy for iOS. 


For Android:

Using the downloaded config file obtained from the Cloud Services Portal, choose each configuration key and add the respective value to it.

Note

  • BloxOne Endpoint Android version 1.0.9 and below require the customerId attribute value in the app configuration.
  • BloxOne Endpoint Android version 1.0.10 and above use the joinToken instead of customerId for authorization. For fresh installations on new devices, the joinToken should be updated in the app configuration settings.
  • The customerId attribute will be removed from app in future versions. You may need to maintain both customerId and the joinToken in the app configuration until such time all devices are update to 1.0.10 or above.



Image: Completing an app configuration policy and assignment for Android.  

2. Go to the device, and refresh the assignments.

This completes the enrollment process. 







  • No labels