Off-Network Cloud Printing (ONCP)

Off-Network Cloud Printing (ONCP) requires zero on-premise infrastructure while allowing anyone to print—no matter their network. It offers zero-trust network authentication and better print availability, with printing handled and stored entirely on the cloud. Off-Network Cloud Printing continues to bridge the gap between network security and flexible user printing but relieves organizations of service client maintenance and oversight.

Key Points

  • The use of ONCP requires licensing for the Advanced Security bundle and must be enabled by a representative. Contact your CSM for details and assistance.
  • ONCP is currently only available for Fujifilm, Fuji Xerox, HP, Kyocera, Lexmark, and Ricoh MFP devices.
  • To install ONCP on HP devices, the Workpath platform must be enabled on the printer. Follow the steps outlined in the HP - Off-Network Cloud Printing (ONCP) topic if configuring.

ONCP exclusively provides support for RAW printing and is accessible solely within Virtual Appliance instances operating on Windows, Mac, and Linux systems.

Prerequisites

  • Create a Service Client ensuring that on the Printer Apps tab, that Printer Apps is enabled and that the HTTPS certificate matches the hostname. 

    The Service Client is solely necessary for installing the ONCP App on the printer. Once the app is installed, it's entirely optional to keep the Service Client running. However, if the Service Client serves other essential functions or integrates with different services, it should remain operational for those specific purposes.

    • Ensure that the PrinterLogicServicePrinterApp.exe service is running on your Service Client machine.
  • If your Service Client is using Windows OS, ensure Visual C++ Redistributable for Visual Studio 2015 (32-bit/64-bit) or newer is installed on the Service Client.
    • Both the x86 and x64 redistributable packages must be installed. These packages can be found in the Microsoft Download Center.
  • All devices, to include Service Client, printers, etc., must be allowed to reach DNS server and resolve names.
  • Be using a supported printer found on the Supported Printers List. Filter your results by selecting the Off-Network Cloud Printing option from the Feature drop-down.
  • Ensure the following allow list URLs are open:
    • Oncp-ofn.<Instance URL>
    • Oncp-pgw.<Instance URL>
  • Ensure needed ports are open based on your printer manufacturer found on the ONCP Setup Requirements topic.

Set Environment Variables

After reaching out to your Vasion representative, the following environment variables must be set in the Virtual Appliance before configuring any steps.

  1. Access your Virtual Appliance persistent storage.
  2. Navigate to \\<Instance URL>.com\appliance-storage\.
  3. Open the secrets.env file.
  4. Ensure the following flags are set.
    1. REPLICAS_STORAGE=1
    2. REPLICAS_ONCP_PGW=1
    3. REPLICAS_ONCP_REG=1
    4. REPLICAS_ONCP_HOLD=1
    5. REPLICAS_ONCP_OFN=1

Enable ONCP At A Global Level

  1. In the PrinterLogicAdmin Console select Tools then Settings then General.
  2. Scroll down to the Off-Network Printing section.

  3. Select the option for Allow Cloud Printing.

    A default global setting can also be configured here to set Cloud Printing as the method for all print jobs.

  4. (Optional) Configure the Off-Network Priority printing based on the on-screen descriptions and your desired outcome.

    The Option for "Off-Network Primary" is not applicable to ONCP, and should not be selected.

  5. Click on Save.

A GIF demonstrating turning on ONCP in General Settings.

Enable ONCP At A Local Printer Level

If you have set Cloud Print as your default global method in the General Settings for all printers, this step is not necessary.

  1. In your Tree View select the printer object you want to enable ONCP on.
  2. Select the Off-Network tab.
  3. In the Off-Network Enabling section select the option for Use Printer-Specific Off-Network Printing Setting.
  4. In the drop-down field, select Cloud Print as your printing method.
  5. Click on Save.

A GIF demonstrating how to set ONCP at the printer level.

Install ONCP On Single Device

  1. Select the printer object you have set for Cloud Print.
  2. Select the Apps tab.
  3. Select the printer manufacturer.
  4. Select CPA 2.0.

  5. Select the Service Client running the printer app service.

    Cloud Print is not dependent on the CPA and can be installed as a stand-alone app or in conjunction with the CPA.

  6. Select the option to Install Off-Network Cloud Printing.
  7. Select the option desired for credentials to use to install the ONCP application on the printer. These can be set at a default level configured in Tools then Settings then General in the Control Panel Application section, or at a Printer Specific level on the current screen. In either case, ensure that the correct user credentials are entered.
  8. Click on Save.

A GIF demonstrating installing Cloud Print on the printer

Install Cloud Print Using the CPA Manager

For information on installing Cloud Print in bulk see the CPA Manager topic.

Troubleshooting

An incorrect admin username and password is a frequent cause of failed installations. To resolve this issue, you can conveniently modify the credentials used for CPA installation on the Apps tab on the individual printer, or through the Modify feature in the CPA Manager. If the same admin name and password are used for multiple manufacturers, you can select several manufacturers simultaneously within the CPA Manager and change the credentials in bulk.

While this may seem evident, it is important to consider that the Service Client machine could be shut down or in an error state.

To easily check the status, you can refer to the Task Manager on the device. Navigate to the Processes tab and ensure that the PrinterLogicServicePrinterApp.exe process is running.

Task manager view of the PrinterLogic Service Printer App .exe service running in the Processes tab..

If neither the PrinterLogicServiceManager.exe or PrinterLogicServicePrinterApp.exe processes are running on the Service Client device, check the following:

  • Verify that the installed client is authorized and configured to connect to the correct instance. You can quickly test this by clicking the system tray icon to open the Self-service Portal. If it opens to the correct URL, and you can sign in, view, and install printers from the portal, then the client is authorized.
  • Navigate to C:\Program Files (x86)\Printer Properties Pro\Printer Installer Client\ServiceHost.
    • If the ServiceHost folder is not present, verify the hostname or IP address of the device and compare it to what you entered in the Admin Console.
    • If the ServiceHost folder exists, check the config folder within it. You should find a JSON token if the Service Client is authorized.
    • If the folder exists but no JSON token is found, it may be necessary to reauthorize the Service Client.
      • Please note that Service Client authorization is different from client authorization.

      • These steps provide the Service Client with a new token if it's missing or the PrinterLogicServiceManager.exe service is crashing.

        Before proceeding with reauthorization, ensure that you have checked the URL, client authorization, and folders as mentioned earlier. Only if those checks have been performed should you proceed with the reauthorization process. It is crucial to complete the following steps within two minutes, as the reauthorization will fail otherwise.

        1. On the machine set up as the Service Client, navigate to C:\Program Files (x86)\Printer Properties Pro\Printer Installer Client\ServiceHost\Config
        2. Verify if there is an existing token. If there is, delete the json token.
        3. Open Task Manager.
        4. Select the Details tab.
        5. Right-click on PrinterInstallerClientLauncher.exe and select End Process Tree.
          • There are three PrinterLogic services running for the client. If the other two services don't close with End Process Tree, they will need to be closed individually.
        6. In the PrinterLogic Admin Console navigate to the Service Client Object.
        7. On the Service Client's General tab, click Reauthorize.
        8. Click Okay in the prompted message.
        9. Back on the Service Client machine, select the Services tab in Task Manager.
        10. Right click on PrinterInstallerLauncher service and select Start.

        When the services start back up the Service Client machine pulls down a fresh token.

By default, the Visual C++ Redistributable for Visual Studio 2015 (32-bit/64-bit) or newer is typically already installed. However, it is essential to have these components installed on the Service Client to generate the required items for a successful installation. Both the x86 and x64 redistributable packages must be installed. These packages can be found in the Microsoft Download Center. Without it, the Service Client will be unable to initiate the app service, leading to repeated attempts to start and subsequent failures.

A quick way to do this is to right-click the Client icon in the system tray of the Service Client machine and select Refresh Configurations.

Before proceeding, it is crucial to double-check two key aspects:

  • Verify that the IP address assigned to the printer is accurate within the admin console.
  • Ensure that you can successfully ping the printer from the Service Client machine.

Confirming these details will help ensure a smooth and error-free process.