Preconfiguring a wired network through the Google Admin console

A useful feature of Chrome Device Management is the ability to pre-configure networks on Chrome devices.

  1. After logging in to your Google Admin console, go to the Device Management section.
  2. On the column on the left side of the screen, click Networks. (Your console may say Network instead, under the Device Settings heading)
  3. Select the Organizational Unit (OU) you wish to apply the network to. If you don’t know which OU to select, pick the top level OU to apply the settings to all devices in the console.
  4. Click CREATE ETHERNET NETWORK.  
  5. In Platform access, check the box next to “Chromebooks (by device)”
  6. In Details, create a name for your network.  If your network requires Authentication (802.1X), you can configure the authentication credentials after selecting 802.1X under Authentication. Be sure to click Save when you’re done configuring the network.

 

Please visit Getting started with Chrome Device Management  for more information regarding Chrome Device Management.

Device Setup

Step 1. Connect your device to the internet

 

Ethernet Connection

If your ethernet connection doesn’t require any extra setup, plug your ethernet cable into your Chromebox and ensure the other end is connected to your switch or router and you should be all set!

If your ethernet internet connection requires additional setup, like a fixed IP address, or extra authentication setup, follow the instructions for manually connecting the device to a Wi-Fi network, but select the Ethernet connection to configure instead of the Wi-Fi network. Chrome Device Manual Wireless Configuration

 
ASUS Fanless Chromebox Ethernet Port LocationAOpen Chromebox Commercial 2 Ethernet Port Location

 

Wi-Fi Connection

First, if your device has external Wi-Fi antennas, connect the antennas now.

ASUS Fanless Chromebox Wi-Fi Antennas

 

If your Wi-Fi connection is not configured in the Google Admin console, you’ll need to manually connect your device to your wireless network. Follow the steps in the Manual Network Configuration article to connect your device to your wireless network. Chrome Device Manual Wireless Configuration

If your Wi-Fi connection is configured in the Google Admin console prior to receiving the device, you should be set! The device should automatically connect to your Wi-Fi connection.

 

Test your device’s connection

Log into your Arreya Dashboard and navigate to the Devices section to see your device’s online status. You can also check the device status from the Google Admin console. If your device is still showing offline, check our article What should I do if my device is showing “offline” in the dashboard?

 

Step 2. Pair your device

If your device is already paired to your Arreya channel you’re all set!

If your device displays a 4 character pairing code,

  1. Power on your Chrome device, verify it starts the Arreya app and displays a 4 character pair code
  2. Log in to your Arreya account
  3. Under “Management” menu click [Devices]
  4. Click [+ Add Device]
  5. Enter a name for your device and the 4 character code displayed on the device
  6. Click [Add Device!]

 

Step 3. Schedule your content

If your device automatically starts playing content, you’re all set!

If your device shows a black screen, you will need to create and schedule content to display. You can learn more about creating content by checkout out our Knowledge Base and tutorials available on our YouTube channel. You can learn about scheduling a presentation by visiting our knowledge base article Scheduling a Presentation

 

Remote Debugging ChromeOS Kiosk Apps and Progressive Web Apps in Kiosk Mode

Preface and prerequisites 

This article is intended for developers interested in remotely debugging their ChromeOS App or Progressive Web Application running in Kiosk mode. 

The target ChromeOS device must be in developer mode, and enrolled into an admin console Organization Unit (OU) with forced re-enrollment and verified boot disabled. If it was previously used with forced re-enrollment (FRE) enabled you’ll need to do the steps below. 

Forced re-enrollment can be found in the Chrome device settings in your Google Admin console. When this is set to ‘Device is not forced to re-enroll after wiping’, it will disable forced re-enrollment and allow developer mode to be enabled.

ChromeOS Forced Re-Enrollment

 

Remove ChromeOS device from forced re-enrollment

  1. Move device to OU with FRE and verified access/boot disabled
  2. Reboot with the recovery button depressed, then attempt to enter developer mode with Ctrl + D. You will not be able to enter developer mode, but the device will factory reset itself.
  3. Run through initial setup, the device should not automatically re-enroll, if it does, check your admin console settings and ensure the device is in the correct OU. 
  4. Log into the device in consumer mode, do not enterprise enroll the device.
  5. Reset the device again with the recovery button, you should be able to enter developer mode using Ctrl + D shortcut.
  6. Device should be in developer mode now, you can enable debugging features and enterprise enroll the device.

https://chromium.googlesource.com/chromiumos/docs/+/master/developer_mode.md

 

Remove rootfs verification

You will need to open a shell on the target Chromebox by either opening a virtual terminal by pressing Ctrl + Alt + F1(back arrow) or you can skip kiosk app on startup with Ctrl + Alt + S, log in, and open a shell by pressing Ctrl + Alt + T and typing ‘shell’

Run the following command:

$ sudo /usr/share/vboot/bin/make_dev_ssd.sh –remove_rootfs_verification

ChromeOS rootfs verification disable

You’ll be prompted to run the command again with the booted partition. e.g.

$ sudo /usr/share/vboot/bin/make_dev_ssd.sh –remove_rootfs_verification –partitions 4

Reboot the device.

 

Enable SSH access

 Install sshd startup files.

$ /usr/libexec/debugd/helpers/dev_features_ssh

Allow password access for root user in either a virtual terminal, or by changing to the root user.

$ passwd

 

Enable remote debugging

Add –remote-debugging-port startup flag to chrome_dev.conf e.g.

$ sudo vi /etc/chrome_dev.conf

Add  ‘–remote-debugging-port=9222’ to a new line at the end of the file

ChromeOS Remote Debugging

 

Chrome device IP address

Take note of your Chrome device’s IP address using system settings, or by using ifconfig command.

$ ifconfig eth0

$ ifconfig wlan0

ChromeOS IP Address

You’re now done with the target device, reboot and allow the device to start in kiosk mode.

 

 

SSH Client and port forwarding

On your other computer, open your favorite SSH client that allows port forwarding, this can be done in ChromeOS using the Secure Shell extension.

https://chrome.google.com/webstore/detail/secure-shell/iodihamcpbpeioajjeobimgagajmlibd

 

Configure your SSH Client with:

  • User: ‘root’
  • Host: IP of Chromebox
  • Port: 22
  • SSH Arguments: ‘-L 9222:localhost:9222’. (-L argument forwards a remote port to a local port. If you used a port other than 9222, replace it here)

 

chrome os ssh client port forwarding

Note: If you have used SSH with the same host, you may need to clear the host from your known_hosts file in the ssh client settings, or append ‘-o UserKnownHostsFile=/dev/null’ to the SSH arguments to use an empty known_hosts file.

 

You’ll be prompted to add the host/key to your known hosts.

chrome os ssh

Enter the root password you set.

chrome os ssh port forwarding

Leave the ssh client window open in the background.

 

Remote DevTools

Open a new Chrome browser window, and navigate to chrome://inspect

remote inspection with chrome devtools

Click Configure… and add ‘localhost:9222’ to the list of targets. Click Done.

configuring target for remote debugging with chrome devtools

Your remote target should now show up under the Remote Target heading. You can select each app, extension, or PWA you wish to inspect.

remote debugging with chrome devtools

remote debugging with chrome devtools

Links

http://dev.chromium.org/chromium-os/how-tos-and-troubleshooting/debugging-features

https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/chromeos-base/chromeos-sshd-init/files/openssh-server.conf.README

How to enable On-Screen Keyboard in Google Admin Console

Enabling the On Screen Keyboard is necessary for certain widgets inside of Arreya, most notably the SMS widget requires the user of a kiosk to input their phone number. While many ChromeOS devices have On Screen Keyboard enabled as a default, the safer option is to enable it in the Google Admin Console. This ensures that the kiosk functions as expected regardless of updates or changes to the configuration or firmware.

 

  1. Log into your Google Admin account at: https://admin.google.com/
  2. From the options on the left, click and expand the Devices category, then click and expand Settings.
  3. Click Device under the settings sub-category.
    on-screen keyboard for digital displays
  4. From here, choose the Organizational Unit for which you would like to enable the On Screen Keyboard. It is important to note that enabling this in a Organizational Unit will change the setting for any device or Organizational Unit underneath it. If you enable it at the top level Organizational Unit, all devices will have On Screen Keyboard enabled.
  5. In the primary window, scroll down until you find a category of settings titled “Kiosk accessibility”
  6. Underneath “Kiosk accessibility” you will find a setting called “Kiosk on-screen keyboard”. Change the setting to “Enable on-screen keyboard” as shown.
    enable on-screen keyboard for digital signage
  7. In the top right of the screen, click Save to save your settings and have the On-Screen Keyboard enabled for your chrome devices.

How to install your Arreya channel PWA as a Kiosk app

Each Arreya channel can be deployed as a Progressive Web App (PWA) and has settings to customize the look and feel of your PWA. The PWA can be force installed to managed devices via the Google Admin Console.

  1. After logging in to your Admin console, go to Devices. Arreya channel PWA as a Kiosk app
  2. In the navigation menu on the left hand side, select Chrome > Apps & extensions > Kiosks Kiosk App 
  3. Select the OU (Organization Unit) on the left hand side of the screen that you wish to configure. Only Chrome devices in this OU will have the settings applied.  
  4. Click on the KIOSKS tabKiosk App
  5. Hover your mouse on the Yellow Plus button on the bottom right corner of your screen, next click on the Add by URL option. 
  6. Enter the address of your Arreya Channel in the URL field. (e.g. arreyademo.arreya.com), click Save to add the PWA. You will be warned that permissions will automatically be granted to the web app. Click Agree to continue.
    Arreya Channel
  7.  After the PWA is added, you will see it in the App listing and the kiosk app will be installed by default. You must select the app to be automatically launched by selecting it in the drop down box next to Auto-launch app.


  8. Once you have set the app to auto launch, you can change the kiosk app settings by selecting the app in the app listing, and adjusting settings in the window on the right hand side. You need to turn on Allow App to Manage Power. We recommend turning on Enable Health Monitoring and Enable System Log Upload. Allow App to Manage Power

 

Please visit Getting started with Chrome Device Management  for more information regarding Chrome Device Management.