Deploy Chromebook Client with Google Admin Console

The MyQ X Chromebook Client can be installed manually by individual users from the Chrome Web Store, or deployed silently to all managed Chromebooks in a Google Workspace organization using Google Admin Console. For environments with managed Chrome OS devices, Admin Console deployment is the recommended approach – it requires no action from users and ensures consistent configuration across the fleet.

If you are an end user installing the extension on your own Chromebook, see Setup instead.

This article covers the administrator tasks required before and during deployment: configuring Google Workspace for correct print job attribution, deploying the extension to managed devices, and deploying certificates where required.

Prerequisites

Before deploying the Chromebook Client via Admin Console, confirm the following:

• MyQ Print Server 10.2 Patch 4 or later is installed and accessible from the network segment used by Chromebook users.

• The Chromebook devices are enrolled in Google Workspace and managed via Google Admin Console.

• The MyQ server certificate is trusted by the Chromebook devices, or you have a CA certificate ready to deploy. See the note on certificate trust below.

• IPPS queues are configured on the Print Server with Jobs via Mobile Devices enabled. To verify this, in Print Server, open the queue detail, go to the Job Receiving tab, and confirm the setting is active.

Configure Print Job Attribution

By default, Chrome OS does not include the username in print job metadata. Without this, MyQ cannot attribute jobs to the correct user – jobs arrive without identity and cannot be accounted or released under the sending user's account.

To enable username inclusion in print jobs:

1. In Google Admin Console, go to Devices > Chrome > Settings > Users & browsers.

2. Scroll to Printing – CUPS print job information.

3. From the drop-down, select Include user account and filename in print job.

This setting must be applied before users begin printing. Jobs sent before the setting is active will not be attributed correctly.

Note that the username passed to MyQ is the user's Google Workspace account name. Ensure that MyQ user accounts use the same identifier – either by synchronizing users from Google Workspace or by ensuring that MyQ usernames match the Google account format used in your organization.

Deploy the Extension to Managed Devices

1. In Google Admin Console, go to Devices > Chrome > Apps & extensions > Users & browsers.

2. Select the organizational unit or group to which you want to deploy the extension.

3. Click the yellow + button and select Add from Chrome Web Store.

4. Enter the extension ID: adneibmfddbhmickjdmlhpnmclmnehkc, or search for MyQ X Chromebook Client.

5. Click Select.

6. Set the installation policy to Force install. This installs the extension silently on all managed devices in the selected scope without requiring user action.

7. Under Policy for extensions, enter the server configuration as a JSON policy to pre-configure the Print Server URL, so users do not need to enter it manually:
   

   JSON

   {
     "serverUrl": {
       "Value": "https://your-print-server-hostname:8090"
     }
   }
   

   
   Replace your-print-server-hostname with the hostname or IP address of the MyQ Print Server, and 8090 with the actual Web Server Port if it has been changed from the default. The server hostname is available in the MyQ Web Interface under Settings > Network > This server hostname. The port is visible in Easy Config.

8. Click Save.
   The extension rolls out to enrolled devices according to the Admin Console sync schedule. Users do not need to restart or take any action.

Deploy Certificates

If the MyQ Print Server uses a certificate signed by a private CA – which is the case for most on-premises deployments using the default MyQ certificate – Chromebook devices will not trust the connection without the CA certificate installed.

To deploy the CA certificate via Google Admin Console:

1. In Google Admin Console, go to Devices > Chrome > Networks.

2. Select the organizational unit or top-level organization as appropriate.

3. Go to Certificates and click Add Certificate.

4. Enter a name for the certificate and click Upload to upload the CA certificate file (.crt or .pem).

5. Under Certificate Authority, select Chromebook. This marks it as trusted for Chrome OS devices.

6. Click Add.

The certificate is pushed to enrolled devices automatically. Devices authenticate to Google and receive the certificate – no user interaction is required. Pushed certificates apply to all enrolled Chrome devices in the selected scope.

To verify the certificate has been installed on a managed device, go to chrome://settings/certificates, click Authorities, and scroll to confirm the CA is listed.

If devices connect over a dedicated guest Wi-Fi network for printing, ensure the certificate push is configured to reach devices on that network before they attempt their first connection to the Print Server.

Verify Deployment

Once the extension has rolled out and the CUPS job attribution setting is active, verify the deployment with a test user:

1. On a managed Chromebook, open Chrome and press CTRL+P.

2. Under Destination, click See more.

3. Confirm that MyQ queues appear in the list, marked with MyQ X Chromebook Client.

4. Print a test job and confirm it appears in the MyQ Web Interface under Jobs, attributed to the correct user.

If queues do not appear, confirm that the Print Server URL in the extension policy is correct and reachable, and that the server certificate is trusted on the device.

If jobs appear without a username or are attributed to an unknown user, confirm the CUPS print job information setting is active and that the Google Workspace username matches the MyQ user account identifier.