Google Cloud Directory  education scenario

Goal

The part-time System Administrator of a school with 350 students is putting in place various measures to reduce IT costs. One measure is to stop using Active Directory (AD) for staff authentication (the students are already authenticated using Google Workspace for Education) and phase out the Active Directory infrastructure altogether. In its place they plan to use:

• PaperCut NG/MF Mobility Print to advertise print queues

• Google Cloud Directory to authenticate all print, scan, and copy jobs for both staff and students.

Staff will be able to use any laptop, and all students will use school supplied Chromebooks or BYOD.

During the transition there is to be minimal, if any, disruption to users, and afterwards there needs to be minimal change management effort required to move staff over to authenticate using their Google Workspace credentials.

Benefits of adopting Mobility Print backed by Google Cloud Directory authentication for all users

• Reduced IT costs.

• Faster and simpler deployment of print queues to end users.

• Continued support for native printing from local applications, for example Learning Management Software or Microsoft Office.

• Reduced system administration overheads, such as maintaining an additional Active Directory environment.

• Opportunity to re-use existing hardware.

• User details (for example, username and email address) are easily synced from Google Cloud Directory to PaperCut NG/MF.

Changes to the system setup

Current setup

Staff:

• use laptops on premises that authenticate using AD

• copy, scan, and print jobs using their AD username and password.

Students:

• use Google Cloud Print (GCP) to print

• copy, scan, and print jobs using their student ID number and PIN.

Future setup

Staff:

• continue to use their current laptops

• can choose to use BYOD with Mobility Print

• copy, scan, and print jobs using their Google credentials and Mobility Print

Students:

• use Mobility Print to print from their Chromebooks and BYOD

• use Sign in with Google on Chromebooks

Implementation

This scenario assumes that the WiFi network is relatively simple and does not block Bonjour/mDNS. If your network is more complex, for example, you have multiple subnets, refer to the Mobility Print Help Center .

This scenario also assumes that you have users and groups already set up in Google Workspace.

1. Set up Mobility Print . Be sure to install it on an existing print server that can be reached by users on either the Staff or Student WiFi.

2. In the Admin web interface, select the Options > Mobile & BYOD > Mobility Print > Allow users to sign in with their Google account checkbox.

   This enables Chromebook users to click Sign in with Google when printing, so they don’t need to re-type their username and password every time.

3. You will then need to deploy the Mobility Print client for any Windows, Android or Chromebook devices, or provide instructions for staff and students to do it themselves.

4. Use Google Cloud Directory Sync to migrate all of your AD users (staff) into your Google Workspace account, in their own group.

5. Review the information in Synchronize user and group details with Google Cloud Directory , then set up a Secondary sync source for Google Cloud Directory. (Your Primary sync source remains AD for now.)

   Staff and Students with Google Workspace logins can now use Mobility Print from their Chromebooks or their chosen BYOD.

   When you’ve finished deprecating your on-premise Active Directory, you’re ready to switch over to Google Cloud Directory for good.

6. In Options > User/Group Sync, change the Primary sync source to Google Cloud Directory, and then disable the Secondary sync source.

Woo hoo! All of the staff and students can now use their Google credentials with PaperCut NG/MF on all platforms, and you can start enjoying the benefits of your new environment!