Skip to main content
Version: 25.2

ChromeOS

The ChromeOS agent allows the inclusion of devices with this operating system in the service consoles, thus enabling complete visibility for support teams, both desktop and mobile devices of users.

Requirements​

To deploy FlexxAgent on Chrome devices, it is necessary to have a mobile device management (MDM) platform, such as Google Admin, which allows centralized distribution and installation of the application.

Once the MDM solution is configured, FlexxAgent can be installed from Google Play.

Supported versions​

FlexxAgent runs on ChromeOS devices version 112 or later. The ChromeOS Flex edition is not supported.

Limitations​

Due to restrictions of this operating system, some functionalities are not available on this type of devices. These include: execution of power actions, remote assistance, flows, user microservices, or execution of microservices from Workspaces.

Some devices, to save battery, stop services or cannot connect to the internet while their screen is locked. When this happens, the device may stop reporting for a while until its screen is unlocked. This behavior varies depending on the manufacturer and the version of the operating system.

Download and installation​

FlexxAgent is available as a private Android app on Google Play.

Flexxible will grant access to FlexxAgent in the Managed Google Play console during the onboarding process.

FlexxAgent requires a managed configuration to be deployed. This configuration will be provided in JSON format by a Flexxible contact during the onboarding process.

Installation​

In broad strokes, the procedure is as follows:

  1. Go to Devices -> Chrome -> Apps and extensions -> Users & browsers and select the organizational unit (OU) in which you want to deploy the app.
  2. Add the app from Google Play (search for FlexxAgent), assign the managed configuration (JSON), and mark it as Force install.

Please review the MDM documentation on how to deploy Google Play applications for managed users.

Please review the linked links for more information on registering apps or deploying them to managed users in Google Admin.

To ensure FlexxAgent configuration applies correctly, the app must be manually opened on each device at least once after installation. It is recommended to follow these steps:

  1. Go to Google Play and navigate to Manage apps and devices. chromeOS_install_1

  2. Go to the Manage tab and click on the FlexxAgent application. chromeOS_install_2

  3. On the application's detail screen, click Open. Next, a window will appear confirming that the app has been successfully configured. chromeOS_install_3 chromeOS_install_3

  4. Close the window.

When running FlexxAgent on a ChromeOS device, the fixed notification indicates that the agent is installed and running.

chromeos

Update​

FlexxAgent updates automatically from Google Play.

Information obtained from the device​

chromeoswks

FlexxAgent obtains and sends the following general information to the consoles:

  • Device Name
  • Device Status: on or off
  • FlexxAgent version
  • FlexxAgent Status: running or stopped
  • Last FlexxAgent report: date and time of last report received
  • Connection: Wireless LAN, mobile network or unknown
  • Network: device network addressing and public IP for internet access. These networks are created automatically when more than four workspaces are connected to the same network.
  • Subnet: network segment of the device.
  • Network changes: last time the network changed
  • Sessions: number of user sessions
  • Last User: last user who logged in
  • Connected From: name of the device from which the user has logged in
  • Connection Time: date and time of session start.
  • Code: this field lets users identify the workspace with a personal code. This code must be manually filled in individually using the Edit option in the Operations menu of the workspace details.
  • RAM: total available RAM capacity
  • Cores: number of processor cores
  • IP address: device IP address on the local network
  • OS: operating system name
  • Operating system: operating system version
  • Uptime: time the device has been running since it was last started or rebooted.
  • Reboot Pending: shows if the device requires a reboot for updates.
  • Public IP and ISP: the ISP is obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
  • Region: obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
  • Session Analyzer: whether configured or not
  • Session Analyzer version: Session Analyzer version number
  • Report group: report group to which the device belongs

chromeosalz

General device data, as well as the installed applications and their versions, are sent to the Analyzer.