Configure Appspace App on Chrome OS with Chrome Enterprise (CDM)

This article provides instructions to configure the Appspace App for Chrome OS devices that are managed by Chrome Enterprise, previously known as Google Chrome Device Management (CDM).

We also provide instructions to allow Appspace to manage your devices automatically by pinning the Chrome OS at our recommended version for seamless device and app management.

For individual Chrome OS based devices not managed by a CDM, you may refer to Install Appspace App and Configure Chrome OS Devices.


  • The device must meet the manufacturer’s minimum hardware and technical specifications. Please refer to Supported Devices & Operating Systems.
  • Google Admin credentials with a G Suite (Google Apps) account.
  • An active Appspace account, with sufficient device licenses to register the device.
  • An active Internet connection.
  • A USB keyboard for activation.
  • It is recommended that the device clock is set to automatically retrieve time from a Network Time Protocol (NTP) server, with the correct time zone, in order for it to sync correctly with the Appspace server.
    Appspace cloud servers by default retrieve time from a NTP server. If an Appspace on-premises server is used, ensure the server time is automatically retrieved by a NTP server.
  • Please ensure your network is configured to allow Appspace Approved URLs and the relevant network ports.
    On your proxy server, ensure our approved URLs are listed in the ‘How to set up networks with SSL content filters’ section in the following article:

Setup Chrome Device Management

Follow the instructions below to set up Chrome device management via Chrome Enterprise:

Please note the specific configurations required by Appspace, stated in each step. Leave all other settings as default.
  1. Create a new Organizational Unit (OU) for Users by following the instructions in the ‘Add an organizational unit for users’ section in the following article:

  2. Configure the Public session settings by following the instructions in the ‘Public session settings’ section in the following article:

    Please note the specific configurations required by Appspace, as listed below:

    • General

      • Session Display Name: Set the Public Session to ON
      • Maximum User Session: Leave this field blank
    • Content > Screenshot: Set to ‘Enable Screenshot

    • Hardware > Audio Output: Set to ‘Enable Audio Output

  3. Follow the instructions in the ‘Manage device settings’ section in the following article:

    • Kiosk Settings > Kiosk Settings

      • Public Session Kiosk: Set to ‘Allow public session kiosk

      • Auto-Launch Public Session: Set to ‘No

      • Auto-Launch Kiosk App: Set to ‘Appspace

        1. Click the Manage Kiosk Applications link.

        2. In the Kiosk Apps window, click Chrome Web Store, and search for “Appspace”.

        3. Click the Add link next to the Appspace App.

        4. In the Auto-Launch Kiosk App drop-down menu, select ‘Appspace’.

          You may choose to enable device health monitoring and device system log upload, if desired.
    • Power & Shutdown > Schedules Reboot: Set as ‘1’ to reboot daily

  4. Configure the User Settings by following the instructions in the ‘Set Chrome policies for users’ section in the following article:

      • Content > Screenshot: Set to ‘Enable Screenshot

      • Hardware > Audio Output: Set to ‘Enable Audio Output

  5. Setup the Kiosk mode as per the instructions in the Setup Kiosk Mode on Chromebox section below.

Setup Kiosk Mode on Chromebox

Follow the instructions below to set up the Kiosk mode:

  1. Enroll the device by following the instructions in the ‘Manual enrollment’ section in the following article: 

    The device must be brand new for this to work. If you have previously signed in to this device, you must perform a factory reset before the Enterprise Enrollment can work.
  2. The device will begin to download the policy settings and kiosk application. Once this is complete, ‘Restart’ is displayed in the bottom left menu, instead of ‘Shut down’.

  3. Click Restart. The device reboots, and launches the Appspace App.

  4. Your device is automatically registered.

Configure Chrome Version Control

  • You must upgrade the Appspace App to version 2.31 (and later) for this feature to work.
  • We recommend Chrome-based devices be pinned to Chrome OS 90, for the app to work seamlessly.

You can now allow Appspace App to determine the Chrome OS version that will be installed on your devices. With this feature enabled, Chrome firmware upgrade will only occur after Appspace engineers have fully verified the Chrome OS version and the Appspace App function well together.

Enabling this feature will result in the following:

  • If you are running Chrome v89 and below, the Appspace App will trigger an upgrade to Chrome v90.
  • If you are running Chrome v90, the Appspace App will keep Chrome at that version until Appspace verifies the next stable version.
  • If you are running Chrome v91 and above, the Appspace App may not work as originally intended. It is not possible to automate a rollback of Chrome. 

To configure the Chrome device settings to disable auto updates and allow Appspace App to control the Chrome OS version, follow the instructions below:

You must have Google Admin credentials with a G Suite (Google Apps) account.
  1. Navigate to Device settings as per the Manage Chrome device settings article:
  2. To disable auto-updates, navigate to Device Update Settings, and select Stop auto-updates in the Auto Update drop-down menu.
  3. To allow Appspace App to control the OS version, navigate to Kiosk Settings, and select Allow kiosk app to control OS version from the Allow Kiosk App to Control OS Version drop-down menu.
  4. Confirm and verify your selection.
  5. Save your settings.

Chrome Enterprise Features

The table below provides a description of the features in Chrome Enterprise (Chrome device management).

Feature Description Management Console
Firmware / OS Upgrade Perform and determine when Firmware/OS updates are done. Yes
Reboot Reboot device on-demand and on schedule. Yes, on-demand reboot request can be sent to specific devices running Kiosk Apps, or via OU policies.
App Restart Restart application on schedule. No
Run Application with Parameters Start application, with set of parameters. For auto registration to Appspace. Yes, via config file.
App Status Displays status of application. Yes
Device Status Displays status of device, whether online or playing an application. If device is offline, it displays last known online time. Yes
Crash Report Detect application crash, and relaunch via email. Yes, crashed app will restart. Application freeze will remain frozen.
App Control Push different applications to different devices based on predetermined groups. Yes, based on OU.
App Updates Push application updates to one or more devices from a central location. Not on-demand, updates go through at next reboot.
Automatic Login Automatically log into the device and launch an application, or launch an application within login. Yes, application required to be a Kiosk App, and will be launched before login.
File Management Delete or download files from the devices. For log gathering. No
System/Device Info Get CPU, memory, and disk space information, both total and current use. Trigger warnings when CPU or memory usage is too high or when disk space is low. Yes
Network Settings Set up Ethernet and WiFi, with proxy information if available. Yes
NTP Set up NTP server and timezone on devices. Supports 5h timezones. No, Google Time. Device requires specific list of websites in order to function correctly.
SSL Certificate Installation Install SSL certificates generated by enterprise CALs. Yes
Screen Control Turn screens connected to a device ON and OFF. No
Screen Capture Take screenshots, so remote users are able to see what is being played on the device. Yes
Screen Rotation Rotate the screen to support portrait mode applications. No, unable to be done via policy.
Related Articles
Latest Articles