Keeping a healthy system

KB Home   |   Keeping a healthy system

Main.KeepingAHealthySystem History

Hide minor edits - Show changes to output

Changed lines 3-4 from:
PaperCut has been around since 1999 and has proven to be a robust and reliable system.  We still have customers running the original version 1 release back from 1999 without any hitches!  One of the design objectives forming the foundation of PaperCut is “self administration”.  Where possible the system should be responsible for it’s own management and maintenance.  PaperCut does a good job in this area and normally manual maintenance is not required.  However, like all systems, Administrators should make regular inspections and avoid configuration or system changes that might upset normal operation. 
to:
PaperCut has been around since 1999 and has a very reliable and robust system.  We still have customers running the original version 1 release back from 1999 without any hitches!  One of the design objectives forming the foundation of PaperCut is “self administration”.  Where possible the system should be responsible for it’s own management and maintenance.  PaperCut does a good job in this area and normally manual maintenance is not required.  However, like all systems, Administrators should make regular inspections and avoid configuration or system changes that might upset normal operation. 
Changed lines 7-10 from:
* Take care when renaming printers.  PaperCut detects printers by name.  After renaming a printer, Administrators should be aware that they will need to manually setup the “new” (renamed) printer again in PaperCut’s charging list.

* Test PaperCut after making large network or domain structure changes.  Renaming a domain or making large Active Directory structure changes may affect PaperCut’s user synchronization process.  Take a few minutes to test PaperCut (print a few test documents) after making network changes
.
to:
* Keep your software up-to-date. PaperCut has a ''check for updates'' feature that points to a detailed release history page allowing you to easily track when new versions are available.
Changed lines 11-14 from:
* Keep an eye on disk space.  PaperCut needs disk space to write log files.  Full disks can cause problems.

* Clear log files.  PaperCut’s log files
will grow indefinitely.  The system will issue a warning when logs grow to a large size.  Very large log files may impede the performance of the server and the web tools interface.  We recommend that Administrators clear the logs at “logical” periods such as end-of-year or end-of-semester.  (Note:  old log files are archived so data is not lost)
to:
* Keep an eye on disk space.  PaperCut needs disk space to write log files and update it's database.  Full disks can cause problems with any software, but even close-to-full disks will cause performance issues.

* Test PaperCut after making large network or domain structure changes.  Renaming a domain or making
large Active Directory structure changes may affect PaperCut’s user synchronization process.  Take a few minutes to test PaperCut (print a few test documents) after making any significant network changes.
Deleted lines 2-3:
''Categories:'' [[!Administration]]
Added lines 20-21:

''Categories:'' [[!Administration]]
Added lines 1-4:
(:title Keeping a healthy system:)

''Categories:'' [[!Administration]]

Changed lines 13-14 from:
* Ensure a good off-disk backup strategy is in place on the server.  (See BackingUpData)
to:
* Ensure a good off-disk backup strategy is in place on the server.  (See [[BackingUpData | +]])
Changed line 1 from:
PaperCut has been around since 1999 and has proven to be a robust and reliable system.  We still have customers running the original version 1 release back from 1999 without any hitches!  One of the design objectives forming the foundation of PaperCut is “self administration”.  Where possible the system should be responsible for it’s own management and maintenance.  PaperCut does a good job in this area and normally manual maintenance is note required.  However, like all systems, Administrators should make regular inspections and avoid configuration or system changes that might upset normal operation. 
to:
PaperCut has been around since 1999 and has proven to be a robust and reliable system.  We still have customers running the original version 1 release back from 1999 without any hitches!  One of the design objectives forming the foundation of PaperCut is “self administration”.  Where possible the system should be responsible for it’s own management and maintenance.  PaperCut does a good job in this area and normally manual maintenance is not required.  However, like all systems, Administrators should make regular inspections and avoid configuration or system changes that might upset normal operation. 
Changed lines 1-17 from:
Describe KeepingAHealthySystem here.
to:
PaperCut has been around since 1999 and has proven to be a robust and reliable system.  We still have customers running the original version 1 release back from 1999 without any hitches!  One of the design objectives forming the foundation of PaperCut is “self administration”.  Where possible the system should be responsible for it’s own management and maintenance.  PaperCut does a good job in this area and normally manual maintenance is note required.  However, like all systems, Administrators should make regular inspections and avoid configuration or system changes that might upset normal operation. 

The following list highlights some problems experienced by our customers over the years, and explains how to avoid them on your own networks:

* Take care when renaming printers.  PaperCut detects printers by name.  After renaming a printer, Administrators should be aware that they will need to manually setup the “new” (renamed) printer again in PaperCut’s charging list.

* Test PaperCut after making large network or domain structure changes.  Renaming a domain or making large Active Directory structure changes may affect PaperCut’s user synchronization process.  Take a few minutes to test PaperCut (print a few test documents) after making network changes.

* Ensure a good off-disk backup strategy is in place on the server.  (See BackingUpData)

* Keep an eye on disk space.  PaperCut needs disk space to write log files.  Full disks can cause problems.

* Clear log files.  PaperCut’s log files will grow indefinitely.  The system will issue a warning when logs grow to a large size.  Very large log files may impede the performance of the server and the web tools interface.  We recommend that Administrators clear the logs at “logical” periods such as end-of-year or end-of-semester.  (Note:  old log files are archived so data is not lost)

* Make a PaperCut health check part of your weekly or monthly system status checks.  Take a few minutes to check the PaperCut Application Event log for errors and print test documents to ensure everything is OK.

By keeping these points in mind, PaperCut should give you years of trouble free operation
.

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 28, 2008, at 03:01 AM
Printable View   |   Article History   |   Edit Article