Changing the name (hostname) or the IP address of a server is generally considered a high impact task and should be treated with some care (much more so than changing the IP of a workstation). Clients/workstations software (e.g. the PaperCut User Client) locate and communicate with the server by using a hostname and/or IP address stored in a configuration file. For correct operation, any hostname/IP address change should also be propagated to the following files:
Please see the example below:
config.properties file located in the client directory (client connection information stored in the same directory as the client executable):
[app-path]/client/mac/PCClient.app (control-click, Show Package Contents) Contents/Resources/config.properties
On Locally Installed Clients:[client-install-path]/config.properties
connection.properties file located in the release directory (release station connection information):
On Locally Installed Stations:[client-install-path]/connection.properties
The print provider config file located at: [app-path]/providers/print/win/print-provider.conf (Note: On windows, the print provider service must be restarted after changing this file)
The print provider config file located on any secondary server or future installed secondary server.
PaperCut MF deployments may also have the system.network-address advanced config key set, specifying a particular address for MFDs to preference when contacting the Application Server. It is wise to use the Advanced Config Editor to double-check the value of this config key. If the key’s value is blank, no change will be required.
If the hostname is being changed and you would like to keep the same printer entries in PaperCut afterwards (i.e. to preserve settings and print history), then the printers in PaperCut must be renamed. See the article How to Rename a Printer for more details.
The impact renaming the server may have on shared printers, or shared file paths.
The URLs used to access the PaperCut server for remote administration may need to change - inform other administrators.
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.