This article will cover manual configuration of a wireless network on a Chrome device, the pictures below show an AOpen Chromebox Mini, but the process for other devices is the same.
If your Chromebox is already powered on, press and hold the power button on the Chromebox to turn it off. The button location may vary depending on the model of Chrome device. Simply unplug the power cord if you’re working with a Chromebit.
Connect a keyboard/mouse to the Chromebox and get prepared to press the key combination: Ctrl + Alt + S. This shortcut will skip Kiosk mode and bring you to the Chrome desktop.
Power on the Chromebox, and press Ctrl + Alt + S when prompted at the white Arreya splash screen. If you do not press the shortcut at the correct time, the Arreya application will not be skipped.
Note: It may help to repeatedly press the shortcut after powering the Chromebox back up, until the Chrome desktop is shown. You have to press all three buttons at the same time.
Do not sign in to the Chrome device!
The first screen that appears when you enter the desktop will either be a login screen or a connection error prompting you to select a network to connect to. If the network selection screen appears, click the dropdown box, select your desired wireless network and enter the password to connect.
If the network selection screen does not appear, click the system tray in the bottom right corner of the screen.
Click “No network” to display available networks to connect to.
Click the desired network, a screen will prompt you to input your password. “Allow other users of this device to use this network” should be automatically turned to on.
After successfully connecting to the network, power the Chrome device down with the power button. Power the Chrome device up again and allow the Arreya app to run.
The device should now be connected to the internet.
An important feature for troubleshooting device issues, is the ability to remotely reboot a Chrome device or take a screenshot of the screen.
After logging in to your Admin console, go to Devices > Chrome Devices and click a serial number to get into the individual device settings.
On the left side of the screen you’ll see your options for Reboot, Remote Desktop, and Take a Screenshot
This screen also has information regarding system information, and troubleshooting features like Remote Desktop, Capture Logs, and Move.
Pressing [Reboot] will send a command to the Chrome device to reboot. You will either get a success message, or an error if the device is offline or it’s unable to communicate with the device.
Pressing [Remote Desktop] will start a dialog for you to remotely view your screen in real time.
Pressing [Take a Screenshot], next to Screen Capture will take a screenshot of what is currently on the screen. This can be used to determine what is showing on the screen currently.
The Screen Capture and Remote Desktop functions will return an error if a user has interacted with the Chrome device, pressed a touch screen, used a keyboard or mouse, etc. This is a security feature to prevent sensitive information from being accessed on a user’s screen.
Sometimes you just want a keyboard on your tablet or handheld device. Now you don’t have to buy a new external keyboard, because Chrome offers the virtual keyboard function.
If your device status is OFFLINE, here are some possible causes and steps to resolve the issue –
Reboot the device
Try pressing the ‘refresh’ button for the device – From your dashboard, go to Management -> Devices, click [Refresh] next to the device that is offline. If it returns to online, there may have been a temporary communication issue.
If you use Chrome Device Management – Log in to your Admin Console, navigate to the device, and look at the current status. If the device is online, try capturing a screenshot or rebooting the device.
Verify that the internet is up and running – The most common cause of an offline device, is an issue with the internet connection. Many ‘stable’ connections fluctuate throughout the day/week and you may see this reflected in the online/offline status as sporadic, short periods of offline status.
Verify that there is no interference from a Content Filter or Firewall – The second most common cause of an offline device, issues with content not showing, or problems pairing a device come from content filters or firewalls that interrupt communication with Arreya. Please follow our instructions for content filters and firewalls – https://arreya.com/kb/allow-past-firewall/