KB Home | End-of-life for 32-bit Operating Systems
As of version 19.0, PaperCut MF and PaperCut NG no longer support 32-bit platforms for any of our solution components. Sites which still accommodate 32-bit workstations may require special handling when upgrading from an earlier release to version 19.0 or later.
Following on from the end of support for 32-bit server components back on March 31st, 2018, 32-bit platforms are no longer supported for PaperCut MF and PaperCut NG workstation components, due to the move to OpenJDK 11 in version 19.0. Namely, this relates to the User Client and Release Station executables, which will no longer run under 32-bit operating systems. For more information on our migration from Java 8 to OpenJDK 11, check out our Changes to Java Licensing Knowledge Base article. For specifics pertaining to the support end-of-life dates for all our 32-bit solution components, head over to our Support End-of-life Policy.
Please note: an exception to this is Mobility Print. For now, Mobility Print will continue to work on 32-bit and 64-bit platforms.
For User Clients locally installed to 32-bit workstations
Locally installed or MSI deployed 32-bit User Clients will continue to function as normal after an upgrade, as locally installed components need to be upgraded separately after the primary Application Server upgrade has been completed. The client-local-install executables bundled with version 19.0 or later will not run on 32-bit workstations.
After upgrading the primary Application Server to version 19.0 or later, we recommend upgrading these 32-bit workstations to the last available 32-bit release of the User Client. Please note that this release is deprecated, and no longer supported for new deployments; any issues found in this release of the User Client will not see fixes introduced into a 32-bit binary in future.
Download this version to each 32-bit workstation which runs the User Client software.
Extract the archive, and run the included client-local-install executable.
You will then need to modify the local config.properties file to provide the User Client with connection details for the primary Application Server, or copy the central config.properties file from the primary Application Server down to the workstation, overwriting the version created during install.
The local copy of the config.properties file can be found in one of the following locations on a workstation, assuming a default install path.
Windows - C:\Program Files (x86)\PaperCut MF (or NG) Client\config.properties
Hot Tip: If deploying to multiple 32-bit workstations, modify the config.properties found in the downloaded copy, and then copy your modified version of these files to each workstation before running the client-local-install executable.
For User Clients launching from the PCClient network share
The User Client is often deployed using our Zero Install strategy, where the pc-client.exe, pc-client-local-cache.exe, or PCClient.app executable is run directly from a shared network folder on the primary Application Server, typically by some form of login script. 32-bit workstations launching the User Client in this fashion will suddenly be unable to successfully run the User Client if the Application Server is upgraded to version 19.0 or later. It is imperative that the User Clients for these 32-bit workstations be replaced with a locally installed copy of the last available 32-bit release as part of the same upgrade activity. Until this is done, the User Client will not be functional for these workstations. For instructions on locally installing the last available 32-bit release of the User Client, see the For User Clients locally installed to 32-bit workstations section above.
For Release Stations running locally on 32-bit workstations
Release Stations are sometimes deployed by copying the component files to a workstation, and then running the software directly from this local copy. This style of deployment will continue to function as normal after the primary Application Server has been upgraded, as the local copy will remain at the older version level.
After upgrading the primary Application Server to version 19.0 or later, we recommend upgrading these workstations to the last available 32-bit release of the Release Station. A copy of this release can be obtained by temporarily deploying a trial of PaperCut NG 18.3.8 to a laptop or workstation.
Once the trial is installed, the contents of the following directory can be copied over to the existing Release Station deployment directory on 32-bit workstations (where [app-path] is the install path of the trial), with the exception of the config.properties file, the client-machine-aliases.properties file, the connection.properties file, and any connection.[machine-name].properties files. The original versions of these files found on the 32-bit workstation should be retained, to maintain the configuration and connectivity details already in use by the Release Station.
For Release Stations launching from the PCRelease network share
Release Stations are most commonly deployed using a Startup shortcut or Login Item which runs one of the pc-release.exe, pc-release-local-cache.exe, pc-release-secure.exe, pc-release-manager.exe, pc-pay-station.exe, or pc-release-mac.command executables directly from a shared network folder on the primary Application Server. 32-bit workstations launching the Release Station in this fashion will suddenly be unable to successfully run the Release Station if the Application Server is upgraded to version 19.0 or later. It is imperative that the Release Stations for these 32-bit workstations be replaced with a locally installed copy of the last available 32-bit release as part of the same upgrade activity. Until this is done, the Release Station will not be functional for these workstations. For instructions on locally installing the last available 32-bit release of the Release Station, see the For Release Stations running locally on 32-bit workstations section above.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.