Do I also need to upgrade secondary servers and clients?

KB Home   |   Do I also need to upgrade secondary servers and clients?

Main.DoINeedToUpgradeOtherComponents History

Hide minor edits - Show changes to output

March 19, 2019, at 06:43 AM by peterf - Added mention of 32-bit KB for 19.0
Changed lines 5-7 from:
The one exception is Site Servers. Due to the specifics of their implementation, and particularly due to the method by which they closely interface with the Application Server, Site Servers must be kept at the exact same version level as the Application Server. When performing an upgrade in an environment that includes Site Servers, it is recommended that they are upgraded immediately following the successful upgrade of the Application Server itself. The Site Server will continue working until this is done, albeit in 'Offline' mode, and thus with certain functional limitations imposed.
to:
One exception is Site Servers. Due to the specifics of their implementation, and particularly due to the method by which they closely interface with the Application Server, Site Servers must be kept at the exact same version level as the Application Server. When performing an upgrade in an environment that includes Site Servers, it is recommended that they are upgraded immediately following the successful upgrade of the Application Server itself. The Site Server will continue working until this is done, albeit in 'Offline' mode, and thus with certain functional limitations imposed.

Another important exception is if your environment still accommodates any 32-bit workstations which are running our User Client or Release Station. If you are upgrading from version 18.3 or earlier to version 19.0 or later, you may need to address these 32-bit workstations as part of your upgrade activity for the primary Application Server. For more information, please see our [[EndOfLife32BitOperatingSystems|+]] article
.
Changed lines 3-7 from:
When upgrading a PaperCut central server, it is generally '''not''' mandatory to upgrade secondary servers, release stations, web print servers or clients immediately unless otherwise stated in the release notes.  We always strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
to:
When upgrading a PaperCut central server, it is generally '''not''' mandatory to upgrade secondary servers, release stations, web print servers or clients immediately unless otherwise stated in the release notes.  We always strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.

The one exception is Site Servers. Due to the specifics of their implementation, and particularly due to the method by which they closely interface with the Application Server, Site Servers must be kept at the exact same version level as the Application Server. When performing an upgrade in an environment that includes Site Servers, it is recommended that they are upgraded immediately following the successful upgrade of the Application Server itself. The Site Server will continue working until this is done, albeit in 'Offline' mode, and thus with certain functional limitations imposed.

Further notes/comments:
Changed lines 3-4 from:
When upgrading a PaperCut central server, it is generally '''not''' mandatory to upgrade secondary servers, release stations, web print servers or clients immediately unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
to:
When upgrading a PaperCut central server, it is generally '''not''' mandatory to upgrade secondary servers, release stations, web print servers or clients immediately unless otherwise stated in the release notes.  We always strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
Deleted lines 6-7:
* Always check the release notes for critical exceptions to this rule.  You'll find these notes linked next to the download link.
Changed lines 9-10 from:
* Best practice suggests upgrading all components at the same time.  This way you maintain a consistent and predictable environment.
to:
* Best practice suggests upgrading all components at the same time.  This way you maintain a consistent and predictable environment.  You should always upgrade your primary server first.
Changed lines 7-8 from:
* Always check the release notes for exceptions to this rule.  You'll find these notes linked next to the download link.
to:
* Always check the release notes for critical exceptions to this rule.  You'll find these notes linked next to the download link.
Changed lines 5-6 from:
* [b]If you encounter unexpected behaviour or problems, please upgrade all components of PaperCut as soon as possible before troubleshooting further. Should you request support for a problem where mismatched component versions is detected, this will be the first troubleshooting step.[/b]
to:
* '''If you encounter unexpected behaviour or problems, please upgrade all components of PaperCut as soon as possible before troubleshooting further. Should you request support for a problem where mismatched component versions is detected, this will be the first troubleshooting step.'''
May 24, 2012, at 12:58 PM by ian - Include new dot point regarding troubleshooting differing component versions.
Changed lines 3-4 from:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers, release stations, web print servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
to:
When upgrading a PaperCut central server, it is generally '''not''' mandatory to upgrade secondary servers, release stations, web print servers or clients immediately unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:

* [b]If you encounter unexpected behaviour or problems, please upgrade all components of PaperCut as soon as possible before troubleshooting further. Should you request support for a problem where mismatched component versions is detected, this will be the first troubleshooting step.[/b]

March 09, 2011, at 10:58 PM by Rick - added web print to the list.
Changed lines 3-4 from:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
to:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers, release stations, web print servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
Changed lines 7-8 from:
* You may need to upgrade secondary print servers, locally installed clients, or release stations to take advantage of new features.
to:
* You may need to upgrade secondary print servers, locally installed clients, release stations, or the web print server to take advantage of new features.
Changed lines 3-4 from:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still take to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
to:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still talk to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
Changed lines 3-4 from:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This meas that old servers can still take to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
to:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This means that old servers can still take to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
Changed lines 3-4 from:
When upgrading a PaperCut central server, it is ''not'' mandatory to also upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This meas that old servers can still take to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
to:
When upgrading a PaperCut central server, it is '''not''' mandatory to upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This meas that old servers can still take to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
Changed lines 3-4 from:
When upgrading a PaperCut central server, it is ''not'' mandatory to also upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This allows you to upgrade other servers at your own convenience.  Further notes:
to:
When upgrading a PaperCut central server, it is ''not'' mandatory to also upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This meas that old servers can still take to new servers allowing you to upgrade servers at your own convenience.  Further notes/comments:
Changed lines 3-10 from:
When upgrading a server, it is ''not'' mandatory to also upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This allows you to upgrade other servers at your own convenience.  Further notes:

* Always check the release notes for exceptions to this rule.

*
You may need to upgrade secondary servers, locally installed clients, or release stations to take advantage of new features.

* Best practice suggests upgrading all components at the same time.  This way you maintain a consistent and prodictable
environment.
to:
When upgrading a PaperCut central server, it is ''not'' mandatory to also upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This allows you to upgrade other servers at your own convenience.  Further notes:

* Always check the release notes for exceptions to this rule.  You'll find these notes linked next to the download link.

* You may need
to upgrade secondary print servers, locally installed clients, or release stations to take advantage of new features.

* Best practice suggests upgrading all components at the same time.  This way you maintain a consistent and predictable
environment.
Added lines 1-16:
(:title Do I also need to upgrade secondary servers and clients?:)

When upgrading a server, it is ''not'' mandatory to also upgrade secondary servers or clients unless otherwise stated in the release notes.  Where possible we strive to maintains backwards compatibility.  This allows you to upgrade other servers at your own convenience.  Further notes:

* Always check the release notes for exceptions to this rule.

* You may need to upgrade secondary servers, locally installed clients, or release stations to take advantage of new features.

* Best practice suggests upgrading all components at the same time.  This way you maintain a consistent and prodictable environment.

* In most cases, sites using the zero-install client deployment method (on windows) will not need to upgrade the client software as this will be automated.

----
''Categories:'' [[!Administration]], [[!Upgrading]]
----
[-keywords: upgrade, update, old versions -]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on March 19, 2019, at 06:43 AM
Printable View   |   Article History   |   Edit Article