Changing the PaperCut Server Name or IP Address
Last modified on 14 August 2020 12:03 AM
“Help! We need to change the IP address and/or Hostname of our PaperCut server. How can we do this while ensuring minimal disruption for our users?”
Changing the hostname or IP address of your PaperCut server is considered a high-impact task and should be treated with some care and planning. Many components on the network rely on the PaperCut server’s hostname or IP address. If the primary PaperCut server’s hostname or IP address is changed it can cause many PaperCut components to communicating with the server.
If instead you are looking to change the IP address of your printers or copiers, we recommend you have a look at this article: Printer and Device IP Address Change Considerations.
Before you go down this path…
PaperCut Components that will need to be updated
Other things to consider
PaperCut MF customers only: If your PaperCut server’s IP address or hostname is changing you may need to reconfigure your copiers and printers running the PaperCut embedded application so that these devices will continue working with the server.
We would strongly advise contacting your Reseller or Authorized Solution Center before changing IP’s on these Device types. Since this Device type is hosted from the PaperCut server, the IP address to which PaperCut points for each device will also need to be changed along with any other settings your Reseller or Authorized Solution Center needs to change.
The PaperCut User Client enables users to select an account for billing when printing, lets users see their balance, and may be used for pop-up authentication in some environments.
If your organization uses these features, you will need to find and update the PaperCut Client’s configuration file with the new server IP address and hostname.
This file, called config.properties, can be opened and edited with any plaintext editing software like TextEdit or Notepad to change the values of the lines that start with
At a minimum, you will want to update the master copies of these files on the server and it may also be necessary to update the config.properties file on each workstation depending on how the PaperCut User Client is deployed.
Update the Client’s config.properties files on the server
After renaming or re-IP-ing a server you should update the master config.properties files for the Client on the PaperCut Server.
If the PaperCut Client has been deployed with the Zero Install method and is running from the share on the PaperCut server, you might be good to go! Just make sure the logon script which launches the client on startup also has the correct server hostname or IP address.
If the PaperCut client is installed locally, then you will need to follow the steps below.
Update the Client’s config.properties file on each workstation
If the PaperCut User Client has been installed locally on each workstation, then the simplest option is to re-deploy the PaperCut Client using the freshly updated copy of the application from the server.
An alternative is to manually edit the config.properties file on each workstation running the PaperCut Client. If you must do this, here is where to find the config.properties file for each client OS type:
The PaperCut Secondary Server application may be installed on additional print servers in your environment other than the PaperCut server to track print jobs.
The Direct Print Monitor may run on individual workstations to track print jobs not sent to a PaperCut server (for example a locally attached USB-connected printer).
If your organization has Secondary servers or workstations running the Direct Print Monitor, you will need to update the Print Provider configuration file, named print-provider.conf, with the new PaperCut server’s IP address and hostname. On Windows workstations running the Direct Print Monitor, this will be called the direct-print-monitor.conf file, but the steps will be the same.
The PaperCut Release Station application may be installed on a dedicated computer in a print room to enable users to securely release print jobs.
If your organization has Release Stations, you will need to update the connection.properties file with the new PaperCut server’s IP address and hostname.
At a minimum, you will want to update the master copies of these files on the server and it may also be necessary to update the connection.properties file on each workstation depending on how PaperCut Release Stations are deployed.
A PaperCut Site Servers hosts a read-only copy of the main PaperCut server and may be used for resilience and failover.
If your organization has Site Servers you will need to find and update the configuration file, called site-server.properties, with the new PaperCut server’s IP address and hostname.
If the server you are migrating to has a different IP address or hostname from your original server, you will need to redeploy the clients with the new server’s hostname. We recommend that you redownload the client from your new server to ensure your clients are also up to date. Note that reinstalling or uninstalling the clients won’t remove the print queues already installed on your users’ computers; users can still print to all queues already deployed by Print Deploy.
Note: For more information on PaperCut application server migration, click here
The Web Print Sandbox is Windowed application running on a separate computer from the PaperCut server to process print jobs submitted via WebPrint.
To accomplish this, the Sandbox communicates with the PaperCut server and fetches print jobs using a ‘hot folder’ (a file share configured on the PaperCut server). The ‘hot folder’ path can either be a mapped network drive or a UNC path and is saved in the web-print.conf file found on the Sandbox. You will want to check this file to see how this path is configured and confirm it points to the new hostname of the server.