Connect a Jamboard device to your network

To save jams or to join video meetings, you need to connect Jamboard to a network.

Step 1: Connect the board to an open network

1. Press the power button on the right rear panel.
2. On initial setup, you can connect Jamboard to an open Wi-Fi, WPA2 with password, or unfiltered Ethernet network.
   
   Note: This network can't use a captive portal or require a proxy. Those capabilities are only available after the device is updated.

Step 2: Activate the board

After you've powered on the Jamboard and connected the device to an open network, a screen appears with an 8-character activation code. If this is the first time a Jamboard is being provisioned on the domain, a Super Admin account must be used to accept the Terms of Service. Afterwards, anyone with the “Jamboard Management” privilege set in the Admin Console (admin.google.com) will have access to the Jamboard Device Management Console.

1. On your computer, open a Chrome browser.
2. Sign in to your Google Admin console.

   Sign in using your administrator account (does not end in @gmail.com).

3. Go to Menu  DevicesJamboardDevices.

   Some features may require having the Jamboard Management privilege.

4. At the top of the page, click the plus sign to add a new device.
5. Enter a location and name for the Jamboard.
6. Enter the 8-character activation code and click Activate Device.

Step 3: Update the board software

If your Jamboard runs on an early software build, you might not have access to the Jamboard Diagnostic tool. If you can't open the tool, wait for your board to update automatically.

Jamboard automatically updates to the latest release version within 10 minutes of connecting to the web. To manually update your board:

1. Tap menu .
2. Tap About Jamboard.
3. Tap Build Number 7 times. The Jamboard Diagnostic Tool displays.
4. Tap Check System Update. You can download a system update if one is available.

Step 4: Connect Jamboard to a Wi-Fi network

Current Jamboard software builds support all of the enterprise Wi-Fi configurations supported by Android 7.0 Nougat, which include:

• Protected Extensible Authentication Protocol (EAP)
• Extensible Authentication Protocol-Transport Layer Security (EAP-TLS)
• Extensible Authentication Protocol-Tunneled Transport Layer Security (EAP-TTLS)
• Extensible Authentication Protocol-Password (EAP-PWD)
• Most proxy network configurations
• Hidden Service Set Identifiers (SSIDs) and captive portal networks

 

You can upload a Wi-Fi network certificate to Jamboard from a connected USB flash drive.

1. Tap menu .
2. Tap Settings.
3. Tap About Jamboard.
4. Tap Build Number 7 times. You will see a countdown for each tap. The Jamboard Diagnostic Tool displays.
5. Tap Wi-Fi Certificates.
6. Insert a USB flash drive (VFAT format, win32/DOS FS only) containing the certificate files into the side USB port on the Jamboard.
7. Tap Install Certificates from USB and choose your certificate file.
8. Tap OK.

 

To configure the Wi-Fi network connection:

1. Tap menu .
2. Tap Settings.
3. Tap Wi-Fi.
4. Tap Add network.
5. Select security type 802.1x in the network settings.
6. Select the certificate from the CA certificate drop down list.
7. Configure the remaining network security fields.

Wi-Fi power and channel specifications

Frequency(Mhz)	Mode	EIRP(mW)	Total Supported Channels	Channel List
2412~2472	802.11b	48.5	11	1,2,3,4,5,6,7,8,9,10,11
2412~2472	802.11g	30.5	11	1,2,3,4,5,6,7,8,9,10,11
2412~2472	802.11n HT20	38.5	11	1,2,3,4,5,6,7,8,9,10,11
5180~5320	802.11a	96.5	8	36,40,44,48,52,56,60,64
5180~5320	802.11n HT20	52.0	8	36,40,44,48,52,56,60,64
5180~5320	802.11n HT40	92.0	4	38,46,54,62
5180~5320	802.11ac VHT20	52.0	8	36,40,44,48,52,56,60,64
5180~5320	802.11ac VHT40	92.0	4	38,46,54,62
5180~5320	802.11ac VHT80	123.0	2	36,40,44,48,52,56,60,64

Hostnames to allow

To access Jamboard services for Jamboard and the Jamboard app, your firewall rules should allow the following hostnames:

• android.clients.google.com
• *.autodraw.com
• *.ggpht.com
• *.googleapis.com
• *.google.com
• *.googleusercontent.com
• *.gstatic.com
• chrome-alpha.sandbox.google.com

Protocols and ports

Jamboard uses the following connections:

• A TCP connection from the participant to Google on ports 19305 through 19309.

• A TCP and UDP connection from the participant to Google on ports 443 (SSL) and 80.

FCM ports and hostnames to open

To access certain Jamboard features that require the use of FCM (Firebase Cloud Messaging), your firewall rules should open specific TCP ports and hostnames. For details, see FCM ports and your firewall.

Notes

• Domain names may resolve to IP addresses that aren't within a particular address range.
• Other Google properties may use the IP addresses that Jamboard uses.
• Jamboard connections to Google servers depend on the correct browser, browser version, device, device version, and networking conditions.
• You may not currently see activity at the addresses listed, but there could be future activity.

The Jamboard team is actively working on expanding Wi-Fi capabilities to work with a variety of solutions. However, these aren’t currently supported by Jamboard:

• Remote certificate management.
• Remote Enterprise Wi-Fi configuration via Jamboard Admin panel or Mobile Device Manager.
• Proxy configurations for non-enterprise network types (for example: WPA, WPA2, WPA/PSK, WEP).
  Note: PEAP/TLS/TTLS configurations are supported.
• Wired 802.1X authentication.