Set up Google Cloud Print on a Windows print server

Note: After December 31, 2020, Google Cloud Print will no longer be supported. Learn more about your migration options.

This article is for IT administrators setting up Google Cloud Print on their MicrosoftWindows print servers. If you're new to Google Cloud Print, see Google Cloud Print services.

If you have a Windows print server or other Windows machine that you’d like to use for print job routing, you can run the Google Cloud Print Connector as a Windows service. This action allows users in your organization who are signed in to a machine running the service to print to your legacy printers from Chrome devices and other web-enabled devices. Running the connector as a service means that Cloud Print is always on—running on your organization's servers. It can be used in parallel with your current print solution.

Note: To print to the legacy printers, users must be signed in to the machine running Google Cloud Print Service for Windows.

Before you begin

Before you install Google Cloud Print for Windows, ensure that:

  • At least some of your business’ printers are not Google Cloud Print Ready.
  • You have a Windows print server or other Windows machine that's  always on to use for print job routing.
  • Ensure that you have installed Google Chrome 27+ for all users. The connector runs as a different user and needs access to Chrome. Chrome should be located under programfiles\Google\Chrome.

Supported platforms

See this article for the supported platforms for Google Cloud Print.

Install Google Cloud Print for Windows

  1. Using Chrome Browser, download and install Google Cloud Print Service for Windows.
  2. From the Start menu, open Google Cloud Print Service and run it.
  3. Enter your Windows administrator username and password.
  4. Click Register.
  5. In the window that opens, sign in to your G Suite account.
  6. Click Add Printers and leave the browser window open. When the setup is complete, the configuration utility will automatically close the window. (You can close the pop-up if it's still open.) In the State: field, you should see Running.
  7. Open the management page and verify that the printers are available.

Uninstall Google Cloud Print for Windows

  1. In Windows, open Control Panel.
  2. Uninstall Google Cloud Print Service.

Troubleshooting

  • You can start, stop, register, and unregister the service using config utility from step 2 of setup.
  • You can enabling logging during service registration. Logs will be available at "C:\Users\<USER>\AppData\Local\Google\Cloud Print Service\chrome_debug.log" (for Windows 7)

Questions?

Does installing Google Cloud Print Service on a Windows 2008\2012 server require a Local Admin account (not Domain Admin)?

It requires permissions in order to see and print to the Windows print shares. If these are locally-attached printers, local admin account is fine. If they're network printers, then you'll need whatever permission is required in order to submit and remove print jobs.

Does the Google Cloud Print Service run as a Local System and not require a service account to run?

Cloud Print set up according to the instructions in this article runs as the Windows account you specify during setup of Google Cloud Print Service for Windows.

What are the minimum Windows permissions required for this service account?

A Windows service or user account is fine.

Is Port 5222 required inbound for the print server?

No, only 5222 outbound is required.

443 TCP (HTTPS), with connections to:
https://www.googleapis.com/*
https://accounts.google.com/*
https://www.google.com/cloudprint/*

5222 TCP (XMPP, using STARTTLS), with a persistent connection to:
talk.google.com

Is Port 5222 required to be opened in or out for all PCs or just the print server?

Port 5222 is required only for the print server. PCs and Chromebooks will submit print jobs to Google over https:443.

Resources



Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

Was this helpful?
How can we improve it?