Руководство Пользователя для Xerox XCounter Page Accounting Support & Software
Mar 2001
XCOUNTER FOR NT USER REFERENCE MANUAL
11
XCounter Printer Control Service
It is necessary for the XCounter Printer Control service to be running on NT printer
hosts where XCounter port monitors are installed. Upon installation, the XCounter
Printer Control service will be configured with startup type: “Automatic”, which means
that it will run at system boot time. However, the service may be started and stopped
at any time using XControl from any Windows 95/98/Me/NT/2000 workstation on the
network, if required network permissions are enabled.
hosts where XCounter port monitors are installed. Upon installation, the XCounter
Printer Control service will be configured with startup type: “Automatic”, which means
that it will run at system boot time. However, the service may be started and stopped
at any time using XControl from any Windows 95/98/Me/NT/2000 workstation on the
network, if required network permissions are enabled.
When changing a printer’s popup or pause all jobs setting, a restart of the Printer
Control Service will be required. All other settings are dynamic (including adding new
monitored printers), and the service need not be restarted.
Control Service will be required. All other settings are dynamic (including adding new
monitored printers), and the service need not be restarted.
The SYSTEM account should have Full Control permission on all XCounter-controlled
printers.
printers.
XCounter Data Server Service
The XCounter Data Server service manages all of XCounter’s printer accounting
data. It can run on any NT/2000 Workstation or Server, even if it is not an XCounter
printer host. Each XCounter printer host has a Data Server configuration option that
can be pointed to the same server - this allows the retention of all the printing data in
one central location for easy access. The XCounter Data Server service only needs
to be run on one computer. If the Data Server goes down after a job begins printing
but before the job is logged, then XCounter will store the job information locally until
the Data Server is restarted, at which time the locally stored data will be sent to the
Data Server.
data. It can run on any NT/2000 Workstation or Server, even if it is not an XCounter
printer host. Each XCounter printer host has a Data Server configuration option that
can be pointed to the same server - this allows the retention of all the printing data in
one central location for easy access. The XCounter Data Server service only needs
to be run on one computer. If the Data Server goes down after a job begins printing
but before the job is logged, then XCounter will store the job information locally until
the Data Server is restarted, at which time the locally stored data will be sent to the
Data Server.
XCounter Port Monitors
XCounter port monitors are required in order for XCounter to perform printer
accounting. XCounter port monitors are custom Windows DLLs that are used by the
spooler to send print data to printers. It is necessary for the XCounter Printer Control
service to be running on NT printer hosts where XCounter port monitors are installed
for printing to be functional.
accounting. XCounter port monitors are custom Windows DLLs that are used by the
spooler to send print data to printers. It is necessary for the XCounter Printer Control
service to be running on NT printer hosts where XCounter port monitors are installed
for printing to be functional.
Updating Port Monitors
It is necessary to stop the Spooler service in order to update the XCounter port
monitor software. XControl provides a way to update the XCounter port monitors from
remote computers by stopping the Spooler, copying the files, and then restarting the
Spooler. Stopping the Spooler will interrupt current print jobs. All the printer queues
can be optionally paused or resumed in order to keep new jobs from starting before
updating.
monitor software. XControl provides a way to update the XCounter port monitors from
remote computers by stopping the Spooler, copying the files, and then restarting the
Spooler. Stopping the Spooler will interrupt current print jobs. All the printer queues
can be optionally paused or resumed in order to keep new jobs from starting before
updating.