[Connectivity Diagnostics Tool for Chrome and ChromeOS]

Occasionally, you may not have an Internet connection on your Chromebook, or you may not be able to connect to a Google services site. At times like this, you may not know if your Chromebook is a problem or if there is a network problem or if there is a problem with  Google service sites. I'd like to show you a good tool to find out what's wrong with your Chromebook.

 

Chrome Connectivity Diagnostics is a fast and simple network testing and troubleshooting tool for Chrome and ChromeOS. The tool…

 

 

 

 

 

Chrome Connectivity Diagnostics is a fast and simple network testing and troubleshooting tool for Chrome and ChromeOS. 

The tool tests a computer's network connection for common issues, port blocking, and network latency by establishing connections to network and Internet services via UDP, TCP, HTTP and HTTPS.

The diagnostic tests include:
• Local network connection availability
• Wifi network signal strength (ChromeOS only)
• Default gateway is reachable (ChromeOS only)
• DNS server availability and latency
• DNS cache poisoning/spoofing 
• Internet traffic blocks by a HTTP captive portal or firewalls 
• Network performance and latency to Google websites
• Google Hangouts service availability

What's new
• Google Hangouts service availability test
• Logging of specific test criteria details

By installing this tool, you agree to the Google Terms of Service and Privacy Policy at https://www.google.com/intl/en/policies/

Installing from Chrome Web Store  

--------------

For more information for Chrome (Chromebook) Device Management- Author:Advanced Chrome Device Management - Kindle edition  - Paperback/Kindle Edition)

 

 

What's new with your Chromebook - ChromeOS Ver 80

What’s new with your Chromebook?

Chromebooks update automatically to provide you with the latest features and keep the software fresh and speedy. Here are some highlights from recent updates.

Master your multitasking


Master your multitasking with Virtual Desks. Use different sets of screens to create spaces for separate projects and activities. To create a new virtual desk, just press Shift + Launcher key + =, or tap the “Show all windows” button on your keyboard and select New desk.

Find out more

Control media without unlocking

Now you can control your media right from your lock screen. When you’re listening to audio on your Chromebook, you can play, pause, and skip tracks without unlocking. This new feature works with YouTube Music, Spotify, iHeartRadio, dozens of other apps, and media played through Chrome.

Place a call from your Chromebook

While browsing on Chrome, right-click any phone number on your Chromebook to place a call from your supported Android phone. To get started, sign in to your Google Account from your Chromebook and phone, and turn on sync in Chrome.

Print quickly and easily

Compatible printers will now appear automatically in your printer list — no setup required. Follow these simple steps: Press and hold CTRL+P.  Choose your printer from the destinations list. Click “Print.” That’s it.

Easier app management


We’ve made it easier to manage permissions for all apps that you use on your Chromebook. It’s now simple to change your notification settings and location, camera, and microphone access for all apps, straight from Settings

Google's Official Blog - http://bit.ly/32M2Izf

[What G Suite administrators need to know when updating ChromeOS version 78]

Below is an official announcement from the Google ChromeOS team.  And Here is what G Suite Administrator should know when updating ChromeOS ver 78.

----------------------------------------

Update your Chrome OS settings by October 29, 2019 to maintain current user access restrictions.

Dear Administrator,

On October 29, 2019, we will release a new Chrome operating system (OS) version, M-78. This release includes changes to where some settings are managed, allowing for a separation of OS and browser settings and facilitating faster page loading.

What do I need to know?

In the new OS, we’ve taken the single page of settings, which included both Chrome OS and browser settings, and separated them into individual pages. Now you can manage your OS settings in its own window.

You will find all of the same settings you use now in the following locations:

• Chrome OS settings: Open the Settings app. You can also access these settings by opening a browser, and in the address field, type the following URL: chrome://os-settings
• Chrome browser settings: Open the browser, click the three-dot menu, and select Settings. You can also access these settings by opening a browser, and in the address field, type the following URL: chrome://settings

Only OS-relevant pages (chrome://settings/display) have moved to the new URL structure (chrome://os-settings/display). All other standard Chrome browser pages will remain in place. For example, you will still find your passwords at the same URL: chrome://settings/passwords.

What do I need to do?

If you’ve restricted access to chrome://settings and its subpages, update your policies to continue to block access to the new chrome://os-settings URL before October 29, 2019.

1. Open the Admin console.
2. Go to Device management > Chrome > User & browser settings.
3. Select the organizational unit that you want to change the URL blocking setting on.
4. Scroll down URL Blocking under Content section. Update the URL blacklist text field to include:
   1. Browser-related setting pages. Example: chrome://settings/passwords
   2. (New) OS-related setting pages. Example: chrome://os-settings/display
5. Note: If you are using your own platform to push GPO policies, you will have to configure URLBlacklist to include the new OS settings page.

If you don't update your settings, pages you wanted to prevent access to may become available for user control.

How can I get help?

If you have additional questions or need assistance, please contact G Suite support. When you call or submit your support case, reference issue number 143349563.

Thanks for choosing Chrome OS.

—The Google Chrome OS Enterprise Team

[Test for Chromebook Auto Update Expiration (AUE) if it is working or not]

I have read an article saying that a Chromebook may have an auto-update validity period, and I ran the following tests to verify it:

The official Google Help Center mentions that automatic update expiration dates are set for Chromebooks (ChromeOS devices).

In fact, I tested with a Chromebook that expired the auto-update  (Acer Chromebook 11 C720P, a device whose auto-update expired in June 2019).

The expiration date for automatic updates for each device on your Chromebook is mentioned in the Google Official Help Center below. I tried to update today the Acer Chromebook 11 C720P model, which appears to have expired in June 2019. We have confirmed that today's date is updated to the most recent version. Just like the attached capture image

"This is the last automatic software and security update for this Chromebook.To get future update, upgrade to a newer model '

In fact, the Chromebook device-specific auto-update expiration mentioned in the Google Help Center seems to be working.

Please note the bellowing:


---------------------
https://support.google.com/chrome/a/answer/6220366?hl=en

Auto Update policy

Overview

Chrome devices receive automatic updates regularly that enhance both the device itself and the software on the device. Chrome device updates are designed to be simple for the user and, therefore, include updates to the device, Chrome operating system, browser and firmware. However, end-to-end updates for all our devices to ensure the highest levels of security requires dependencies on many third-party hardware and software providers so we cannot indefinitely ensure that older Chrome devices will receive updates to enable new OS and browser features.

General policy

• Each device has an Auto Update Expiration (AUE) date listed; this means that before this date, devices will receive new software updates from Google.
• Google provides each new hardware platform with 6.5 years of Auto Update support. Multiple devices can share the same hardware platform. The 6.5 years starts when the first device on the platform is released(1). Manufacturers are advised to choose the newest platforms to ensure that they produce devices that have the longest Auto Update support available.
• Google will provide advanced notice of a model’s AUE date on this page, giving buyers time to make purchase decisions. Devices that are due to have an AUE date within 90 days will be highlighted in bold. Please check the Auto Update Expiration date when making a purchasing decision.
• Chrome device models that have not reached their AUE date will continue to receive OS updates and function with the business and education management service.
• When a device reaches AUE, it means that automatic software updates from Google will no longer be provided.
• Enrolled Chrome devices that have reached their AUE date will no longer receive technical support from Google.
• Business and education customers using devices that have passed their AUE date should not expect that they can manage their devices as expected using the Google Admin console or leverage new management features released.
• The End of Sale date is controlled by the manufacturer of the device model and has no relation to model’s AUE date.
• 
  

[Tip:Chrome Device Management ] Chrome Release Channel best practices

While the majority of your users will be on the Stable channel of Chrome OS, if your organization has a large number of Chromebooks, there are several reasons why you should always keep some devices on the Beta channel:

Google recommends that you keep most of your users on the Stable channel, and 5% of your users on the Beta channel. We also recommend you keep your IT team on the Beta or Dev channels.

There are three types of Chrome OS releases: Stable, Beta, and Dev. You can set the release channel for your Chrome device users in the Admin console under Device management > Chrome > Device Settings.

Keep 5% of your organization on the Chrome OS Beta channel

While the majority of your users will be on the Stable channel of Chrome OS, if your organization has a large number of Chromebooks, there are several reasons why you should always keep some devices on the Beta channel:

• Your organization will get a 4-6 week preview of new features.
• Some features you discover may require you to communicate additional information to your organization.
• Some features may not be suitable for all of your users, and you may need to investigate ways to block these features.
• In some cases, you may find issues which could impact the use of the devices in your environment. Finding this out early enough with fewer devices will give you enough time to contact Google, and if we can’t resolve the issue, block the update before it hits all of your users.

As a general rule, we recommend you keep at least 5% of your devices on the Beta channel at all times. If you have multiple types of hardware, we recommend you keep 5% of each type of hardware on the Beta channel.

Google will actively investigate issues on the Beta channel. Please contact Enterprise support to report any issues that you notice.

Keep your IT staff on the Beta and Dev channels

In addition to keeping most of your IT staff on Beta channel, it can be helpful to keep some devices on the Dev channel, which will give you 9-12 week preview of what is coming to the stable version of Chrome OS. Benefits of being on the Dev channel include the following:

• Your IT staff can test to make sure that your apps and systems are compatible with the latest Chrome OS software updates and feature changes.
• While we automatically fix most issues before the release is marked as stable, we may not be able to catch all the corner cases which may uniquely impact your environment. Should any issues arise, your developers and IT staff can identify and report (via the Chromium site) any changes that may impact your environment before they reach the Beta or Stable channel.

Note that the Dev channel, by its nature of being an early release of Chrome, is not 100% stable, and should be used by IT staff or developers. Since some instability is expected, the Dev channel is more useful for staying aware of upcoming features in the OS.

For More information - https://goo.gl/IMl8Bu Kindle Edition

Unboxing Chromebit for Digital Signage

A set of 3 ChromeOS devices (Chromebook, Chromebox, Chromebit) I am using.

In the meantime, I was  useing Chromebooks and Chromeboxes based on Chrome OS, but recently I bought a Chromebit that was released by Asus.

The purpose of this Chromebit purchase is to compare how much better the Chromebook and Chromebox compared to the Chromebit, but the main purpose is to register as a Chrome Device Management Console device and review whether it is good for the ChromeOS Kiosk and Digital Signage.

I think that the Chromebit size (about the size of the thumb) and the price ($ 85) would have a positive ratio and would be a signage kiosk device. After this release, Chrome OS and Kiosk apps will be linked to the second installment.

Thumb-sized ChromeOS devices - 2GB Ram, 16GB storage, WiFi 802.11ac, Bluetooth 4.0, 1 USB 2.0 port, HDMI port, price $ 85

As an option, I bought a Logitech wireless keyboard (wireless dongle + keyboard + touchpad) for $ 25 and a set of Chrome OS devices.

Box components are very simple - power cord, sticker to monitor, chrome comb body, HDMI extension cable.

Plug-in the Logitech keyboard wireless dongle into the USB 1 port terminal, plug in the power cord, and plug it into the monitor's HDMI port to boot up immediately

YouTube launch screen

After signing in with an existing G Suite account, we found that it performs significantly better than writing Gmail and Drive documents.

--------------------

Kindle Edition-Paperback/eBook -

"Advanced Chrome Device Management & 2017 Essential Guide for Chromebook Users"