Upgrading the Client Software

KB Home   |   Upgrading the Client Software

Main.UpgradingClientSoftware History

Hide minor edits - Show changes to output

July 05, 2018, at 07:14 PM by Aaron Pouliot - Added categories Upgrading and UserClientTool
Changed line 15 from:
[-keywords: client tool, upgrading, msi -]
to:
Added lines 17-19:
''Categories:'' [[Category.Upgrading|+]], [[Category.UserClientTool|+]]
----
[-keywords: client tool, upgrading, msi -]
Added lines 11-12:
At the time of writing PaperCut version 11 servers still support back to version 6 clients.
January 26, 2011, at 06:33 PM by Rick - added link to page with zero install strategy info.
Changed lines 5-6 from:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login. 
to:
A: If you've deployed the client software using the suggested method - the [[https://www.papercut.com/products/ng/manual/ch-user-client.html | zero-install]] strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login. 
Changed lines 5-6 from:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your users to benefit from any new features introduced on the client-side.  Having said that, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function.
to:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login. 

If you've done a local install, then an upgrade is recommended as this will allow your users to benefit from any new features introduced on the client-side.  Having said that, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function.  If we introduce a new feature in the client then you would need to upgrade to get access to the new feature.
Changed lines 5-6 from:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your users to benefit from any new features introduced the client-side.  Having said that, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function. There will be a statement in the release notes if a client update is required.
to:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your users to benefit from any new features introduced on the client-side.  Having said that, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function.
Changed lines 5-6 from:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function. There will be a statement in the release notes if a client update is required.
to:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your users to benefit from any new features introduced the client-side.  Having said that, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function. There will be a statement in the release notes if a client update is required.
July 20, 2010, at 08:38 PM by Rick - wordsmithing for better flow
Changed lines 5-7 from:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstation will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, unless statement in the release notes, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function.

to:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstations will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function. There will be a statement in the release notes if a client update is required.
December 12, 2008, at 05:17 PM by Rick clarified server local install language - changed comparability to compatibility - a higher standard : )
Changed lines 5-7 from:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstation will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, unless statement in the release notes, we do always maintain ''backwards comparability'' with older clients, so users running old clients will see no change or loss in function.

to:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstation will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, unless statement in the release notes, we do always maintain ''backwards compatibility'' with older clients, so users running old clients will see no change or loss in function.

October 23, 2008, at 03:51 AM by 218.214.136.161 -
Changed lines 10-11 from:
* Just a little caveat - one day we may need to break compatibility but if we do we'll give plenty of warning in the release notes and will restrict such changes to major releases only. 
to:
[-'''*''' Just a little caveat - one day we may need to break compatibility but if we do we'll give plenty of warning in the release notes and will restrict such changes to major releases only.-]
October 23, 2008, at 03:50 AM by 218.214.136.161 -
Added lines 7-9:

The [@version.txt@] file (a text file containing the version and build number) installed into the client directory can assist in tracking the client version.

Deleted lines 10-12:

The [@version.txt@] file (a text file containing the version and build number) installed into the client directory can assist in tracking the client version.

October 23, 2008, at 03:49 AM by 218.214.136.161 -
Added lines 7-8:
* Just a little caveat - one day we may need to break compatibility but if we do we'll give plenty of warning in the release notes and will restrict such changes to major releases only.
Changed lines 13-14 from:
''Categories:'' [[!UserClientTool]], [[!Upgrading]]
to:

Changed lines 5-6 from:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstation will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, we do always maintain backwards comparability with older clients, so users running old clients will see no change or loss in function.
to:
A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstation will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, unless statement in the release notes, we do always maintain ''backwards comparability'' with older clients, so users running old clients will see no change or loss in function.
Changed lines 7-8 from:
The [@version.txt@] file installed into the client directory can assist in tracking the client version.
to:
The [@version.txt@] file (a text file containing the version and build number) installed into the client directory can assist in tracking the client version.
Added lines 7-8:
The [@version.txt@] file installed into the client directory can assist in tracking the client version.
Added lines 1-9:
(:title  Upgrading the Client Software:)

Q: I have recently upgraded my server.  Do I also need to upgrade the client software on each workstation?

A: If you've deployed the client software using the suggested method - the zero-install strategy (e.g. running directly off the share) - then no update will be required.  All workstation will pick up the new version on their next reboot/login.  If you've done a local install, then an upgrade is recommended as this will allow your uses to benefit from any new features introduced the client-side.  Having said that, we do always maintain backwards comparability with older clients, so users running old clients will see no change or loss in function.

[-keywords: client tool, upgrading, msi -]
----
''Categories:'' [[!UserClientTool]], [[!Upgrading]]

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 July 05, 2018, at 07:14 PM
Printable View   |   Article History   |   Edit Article