HSLAB Print Logger 5 Installation Guide

NOTE: Information and screen shots in this document are related to the Print Logger EE edition. In different editions some features may be not available. See editions matrix for details.

 
 
Windows Small Business Server 2003 Standard Edition SP1, Windows Small Business Server 2003 Premium Edition SP1
Windows XP Professional SP2, Windows XP Home Edition SP2, Windows XP Tablet Edition SP2, Windows XP Media Edition SP2
 
Windows 2000 Professional Edition SP4, Windows 2000 Server Edition SP4, Windows 2000 Advanced Edition SP4, Windows 2000, Datacenter Server Edition SP4, Virtual Server
 
Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Business, Windows Vista Enterprise, Windows Vista Ultimate
(XP/Vista is supported, but not recommended). CPU Pentium III Compatible or higher. Minimum: 500 MHz, Recommended: 1 GHz or higher. See editions matrix for details.
32-bit and 64-bit

At least one local/LPR printer locally installed. Internet connection for updates is recommended, TCP/IP is required.
 
System memory:
Minimum: 192 MB, Recommended: 512 MB or higher
 
Disk space:
250 MB free space
 
 
800 x 600 (with any color depth), 1024 x 768 x 16-bit color recommended.

Prerequisite software:

NOTE: All or the majority of these components most likely already installed on your system by the Windows Update. If some components are missing, Print Logger installation package will download and install the required software for you.

Microsoft .NET Framework v2, download from the .NET Framework 2.0 Download Center.
Microsoft Internet Explorer 6.0 Service Pack 1 (SP1) or later (prerequisite for .NET Framework)
Windows Installer 3.1
Microsoft Data Access Components (MDAC) 2.8
Windows 2000 Service Pack 4
Windows XP Service Pack 2
Windows Server 2003 Service Pack 1

NOTE: Print Logger software is designed for monitoring local printers or LPR printers, which are using your print server as spooler for print jobs. See Frequently asked question entry:

My printer has its own network interface card. How can I use the Print Logger software with it?

If you’re wanted to monitor printers, physically connected to the other computers, you should install the Print Logger software to each of these computers.

NOTE: You can store print jobs statistics in one storage and create and view reports from the one point, independently on number of a print servers and print clients in your network.

Please see:

Multiply Print Logger installation in your network

Tasks: print jobs monitoring on one print server, all data is stored locally using embedded data storage engine.

Start the installation process double clicking on hslab-print-logger-5-XX.exe, where XX is an edition marker. Installation process is a simple and traditional.

You’re should set installation directory and product installation type.

NOTE: If you’re installing this software on cluster system, you should place Print Logger directory on your cluster shared drive.

For server installation you’re should select “”

Or “Print Logger Server Components”.

In this case the client components will not be installed. Client components are not required for server installation. See more about client components installation:

Remote Info Console

My Print Jobs

Before actual installation the Print Logger Install wizard will create the system restore point.

The Print Logger Install wizard will check your system for Prerequisite software:

And will try to install missing components automatically. If some components are failed to install, please try to install missing components manually.

The Print Logger software using Microsoft SQL server 2005 express edition. This component will be installed automatically without user intervention.

If you’re planning to use this Print Logger installation as data collector for other Print Logger installations and/or allow remote access to the statistics and reports (from the local network) please enable set of firewall rules. These rules will be created automatically by the install wizard.

At this step you should start the Print Logger configuration:

Printer Properties

Accounting Engine

2. Multiply server installation, local database on one server using embedded database engine.

The software installation process is similar to 1. Configuration for the server, which will keep statistics from other print servers, should be configured for using embedded storage engine. Firewall rules should be added to the firewall on this server. You do not need to add firewall rules to the firewalls on other servers.

Other servers will store all configuration information and print jobs statistics in database on first print server and should be configured for using remote SQL server as data storage. The first server acts as remote SQL server.

In “SQL Configuration Wizard” you should set server type as Microsoft SQL server.

See: SQL serSelect SQL Server Typever typedata storage. If this SQL server is not visible in the available SQL servers list, please enter it’s name manually. If your first server has name SERVER1 (for example), you should enter SERVER1\PRINTLOGGER. NOTE: This notation is valid only if you’re using embedded data storage engine.

You should repeat this steps on all print servers, excluding the first server.

3. .

This configuration is more suitable for corporate networks. Most large and middle size companies use one or more SQL servers for centralized data storage. Print Logger also allows you storing all its statistical and configuration data in one shared SQL database.

The software installation process is similar to 1. All servers will store all configuration information and print jobs statistics in one database on single corporate SQL server and should be configured for using remote SQL server as data storage.

Firewall rules should be added to the firewall on all servers.

In “SQL Configuration Wizard” you should set server type as Microsoft SQL server.

See: SQL server type configuration. You should select SQL server on each print server as data storage. If your SQL server is not visible in the available SQL servers list, please enter it’s name manually.

If your SQL server has name SERVER1 (for example), you should enter SERVER1 or SERVER1\PRINTLOGGER, if your SQL server installed as instance. You should repeat this steps on all print servers.