Mobile Endpoint Agent Installation on ChromeOS Devices

This guide outlines the policies and configuration steps required to seamlessly deploy the ThousandEyes Mobile Endpoint Agent (MEPA) across your ChromeOS fleet using Google Workspace Endpoint Management (EMM). By leveraging this approach, you can ensure the agent installs with minimal user interaction and runs continuously in the background, providing reliable, uninterrupted monitoring for your devices.

Managed Deployment Requirements

For MEPA to function correctly, you need:

• Managed Google Play installation of the agent.

• Managed configuration set correctly, including a valid connection string from your ThousandEyes organization.

• Permissions granted.

• Location services enabled.

• Battery optimization exemption granted.

• Exact alarms capability granted.

• App links registered so links open in the app.

Application auto launch is unsupported on ChromeOS and must be initiated manually by the user once. Google is expected to address this limitation as part of its work to merge Android and ChromeOS into one unified platform. For more information, see Building a faster, smarter Chromebook experience with the best of Google.

Interactive Installation

You can register ChromeOS devices manually by using QR code registration or deep link registration.

QR Code Registration

1. Download and install the ThousandEyes Endpoint Agent from Google Play.

2. In the ThousandEyes platform, go to Endpoint Experience > Agent Settings and select Add New Endpoint Agent.

3. Select Android.

4. Click on Generate Link then download QR Code Image.

5. From the ChromeOS device, open the Mobile Endpoint Agent app and scan the QR code to register the device when prompted.

QR code registration requires a ChromeOS model with a back-facing camera. If the device does not have a back-facing camera, use deep link registration.

Deep Link Registration

1. Download and install the ThousandEyes Endpoint Agent from Google Play.

2. In the ThousandEyes platform, go to Endpoint Experience > Agent Settings and select Add New Endpoint Agent.

3. Select Android.

4. Click on Generate Link and Copy the Activation Link

5. From the ChromeOS device, open the Mobile Endpoint Agent app and follow the on screen steps. Please ensure 'Link Handling on the Device' is configured prior to starting deep link registration. ChromeOS devices open links in Chrome by default. For deep link registration, configure registration links to open in the Endpoint Agent app instead of Chrome.

You can configure link handling locally on the device or globally through Google Workspace Endpoint Management (EMM).

Configuring Link Handling on the Device

On the ChromeOS device, configure device system settings so supported registration links open in the Endpoint Agent app. The option to select how links should be opened can be found at Device System Settings -> Apps -> Manage your apps -> Endpoint Agent -> Opening supported links -> Open in Endpoint Agent app

Configuring Link Handling Through Google Workspace Endpoint Management

If you deploy the app through Google Workspace Endpoint Management, configure link handling globally.

In Google Workspace Endpoint Management, go to Devices > Chrome > Settings > Users & browsers > Open links in Chrome browser by default.

Set the policy so ChromeOS devices do not open Endpoint Agent registration links in Chrome by default. After the setting is applied, ChromeOS devices can enroll with ThousandEyes using the deep link.

If you do not configure one of these options, the registration link might open in Chrome instead of the Endpoint Agent app, which prevents registration from completing successfully.

Managed Deployment Steps

1. Application Deployment

Navigate to:

Devices > Chrome > Apps & extensions > Users & browsers

Configure:

• Add app > Managed Google Play.

• Select ThousandEyes Endpoint Agent.

• Set Installation policy to Force install.

• Accept all permissions.

Permissions

When you deploy through Managed Google Play in a managed environment, required runtime permissions are granted automatically by administrator policy. You do not need to complete extra prompts for standard permissions.

a. Background Execution

In managed ChromeOS environments, certain capabilities required for background execution might be permitted automatically, depending on device policy and management configuration.

This can include:

• Battery optimization exemption (might be applied automatically in managed environments).

• Exact alarm capability (might be available depending on system policy).

These behaviors are not guaranteed across all environments. They are ultimately controlled by the Android platform and device policy.

b. Foreground Service

ChromeOS aggressively manages background applications. Without additional measures, apps might be deprioritized, processes might be killed under memory pressure, and background tasks might stop running.

To keep MEPA running in the background, the application runs a foreground service on ChromeOS. This provides elevated process priority (lower out-of-memory score), continuous background execution, reliable scheduling of tasks, and stable location access.

How to confirm it is running

The foreground service:

• Starts automatically when the application runs on ChromeOS devices.

• Displays a persistent notification (as required by Android).

• Remains active for the duration of monitoring.

2. Managed Configuration

In the app configuration panel, add the required JSON configuration:

{
  "connection_string": "YOUR CONNECTION STRING",
  "device_name": "${DEVICE_SERIAL_NUMBER}",
  "skip_terms_of_service": true,
  "auto_register_agent": true,
  "close_app_after_registration": true
}

This configuration:

• Associates the agent with the correct ThousandEyes organization.

• Applies device naming and automatic registration.

3. Google Admin MDM Policies to Update

Configure the following policies for a successful deployment.

a. Location Services

Ensure device location is enabled.

Devices > Chrome > Settings > Users & browsers > Google location services

Set Allow geolocation access to all apps and websites.

• Location services must be enabled for the device.

• This allows the application to retrieve location data.

b. App Links (Open in App)

Devices > Chrome > Settings > Users & browsers > Open links in Chrome browser by default

Set Open links in Android apps by default.

First Launch Behavior

Due to ChromeOS platform constraints, apps cannot be launched silently after installation.

Google and Cisco remain committed to working together to support seamless enterprise deployment of the ThousandEyes Mobile Endpoint Agent on ChromeOS and future Googlebook.

The application is initially in a stopped state after deployment. Manually launch the app once to:

• Exit the stopped state.

• Register background services.

• Apply managed configuration.

• Begin scheduled tasks.

• Start the foreground monitoring service.

If the managed configuration includes:

"close_app_after_registration": true

Then a single launch is sufficient to complete onboarding. After registration is complete, the application closes automatically and returns to the background, allowing the device to continue normal operation without further user interaction.

Fallback Handling

If any required settings are not applied automatically, the application provides:

• An in-app dashboard indicator.

• Clear visibility of missing permissions or settings.

• One-tap actions to resolve issues.

This design keeps required user effort small.

Verifying the Agent Installation

After the device syncs, the process can complete automatically. To verify that the agent is registered to your ThousandEyes organization, log in to the ThousandEyes platform and go to Endpoint Experience > Agent Settings. The newly installed agent should appear in the list, confirming successful registration and connection to your organization.

Registered ChromeOS Endpoint Agent in Agent Settings

Additional Resources

• For licensing, supported tests, views, dashboards, alerts, and limitations that apply to all mobile agents (including ChromeOS), see Mobile Endpoint Agent Installation on Android Devices.

• For permission identifiers and additional MDM patterns, see Silent Deployment of Mobile Endpoint Agent (MEPA) on Android Devices using Mobile Device Management (MDM).