Implementing Chrome OS Player implementing-chrome-os-player

This section describes how to implement the Chrome OS Player using the Chrome Management Console.

Using Chrome Management Console using-chrome-management-console

Follow the steps below to set up the Chrome management console:

  1. Register for the Chrome Management Console. You must obtain a license for Chrome Management Console. Contact Google Support to Manage Chrome device settings for more information.
  2. Enroll your Chrome OS Device into the domain and wait for 15 minutes for the device to sync with the Chrome Management Console. To learn more about enrolling Chrome device, click here.
  3. The Chrome Player is available in the Chrome Web Store.
A device management solution such as the Chrome Management Console is recommended for deployment and management of Chrome OS Devices. Although this document provides implementation for Chrome Management Console there are other vendors who claim to provide similar functionality. Contact the vendor of your device management software.

Naming Chrome OS Player name-chrome

You can assign a user-friendly device name to your Chrome Player, thus sending the assigned device name to Adobe Experience Manager (AEM). This capability not only lets you name your Chrome Player but also lets you easily assign appropriate content.

You can choose the Player name only before registration. After the Player is registered, the Player name cannot be changed anymore.

Follow the steps below to configure the name in Chrome Player:

  1. You can optionally allow Audio-Video integrators or IT administrators to set the Asset ID and location as part of enterprise enrollment.


  2. You are presented with the options when you can enroll the device.


  3. You can set the Asset ID as part of enterprise enrollment and in the Chrome Management Console.


    note note
    Chrome Players must be enrolled in enterprise enrollment and the Chrome Player must be deployed through Chrome Management Console, otherwise the Asset ID returns blank (for example, Chrome as an extension). The device name is only recorded at the time of registration. Future changes do not get picked up by Adobe Experience Manager (AEM).

Enabling Kiosk Mode enabling-kiosk-mode

Follow the steps below to enable the Kiosk mode:

  1. Log in to the Chrome Developer Console.


  2. Browse to Device Management > Chrome Management > Device Settings.

  3. Scroll down to Kiosk Settings and click Manage Kiosk Applications.


  4. Click the AEM Screens Player from the Chrome Web Store.

    note note
    A recently published app may take about 15 minutes to appear in this list.
  5. Click AEM Screens Player from the Auto Launch Kiosk App dropdown.

    It may take a few minutes depending on the network for the changes to take effect. A reboot is recommended.

Checking Remote Device Status checking-remote-device-status

  1. Log in to the Chrome Developer Console.
  2. Browse to Device Management > Chrome Devices and click the device you want to control.
  3. Click System Activity and troubleshooting.
  4. Check the Reboot Device and Screen Capture properties of the device. You can also check the device status and health information.
These settings can be enabled several minutes after the device is enrolled. Each option can become enabled over time.

Configuring Remote Configuration of Chrome OS Players configuring-remote-configuration-of-chrome-os-players

The AEM Screens Player is a Kiosk enabled application that also enables Remote Policy Configuration for Chrome OS Players.

Follow the steps below to configure the various options of the player:

  1. Log in to the Chrome Management Console.
  2. Click Device Management > Chrome Management > App Management. The AEM Screens Player displays in the list.
  3. Click the application AEM Screens Player.
  4. Click Kiosk settings and click your org (if using a test environment).
  5. Click upload configuration file and upload the configuration policy (JSon file).
  6. Click Save. Reboot the device so you can sync the policy.
Reboot the device so you can sync policy changes.

Example Policy JSON file example-policy-json-file

  "server": {
    "Value": ""
  "resolution": {
    "Value": "auto"
  "rebootSchedule": {
    "Value": "at 4:00am"
  "enableAdminUI": {
    "Value": true
  "enableOSD": {
    "Value": true
  "enableActivityUI": {
    "Value": true

Policy attributes and purpose policy-attributes-and-purpose

The following table summarizes the policies with their functions.

Policy Name
The URL to the Adobe Experience Manager (AEM) server.
Used for bulk registration of devices using pre-shared key.
The resolution of the device.
The schedule to reboot the player.
Enable the Admin UI to configure the device on site. Set to false once it is fully configured and in production.
Enable the channel switcher UI for users to switch channels on the device. Consider setting to false, once it is fully configured and in production.
Enable so you can show the progress of activities such as download and sync. Enable for troubleshooting and disable once it is fully configured and in production.
Set to true if you want the Chrome Player to connect to Screens as a Cloud Service. Set to false to connect to AMS or on-prem AEM.
Registration token to register against Screens as a Cloud Service.
Policy configurations are strictly enforced and the player’s Admin UI does not override manually. To allow manual player configuration for a particular policy, do not specify the policy in the policy configuration. For example, if you want to allow manual configuration for reboot schedule, do not specify the key rebootSchedule in the policy configuration.

Using the Screens Remote Control using-remote-control

AEM Screens provides Remote Control functionality. Learn more about this feature here: Screens Remote Control