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

Share on print
Share on facebook
Share on linkedin
Share on whatsapp
Share on email

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.

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

Prerequisites

  • 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.
    Note
    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: https://support.google.com/chrome/a/answer/3504942#sslinspection.

Configure Chrome Device Management

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

Important
Please note the specific configurations required by Appspace, stated in each step. Leave all other settings as default.
  1. Create a new Organizational Unit by following the instructions in the Add an organizational unit article here: https://support.google.com/a/answer/182537?hl=en
  2. Configure the Manage guest sessions settings by following the instructions in the Managed guest session devices article here: https://support.google.com/chrome/a/answer/3017014?hl=en&ref_topic=2935995.
    Please note the specific configurations required by Appspace, as listed below:
    • MANAGE GUEST SESSION SETTINGS


      • General
        • Managed guest session: Set to Allow managed guest sessions.
        • Session display name: Enter Appspace or the desired session name to be displayed on the login screen.
        • Maximum user session length: Ensure this field is left blank.
      • Content
        • Screenshot: Set to Allow users to take screenshots and video recordings.
      • Hardware
        • Audio output: Set to Enable Audio Output.
  3. Configure the Device settings by following the instructions in the Set Chrome OS Device policies article here: https://support.google.com/chrome/a/answer/1375678
    Please note the specific configurations required by Appspace, as listed below:
    • DEVICE SETTINGS
      • Kiosk Settings


        • Click the new apps & extensions page to make the following settings:
          • Auto-launch app: Set to Appspace


            1. Click the Add from Chrome Web Store icon, and search for “Appspace”.
            2. Select and add the Appspace app, and in the Auto-launch app dropdown menu, select Appspace.
          • Auto-Launch Kiosk App Settings side panel
            • Enable Health Monitoring: Toggle switch to Enable
            • Enable System Log Upload: Toggle switch to Enable
        • Managed Guest session: Set to Allow managed guest sessions
      • Power and shutdown


        • Reboot after uptime limit: Set to 1
        • Scheduled Reboot: Set to Enable schedule reboots, and proceed to select the Time (HH:MM) and select Daily for Frequency.
  4. Configure the User & browsers settings by following the instructions in the Set Chrome policies for users or browsers article here: https://support.google.com/chrome/a/answer/2657289.
    • USER & BROWSER SETTINGS


      • Content
        • Screenshot: Set to Allow users to take screenshots and video recordings.
      • Hardware
        • Audio output: Set to Enable Audio Output.
  5. Once done, proceed to the Configure Kiosk Mode on Chromebox section below.

Configure 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:https://support.google.com/chrome/a/answer/1360534 

    Important
    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

Important
  • 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 102, 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 v101 and below, the Appspace App will trigger an upgrade to Chrome v102.
  • If you are running Chrome v102, the Appspace App will keep Chrome at that version until Appspace verifies the next stable version.
  • If you are running Chrome v103 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:

Important
You must have Google Admin credentials with a G Suite (Google Apps) account.
  1. Configure the Device settings by following the instructions in the Set Chrome OS Device policies article here: https://support.google.com/chrome/a/answer/1375678

    • DEVICE SETTINGS


      • Device update settings
        • Auto-update settings: Set to Block updates
        • Kiosk-controlled updates: Set to Allow Kiosk app to control OS version. You will be required to verify the Kiosk’s app manifest file having the correct “required_platform_version” value.
  2. Once done, click SAVE.

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