Print Fleet Proxy 2.0 for New Customers

  • Updated on Oct 16, 2026
  • Published on Oct 15, 2026
  • 4 minute(s) read
Prev Next

Introduction

Workforce Experience Print Fleet Proxy 2.0 connects supported printer information from HP Web Jetadmin (WJA) to HP Workforce Experience Platform (WXP). Print Fleet Proxy 2.0 replaces the earlier version, which depended on a third-party component that has reached end of life (EoL).

This article provides a workflow for new customers to install the enhanced Print Fleet Proxy.

Prerequisites

Before installing or upgrading Print Fleet Proxy, ensure that the following requirements are met:

  • The computer has internet connectivity and can access WXP.

  • HP Web Jetadmin (WJA) is installed on the computer.

  • IT Admin or Print Admin roles in WXP.

Hardware Requirements

Ensure that the computer meets the following minimum or recommended hardware requirements.

Minimum Configuration:

  • CPU: Dual-core processor

  • RAM: 8 GB

  • Storage: 100 GB available disk space

  • Supported Device Load: Up to 6,000 devices for a single discovery operation and data collection for up to 6,000 managed devices.

Recommended Configuration:

  • CPU: Quad-core processor

  • RAM: 16 GB

  • Storage: 200 GB available disk space

  • Supported Device Load: Up to 6,000 devices per discovery operation per agent. 

Software Requirements

Ensure that the computer is running one of the following supported operating systems:

  • Microsoft Windows Server 2025

  • Microsoft Windows Server 2022 (64-bit edition only)

  • Microsoft Windows Server 2019

  • Microsoft Windows Server 2016

  • Microsoft Windows 11 (64-bit edition only)

Network Requirements

Ensure that the following network ports are open and accessible:

  • Port 3000: Used by the backend application.

  • Ports 80 and 443: Used for HTTP and HTTPS communication between the HP Fleet Onsite Agent and web services, enabling unsecured and secure data transfer.

  • Port 443: Used for MQTT communication with ALPN configured to the global value x-amzn-mqtt-ca.

  • Ports 161 and 7627: Used for SNMP and WS communication respectively, between the HP Fleet Onsite Agent and printers, facilitating device discovery, monitoring, and data collection.

Note: If HP Web Jetadmin is not installed, the installer stops the installation.

Installing Print Fleet Proxy for New Customers

New customers must install Print Fleet Proxy, create a proxy connection in WXP, and discover printers through HP Web Jetadmin.

Step 1: Downloading and Installing Print Fleet Proxy

  1. Sign in to WXP. The Home page is displayed.

  2. From the left menu of WXP, click Devices > Printers. The Printers page is displayed.

  3. On the Printers page, click the Proxies tab. The existing proxies are displayed.  

  4. In the Proxies tab, click Download Print Fleet Proxy. The Print Fleet Proxy installer is downloaded.

  5. Run the Print Fleet Proxy installer.

  6. Follow the onscreen instructions to complete the installation.

  7. Click Finish.

During installation, the setup installs the agent and WXP Fleet Proxy. It also installs the files required to retrieve printer information from HP Web Jetadmin.

Note: After installation, the Print Fleet Proxy icon is available on the Windows taskbar and in the notification area (system tray).

Step 2: Connecting Print Fleet Proxy to WXP

After installation, register the Print Fleet Proxy with WXP.

  1. Open the Workforce Experience Print Fleet Proxy application.

  2. On the Welcome screen, click Generate Verification Code. A verification code is generated.

  3. Copy the code. The screen also shows the remaining time before the verification code expires.

  4. From the left menu of WXP, click Devices > Printers. The Printers page is displayed.

  5. On the Printers page, click the Proxies tab. The existing proxies are displayed.  

  6. In the Proxies tab, click Add proxy.

  7. Enter the verification code generated in the Print Fleet Proxy application.

    Note: You can verify the code in either of the following ways:

    • Copy the verification code, sign in to WXP, and paste the code.

    • Select Verify Code on the screen to automatically navigate to WXP.

  8. Start the proxy verification. WXP validates the following information:

    • Tenant information.

    • User permissions.

    • Network connectivity.

    • Existing proxy registration status.

  9. In WXP, after verification succeeds, the Proxy Connected message appears.

  10. In the Print Fleet Proxy application, click Go to Print Fleet Proxy Dashboard. The Dashboard is displayed, where you can monitor the health and connection status of the proxy agent that connects HP Web Jetadmin printers to the HP cloud service.

Step 3: Finding Printers in HP Web Jetadmin

After connecting the proxy, use HP Web Jetadmin to find the printers that must be added to WXP.

  1. Open HP Web Jetadmin.

  2. Find printers using individual IP addresses or an IP address range.

  3. Confirm that the printers are discovered in HP Web Jetadmin.

Step 4: Viewing Discovered Printers in WXP

Printers discovered through HP Web Jetadmin automatically appear in WXP.

  1. From the left menu of WXP, click Devices > Printers. The Printers page is displayed.

  2. On the Printers page, click the Printers tab.

  3. Locate the discovered printer in the printer list.

  4. Verify that Connectivity Type is displayed as Proxy.

The registered Fleet Proxy appears on the Proxies tab. Printers discovered through the Fleet Proxy appear on the Printers tab with Connectivity Type = Proxy.

Checking the Print Fleet Proxy Status

Use the Print Fleet Proxy Dashboard to check the agent and connection status.

From the Dashboard, you can view:

  • The agent status.

  • The Communication API status.

  • The MQTT status.

  • The certificate and secret validity information.

Exporting Diagnostic Logs

On the Print Fleet Proxy Dashboard, click Export logs in the Diagnostic Logs section.

Note: Older events are overwritten when the file size reaches 10 MB.

Generating a New Verification Code

If the verification code expires, the Verification Code Expired message appears.

An expired verification code cannot be used to complete the connection. Generate a new verification code in the Fleet Proxy application, copy the code, and enter it in WXP to verify the connection.

Troubleshooting Proxy Verification

If WXP cannot verify the proxy, the Unable to Verify Proxy message appears.

Verification can fail for the following reasons:

  • An invalid verification code.

  • An expired verification code.

  • A proxy that is already registered.

  • A network or connectivity problem.

  • A WXP service availability issue.

  • An authentication problem.

Generate a new verification code in the Fleet Proxy application and retry the verification.

Contact Us

For any assistance, create a support case or email support@wxp.hp.com.

Related articles