Mobility Print - Chrome App to Extension migration guide

If you deployed the Mobility Print Extension to the correct OU (Organizational Unit) in Google Workspace and you still don’t see the Mobility Print Extension in chrome://extensions:

1. As a test user, log in to Chrome and enable Sync:
   1. At the top right of Chrome, click Profile.
   2. Click Turn on sync….
   3. You’ll be prompted to sign in if you’re not signed into your Google Account. Sign in.
   4. Click Yes, I’m in.
2. In Google Workspace, check that your test account is part of the OU you deployed the extension to. In Google Workspace, open your user under Directory > Users. Check the Organizational Unit on the left.
3. In Google Workspace, check whether a policy is set at an org level that is overwriting the policy on your OU.
   1. In Google Workspace, open Devices > Chrome > Apps & extensions.
   2. Open the Users & browsers tab.
   3. On the left, under Organizational Units, check that the OUs above your OU don’t potentially have a Block or Allow Install policy set for the Mobility Print Extension.

1. If you use Print Deploy, ensure you can reach the Mobility Print and the Application Server from your Chromebook. You can open the Mobility Print and Application Server URLs in Chrome, usually via something like https://mobility-server:9164 and https://app-server:9192.
2. Check the address that Mobility Print is trying to connect to.
   1. Follow the steps in the Use the extension’s background page for troubleshooting section above.
   2. Enter GET in the Console’s filter field at the top.
3. If you use Known Host printer discovery in Mobility Print or Print Deploy, check that your policy was set.
   1. In Chrome, open chrome://policy.
   2. Scroll down to Mobility Print and check that the policy is what you expect. If it’s not correct (a few examples are available below), then fix it in Google Workspace:
      1. In Google Workspace, open Devices > Chrome > Apps & extensions.
      2. Open the Users & browsers tab.
      3. Select your OU on the left.
      4. Open Mobility Print.
      5. On the right, scroll down to Policy for extensions and enter your policy.
4. If you are using Cloud Print, your Cloud Print invite link might be expired. Check the status of your Cloud Print invite link:
   1. In the Mobility Print admin interface, click Manage.
   2. In the table, if printing is disabled, toggle the Enable Printing toggle for your invite link. See Set up Cloud Print on Chromebooks for more information.

Mistakes happen, whether it was a copy-and-paste issue, your 5-year-old came and pressed some buttons, or you inherited printing, and no one told you what the Mobility Print policies should be. Here are some examples:

Mobility Print Known Host

{
    "MobilityPrintServerHosts": {
        "Value": ["MobServerAddress"]
    }
}

Double-check that the MobServerAddress is your Mobility Print server’s FQDN or IP. For example, print.company.ltd or 192.168.1.16.

The preference is to use an FQDN, as it will fail quicker when a user is not on the network, so it doesn’t interfere with their printing at home.

For more options, see Configure printer discovery with a known host.

Mobility Print Cloud Print

{ "CloudPrintInviteLinks": { "Value":[ "your cloud print link"] } }

Get your Cloud Print invite link:

1. Open the Mobility Print server admin page. It is usually available at https://MobServerAddress:9164.
2. Replace MobServerAddress with your address.
3. In the Cloud Print section, click Manage.
4. In the table, on the Cloud Print link you want to share, click Share.
5. Click Copy Link.

For more information, see Set up Cloud Print on Chromebooks.

Print Deploy

{
	"PrintDeployServerHosts": {
		"Value": ["AppServerAddress"]
	}
}

Double-check that the AppServerAddress is your Application Server’s FQDN or IP. For example, print.company.tld or 192.168.1.16.

The preference is to use an FQDN, as it will fail quicker when a user is not on the network, so it doesn’t interfere with their printing at home.

For more options, see Deploy print queues to Chromebooks using Google Chrome Enterprise Administration and Print Deploy.

If you are getting an error when trying to sign in with Google, it might be the result of your security policy in Google Workspace. Follow these steps to confirm that the Mobility Print Chrome Extension has the required access to perform OAuth authentication for Google SSO.

1. From the Google Workspace Homepage, navigate to Security > Access and Data Control > API Controls.
2. Click Manage Third-Party App Access.
3. Click Add App and select Oauth App Name Or Client ID.
4. Paste the above OAuth Client ID in the text field and search.
5. From the search results select PaperCut Mobility Print, click the check box next to it, then click Select.
6. Choose the necessary OUs you want to configure access for and click Continue.
7. Choose Trusted access to Google Data parameters, then click Continue.
8. Review changes and click Finish.

The Mobility Print App and Mobility Print Extension can advertise printers to Chrome simultaneously, resulting in duplicate printers when pressing Ctrl+P.

If you see duplicate printers, check whether the Mobility Print App is still installed:

1. In Chrome, open chrome://extensions
2. Check whether the Mobility Print App with App ID alhngdkjgnedakdlnamimgfihgkmenbh is listed.
3. If it’s listed, remove it or block it via Google Workspace.