MindLink Mobile supports Android for Work deployments.
1 Android for Work - Deployment
MindLink supports the deployment of our mobile app through Android for Work. Before beginning the deployment process ensure that Android for Work is enabled.
To enable Android for Work, AirWatch administrators can leverage token-based setup by visiting the Google portal, verifying their domain and obtaining an EMM token for Android for Work. Administrators will then upload and verify the token in AirWatch.
Assuming the above has been done, to begin deployment through Android for Work you will want to head to the 'Apps & Books' section of the AirWatch console.
Once you have opened the 'Apps & Books' tab you will want to open the 'List View. From here you will want to navigate to the 'Public' tab.
Add the application
Once you are ready to add the application, you will want to press the 'Add application' button as shown above.
Once you have pressed the 'Add Application' button you will be presented with the above screen. Here you will want to select the 'Search App Store' option, this will search the Google Play Store for the MindLink Mobile app. Ensure that the chosen platform is Android.
When the search term 'MindLink' has presented itself you will want to click the 'Select' button. This will allow you to configure the various options based around the applications, such as deployment.
Once you are happy with the configuration of the application deployment, you will want to ensure that the option 'Device must be MDM managed to install this App' is ticked. When this is selected, enrolment using Agent leverages the Android for Work functionality thus allowing you to manage the app through the AirWatch console.
2. Per-app VPN
The VPN Profile will alter how you connect. As the name suggests, it is applied on a per-app basis and will alter the behaviour of your application(s) to utilise the AirWatch VPN Connectivity.
2.1 Creating the per-app VPN
Add app profile In order to begin leveraging an app specific VPN to Android for Work enabled MindLink, you will need to create a profile specific to your Android for Work deployment. This guide will walk you through the VPN section so as to enable MindLink to utilize an app specific VPN.
Once you have clicked 'Add' you will want to choose the platform which in this case is 'Android'.
When you have chosen your platform, you will want to select 'Android for Work' as shown above
Once you have reached this stage you can begin configuring the app-specific VPN. Note: that the settings here will depend on your existing IT infrastructure and is as such custom to your organisation.
2.2 Applying the per-app VPN
By utilizing the AirWatch console you are able to enable an app-specific VPN configuration which will be applied to your Android for Work enabled MindLink Mobile app. To begin this process head to the 'Apps & Books' section of the AirWatch console.
Once you have completed the above step you will want to navigate to the 'Public' tab from here you will want to look for the 'MindLink' app under 'app source' you will want to look for Android for Work.
Once you located the application you will want to click on the 'Edit' button, from here you will be able to enable the app-specific VPN which will be leveraged by the MindLink Android for Work enabled app.
Once you have clicked 'Edit' you will be brought to the screen above, if you navigate to the 'Deployment' tab you will want to enable the 'Use VPN' option and will then want to select your VPN specific profile that you created earlier. Note: that the profile used will be entirely dependent on your setup and organisational standards. Once this is done assuming everything is setup correctly Android for Work enabled MindLink will be leveraging the VPN profile you have created.
3 Pre-configuring the username and server details
To start you will want to navigate to Apps & Books > Applications > Native, where your applications should be available
Beginning the assignment
From the list of applications you will want to select your MindLink app using the radio button (purple box). Then click the Assign button.
Edit the assignment After clicking assign you will be met with the assignments window
Select the assignment group (in our case we simply use 'All devices' but you may have several of your own, so ensure you choose the one you wish to apply.)
Click 'Edit' to make your configuration changes. You will be met with a window similar to the following:
Application Configuration Scroll down to find the Application Configuration section
begin by enabling application configuration. By default this is disabled, and the configuration key section is not shown.
Once enabled the section where configuration keys are added will be shown. The values for this may depend on your setup, but in this case the keys are:
- mlmServerUrl : The server address that the device will connect to.
- mlmLogOnUrl : The name to pre-authenticate the username field with.
Save the configuration Once you have entered the preconfigured data it is time to save and push changes to the device.
On the next screen you will see the Save And Publish button.
You will then transition to a window to preview the assigned devices, from which you can publish the changes. It may be good to double-check the list of devices to ensure your target device(s) are there, after which you can publish.
Once published the configuration is ready for the device to receive.
Preconfigured values on the device Once changes have been made to the configuration the device will need to Send Data through the AirWatch device application so that it will sync with the AirWatch console. After a successful sync the configuration changes should push to the device and preconfigure the server URL and/or Username field.