Information Technology Services » Google Suite and Chromebooks

Google Suite and Chromebooks

GSE – Google Suite for Education

G-Suite Status Dashboard

Gmail

Please note the link for Staff Email (Gmail) on the district web site.

Accounts, Login, and Password reset

Please read the Login FAQ.

Clever login on Chromebooks for Elementary Students

Clever badges allow primary grade (TK-2) students to sign into Chromebooks using a Clever badge. With Clever Badges, students can simply hold up a physical Badge to the computer's webcam instead of typing in credentials.
 
 
 
 

Team Drive

Team Drive:  All District Team Drives have been created based on District Staff Groups as requested by Curriculum.

Team Drive Operating rules:

  • You may never change the share permissions for the Team Drive, including adding or removing staff, students, or anyone else inside or outside the district. Team Drive only provides read/write drives by also giving users full access to all file and share permissions. Please contact Curriculum if you have questions.
  • Google Team Drive is similar to the current S: and T: drives, but comes with the risk of someone adding or removing access rights (see item 1). This limitation is for Google to fix.

Google’s G Suite Learning Center:   http://learn.googleapps.com/

For up-to-date help, please visit Google’s built-in help:  it's excellent and always current.

Sharing Documents on the Web and with Google Sites

Please read the Lucia Mar best practices document.

 

Cell Phones

Users of district-issued cell phones should use Gmail and Google Calendar apps even when the phone vendor supplies their own apps (this primarily affect Apple device).

In the Google documentation the “gmail address” or “Google for Work address”  refers to your firstname.lastname@lmusd.org address.

How to add Gmail on an Android phone

How to add Gmail on an iPhone/iPad

Chromebook

 

Chromebooks

Chromebooks at Lucia Mar

  • Staff and students must log in with their district login ("district credentials"). This establishes the appropriate access rights (student, staff, administrator, etc.). “Browse as Guest” does not work as there are no rights associated with “guest”.  Login FAQ. Without proper authentication internet access will not be granted or will be restricted in accordance with the district’s acceptable use policy (AUP).

  • Boot your Chromebook so it can update. If a Chromebook is left without updates for a few months, Google "drops" the Chromebook from its update cycle and the device essentially goes "stale". A stale Chromebook does not get any further updates, does not get district policies, and cannot be used for state testing (CAASPP). Try triggering a ChromeOS update if your Chromebook has fallen behind (see below for instructions).

  • Disabled Chromebooks: If your Chromebook is disabled, it means Google’s infrastructure lost track of it or that the Chromebook is obsolete. IT can re-activate a supported non-obsolete Chromebook.

  • District Chromebooks automatically connects to a Wi-Fi network "LMUSD-Chrome". Do not attempt to change this unless instructed to do so.

  • District Chromebooks rely on a Chrome app "PA User Agent for CrOS" to properly identify users on ChromeOS. The app is automatically installed on connected and updated district Chromebooks. See screenshot below.
 
 

How to trigger a ChromeOS update

  1. Power up the Chromebook and log in with your district credentials
  2. Select Settings icon in the lower right, then "Settings"
  3. Select “About Chrome OS”
  4. Select “Check For Updates”
  5. Reboot if necessary  
 Google's instructions for updating ChromeOS: https://support.google.com/chromebook/answer/177889?hl=en
 

Common problems:

My Chromebook is slow: This is typically caused by not having used a Chromebook for several weeks. On boot, the ChromeOS will start downloading any missing ChromeOS updates. If an OS update is pending, it is indicated by a download arrow in the lower-right system tray: Click on the icon and install the update (this generally takes 10-15 seconds).
 

Internet is not working on a Chromebook: This is typically caused by not logging in with a district account and thus getting restricted access. Reboot the Chromebook and log in with your District credentials.

 
I cannot find the CAASPP/SBAC Browser:  Please read the following document, including the troubleshooting section at the end.

Printing from Chromebooks, Chromeboxes, etc.

Printing from Chromebooks does not work reliably.  The printing process is convoluted and involves transmitting documents to an internet-based print server and then the print server must communicate with the local printer.  This has been found to be problematic, unreliable, and error-prone.  At best, it works intermittently.

 Printing from stationary Chrome devices (e.g. Chromebox): 

  • Printing is supported on stationary Chrome devices such as Chromeboxes in designated labs assuming availability of a compatible printer in the room.

Printing from Chromebooks or other mobile Chrome device:

  • Save a .PDF to a USB drive.  Print the .PDF on a PC, or print from a printer with USB.
  • Log into Google on a PC and print.

Chrome Browser

In April of 2015 Google hid support for NPAPI with Chrome release 42.  This was originally scheduled for the end of 2014, but the deadline was extended. NPAPI is essentially being superseded by HMLT 5, and Google has chosen to accelerate the obsolescence of the NPAPI legacy technology.  NPAPI was removed at the end of 2015.

This affects Lucia Mar as follows:

  • Google Suites for Education is not affected.
  • Chromebooks are not affected.
  • Silverlight, Java, Unity3D and other extensions built on NPAPI no longer work as browser extensions in Chrome, but may work in other browsers such as Firefox and Internet Explorer as long as those browsers support NPAPI.
    • Silverlight is used by OWA and Software Center.
    • Java is used by NetView Observer, our Camera Software.

The removal of NPAPI is Google’s decision, and the issue is not “fixable” by ITS.

You may want to experiment with Internet Explorer or Firefox if you have extensions depending on NPAPI.

Please refrain from implementing any of the “fixes” you can find on the internet. The NPAPI technology has been deprecated by Google, and is being removed fully from the code base over time.