Network Install Guide

(1)

(2)

Technical support can be obtained via the following:

- Our web site http://www.printaudit.com or E-mail [email protected]

- Telephone toll free in North America 877-412-8348 or outside North America 403-685-4932

IMPORTANT: READ THIS BEFORE PERFORMING A PRINT AUDIT

ANALYSIS INSTALLATION

Print Audit Analysis is a desktop application that you must install on every computer where you want to track printing. Users installing Print Audit Analysis must have Administrator rights, or you must use third-party tools that can install software in a locked down environment. Installing Print Audit Analysis across a network requires knowledge of the network design, user rights and technologies available in your organization. Print Audit supplies various tools to aid in the network rollout of Print Audit software but these tools are meant to complement your

organization's current desktop software rollout procedures. If you do not have an established way to rollout software in your organization then we strongly advise that you develop a software rollout plan for all desktop software before attempting to roll out Print Audit software.

Overview

Print Audit allows you to install its components quickly and easily across your entire network of computers. This document outlines the basic steps needed to mass install Print Audit and what mass installation technologies Print Audit supports.

Step 1: Administrator Install

We highly recommend doing your first installation manually on the person’s computer who is going to be administering Print Audit. This will allow you to create your database and configure Print Audit for operation. This also allows you the opportunity to familiarize yourself with Print Audit’s features and gain access to the help files for general reference.

(3)

Step 2: Creating the Network Installation

(4)

1. Selecting a Network Install Path

(5)

2. Selecting the Install Directory

(6)

3. Enter your Database Settings

(7)

4. Advanced Install Options

In these steps you need to select some advanced options as to how you want the install to behave. If you are not one hundred percent sure what an option does, we highly recommend leaving the default. Here are the available options:

(8)

• Create the Uninstall Information – If checked, the installer creates the necessary entries on the computer so that the software can be easily uninstalled. If unchecked you cannot uninstall the software through scripts or on the desktop. You will have to manually delete files and registry entries to remove it. Uncheck this option at your own risk.

5. Create the Network Install

After filling in all steps, the installation program will create your network install. It copies all required files for the install into the directory you selected for the network install. The next step is to customize the silent network installation files.

Step 4: Customizing the Silent Network Installation Files

When you create your custom network install, Print Audit copies several critical files into the custom network install directory you chose. Here is a list of the files created.

1. Configuration File (painst.cfg)

This file (painst.cfg) contains the settings you chose while answering questions during the creation of your network install. This is a text file arranged as a standard INI file. You can edit this file with Notepad and make changes directly to it. Please be careful making changes to this file. For detailed documentation on each setting in these files as well as optional settings you can add in manually, look for the “silent install” topic in your Print Audit help files index.

(9)

2. Silent Install Batch File (pasilent.bat)

This file (pasilent.bat) is the file responsible for running the Print Audit installation in silent mode. When running in silent mode the installer reads the settings you entered in the configuration file and installs Print Audit with no interaction necessary from the user. There is detailed

documentation in the pasilent.bat file, please read this information carefully before altering this file.

The key to the pasilent.bat file is to ensure the following line is set properly: SET PAINSTPATH=[Your net install path directory]

You need to set this line to the path of the Print Audit network install directory. If you do not have this path set properly Print Audit will not read your configuration file and the install will not work as you have anticipated.

3. Silent Uninstall Batch File (pauninst.bat)

This file allows you to silently uninstall Print Audit from your users’ computers. Just like the silent install batch file you must ensure the following line is set properly: SET PAINSTPATH=[Print Audit install directory]

The directory you set should be the SHORT path version of your end user’s Print Audit installation directory. For example, if you keep the default install paths this should be: C:\PROGRA~1\PRINTA~1

If Print Audit cannot find this directory then Print Audit will not uninstall. Keep in mind that if you chose not to create un-installation information when you created your install, this file will not uninstall Print Audit.

4. Sleep Command File (sleep.exe)

This file is a simple DOS utility to cause the computer to pause for a few seconds. The batch files call this command; you do not need to do anything with it.

5. Print Audit Silent MSI Wrappers (PAInstallWrap.msi, PAUninstallWrap.msi)

These files are Windows Installer MSI wrappers that call the “pasilent.bat” and “pauninst.bat” files respectively. Print Audit provides this file so you can distribute Print Audit using Active Directory. Please see the section Distributing the Silent Network Install in this document for more information.

Step 5: Testing and Troubleshooting the Silent Network Install

The next step is to test to ensure the pasilent.bat file successfully installs Print Audit the way you want on an individual’s workstation. We recommend going to a user’s computer who does not have Print Audit installed, navigating to the network install directory and manually running the “pasilent.bat” file by double-clicking on it. If everything works the way you expect you can then distribute Print Audit across your network.

(10)

Common Problems and Their Solutions

1. Database settings are incorrect

If the database settings are wrong, IE: Print Audit asks for a database when you run it or says it cannot connect, check your database settings in the configuration file (painst.cfg), and double-check the “SET PAINSTPATH” line in your pasilent.bat to ensure it is correct.

2. The wrong components are installed

This is caused by an incorrect configuration file or the “SET PAINSTPATH” line is incorrect. Please double-check these settings in the “painst.cfg” file. For more information on the contents of this file please see the silent installation topic in your Print Audit help files.

3. Database settings are correct, but I still get database connection errors

Ensure the Print Audit Data Server is running and that its port and location settings match the ones in the painst.cfg file

Step 6: Distributing the Silent Network Install

Once the silent installation is working properly you need to decide how you want to distribute it across your network. This is entirely dependent on your network and the tools you have available but here are the most common ways along with their advantages and pitfalls.

1. Login Scripts

The easiest way to run the “pasilent.bat” file to get the install going is to include it in a standard Windows login script. This works great for networks that are running Win95/98 or where your users have local Administrator rights on their computers. The Print Audit installs need permission to create directories, create registry keys and in some cases copy files into areas that can be locked down for users with restricted permissions.

2. Active Directory Managed Software Packages

Print Audit provides two files, “PAInstallWrap.msi” and “PaUninstallWrap.msi” that you can assign as managed software packages using group policies in Active Directory. These files simply call the “pasilent.bat” and “pauninst.bat” files respectively. Using the MSI packages and Active Directory allow the Print Audit installs to run at system level security when a computer boots up so that users do not need to have elevated permissions.

The downfall of this approach is that this will not install software to older operating systems, so if you have a mix of operating systems in your organization you will have use a combination of this approach and login scripts.

As well your organization must have knowledge of group policies and distributing software in this environment. The “msi” packages are to be used at your discretion. For more information on using Group Policies with Active Directory to install software, please refer to your Microsoft server help files or Microsoft’s website.

3. Third Party Installation Tools

(11)