Sharp PRINT AUDIT (serv.man2) Handy Guide ▷ View online
26
th
September 2002
PRINT CONTROL SOLUTIONS
Print-Auditor Thin Client Agent 2.4
Installation Guide
Issue
2.4
P R I N T C O N T R O L S O L U T I O N S
Print-Auditor Thin Client Agent 2.4
Installation Guide
Chapter 1 - Product Overview and Implementation
Chapter 2 – Installation
Installation of the Data Collection Server
Installation to Windows NT based workstations and mixed Win NT and 9X
environments
environments
Installation to Windows 9x environments only
Standalone
Installation
Chapter 3 – Data Collection Methods
Data Collection Server
Local
Collection
Chapter 4 – Removing software
Local Uninstall
Global
Uninstall
Chapter 5 – Diagnostics Shortcut
Overview
Implementation
General Notes
P R I N T A U D I T O R T C A 2 . 4 I N S T A L L A T I O N G U I D E
1
Chapter
1
Product Overview & Implementation
he Thin Client Agent (TCA) is a data collection agent for
desktop clients running Windows 95, Windows 98, Windows
ME, Windows NT and Windows 2000. The TCA monitors and
records a user’s printing activities, and writes this information to a
log file, which is stored locally. This log file is either uploaded to a
central location via HTTP where it can be analysed to produce a
complete picture of local and networked printing, or it can be kept
locally where it will remain indefinitely. When the log file is uploaded
to the central location the file stored locally will be removed. The
local log file name is COMPUTERNAME.log and the central log file
is called Printauditor.dca.
log file, which is stored locally. This log file is either uploaded to a
central location via HTTP where it can be analysed to produce a
complete picture of local and networked printing, or it can be kept
locally where it will remain indefinitely. When the log file is uploaded
to the central location the file stored locally will be removed. The
local log file name is COMPUTERNAME.log and the central log file
is called Printauditor.dca.
The Print-Auditor Wizard provides 4 methods of installation. Firstly,
there is the local installation to be used when manually installing the
TCA onto individual workstations. Secondly, the TCA Installer is
capable of installing onto Windows NT based clients without any
user interaction. Alternatively, a login script that can be appended to
existing login scripts enabling automatic installation of the TCA onto
any Windows client PC’s across a network. These scripts can vary
from site to site based on permissions and environment. In the
event of the site not using log-in scripts, an email distribution can be
used.
there is the local installation to be used when manually installing the
TCA onto individual workstations. Secondly, the TCA Installer is
capable of installing onto Windows NT based clients without any
user interaction. Alternatively, a login script that can be appended to
existing login scripts enabling automatic installation of the TCA onto
any Windows client PC’s across a network. These scripts can vary
from site to site based on permissions and environment. In the
event of the site not using log-in scripts, an email distribution can be
used.
T
P R I N T A U D I T O R T C A 2 . 4 I N S T A L L A T I O N G U I D E
2
Chapter 2
Installation Overview
System Pre-requisites and general notes
1. Internet Explorer 3.0 or higher is required.
2. Windows NT 4.0 Service Pack 3 or higher is required
3. Please be aware that Share and NTFS permissions on the
distribution folder (if applicable) should be set to Users/Domain
Users “Full Control”
Users “Full Control”
4. The TCA cannot currently be used with workstations running
CAD applications that do not use the Windows printing
subsystem.
subsystem.
5. If the intention is for the data to be uploaded centrally then it is
imperative that there are no restrictions on port communication
(specifically port 4653) from the workstations.
(specifically port 4653) from the workstations.
To Windows NT/2000 based workstations
For Windows NT 4.0 or Windows 2000 the installation of the Thin
Client Agent can be performed over the network without having the
user logged in. This is referred to as a “push” installation.
For this method of deployment to be successful, the client OS must
have the ADMIN$ share available, the Server Service must be
available and there should be no policy in place disabling the
Windows Installer – none of these restrictions are in place by
default, your Administrator would have set these up as additional
security restrictions.
To Windows 9x based workstations
For Windows 9x machines it is not possible to remotely install the
Thin Client Agent, it is necessary that a login script or e-mail be set-
up for networks containing Windows 9x clients, which is performed
in the wizard.