Prerequisites

Before you get started with UXI agent make sure that:

The Android device has OS version 11 or above.
Only devices with a camera are supported for manual onboarding. Devices without a camera can only be onboarded from the MDM using managed configurations.
Ensure connectivity with the UXI cloud. The device will need to be able to report results to the UXI cloud over the network it is connected to. The required URLs are described here.
Identify the wireless network the device is connected to. Make sure to create that exact wireless network in the dashboard first, then assign it to the group you plan to add the agent to. You do not need to add the credentials of the network for the agent to test it, but the network needs to exist and be assigned to the group the agent is in.

Getting Started

When you are ready to start using the UXI Agent, the first step will be to get a Provisioning Token / QR Code from your UXI dashboard. This Provisioning Token / QR Code is used by the agent to know which UXI dashboard the device belongs to.

Provisioning Token / QR Code for Existing Dashboards

To get a Provisioning Token / QR Code for an existing dashboard, go to Settings -> Agents and select Add Agent.

From the drop-down, select the group you want the sensors to appear.

From this screen, you can scan the QR code or copy the provisioning token to your clipboard to be used in your MDM.

Provisioning Token / QR Code for New Dashboards

To get a Provisioning Token / QR Code for a new dashboard, you can follow the steps in the onboarding wizard.

If you have never logged in to UXI before, you can create a new account here - https://help.capenetworks.com/en/articles/8678051-uxi-hpe-greenlake-cloud-platform-getting-started

On the first step on the onboarding wizard, select the type of sensor to be an Agent

On the next page, the QR Code / Provisioning token is displayed.

From this screen, you can scan the QR code or copy the provisioning token to your clipboard to be used in your MDM.

Install, Configure, and Start the Agent

The UXI Agent is available on Google Play or on the HPE Networking Support Portal.

It is recommended to install the agent from your MDM and use Managed Configurations to apply the provisioning token, but it can also be installed from Google Play or as an APK locally on the device.

If your MDM is not integrated with Google Play, you can also download the Agent from the HPE Aruba Networking Support Portal.

Note: During the provisioning process, the agent will attempt to derive a unique device identifier for the UXI dashboard. To derive a unique identifier, the agent uses a combination of device serial and device MAC address (if available). If you are provisioning a device for a second time, it's possible you will see duplicate device entries in your dashboard, especially if you changed what is being sent in the managed configuration or switched from QR code to the provisioning token. You can remove the old device entry from your dashboard.

MDM Installation and Configuration (Recommended)

This method is only available if you are using the agent from Google Play or your MDM supports Managed Configurations using the APK.

The agent supports Managed Configurations to install and configure the agent on your android devices quickly and easily. Each MDM has a slightly different workflow, but through your MDM you want to do the following:

Add the "UXI Agent” to your MDM from Google Play or upload the UXI Agent APK.
Ensure all permissions are accepted for the application.
For example, in Workspace One, this is set in your device profile
Install the agent to a select group of devices.
When installing the agent, send the configuration as follows:
- Enter your provisioning token provided by the UXI Dashboard in the UXI Provisioning Token field.
- Enter the variable for the device name in the UXI Device Name field.
- Enter the variable for the device serial in the UXI Device Serial field.
- Enter the variable for the device MAC Address in the UXI Mac Address field.
- Select Disable on the option for UXI Dialogs. This new option, only available in Agent version 2.4.1 and onward, accepts the automatic popups that advise the user about the agent permissions.
By using these variables, the device will use the device-specific properties from the MDM. For example, in VMWare Workspace One, the parameters will look like this - {DeviceFriendlyName}, {DeviceSerialNumber}, {DeviceWLANMac}

The agent must be started once. After that, it will automatically start when the device reboots. The agent can be started manually (the easiest way for testing a few devices) or via the MDM (easier for managing thousands of devices). The directions below describe how to launch the agent from Workspace One. We are not experts in MDMs, so if you want to share your process, please let us know via support.

In workspace one, navigate to Orchestration -> Components -> File Actions
- Click on ADD FILES/ACTIONS -> Android
  - Under the General tab:
  - Enter a name and a description (optional).
  - The Managed By field should be pre-filled in. If not, choose the group.
- Under the Manifest tab, configure the following then click Save.
  - Under Install Manifest, click Add Action and select Run Intent in Action(s) To Perform.
  - For Command Line and Arguments to run, enter the following (Case sensitive: No space before or after):
    mode=explicit,broadcast=false,action=android.intent.action.MAIN,category=android.intent.category.LAUNCHER,package=com.hpe.arubanetworking.uxi.agent.mobile,class=com.hpe.arubanetworking.uxi.agent.mobile.main.ui.MainActivity
  - For TimeOut, choose -1 for infinite (so that the command will be delivered in case a device is offline and comes back online later)
Save the file action
In workspace one, navigate to Devices -> Provisioning -> Product List View.
- Click ADD PRODUCT -> Android
- Under the General tab:
  - Enter a name and a description (optional).
  - The Managed By field should already be filled in.
  - In the Smart Groups field, choose all your smart groups.
- On the Manifest tab, configure the following then click Save.
  - Select click Add and select “File/Action - Install” in Action(s) To Perform
  - In Files/Actions, select the File/Action you configured previously.
  - Tick Persistent through enterprise reset if you would like this to persist after a device has been reset.
Under the Deployment tab, choose your activation date. If you would like the command to be sent automatically, choose a date prior to your current time.
Click Activate.
After 30 seconds to 2 minutes, if your device is online and has access to the internet, the app should launch automatically.
If you need to auto-launch the app the second time, under the product list view, click on the number under Compliant, tick the device(s), and click on FORCE REPROCESS, and click OK to confirm. After some time, the app should launch.

Local Installation and Configuration

If you are not installing the agent through your MDM, you can install it locally on the device from Google Play or from the HPE Networking Support Portal.

Install the "UXI Agent”
Start the agent on the device, grant all requested permissions in the most permissive settings
Scan the QR code obtained from your UXI dashboard. You can scan using the device camera. If the device does not have a camera, you can scan the QR code on Zebra devices using the built-in barcode scanner. If you are using the camera, select the option "link to dashboard" and grant permission to use the camera. If using the built-in barcode scanner, simply launch the agent and scan the QR code from the default screen of the agent.

Android Doze Mode and Battery Optimization

Although the agent has been optimized to minimize its impact on battery life, Android 11 and above have become more aggressive in optimizing background apps to preserve battery life.

To ensure the agent collects data in the background and prevents Android from ending the process, you must set the UXI agent application's Battery Optimization settings to “Do Not Optimize.”

You can do this manually on the device by following these steps:

Settings → Battery → Background usage limits → Never auto sleeping apps
Add the Aruba UXI Agent app

Please note that the steps may vary slightly depending on the phone manufacturer.

Post Installation Steps

Once the agent is started, it will appear on your UXI dashboard and begin reporting test results within 10 to 15 minutes. The UXI agent runs in the background on the device and performs low-impact synthetic tests to measure the end-user experience from the perspective of the handheld device.

The agent will only test networks that are defined in the "Wireless" list on the UXI cloud. You don't need to assign a network to the agent; when the agent connects to a network in the list, it will start testing the network.
The SSID name is the only mandatory field required to define a network for the agent to test it.
You must assign the SSID to the group the agent is in in order for the agent to test that network.

Example Scenario:

Previously, the agent automatically tested the user's home network and reported the results. Moving forward, this automatic testing will cease unless the user's home network—at the very least its SSID—is defined in the "Wireless" network list on the UXI dashboard and the network is also assigned to the group the agent is in.

The agent can only test the network it is connected to. You cannot change the network settings as you would for a hardware sensor.