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

• 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.
• Please review Google’s supporting documents:
  • Long-term Support (LTS) on ChromeOS: https://support.google.com/chrome/a/answer/11333726
  • Manage updates on ChromeOS devices: https://support.google.com/chrome/a/answer/3168106#zippy=%2Cturn-on-auto-updates-recommended%2Cpin-chromeos-updates-to-a-specific-version%2Cchoose-a-release-channel 

Configure Kiosk Mode on Chromebox

Configure Chrome Version Control

There are 3 Chrome OS release channels available for consumers to update their devices, the first being the Stable (S) channel which is updated every 4 weeks, with minor updates consisting of security fixes and software updates every 2 weeks. Then we have the Long-Term support Candidate (LTC) and Long-Term Support (LTS) channels that have a slower release cadence, but are generally much more stable and secure.

With that in mind, Appspace recommends organizations pin their Chrome OS devices based on the latest Chrome OS release (LTS) channel, as organization devices are usually left unattended, running for long periods of time non-stop, and without the risk of breaking anything due to frequent feature updates if organizations were to pin to the Stable (S) channel. With that in mind, Appspace engineers focus their efforts on ensuring the latest Chrome OS (LTS) channel release is certified and supports all Appspace App functionality.

With versioning control enabled, you allow the Appspace App to determine the Chrome OS version, which is supported and certified by Appspace engineers, to be installed or updated on your devices.

Enabling this feature will result in the following:

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

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