Implementing Chrome OS Player

Last update: 2023-11-08
  • Created for:
  • Intermediate

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

Using Chrome Management Console

Follow the steps below to set up chrome management console:

  1. Register for the Chrome Management Console. You need to 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 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 will be 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. Please contact the vendor of your device management software.

Naming Chrome OS Player

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


You can choose the Player name only before registration. Once 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 AV integrators or IT administrators to set the Asset ID and location as part of enterprise enrollment.


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


  3. You can set the Asset ID as part of enterprise enrollment as well as in the Chrome management console.



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

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. Select the AEM Screens Player from the Chrome Web Store.


    A recently published app may take about 15 minutes to appear in this list.

  5. Select 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

  1. Log in to the Chrome Developer Console.
  2. Browse to Device management > Chrome Devices and select the device you wish 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.

Please note that these settings maybe enabled several minutes after the device is enrolled. Each option may become enabled over time.

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 various options of the player:

  1. Login to 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 select select your org (if using a test environment).
  5. Click on upload configuration file and upload the configuration policy (Json file).
  6. Click Save. You must reboot the device to sync the policy.

Reboot the device to sync policy changes.

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

The following table summarizes the policies with their functions.

Policy Name Purpose
server The URL to the Adobe Experience Manager (AEM) server.
registrationKey Used for bulk registration of devices using pre-shared key.
resolution The resolution of the device.
rebootSchedule The schedule to reboot the player.
enableAdminUI Enable the Admin UI to configure the device on site. Set to false once it is fully configured and in production.
enableOSD Enable the channel switcher UI for users to switch channels on device. Consider setting to false, once it is fully configured and in production.
enableActivityUI Enable to show progress of activities such as download and sync. Enable for troubleshooting and disable once it is fully configured and in production.
cloudMode Set to true if you want the Chrome player to connect to Screens as a Cloud Service. Set to false in order to connect to AMS or on-Prem AEM.
cloudToken Registration token to register against Screens as a Cloud Service.

Policy configurations are strictly enforced and are not manually overridden at the player’s admin UI. 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

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

On this page