Uniprint Planning and Installation Guide

Uniprint Planning and Installation Guide
Pharos Uniprint® 9.0
Planning and Installation Guide
Document Version: UP90-Install-1.0
Distribution Date: May 2014
Pharos Systems International
| Suite 310, 80 Linden Oaks | Rochester, New York 14625 | Phone: 1- 585-939-7000 | US/Canada Toll Free: 888-864-7768 | www.pharos.com
Copyright © 2014 Pharos Systems International, Inc.
Pharos®, Uniprint®, Secure Release Here®, and Off-The-Glass® are registered trademarks of Pharos
Systems International, Inc. The trademarks and names of other companies and products mentioned
herein are the property of their respective owners.
2
Planning and Installation Guide
Table of Contents
Introduction .......................................................................................................................... 7
About This Document ............................................................................................................................... 7
Other Documentation ........................................................................................................................... 7
Getting Help .............................................................................................................................................. 7
Pharos Website ..................................................................................................................................... 7
Contact Details ...................................................................................................................................... 7
Pharos Uniprint Suite Overview ............................................................................................. 8
Pharos Uniprint® Suite Core Products ...................................................................................................... 8
Pharos Uniprint® ................................................................................................................................... 8
Pharos Off-The-Glass® .......................................................................................................................... 8
Pharos SignUp ....................................................................................................................................... 8
Pharos Uniprint Applications .................................................................................................................... 9
Secure Release Here® ........................................................................................................................... 9
Informed Print ....................................................................................................................................... 9
Third-Party Charging ............................................................................................................................. 9
Pharos Print Center ............................................................................................................................... 9
MobilePrint ........................................................................................................................................... 9
Credit Card Gateway ........................................................................................................................... 10
Planning Your Installation .................................................................................................... 11
Uniprint Suite Components .................................................................................................................... 11
Server Components............................................................................................................................. 11
Client Components.............................................................................................................................. 12
Administrative Components ............................................................................................................... 13
Web Components ............................................................................................................................... 14
Other Components ............................................................................................................................. 14
Which Pharos Server Components to Install? ........................................................................................ 15
Sizing Your Installation ............................................................................................................................ 16
Your Environment ............................................................................................................................... 16
Number of Servers .............................................................................................................................. 17
Database Sizing ................................................................................................................................... 18
Example ................................................................................................................................................... 19
System Requirements ............................................................................................................................. 19
3
Planning and Installation Guide
Pharos Server Components Requirements ......................................................................................... 19
Example 1: ............................................................................................................................................... 21
Example 2: ............................................................................................................................................... 21
Administrative Components Requirements........................................................................................ 26
Client Components Requirements ...................................................................................................... 28
TCP/IP Ports in Uniprint .......................................................................................................................... 30
Default Ports ....................................................................................................................................... 30
Required Ports .................................................................................................................................... 31
Optional Ports ..................................................................................................................................... 31
Principal Server ................................................................................................................................... 31
Print Server ......................................................................................................................................... 32
EDI Server ............................................................................................................................................ 33
Administrative Components ............................................................................................................... 33
Client Components.............................................................................................................................. 35
Other Server Components .................................................................................................................. 35
Windows Firewall.................................................................................................................................... 37
Installation Overview .......................................................................................................... 38
Server Roles ............................................................................................................................................ 38
Typical Order of Installation.................................................................................................................... 39
Important Installation Notes................................................................................................................... 39
Installing Other Pharos Components ...................................................................................................... 39
Client Components.............................................................................................................................. 40
Administrative Components ............................................................................................................... 40
Web Components ............................................................................................................................... 41
Other Components ............................................................................................................................. 41
Installing Server Components .............................................................................................. 42
Pre-Installation Checklist ........................................................................................................................ 42
Using the Installation Wizard .................................................................................................................. 45
Installing Uniprint Suite Server Components.......................................................................................... 45
Main Installer Wizard Screens ............................................................................................................ 46
Component-Specific Screens .............................................................................................................. 49
Typical Installation Workflows ................................................................................................................ 59
Installing Print Services ....................................................................................................................... 59
Installing SignUp Services.................................................................................................................... 59
Installing the Pharos EDI Service ......................................................................................................... 60
4
Planning and Installation Guide
Installing Server Components on a Cluster ........................................................................... 61
Supported Configurations ....................................................................................................................... 61
Before You Begin..................................................................................................................................... 61
Typical Order of Installation.................................................................................................................... 62
Preparing Cluster for Installation ............................................................................................................ 62
Installing Database and Principal Services .............................................................................................. 63
Before You Begin ................................................................................................................................. 63
Installing the Database and the Principal Services on the First Node ................................................ 63
Installing Principal Services on the Second Node ............................................................................... 64
Configuring the Pharos Principal Services as Cluster Resources ........................................................ 64
Validating the Installation ................................................................................................................... 65
Installing Other Pharos Services ............................................................................................................. 66
Before You Begin ................................................................................................................................. 66
Installing Print Service, SignUp Service, EDI Service and Web Services.............................................. 66
Configuring the Print Server and SignUp Server as Cluster Resources ............................................... 67
Validating the Installation ................................................................................................................... 67
Configuring Web Components ............................................................................................................ 68
SSL Certificates .................................................................................................................................... 69
Installing SignUp Clients ...................................................................................................... 70
Command Line Options........................................................................................................................... 71
After installing a SignUp client: ........................................................................................................... 71
Installing Popup Clients ....................................................................................................... 73
Pre-requisites .......................................................................................................................................... 73
Creating Install Packages ........................................................................................................................ 73
Specifying the global properties of the Install Package ...................................................................... 74
Adding Optional Custom Modules ...................................................................................................... 74
Adding Package Definitions ................................................................................................................ 74
Building Packages ................................................................................................................................ 74
Deploying Install Packages ...................................................................................................................... 74
Installing Pharos Stations .................................................................................................... 76
Pre-requisites .......................................................................................................................................... 76
Before You Begin..................................................................................................................................... 76
Installing the Pharos Station ................................................................................................................... 76
Command Line Options........................................................................................................................... 77
Installing Pharos Remote ..................................................................................................... 78
5
Planning and Installation Guide
Pre-requisites .......................................................................................................................................... 78
Installing Pharos Remote ........................................................................................................................ 78
Installing Pharos Reports ..................................................................................................... 79
Installing Pharos Print Center .............................................................................................. 80
Installing the Print Center Web .............................................................................................................. 80
Pre-requisites ...................................................................................................................................... 80
Installing the Print Center Services (Pharos API) .................................................................................... 80
Pre-requisites ...................................................................................................................................... 80
Setting up SSL ...................................................................................................................... 82
When to Use SSL ..................................................................................................................................... 82
Setting up Encryption.............................................................................................................................. 82
Installing the Pharos CA Certificate .................................................................................................... 82
Requesting a Server Certificate........................................................................................................... 83
Installing the Server Certificate........................................................................................................... 85
Directing the System to Use SSL ......................................................................................................... 86
Supporting Legacy EDI Addresses in IIS7............................................................................... 87
Changing the Application Pool ................................................................................................................ 87
Step 1- Enable the URLRewriteModule .............................................................................................. 87
Step 2 -Change the Application Pool .................................................................................................. 88
Step 3- Test Connection ...................................................................................................................... 88
Moving the EDI Server to a separate application pool ........................................................................... 89
Creating an application pool ............................................................................................................... 89
Moving the Pharos EDI to the created application pool ..................................................................... 89
Uninstalling ......................................................................................................................... 90
6
Planning and Installation Guide
Introduction
Introduction
About This Document
This document covers the process of installing the Pharos Uniprint® Suite (also called the Pharos
Solution Suite). It provides information on determining the number of servers required and how to
prepare these servers for installation. This document also covers post-install operations such as
uninstalling and setting up SSL encryption.
Other Documentation
Other documents are available covering different aspects of the Uniprint Suite. For a complete list of the
available documentation, please refer to the “Uniprint Available Documentation” document.
Getting Help
Below is a list of options for obtaining support in the event you have questions or encounter issues
during or after the installation of the Pharos Uniprint Suite.
Pharos Website
The Pharos website (www.pharos.com) contains information about Pharos products, including product
updates, fixes and firmware releases. It also includes the Pharos Knowledge Base, which provides a
comprehensive source of solutions and workarounds to known problems and issues. The Knowledge
Base is updated often to ensure that it always contains the latest information.
Contact Details
Corporate Headquarters
Phone:
US/Canada)
888-864-7768 (toll free
Post-Sales Technical Assistance
Email:
support@pharos.com
North America:
(585) 939-7000
(877) 848 0397 (toll free)
Fax:
(585) 249-9229
(585) 939-7099
Address:
Suite 310
80 Linden Oaks
Rochester, New York 14625
United States of America
Australia/New Zealand:
+64 9 523 0737
Rest of the world:
+1 (585) 939-7099
7
Planning and Installation Guide
Pharos Uniprint Suite Overview
Pharos Uniprint Suite Overview
The Pharos Uniprint® Suite allows you to manage, control and account for a range of networked
resources. In addition to the core software products, Pharos Uniprint® Suite also offers a comprehensive
range of applications that provide additional capabilities and features, including Secure Release Here
and Informed Print.
This section provides a brief description of each of the Pharos Uniprint Suite core software products
included in the Pharos Uniprint Suite and the Uniprint applications.
Pharos Uniprint® Suite Core Products
The Pharos Uniprint Suite, also called the Pharos Solution Suite, is a collection of software products
consisting of:



Pharos Uniprint®
Pharos Off-The-Glass®
Pharos SignUp
All three products store information in a common core of accounting and database software. This allows
all of them to work as a single and tightly integrated system.
Pharos Uniprint®
Uniprint is a print accounting and management software product that allows you to monitor and
account for network printer use. Uniprint ensures that only permitted users can access printing
resources and charges users based on how they are using them.
Pharos Off-The-Glass®
Pharos Off-The-Glass allows control over the use of photocopiers and multi-function devices (MFDs).
Like Uniprint, Off-The-Glass ensures that only permitted users can access copying resources and charges
users based on how they are using them.
Pharos SignUp
Pharos SignUp is a system for reserving the use of public access computers. A user can reserve a
computer for a particular date/time or join a virtual queue to wait for an available computer. SignUp
ensures fair access to computers without any staff interaction.
8
Planning and Installation Guide
Pharos Uniprint Suite Overview
Pharos Uniprint Applications
Uniprint also offers a range of applications that provide additional capabilities and features.
Secure Release Here®
Secure Release Here is a Uniprint application that controls the release of print jobs sent from
workstations to printing devices, allowing for improved security when printing to shared, network
devices. In addition, users experience the convenience of being able to collect their documents from any
devices that have been grouped together. Secure Release Here® addresses network device issues, such
as lack of security and excessive waste.
Informed Print
Informed Print is a Uniprint application that allows you to notify each user of the cost of each print job
at the time it is printed, by displaying a message on the user’s workstation. This message informs the
user of the cost of their job, and optionally asks them if they wish to proceed with printing it.
Third-Party Charging
Third-Party Charging is a Uniprint and Off-The-Glass application that allows users to assign the cost of
their print and copy activities to a particular department, budget center, grant number, etc. For
example, when a user attempts to release their print job at the device, they are prompted to select the
budget center to associate that print job with.
Third-Party Charging requires a network terminal or iMFP that supports cost center billing; please
contact Pharos Systems for more information.
Pharos Print Center
Pharos Print Center provides a convenient way to release documents. The Pharos Print Center that
comes standard with Uniprint 9.0 allows users to manage their printing and their accounts. For example,
it allows users to:






Release print jobs sent via Pharos Queues and Popups, including password protected jobs.
Check available balance/funds.
View activity history.
Delete print jobs.
Create guest accounts.
Charge their print jobs to Third Party Charging (i.e. Cost Centers, Grants).
MobilePrint
Pharos MobilePrint is an application that allows users to print from their mobile devices to any
MobilePrint enabled printers within the campus. Users print by simply sending or forwarding an email
9
Planning and Installation Guide
Pharos Uniprint Suite Overview
(with the document to print as a file attachment) to the email address set up for MobilePrint (e.g.
print@university.edu). Once authorized, users receive a reply email showing them a list of documents
that are ready for release. The users can then release their documents from any Pharos Release Station.
Pharos Terminal, or from a web browser via the Pharos Print Center website. For more information
about MobilePrint, please contact your authorized Pharos reseller or Pharos Support.
Credit Card Gateway
Credit Card Gateway is a Uniprint application that allows users to add funds to their Pharos accounts
from the Pharos Print Center using a credit card, a debit card, or a PayPal account.
For more information on Credit Card Gateway, please refer to the “TechNote Pharos Print Center Credit
Card Gateway” document.
10
Planning and Installation Guide
Planning Your Installation
Planning Your Installation
The process of installing and setting up the Pharos Uniprint Suite is straightforward, but as with any
enterprise solution, pre-installation planning is critical. Before you begin your installation, it is important
to understand the various components of a Pharos Uniprint system to help you decide how to best
deploy the software to meet your requirements.
Uniprint Suite Components
A Uniprint system uses a multi-level architecture consisting of several cooperating components,
including server, client, administrative, and web components.
Server Components
Server Components
Pharos Database
Description
The Pharos Database is central to all Pharos products - all
configuration and transaction data information is stored
here.
The core group of services required for all Uniprint Suite
installations. These services include:
Principal Services




Pharos Database Server
Pharos License Server
Pharos Online Services
Pharos Logging Service
These components must be installed on a server machine.
Print Services comprise the following four services.

Print Services
Print Server – The component that handles costing
and billing of print jobs. It also controls copyrelated processes.
 Secure Release Service –The component that
controls print-related services (e.g. secure job
storage, retrieval, release).
 Popup Server – The component that determines
which Questions to display to users.
 LPD Server – The components that processes print
jobs via the LPR protocol.
Print Services must be installed on a server machine. It
may be installed on the same machine as the Principal
Services.
11
Planning and Installation Guide
Planning Your Installation
Server Components
SignUp Services
EDI Service
Description
The component that implements the tracking and
reservation process for a specified group of computers.
The SignUp Service controls the SignUp Clients installed on
these computers.
The External Device Interface (EDI) Service provides a
suitable protocol for approved, external devices and
integrations to connect to the Uniprint Suite installation.
Pharos Network Terminals and Pharos iMFPs require the
Pharos EDI.
Web Services consist of the SignUp Web Components
(Queue Station and Nerve Center) and Uniprint Website.
These are installed on a central web server running
Microsoft Internet Information Server.
Web Services
The SignUp Web Components allows staff members to
monitor the computer reservation system.
The Uniprint Website allows users to find available
printers and download the necessary software to access
these print devices.
It consists of the following components:
Print Center Services (Pharos
API)

Pharos Rest API - This component allows PayPal to
be connected with the Pharos system. It also
enables communication between the Print Center
website and Print Services.

Pharos PayPal IPN Processor – This service is
responsible for processing approved PayPal
transactions. It will credit the Pharos user
accounts based on the details provided by PayPal.
Client Components
Client Components
Pharos Popup Client
Description
The Popup Client is an application that is activated every
time a user prints a document from their workstation to a
Uniprint controlled output device. The Popup Client can
then request additional information from the user, e.g.
12
Planning and Installation Guide
Planning Your Installation
Client Components
Description
authentication credentials. This is useful for sites where
users are not required to authenticate on the workstation
itself.
The Popup Client also incorporates the Pharos Notify
component. Notify allows a Uniprint server to send
messages back to the user at the workstation. These
messages may simply be information based or prompt the
user for additional information.
Pharos SignUp Client
The SignUp Client is installed on each computer that will be
managed by SignUp. It enforces access permissions,
reservations, and reservation durations as part of SignUp.
Pharos Station
Pharos Stations are dedicated user stations that allow endusers to (1) collect and pay for printing, (2) manage their
account, and (3) create and manage computer
reservations.
Administrative Components
Administrative
Components
Description
The Pharos Administrator is the main user interface used to
configure, manage and maintain the Pharos system.
Pharos Administrator
Pharos Remote
Pharos Reports
Pharos Administrator is installed with all Pharos Services,
but it can also be installed standalone for remote
management of the Pharos system.
Pharos Remote is an Administrative Component that allows
the Administrator, Cashiers and Proctors to remotely
manage certain aspects related to print jobs and user
accounts.
A component that installs independently of Pharos
Administrator and offers statistical reporting, auditing, and
data exporting capabilities.
To run Reports, you must have a role of Proctor, Cashier, or
Administrator.
13
Planning and Installation Guide
Planning Your Installation
Web Components
Web Components
Description
Pharos Nerve Center
Pharos Nerve Center is a web application used to manage
Pharos SignUp. It allows onsite staff to check on the status
of users, computers, reservation queues and active
sessions, as well as performing various administration
functions.
Uniprint Website
The Uniprint Website is a template web site that allows
users to find and connect to Uniprint-managed output
devices without any staff involvement.
It provides access to Install Packages that users can
download to install printers and Popup Client components
on their computers.
This is the website component that allows users to release
print jobs from laptops and traditional desktops to any
Pharos controlled device.
Print Center Web
This can be extended by integrating the standard Print
Center web with MobilePrint 2.0. When the Print Center is
integrated with MobilePrint, users will be able to upload
documents via the Print Center, send jobs to Print Center
via email, and change finishing/print options before
releasing print jobs.
Other Components
Other Components
Network Terminal
Description
A hardware device that provides the necessary user
interface at the output device. Users can use this device to
supply authentication credentials (e.g.
username/password, proximity card), view their print jobs
available for release, and use the copy function of an MFD.
Examples of Network Terminals are Omega PS60 and
Omega PS200.
Integrated MFP (iMFP)
Offering similar functions as a network terminal, the iMFP
is a software component that can be installed directly on
select output devices, normally without any additional
external hardware.
14
Planning and Installation Guide
Planning Your Installation
Which Pharos Server Components to Install?
Not all server components are required for all installations. You will need to install different
combinations of the components depending on the Pharos software product or application you want.
The following table shows both the essential and the optional components that you need to install for
each of the Uniprint Suite core software products and Uniprint applications:
Product/Application
Components

Pharos Database
Uniprint

Principal Services
(including Secure Release Here®,
Informed Print and Third Party
Charging)

Print Services

EDI Service

Web Services (optional)

Pharos Database

Principal Services

Print Services

EDI Service

Pharos Database

Principal Services

SignUp Services

Web Services (optional)

Pharos Database

Principal Services

Print Services

Print Center Services (Pharos API)

Pharos Database

Principal Services

Print Services

Print Center Web

Print Center Services (Pharos API)
Off-The-Glass
SignUp
MobilePrint
Pharos Print Center
15
Planning and Installation Guide
Planning Your Installation
Sizing Your Installation
Before beginning your installation, it is important to determine how many servers are required to
manage the expected load in your environment. This section provides guidelines to help you determine
this and also includes the recommended hardware specifications of the servers.
Your Environment
First, you must select an appropriate size category based on your environment. The size category helps
you to quickly determine when a single server is sufficient or when Pharos services must be split across
multiple servers. You must select the largest category that applies to your environment, e.g. if you have
50 printers (size category – Medium) and 70,000 students (size category – Large), you must base your
planning on the “Large” size category.
Once you have determined the size category of your environment, you can establish the base number of
servers required. Use the following table as a general guideline to determine your environment’s size
category and the number of base servers needed.
Size Category
Environment
Number of Servers
A small environment is defined as having all of
the following characteristics:

20 or fewer output devices (i.e. printers
and MFPs)

Fewer than 10,000 full-time equivalent
students

Fewer than 300 SignUp Client computers
Small
A medium-sized environment is defined as having
one or more of the following characteristics:

50 – 100 output devices (i.e. printers and
MFPs)

10,000 – 50,000 full-time equivalent
students

300 – 500 SignUp Client computers
Medium
A single server can be used for
all Pharos services
1 server for SQL Server,
Pharos Database and Pharos
Principal Services
1 server for all other services
(including Print Services and
SignUp Services)
16
Planning and Installation Guide
Size Category
Planning Your Installation
Environment
A large environment is defined as having one or
more of the following characteristics:
Large

100+ output devices (i.e. printers and
MFPs)

50,000 + full time equivalent students

500 – 2,500 SignUp Client computers
Number of Servers
1 server for SQL Server, the
Pharos Database, and Pharos
Principal Services
1 or more servers –for all
other services refer to the
“Number of Uniprint Print
Servers” and “Number of
SignUp Servers” sections
below.
Number of Servers
The following section provides information in determining the number of Uniprint Print Servers and
SignUp Servers needed.
Number of Uniprint Print Servers
The number of Uniprint Print Servers required depends on the size of your deployment and the
application(s) that you are running. For example, the Secure Release Here™ application places a greater
load on your print server than SignUp. The main factor to consider when sizing organizations running
Secure Release application is the printing volume across the site.
In addition, the performance of your print server will be affected by the following factors:





The number of print server clients connecting to the server (e.g. Pharos Remote, Pharos
Stations, Popups, etc.)
The types of print jobs sent to the print server (e.g. graphics, text)
The size of the print jobs, which will depend on whether they are PCL or Postscript, graphics or
text
The number and type of Devices and Release Stations served by the print server
The types of print drivers each printer uses
A single dedicated Uniprint Print Server supports a maximum sustained rate of 10,000 jobs/hour. This
figure is based on the following assumptions:


The average print job submitted to the print server contains 1 page with limited graphics, is not
complex (i.e. the graphic images are not complex), and uses PostScript.
An average of 1 print job per user per hour.
The number of print servers is determined based on the number of users, their typical print activity in an
hour, and the maximum number of jobs that a print server can hold.
Therefore, for a site that expects to process 50,000 print jobs/hour for example, at least five (5)
Uniprint Print Servers are required.
17
Planning and Installation Guide
Planning Your Installation
If a single Uniprint Print Server is processing more than 10,000 jobs per hour, you may find that there is
a significant decrease in its performance. This can be due to a number of factors that affect the capacity
of the print server, including, but not limited to:




High Sustained Rate of Print Job Submission: When print jobs are submitted consistently above
the rate of 10,000 jobs per hour, the processing demand on the server increases dramatically.
This may also apply if the server consistently experiences high peak job submission rates for
extended periods of time.
Complex Print jobs: Complex print jobs such as those containing graphics place extra load on
the print server.
Number of Release Stations: In a Secure Release printing environment, Release Stations are
used to view jobs sitting in Print Groups, and to release these print jobs to the printers. The
Release Station interacts with the Print Server requesting information such as the list of print
jobs, the cost and details of a selected print job, information about the user, and so on. Each
request places a load on the Print Server. A single print server can support approximately 200
terminals (i.e. MFPs, Omegas).
Type of Release Stations: Certain types of Release Stations are controlled by services on the
server itself. Due to this, these devices can place significant extra load on the server.
Number of SignUp Servers
The number of required SignUp Servers is typically based on the number of SignUp Clients. A single,
dedicated SignUp Server can support a maximum of 500 SignUp Clients.
Database Sizing
The Pharos Database is used to store configuration, user, costing, and activity data. To determine the
minimum storage space required for the Pharos Database, first determine the following:



The number of users accounts that will be stored in the Pharos Database
The average number of transactions you expect per day multiplied by the number of months
that you will keep these transactions for reporting purposes
The number of cost centers (for Third Party Charging) that will be stored in the Pharos Database
(if any exists)
Then use the following formula to determine the required database storage space:
Storage Required (KB) = 2KB per user account + 0.5 KB per transaction + 1KB per Cost Center +
102,400 KB system overhead (configuration data, alerts, etc.) + Log Size
Take into consideration the following factors:

The amount of space for indexes – a factor of 2
18
Planning and Installation Guide

Planning Your Installation
Logsize/Datasize – i.e. how much SQL Server log is required for a given amount of data? By
saying 1/3, we are saying that whatever the size of the data, allocate another 1/3 of that size for
the log space.
System Requirements
Once you have determined the number of required servers, you must ensure that your environment
meets the hardware and software requirements for installation. This section describes the hardware,
software, and database requirements as well as other pre-requisites for the Uniprint Suite components.
Pharos Server Components Requirements
The following sections list the hardware and software requirements for the Pharos server (Pharos
Database, Principal Services, Print Services, SignUp Services, EDI Service, and Web Services)
components.
Hardware Specifications
The system requirements vary for each installation. The requirements depend on a number of factors,
such as the number of servers, the number of Pharos services installed on each server, and the number
of resources managed by each server. This section provides the minimum hardware requirements based
on typical server configurations.
Example
A site has 10,000 students, generating 5,000 print jobs per day, and wants to keep 12 months’
worth of data, how much disk space will they need?
Storage Required = (10,000 x 2KB) + (5,000 x 365 days x 0.5KB x 2) + 102,400 KB = 1900MB
Logs = 1900 x 1/3 = 633 MB
Altogether they will need about 2500 MB (or 2.5 GB) of disk space for the Uniprint database.
Note: Set aside extra disk space, including logs to allow for future growth and to ensure your
database never runs out of space. If, as in the above example, 2500 MB is recommended for data
storage, we suggest allowing up to 4GB of disk space for the Database.
Single Server running all Pharos Services
The minimum requirements for a single server running all Pharos Services:
19
Planning and Installation Guide
Component
CPU
Planning Your Installation
Single Server running all Services
2 or more processors
4 GB RAM (Microsoft® SQL Server is on the same server).
Memory
If running newer versions of operating systems, such as Windows
Server 2012 R2, Pharos recommends 8 GB of RAM,
Program Files(x86) – 246 MB
Disk space
Database – For a site with 10,000 students generating 5,000
transactions per day (keeping 12 months’ worth of data), the
Database requires approximately 4GB of disk space.
Application Data – For a site generating 5,000 transactions per day
and running Secure Release Here® only, the Application Data
folder needs approximately 3 GB of disk space. Refer to the
examples on the next page.
The disk space requirements are broken down into three key parts:

Program Files – The Pharos Uniprint® software (with all the components installed) is about 246
MB. Therefore allowing 300 MB for software disk space will suffice.

Database – The Pharos Database is used to store configuration, user, transaction, billing, etc.
For information about how to determine the Database size for a site, refer to the “Database
Sizing” section on page 18.

Application Data – The Application Data directory(on every Uniprint Print Server) stores the
following information:
o
o
o
o
Secure Release SQLite Database
Plug-ins (e.g. MobilePrint Plugin files)
Spool Files, including spool files when Page Counter fails
Asset Management rules file
Secure print jobs are temporarily stored in the Application Data directory (location depends on
the path defined during Print Service install) before being released or before expiry. Therefore,
the Print Server needs to have sufficient disk space to hold these jobs. The amount of disk space
required for the spool files depends on a number of factors:
o
o
o
The print volume
The size of each print job (e.g. graphics or text, PCL or Postscript)
The length of time the jobs are held in the Application Data before being printed or
expired. Print jobs that are immediately released are only held in the Application Data
directory for a short period of time. Uniprint performs a maintenance task every hour to
delete expired print jobs.
20
Planning and Installation Guide
o
Planning Your Installation
The type(s) of application running (e.g. Secure Release Here®, SignUp) also affects the
space required. For example, Secure Release Here will require more spooling space than
direct printing or SignUp.
Example 1:
If a site generates 5,000 print jobs per day, and is running Secure Release Here, how much disk
space will they need? The following example assumes that the size per job is 5KB. PCL graphics jobs
may range from 20KB to 100KB.
Spool File = (5,000 x 5KB) = 25 MB of spool space (jobs are deleted as soon as they are
released)
SQLite Database = 1 GB
A conservative recommendation for this site, i.e. one that allows for peaky volumes, is to allocate 3
GB for the Application Data.
Example 2:
If a site generates 5000 print jobs per day, and is running Secure Release Here, how much disk space
will they need? The following example assumes that the size per job is 100KB.
Spool File = (5,000 x 100KB) = approximately 500 MB of spool space (jobs are deleted as soon as
they are released)
SQLite Database = 2 GB
Allocate 4 to 5 GB for the Application Data for this site.
Principal Server (with SQL) and Separate Print Servers
The following section provides minimum requirements for configuration with one Principal Server and
dedicated Print Servers. For Print Servers that will be handling larger loads (particularly large complex
print jobs):
21
Planning and Installation Guide
Component
CPU
Planning Your Installation
Principal Server (with SQL Server)
2 or more processors
Print Server
Quad Core processor
4 GB RAM (Microsoft® SQL Server is
on the same server)
Memory
Disk space
If running newer versions of
operating systems, such as Windows
Server 2012 R2, Pharos recommends
8 GB of RAM,
3+ GB RAM
Program Files – Allow 200MB for
software disk space
Program Files(x86) – Allow 300 MB for
software disk space.
Database – Refer to the “Database
Sizing” section on page 18.
Application Data – On a site generating
5,000 print jobs per day, allow 5GB of
spool space. Refer to the examples on
page 18.
General Recommendations when planning for disk space
Consider the following recommendations when planning for disk space



On a single server configuration, keep all the Pharos software and components on the C:\ drive
if possible and then set up a separate disk (e.g. D:\ drive) for the following:
o Database
o Application Data
o Log files (including IIS)
In general, increasing the amount of memory will not affect performance of the Pharos
components. However, if a server is also running Microsoft SQL Server, additional RAM may
improve the database processing time.
For optimum server performance, Pharos highly recommends using two separate physical hard
disks – one for the Windows spooler and the other for the Application Data folder (Secure
Release Job Store).
Database Requirements
The Pharos Database requires a database engine. The following database engines are supported:
Requirements
SQL Server

Microsoft® SQL Server 2012

Microsoft® SQL Server 2008 R2

Microsoft® SQL Server 2008
22
Planning and Installation Guide

Planning Your Installation
Microsoft® SQL Server 2005
All editions are supported including SQL Express, but Express is
recommended only for demo installations and limited pilots.
Pharos recommends using the most recent version of SQL Server supported by the host OS, with the
latest service pack applied.
Operating Systems Requirements
The following table lists the software requirements for the Pharos server components installed on a
standard server (i.e. not clustered). For clustering requirements, refer to the “Installing Server
Components on a Cluster” section on page 61.
Operating System
Edition
32-bit
support
64-bit
support
Windows Server 2012 R2
Standard, Enterprise
NA
Yes
Windows Server 2012
Standard, Enterprise
NA
Yes
Windows Server 2008 R2
Standard, Enterprise
NA
Yes
Windows Server 2008
Standard, Enterprise
Yes
Yes
Business, Enterprise, Ultimate
Yes
Yes
Windows 7
Enterprise, Professional, Ultimate
Yes
Yes
Windows 8
Windows 8 (Basic), Pro,
Enterprise
Yes
Yes
Windows 8.1 (Basic), Pro,
Enterprise
Yes
Yes
Windows Vista
Windows 8.1
Pre-requisites
Ensure that the following pre-requisites are installed before installing the Uniprint Suite server
components.
Pre-requisites
Microsoft® Windows
Installer 3.1 or later
Description
Windows Installer 3.1 or later is required by the .NET Framework
4.0. Windows Installer 3.1 is available on the Pharos disk at
common\win32\DotNETFramework or it can be downloaded
from Microsoft’s website.
23
Planning and Installation Guide
Planning Your Installation
Pre-requisites
Description
The Microsoft .NET Framework should be present on any
computer running Pharos Administrator, Pharos Remote, Pharos
Station, Pharos Reports or any Pharos Server (e.g. Principal
Server, Print Server, EDI Server, Pharos Print Center
Services(Pharos API), and web server running Pharos Web
Components).



All Pharos services require of Microsoft® .NET
Framework 4.0. (Microsoft .NET Framework 4.5 is also
suitable.)
Any computer running Pharos Print Center Services
requires Microsoft® .NET Framework 4.5, plus ASP.NET
Any computer running EDI Server on Microsoft®
Windows Server 2012 also requires ASP.NET 4.5
Notes:

Installers for the .NET Framework and Windows Installer
3.1 (required by .NET 4.0) are available on the Pharos
disk image at common\win32\DotNETFramework. You
must install the Windows Installer first, then the .NET
Framework.

ASP.NET is not installed by default. It can be installed
through the “Add Roles and Features” wizard of the
Server Manager interface.
Microsoft® .NET
Framework 4.0, and 4.5
WARNING! If .NET Framework version 3.5 happens to be
installed following the install of .NET 4.0 or 4.5, the EDI and the
Pharos Print Center Services (Pharos API) may not start.
The following error is returned Could not load type
'System.ServiceModel.Activation.HttpModule' from assembly
'System.ServiceModel, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089'.
On Windows Server 2008, it could happen when you install .NET
3.x framework or IIS 7.5 with Activation features after .NET
framework 4.x is installed. However, on Windows Server 2012, it
always happens when you install .NET framework 3.x with
Activation features.
Microsoft Management
Console(MMC) 3.0 or later
Pharos Administrator and Pharos Remote require Microsoft
Management Console 3.0 or later. MMC is available on the
Pharos disk image at common\win32\MMC or it can be
downloaded from Microsoft’s website.
24
Planning and Installation Guide
Planning Your Installation
Additional Pre-requisite for Pharos EDI Services, Pharos Print Center , and Pharos Web
Components
Pre-requisites
Description
The following Pharos components require Microsoft Internet
Information Services.
Microsoft Internet
Information Services (IIS)
6.0 or later

Pharos EDI service

Pharos Web Components

Pharos Print Center Web

Pharos Print Center Services (Pharos API)
Note:
Windows Server 2008, Windows Server 2008 R2,
Windows Server 2012, and Windows Server 2012 R2
come with IIS7 7.0. However, IIS is not installed by
default. Please refer to the additional pre-requisites
for these operating systems below.
Additional Pre-requisites for Windows Server 2008, Windows 2008 R2, Windows
Server 2012, or Windows Server 2012 R2
If you are installing Pharos Uniprint on Windows Server 2008, Windows Server 2008 R2, Windows Server
2012, or Windows Server 2012 R2, you also need to install the following pre-requisites in addition to the
standard pre-requisites.


Install the IIS 7.0 Manager (if it is not already installed), by adding "Web Server (IIS)" Role from
the Server Manager.
After adding the "Web Server (IIS) Role, you must add the following "Role Services" for Uniprint
to work with IIS 7.0.
Operating System
Role Services


Windows Server 2008,
Windows Server 2008 R2

Common HTTP Features
o Static Content
Application Development
o ASP .NET
o .NET Extensibility
o ASP
o ISAPI Extensions
o ISAPI Filters
Management Tools
25
Planning and Installation Guide
Planning Your Installation
o
o
o
o

Windows Server 2012,
Windows Server 2012 R2

IIS Management Console
IIS Management Scripts and Tools
Management Service
IIS6 Management Compatibility (including all
components under this tree).
Web Server (IIS)
o Common HTTP Features
 Static Content (not required for EDI server)
 Default Document
o Security
o Application Development
 Web Services and Print Center Web require
ASP
 EDI Service requires ASP .NET 4.5
 Print Center Web requires ASP.NET 4.5 and
.NET Extensibility 4.5
 ISAPI Extensions (Must be included for ASP and
ASP.NET 4.5)
 ISAPI Filters (Must be included for ASP.NET 4.5)
Management Tools
o IIS Management Console
o IIS 6 Management Compatibility (required for IIS 6
Scripting Tools)
o IIS 6 Scripting Tools (required for IIS 6 Scripting Tools)
Administrative Components Requirements
The following table lists the hardware and software requirements for the Uniprint Suite administrative
components (Pharos Administrator, Pharos Remote, Pharos Station, and Pharos Reports).
Hardware Specifications
Hardware Requirements
CPU
Pentium compatible processor or higher
Memory
RAM and disk space as required by the operating system
Disk Space
RAM and disk space as required by the operating system
26
Planning and Installation Guide
Planning Your Installation
Operating Systems Requirements
Operating System
Edition
32-bit
support
64-bit
support
Windows Server 2012 R2
Standard, Enterprise
NA1
Yes
Windows Server 2012
Standard, Enterprise
NA2
Yes
Windows Server 2008 R2
Standard, Enterprise
NA
Yes
Windows Server 2008
Standard, Enterprise
Yes
Yes
Windows Vista
Business, Enterprise, Ultimate
Yes
Yes
Windows 7
Enterprise, Professional, Ultimate
Yes
Yes
Windows 8
Windows 8 (Basic), Pro,
Enterprise
Yes
Yes
Windows 8.1
Windows 8 (Basic), Pro,
Enterprise
Yes
Yes
Pre-requisites
Ensure that the following pre-requisites are installed before installing the administrative components.
Pre-requisites
1
2
Description
Microsoft® Windows
Installer 3.1 or later
Windows Installer 3.1 or later is required by the .NET
Framework. It is available on the Pharos disk at
common\win32\DotNETFramework or it can be downloaded
from Microsoft’s website.
Microsoft Management
Console(MMC) 3.0 or later
Pharos Administrator and Pharos Remote require Microsoft
Management Console 3.0 or later. MMC is available on the
Pharos disk image at common\win32\MMC or it can be
downloaded from Microsoft’s website.
Windows Server 2012, Windows Server 2012 R2, and Windows Server 2008 R2 are 64-bit only.
Windows Server 2012, Windows Server 2012 R2, and Windows Server 2008 R2 are 64-bit only.
27
Planning and Installation Guide
Planning Your Installation
Pre-requisites
Description
Microsoft .NET Framework 4.0 should be present on any
computer running Pharos Administrator, Pharos Remote,
Pharos Station, and Pharos Reports.
Microsoft® .NET
Framework 4.0
Client Components Requirements
Hardware Specifications
The following table lists the hardware requirements for all the Uniprint Suite client components. Client
components include the Popup Client and SignUp Client.
Hardware Requirements
CPU
Pentium compatible processor or higher
Memory
RAM and disk space as required by the operating system
Disk Space
RAM and disk space as required by the operating system
Supported Popup Client Platforms
The Popup Client supports the following platforms:
Operating System
Edition
32-bit
support
64-bit
support
Windows Server 2012 R2
Standard, Enterprise
NA
Yes
Windows Server 2012
Standard, Enterprise
NA
Yes
Windows Server 2008 R2
Standard, Enterprise
NA
Yes
Windows Server 2008
Standard, Enterprise
Yes
Yes
28
Planning and Installation Guide
Planning Your Installation
Operating System
Edition
32-bit
support
64-bit
support
Windows Vista
Home Basic, Home Premium,
Business, Enterprise, Ultimate
Yes
Yes
Windows 7
Enterprise, Professional, Ultimate
Yes
Yes
Windows 8
Windows 8 (Basic), Pro,
Enterprise
Yes
Yes
Windows 8.1
Windows 8 (Basic), Pro,
Enterprise
Yes
Yes
Mac OS X
10.6 - 10.8
NA
NA
32-bit
support
64-bit
support
Supported SignUp Client Platforms
The SignUp Client supports the following platforms:
Operating System
Edition
Windows 8.1
Windows 8 (Basic), Pro,
Enterprise
Yes
Yes
Windows 8
Windows 8 (Basic), Pro,
Enterprise
Yes
Yes
Windows 7
Home Basic, Home Premium,
Business, Enterprise,
Professional, Ultimate
Yes
Yes
Windows Vista
Home Basic, Home Premium,
Business, Enterprise, Ultimate
Yes
Yes
Mac OS X
10.6 - 10.8
NA
NA
Note: Support for client components (Pharos Station, Popup, SignUP Client) on Windows XP and
Windows Server 2003 is included to assist customers while they are in the process of updating to
operating systems currently supported by Microsoft. Pharos Remote is not supported on Windows XP or
Windows Server 2003.
29
Planning and Installation Guide
Planning Your Installation
TCP/IP Ports in Uniprint
The Pharos suite of products uses TCP/IP for all client/server communications. This section lists the ports
that the various Pharos components use by default, and discusses issues that arise when Pharos
components attempt to communicate through firewalls using these ports.
Default Ports
The following table summarizes the ports that the main Pharos components listen on. This information
can be viewed (and altered if necessary) in Pharos Administrator on the Network tab of the System >
System Settings context.
Component
Listening Port
Database Service
2355
Database Service Change Control port
28205
License Service
2352
Notify Service
28201
Pharos LPD Server
515
Popup Service
28203
Print Service
2353
Print Service Change Control port
28206
Pharos REST API Service
443
Secure Release Service (HTTP)
8080
Secure Release Service (Net. TCP)
808
SignUp Client
28202
SignUp Server
2351
SignUp Change Control Server
28207
30
Planning and Installation Guide
Planning Your Installation
Required Ports
Component
Protocol
Listening Port
LPR Communication
TCP
515
HTTP Communication
TCP
80 / 443
Microsoft SQL Server
TCP
1433
MS SQL Server Browser
UDP
1434
Optional Ports
Component
Protocol
Listening Port
Billing Gateways
TCP
2111
Logon Gateways
TCP
2222
Boscop VCC or VCA
TCP
1234 & 1235
The following table lists which Pharos Uniprint components communicate with each other using the
ports listed on page 30. The “Source” column represents the Uniprint component that initiates a
connection with the component in the “Target” column. Open these network ports to ensure proper
communication among the Pharos Uniprint components.
Principal Server
Source
Target
Protocol
Port
Database Service
Microsoft SQL Server
TCP
1433
Database Service
Microsoft SQL Server Browser
UDP
1434
31
Planning and Installation Guide
Planning Your Installation
Print Server
Popup Server, Print Server, Secure Release Service, and LPD Server
Source
Target
Protocol
Port
Popup Service
Database Service if the Print
Server is installed with the
Principal Server OR Database
Proxy Service if present
TCP
2355
Popup Service
Print Service
TCP
2353
Print Service
Database Service if the Print
Server is installed with the
Principal Server OR Database
Proxy Service if present
TCP
2355
Print Service
License Service
TCP
2352
Print Service
Pharos Notify on client PC
TCP
28201
Secure Release
Service
Print Service
TCP
8080
TCP
808
Secure Release
Service
Secure Release Service
(on other servers)
Secure Release
Service
Print Device (LPR)
TCP
515
Secure Release
Service
Print Device (SNMP)
UDP
161
Note: The Secure Release Service connects to instances of the Secure Release Service on other servers.
Database Proxy Server
The Database Proxy Service is installed only when Print Server is separate from the Principal Server.
Note: Every component that can be on the same computer as a Proxy Service can connect to that Proxy
Service (or the same computer) using any port that the component would use to connect to the
Database Server or the License Server.
32
Planning and Installation Guide
Planning Your Installation
Source
Target
Protocol
Port
Database Proxy Service
Database Service
TCP
2355 & 28205
Database Proxy Service
License Service
TCP
2352
EDI Server
The EDI Server is typically installed with the Print Server, but it can also be installed with the Principal
Server or a separate machine.
Source
Target
Protocol
Port
EDI Service
Database Service if it is on
the same machine as the EDI
Service, via the Database
Proxy Server otherwise
TCP
2355 & 28205
EDI Service
Print Service
TCP
2353
EDI Service
License Service
TCP
2352
EDI Service
SignUp Service
TCP
2351
Administrative Components
Pharos Administrator (MMC)
If the Pharos Administrator is installed separately, the following ports are needed for communication.
Source
Target
Protocol
Port
Pharos Administrator
Database Service
TCP
2355
Pharos Administrator
Print Service
TCP
2353
Pharos Administrator
License Service
TCP
2352
Pharos Administrator
SignUp Service
TCP
2351
Pharos Administrator
(Popup Client Tester)
Print Server (Popup Service)
TCP
28203
33
Planning and Installation Guide
Planning Your Installation
Source
Target
Protocol
Port
Pharos Administrator
(Print test page)
Print Device (LPR)
TCP
515
Pharos Administrator
Print Device (SNMP)
UDP
161
Source
Target
Protocol
Port
Pharos Remote
Database Service OR
Database Proxy Server if
present
TCP
2355
Pharos Remote
License Service
TCP
2352
Pharos Remote
Print Service
TCP
2353
Pharos Remote
SignUp Service
TCP
2351
Source
Target
Protocol
Port
Pharos Reports
Database Service OR
Database Proxy Server if
present
TCP
2355
Pharos Reports
License Service
TCP
2352
Pharos Reports
MS SQL Server
TCP
1433
Pharos Reports
MS SQL Server Browser
UDP
1434
Pharos Remote (MMC)
Pharos Reports
Pharos PC Station (Account, Print Release, Reservation)
Source
Target
Protocol
Port
Pharos Station
Database Service OR
Database Proxy Server if
TCP
2355 & 28205
34
Planning and Installation Guide
Planning Your Installation
Source
Target
Protocol
Port
present
Pharos Station
Print Service
TCP
2353
Pharos Station
License Service
TCP
2352
Pharos Station
SignUp Service
TCP
2351
Source
Target
Protocol
Port
SignUp Client
SignUp Service
TCP
2351
SignUp Client
SignUp Change Control Port
TCP
28207
SignUp Client
SignUp Client Listening
TCP
28202
Source
Target
Protocol
Port
Popup Client
Print Server (Popup Service)
TCP
28203
Popup Client
Print Server (LPD Service)
TCP
515
Client Components
SignUp Client
Popup Client
Other Server Components
SignUp Server
Source
Target
Protocol
Port
SignUp Server
Database Service OR Database
Proxy Server if present
TCP
2355 & 28205
SignUp Server
License Service
TCP
2352
35
Planning and Installation Guide
Planning Your Installation
Source
Target
Protocol
Port
SignUp Server
Pharos Notify (on Popup
Client)
TCP
28201
Source
Target
Protocol
Port
SignUp Nerve Center
Database Service OR
Database Proxy Server if
present
TCP
2355
SignUp Service
TCP
2351
SignUp Nerve Center
SignUp Nerve Center
The following diagram shows the communication ports needed for Pharos Uniprint, including other
Uniprint components (e.g. Gateways, SignUp, Popup). Take note that this is an example of a mediumlarge Uniprint site with a single server MobilePrint installation.
36
Planning and Installation Guide
Planning Your Installation
Windows Firewall
When Pharos is installed on a PC running the Windows Firewall, it automatically opens the ports for
Pharos client and server components as required.
Ports 80 and 443(if SSL has been configured) are not automatically opened by the Pharos installers, they
must be opened manually.
37
Planning and Installation Guide
Installation Overview
Installation Overview
The process of installing the Uniprint Suite differs depending on the product and applications that you
will be implementing. This section provides an overview of the installation process and includes
important details that you need to consider prior to installing.
Pharos server components are installed from the main product disk image. The installers use a common
install wizard for all components which gathers any required information and installs all files. For more
information, refer to the “Using the Installation Wizard” section on page 45.
Server Roles
In a Uniprint Suite install, server components are grouped based on a series of server roles. The
following server roles are available:
Role
Database
Includes
Pharos SQL Server Database
Pharos Database Server
Principal Services
Pharos License Server
Pharos Online Services
Pharos Logging Service
Pharos Print Server
Print Services
Pharos LPD Server
Pharos Popup Server
Pharos Systems Secure Release Service
SignUp Services
Pharos SignUp Server
EDI Service
Pharos EDI Server
Web Services
SignUp Web Components
Uniprint Web Components
Print Center Services
(Pharos API)
Pharos REST API
Pharos Print Center Web
Print Center Web
Additional Components
Pharos PayPal IPN Processor
Pharos Administrator
Pharos Reports
38
Planning and Installation Guide
Installation Overview
Typical Order of Installation
In general, server components are installed first, and then client and administrative components are
installed as necessary.
The following steps show the installation order:
1. Install the core server components
a. Install the Pharos Database. The Database must be installed first in any installation.
b. Install Principal Services. This may be on the same machine on which the Pharos
Database is installed.
2. Install other Pharos Services depending on the Uniprint Suite product and applications being
implemented.
3. Install Pharos client components and administrative components (as needed).
Additional components and applications may be required once the system is up and running - these can
be installed as necessary.
Important Installation Notes






When installing the Database or Principal Services roles, it is not possible to install other roles at
the same time. Other roles, such as Print Services, expect the core server components to already
be installed and running.
It is possible to install the Database and the Principal Services separately, e.g. the Database on a
dedicated SQL Server and the Principal Services on a server dedicated to the Pharos services.
Alternatively, all of the Database and Principal Services components can be installed on the
same server.
When installing the Pharos Database, the installer will connect to the SQL Server instance using
a TCP/IP socket connection. Ensure that the SQL Server accepts TCP/IP connections (i.e. the
TCP/IP network option is installed and enabled).
On SQL 2005 Express, the TCP/IP network option must be manually enabled before installing
Pharos. Enable TCP/IP from the SQL Server Surface Area Configuration tool.
For a smaller installation where the expected load can be handled by one server, all of the
Pharos server components can be installed on a single machine.
SQL Server must be installed with the “Mixed Authentication mode”. If it is already installed and
is set to “Windows Authentication mode” you must change it to Mixed Authentication instead.
Pharos Uniprint requires the built-in SQL Server system administrator account.
Installing Other Pharos Components
Pharos Server components are installed using the main installer found in the Pharos disk image. Client
components and administrative components are installed using different methods. In general, the client
and select administrative components are installed using self-contained install packages.
39
Planning and Installation Guide
Installation Overview
The following table gives you a brief overview of how to install other Pharos components:
Client Components
Other Pharos Components
SignUp Client
Installation Details
The SignUp Client has a self-contained install package,
which can be copied from the Pharos disk image and run
on SignUp Client computers.
For more information on how to install a SignUp Client,
refer to the “Installing SignUp Clients” section on page 70.
Popup Client
The Popup Client is installed using install packages, which
are created from Pharos Administrator.
For more information on how to install Popup Clients, refer
to the “Installing Popup Clients” section on page 73.
Administrative Components
Administrative
Components
Pharos Administrator
Installation Details
When installing any server component, the Pharos
Administrator is installed along with it. However, you can
install the Pharos Administrator standalone using the main
installers.
For more information, refer to the “Installing Uniprint Suite
Server Components” section on page 45.
Pharos Station
The Pharos Station has a self-contained install package
which can be copied from the Pharos disk image and run
on Pharos Station computers.
For more information on how to install Pharos Station,
refer to the “Installing Pharos Stations” section on page 78.
Pharos Remote
The Pharos Remote has a self-contained install package
which can be copied from the Pharos disk image and run
on computers.
For more information on how to install Pharos Remote,
refer to the “Installing Pharos Remote” section on page 78.
40
Planning and Installation Guide
Administrative
Components
Pharos Reports
Installation Overview
Installation Details
The Pharos Reports is installed using the main installers on
the Pharos disk image.
For more information on how to install Pharos Reports,
refer to the “Installing Pharos Reports” section on page 79.
Web Components
Web Components
Installation Details
The Pharos Print Center is installed using the main
installers on the Pharos disk image.
Pharos Print Center
For more information on how to install Pharos Print
Center, refer to the” Installing Pharos Print Center” section
on page 80.
Other Components
Component
Print Center Services (Pharos
API)
Installation Details
The Pharos Print Center Services is installed using the main
installers on the Pharos disk image.
For more information on how to install Pharos Print
Center, refer to the” Installing Pharos Print Center” section
on page 80.
41
Planning and Installation Guide
Installing Server Components
Installing Server Components
This section gives you instructions on how to install Pharos server components and provides important
installation details, including how to prepare your site
for installation.
Note: If you are installing the
Before starting the installation, review the Readme.htm
Uniprint Suite server components on
file that comes on the Pharos disk image. It contains
a cluster, please refer to the
additional information on software prerequisites,
“Installing Server Components on a
special scenarios, and known issues that might affect
Cluster” section.
how you proceed with your installation.
Pre-Installation Checklist
Before you install Pharos server components, you must complete several pre-installation tasks. The
following table outlines the pre-installation checks that you must perform and provides the details that
you need to complete these tasks.
General
Yes
Have you determined the appropriate use scenario for your site and understand
how you want your system to work?
If you are unsure, please contact Pharos Systems to discuss.
Do you have enough servers that meet the standard hardware and software
requirements for the Pharos server components?
Refer to the “Sizing Your Installation” section on page 16.
All Pharos Components
Servers are installed with a supported OS (2008, 2008 R2, 2012, or 2012 R2).
Refer to the “Operating Systems Requirements” section on page 23.
Servers have the latest service pack and hot-fixes applied.
Servers have TCP/IP v4
Name resolution works correctly for all servers.
Server names do NOT contain an underscore or any special characters.
Reference: http://support.microsoft.com/kb/101785
42
Planning and Installation Guide
Installing Server Components
Servers have Web Server (IIS) role installed. This is applicable to Windows Server
2008, 2008 R2, 2012, and 2012 R2.
Refer to the “Additional Pre-requisites for Windows Server 2008, Windows 2008 R2,
Windows Server 2012, or Windows Server 2012 R2” section on page 25 for more
information.
All Pharos Server components have .NET 4.0 installed.
The Pharos Print Center Web component has NET Framework 4.5, ASP, ASP.NET
4.5, .NET Extensibility 4.5, and IIS 6.0 or later.
The Pharos API has .NET Framework 4.5 and IIS 6.0 or later.
Servers are live on the network and are able to access the Internet with a web
browser.
Local Administrator account has been given to the Installation Engineer for all
Pharos servers.
Any security or anti-virus software is either disabled or will be disabled prior to the
installation.
Remote access (RDP and/or VPN) has been provided to the Installation Engineer.
DNS Entries (for forward and reverse lookup) have been implemented for every
Pharos server.
Pharos License key has been copied onto server or otherwise available (e.g. USB
flash drive).
The license key will be sent to you (usually by email) at the same time as the Pharos
disk image is supplied.
Pharos Uniprint installation media has been downloaded (e.g. Network share or USB
flash drive).
Network and client firewalls are disabled or will be disabled during the installation
and testing.
Refer to the “Error! Reference source not found.” section on page Error! Bookmark
not defined. for locking things down after the install has been completed.
SQL Server for Pharos (often installed on Pharos Principal Server)
Microsoft SQL Server 2005, 2008, 2008R2, or 2012 with the latest service pack.
NT and SQL (Mixed Mode) authentication is enabled.
43
Planning and Installation Guide
Installing Server Components
SQL Administrator (SA) account has been granted logon rights (SQL 2008 & 2008R2)
SQL Administrator (SA) account and password have been provided to the Installation
Engineer.
Network Libraries – Named Pipes, TCP/IP sockets, and Multi-Protocol are enabled.
SQL Server Agent service is set to start “Automatic”.
Print Servers for Uniprint (for small sites, all services are often installed together)
Every print server has printer drivers installed for all printing devices to be
controlled by Pharos.
Naming convention for Pharos print queues has been provided to the Installation
Engineer.
Naming convention for all “devices” and “release stations” has been provided to the
Installation Engineer.
Each Print Server has Printer Management role installed (Windows 2008 and 2008R2
only).
Printers
Each printer has an assigned static (or DHCP reserved) IP address.
Each printer is available on the network and able to receive print jobs via port 515
(LPR).
Pharos PC Release Stations (if used)
PCs are in place and ready for software installation.
Pharos iMFPs (if used)
All models are listed on the Pharos supported models web page.
All pre-requisites have been met per the specific iMFP documentation
Card Readers (if used)
Card Readers are onsite and configured (if applicable).
Test card(s) have been sent to Pharos for verification of card type and data
44
Planning and Installation Guide
Installing Server Components
Test cards (with funds) are available to the Installation Engineer (if applicable).
Data Import file is available to match user’s domain “Logon_ID” with their “Card_ID”
(if applicable).
Using the Installation Wizard
All server components are installed using a common installation wizard, which gathers configuration
details and installs the relevant files. The Pharos Installation Wizard is opened from the Pharos disk
image. All wizard screens use the same layout:
The installation wizard is also used for product upgrades—if the installer detects that the computer
already has older versions of Pharos components installed, it will switch to its upgrade mode. For more
information, refer to the “Uniprint Upgrade Guide”.
Use the Next button to progress forward through the
installation wizard. If you need to change details, use
the Back button to return to a previous screen. The
Cancel button allows you to exit the installer at any
time.
Note: Most properties set during
installation can be changed later
using the Pharos Administrator
application.
Installing Uniprint Suite Server Components
To begin the Uniprint server component installer:
45
Planning and Installation Guide
Installing Server Components
1. Access the Pharos disk image from computer on which you want to install the components.
2. If the installer does not start automatically (e.g. if you are accessing the disk image from a
network share), double-click on setup.exe from the root directory of the disk image. The Pharos
splash screen appears.
Main Installer Wizard Screens
The following screens are displayed during an install of the Pharos server components.
Welcome screen
Basic information about the Uniprint
Suite installer.
46
Planning and Installation Guide
Installing Server Components
Pharos Components
If any Pharos components are already
present on this computer, they will be
listed on this screen.
If no components are detected, this
screen is not displayed.
Click Next to continue.
Destination Directory
Click Browse if you want to specify a
different folder that Pharos files should
be installed to.
When the appropriate installation folder
has been selected, click Next to
continue.
Select Components
Select the server role(s) to install.
Highlighting a role displays information
about it in the lower half of the screen,
including a list of components installed
with the role.
Check the boxes for all server roles you
want to install and then click Next.
Note: Selecting “Additional
Components” leads to another
screen where you can select the
specific components you want to
install.
47
Planning and Installation Guide
Installing Server Components
Database Server TCP/IP Host Name and
Address
The screen is displayed when installing
roles other than Database or Principal
Services.
Enter the network name of the
computer that hosts the Pharos
Database Service (not Pharos Database)
and then click Next.
Start Installation (Principal Services and
Database)
This screen is displayed once the
installers have gathered all of the
information they need. A summary of
the components being installed is listed.
Click Start to begin the installation.
Start Installation (Print Services and
other Services)
This screen is displayed once the
installers have gathered all of the
information they need.
A summary of the components being
installed is listed.
Click Start to begin the installation.
48
Planning and Installation Guide
Installing Server Components
Finished Installation
This screen is displayed once the
installation is complete.
Click Finish to exit the installer.
Depending on which components were
installed, the computer may need to be
restarted to complete the installation. If
this is the case, a small dialog asking if
you want to restart the computer is
displayed. Click Yes to restart
immediately or No to return to Windows
and restart at a later point.
At this point, you have only installed the
Principal Services. A server restart is not
necessary here, nor will you be
prompted for the restart.
Component-Specific Screens
At this point, any screens specific to the components being installed are displayed. Component screens
are displayed in the order that the components are listed on the Select Components screen.
Refer to the Pharos Help for more information on the specific properties mentioned. If a component is
not mentioned below, it has no extra install wizard screens.
Pharos Principal Services and Database
SQL Server Name
Enter the name of the server that the
Pharos Database is installed on and click
Next.
You may enter the server name or the
fully qualified server name. If the
Database is not installed on the default
SQL instance, specify the instance name
(e.g. hostname\instancename).
49
Planning and Installation Guide
Installing Server Components
Pharos License Key Location
Click Browse to locate the registry file
containing your license information. Click
Next once you have specified the location
of the registry file.
License Agreement screen
The Uniprint End-User License is
displayed.
You must accept the terms of the license
and click Next to continue.
SQL Server Instance
Select the SQL Server on which Pharos
Database should be installed
If the SQL Server is running on your local
machine, the drop-down list shows the
name of the local SQL Server instance(s).
If the SQL Server is on a remote machine,
enter the instance name of the remote
SQL Server.
Click Next to continue.
50
Planning and Installation Guide
Installing Server Components
SQL System Administrator Logon
Enter the SQL Server administrator user
name and password and then click Next
to continue.
Note: Consult your SQL Server
administrator for the appropriate
logon details to use.
Database Connection
Note: This screen appears only when
installing the Database and Principal
Services on separate machines.
This screen shows important Pharos
Database connection information. Make
sure to keep a record of the following
database information:



Pharos Database Name
Pharos DBO User ID
Pharos DBO Password
You will need this information to install
Principal Services.
Click Next to continue.
Pharos Database
Note: This screen appears only when
installing the Database and Principal
Services on separate machines.
Enter the database name and database
logon details for the Pharos Database.
Then click Next to continue.
51
Planning and Installation Guide
Installing Server Components
Note: In a default install, the
database name and user name are
set to “pharos”.
In the Database Password field,
enter the password you copied from
the Database Information Screen
when you installed the Database.
Pharos Print Services
Application Data Directory
This screen appears only when installing
Print Services.
Confirm the location of the Application
Data Directory. This is where print jobs
will be stored temporarily. You can either
accept the default location or click
Browse to specify a different folder.
Note: The default location is the
Application Data folder (e.g.
C:\ProgramData on Windows Server
2008).
Click Next to continue.
The following Application Data folders are
created after install:

Database – holds the Secure
Release Service SQLite Database.

JobOperationPlugins – holds any
plugins installed. For example, If
MobilePrint is installed; this
folder shows all the MobilePrint
52
Planning and Installation Guide
Installing Server Components
plugins.

JobStore – holds the spool files.

PageCounting – this holds the
spool files when Page Counter
fails. This depends on the
StoreFiles registry entry. For
more information, refer to the
Online Help.
Pharos Print Center Web
Select Components
Select the Print Center role to install the
Pharos Print Center website.
Note: For more information about
the Pharos Print Center, please refer
to the “Uniprint 9.0 New Features
Guide” and other Pharos Print Center
documents in the “Documentation”
folder of the Pharos install media.
Select Components
This screen appears if you are trying to
install Print Center Web separate from
the Pharos Print Center Services (Pharos
API).
Pharos recommends configuration of the
Application Request Routing feature of IIS
if you wish to install the Print Center Web
and the Print Center Services separately.
For more information, please refer to the
“Technote Print Center Deployment
Guide” found in the Documentation
folder of the Pharos install media.
53
Planning and Installation Guide
Installing Server Components
The installer adds firewall exceptions for
all the Pharos-specific services during
install, but does not add firewall
exceptions for ports 80 and 443. These
ports need to be open for the Pharos
Print Center.
This screen shows a warning that an
exception has to be added to the Firewall
on this machine for Secure World Wide
Services (HTTPS).
Pharos Database Server TCP/IP Host
Name and Address
Enter the network name of the
computer that hosts the Pharos
Database Service (not Pharos Database)
and then click Next.
Pharos Print Center Services (Pharos API)
Select Components
Select Print Center Services (Pharos API)
to install the Pharos REST API and the
Pharos PayPal IPN Processor. This
component enables communication
between Print Center Web and Print
Services.
54
Planning and Installation Guide
Installing Server Components
Select Components
This screen appears if you are trying to
install Pharos Print Center Services on a
machine without Print Services.
Print Center Services has to be installed
on a machine running Print Services.
Select Components
The installer adds firewall exceptions for
all the Pharos-specific services during
install, but does not add firewall
exceptions for ports 80 and 443. These
ports need to be open for the Pharos
Print Center.
This screen shows a warning that an
exception has to be added to the Firewall
on this machine for Secure World Wide
Services (HTTPS).
Pharos Certificate Warning
This screen shows a note that both the
Pharos API Services and the Print Center
Web components require Server
Certificates in IIS. If the machine on which
you are installing both components does
not have a certificate installed, the
installer will add a self-signed certificate.
Please review the Default Web Site in IIS
to ensure that a current certificate has
been added for the https binding.
55
Planning and Installation Guide
Installing Server Components
Print Center Install
This screen appears when attempting to
install another instance of the Pharos
Print Center Services (Pharos API).
Pharos Web Services
IIS Configuration
This screen appears if you selected to
install “Web Services”.
Clicking “Yes” automatically configures
the following IIS properties for the Web
Services to be installed:

‘Enable Direct Metabase Edit’ and
‘AspEnableParentsPaths’ will be
set to “True”.

‘Active Server Pages’ and ‘Server
Side Includes’ Web Service
extensions will be set to “Active”.
Clicking “No” will take you to the previous
screen. You will need to deselect “Web
Services” for it to not be installed.
56
Planning and Installation Guide
Installing Server Components
Pharos EDI Service
Pharos EDI Server Password
All external clients that communicate
with the EDI Server authenticate
themselves by supplying the password
you create here.
Enter the password and click Next to
continue.
The EDI Server Password can be viewed
later in Pharos Administrator on the
System Settings > Security context.
Pharos Administrator
Select Additional Components
Select Administrator from the Select
Additional Components screen and then
click Next to continue.
57
Planning and Installation Guide
Installing Server Components
Administrator User
If no Administrator-level users are
detected in the Pharos Database, an
Administrator User must be created.
Enter details for a new user account to be
created and then click Next to continue
the install.
Note: The Administrator User
password should meet the following
complexity requirements:
 At least six characters long
 Contains characters from at
least three of the following
o Uppercase (A-Z)
o Lowercase (a-z)
o Numeric (0-9)
o Special Characters
58
Planning and Installation Guide
Installing Server Components
Typical Installation Workflows
The following section outlines the typical installer workflow for the common Uniprint Suite roles. Each of
these workflows assumes that the Pharos Principal Services are already installed and operational.
Installing Print Services
The Print Services components are installed using the main installer on the Pharos disk image.
To install the Print Service components on a computer:
1. Access the Pharos disk image from the computer on which you want to install the Print Service
components.
2. If the installers do not start automatically, run setup.exe in the root directory of the disk image.
3. Select Install Pharos from the main splash screen.
4. Click Next at the Welcome screen.
5. If any other Pharos components are installed on this computer, they will be listed. Click Next.
6. Leave the install directory as the default. Click Next.
7. Select "Print Services" and click Next.
8. Enter the network name of the server on which you installed the Pharos Database Service and
click Next.
9. Check the installation details and click Start. The installation will begin.
10. Once the installation is complete, click Finish.
11. You will be asked to restart the computer. Click OK to allow the installer to perform the reboot.
Once the Print Service components are installed, they are listed under their server name on the System
> Server Configuration context in the Administrator.
Installing SignUp Services
The SignUp Service component is installed using the main installers on the Pharos disk image.
To install the SignUp Service component on a computer:
1. Access the Pharos disk image from the computer on which you want to install the SignUp
Service components.
2. If the installers do not start automatically, run setup.exe in the root directory of the disk image.
3. Select Install Pharos from the main splash screen.
4. Click Next at the Welcome screen.
5. If any other Pharos components are installed on this computer, they will be listed. Click Next.
6. Leave the install directory as the default. Click Next.
7. Select "SignUp Services" and click Next.
8. Enter the network name of the server on which you installed the Pharos Database Service and
click Next.
9. Check the installation details and click Start. The installation will begin.
10. Once the installation is complete, click Finish.
11. You will be asked to restart the computer. Click OK to allow the installer to perform the reboot.
59
Planning and Installation Guide
Installing Server Components
Installing the Pharos EDI Service
The Pharos EDI is installed from the main Pharos disk image.
Before installing the EDI Service, make sure of the following:


At least one server has already been installed with Pharos Print Services or Pharos SignUp
Services.
On the computer on which you will be installing the EDI Service, the following pre-requisites are
installed:
o Microsoft Internet Information Service 5.0 or later is installed.
o Microsoft .NET Framework 3.5 SP1 and 4.0 are installed.
To install the Pharos EDI Service:
1. Access the Pharos disk image from the computer on which you want to install the EDI Service
components.
2. If the installers do not start automatically, run setup.exe in the root directory of the disk image.
3. Select Install Pharos from the main splash screen.
4. Click Next at the Welcome screen.
5. If any other Pharos components are installed on this computer, they will be listed. Click Next.
6. Leave the install directory as the default. Click Next.
7. Select "EDI Service" and click Next.
8. Enter the network name of the machine on which you installed the Pharos Database Service and
click Next.
9. Enter the EDI service password that clients will use to connect to the EDI Server and click Next.
10. Check the installation details and click Start. The installation will begin.
11. Once the installation is complete, click Finish.
12. You will be asked to restart the computer. Click OK to allow the installer to perform the reboot.
Once the computer has restarted, you can check the EDI Service status in the Pharos Administrator on
the System > Server Configuration context.
60
Planning and Installation Guide
Installing Server Components on a Cluster
Installing Server Components on a Cluster
Installing server components on a cluster server uses a similar process as a standard server installation.
However, some additional preparation, installation and post-installation steps are required. This section
details the process of installing Uniprint Suite server components on a Microsoft Failover Cluster.
These instructions assume that Uniprint is being installed on a Windows Server 2008 or Windows 2008
R2 cluster. If installing Uniprint on Windows Server 2012 or Windows 2012 R2, please see note below.
Note: Windows Server 2012 clustering is different to 2008. In Server 2012, clustering is done by having a
virtual machine (i.e. Hyper-V cluster setup) that is "transferred" between the nodes. This means that
installation of Uniprint on a 2012 Cluster consists of installing Uniprint to the virtual machine and using
the VM as a clustered resource. Thus, the only difference between installing Uniprint on a non-clustered
2012 server and a cluster is installing it onto the VM. With the Hyper-V setup, Uniprint is only installed
once on a VM as with a standard install, and the Hyper-V system takes care of the high-availability.
Installing directly on the nodes themselves is not supported. Refer to Microsoft documentation for how
to set up a VM as a clustered resource.
Note: While the traditional method of clustering (using separate physical nodes to present as a single
machine) is still available in Windows Server 2012, the print spooler is no longer offered as a clusterable
resource. Microsoft no longer supports clustered Print Services except under the Hyper-V model. As a
result, Uniprint Print Services also can only support Hyper-V clusters on Server 2012.
Supported Configurations
The Uniprint Suite server components can be installed in an active/passive mode on a Microsoft Failover
Cluster. This means that the Uniprint Suite components (and any other services that these components
depend on) can only be listed as resources in one resource group in the cluster. Effectively, this means
that the services can only be running on one node at a time. Active/Active clustering is not supported.
Since the Print Service components are dependent on the Microsoft spooler, the spooler can also only
be listed as a resource in one resource group (i.e. it can only be active on one node at a time).
Before You Begin
These instructions assume familiarity with Microsoft Failover Clusters and the terms associated with
clustering technology.
In addition to the standard pre-requisites, ensure that the
following additional pre-requisites are met:

Microsoft Failover Cluster environment built on the
following Operating Systems
Note: If the Pharos Database
is hosted on a remote SQL
Server instance (i.e. SQL is
not running on the cluster),
you do not need a clustered
SQL Server and MSDTC.
61
Planning and Installation Guide


Installing Server Components on a Cluster
o Windows Server 2008 Enterprise Edition (32 and 64 bit)
o Windows Server 2008 R2 (R2 is 64-bit only)
o Windows Server 2012 (2012 is 64-bit only)
o Windows Server 2012 R2 (2012 R2 is 64-bit only)
Clustered Microsoft SQL server 2005 or later.
MSDTC (Microsoft Distributed Transaction Coordinator)
Before you begin the installation, ensure the cluster environment is functioning correctly. Create the
required resource group (refer to the “Preparing Cluster for Installation” section on page 62) and ensure
that this resource group can be moved between nodes without issues.
Typical Order of Installation
If you are installing both Principal Services and other roles on the same cluster, you will need to install
the Principal Services first (as you would with a standard installation). If the Principal Services are hosted
on another server, you can simply install the required roles on the cluster.
1. Installing Pharos Database and Principal Services
a. Prepare the cluster for installation.
b. Install the Pharos Database and the Pharos Principal Services on the first, active node.
c. Fail-over to the other node.
d. Install the Principal Services on the second node.
e. Configure the Pharos Principal Services as generic cluster resources and add to the
resource group.
f. Validate the installation.
2. Installing Print Services, SignUp Services, EDI Services and Web Components
a. Prepare the cluster for installation.
b. Install Print Services, SignUp Services, EDI Services and/or Web Components on the first,
active node.
c. Fail-over to the other node.
d. Install the same Print Services, SignUp Services, EDI Services and/or Web Components
on the second node.
e. Configure Print Services, SignUp Services and/or Web Components.
f. Validate the installation.
Preparing Cluster for Installation
Initial preparation of a cluster requires the creation
of a cluster resource group that will be used as the
“virtual server” for the various Uniprint Suite
services. This group should be set up with the
following resources:

Physical Disk: The shared disk used to
store data files (e.g. spool files). The space
Note: If the Pharos Database is being
installed on the cluster, the SQL
Server instance must be installed on
the same cluster. However, SQL
Server does not need to be in the
same resource group as the other
Pharos services.
62
Planning and Installation Guide


Installing Server Components on a Cluster
required on the shared disk will depend largely on the SQL Database sizing requirements and
the storage space required for the Application Data (which holds the spool files).
IP Address (IP Address resource)
Network Name: This network name will be used by all other components to connect to the
components installed on the cluster.
If the Pharos Database is being installed on this cluster, the resource group should also include these
SQL resources:




SQL Server
SQL Server Agent
SQL Server Fulltext
Microsoft DTC
If the Print Services are being installed on this cluster, the resource group should also include:
 Microsoft Spooler
Installing Database and Principal Services
The installer will automatically detect the presence of a cluster. When a cluster is detected, it will
prompt you for the virtual host name of the cluster rather than automatically using the host name of the
physical node.
Before You Begin
Prepare the cluster as specified in the “Preparing Cluster for Installation” section on page 62.
In addition, make sure that the physical node you are installing on is the active node and ensure that the
other physical node of the cluster is running.
Installing the Database and the Principal Services on the First Node
To install the Database and the Principal Services on the first node:
1. Run setup.exe on the first node. This node must be currently active, i.e. it owns the disk
resource.
2. On the Select Components screen, select the Database and Principal Services roles.
3. Optional: Tick the Enable the Pharos Online Services checkbox if you want to enable this
feature.
4. In the Virtual Server Name field, enter the Virtual Server Name of the cluster resource group
that the Pharos services will be part of. Pharos clients will use this name to access the Pharos
services.
5. Click Browse to locate the registry file containing your license information.
6. In the License Agreement screen, accept the terms of the license and click Next to continue.
7. In the Microsoft SQL Server Name field, select or enter the SQL Server name that the Pharos
Database should be installed on.
63
Planning and Installation Guide
Installing Server Components on a Cluster

8.
9.
10.
11.
12.
If the SQL Server is running in the cluster, enter the Virtual Server Name of the resource
group that SQL Server is part of.
 If the SQL Server is on a remote machine, enter the server name or server / instance
name of the remote SQL Server.
Click Next to continue.
Enter the SQL Server Administrator User Name and SQL Server Administrator Password.
Enter the details of the logon account that will be used to log on to Pharos Administrator.
Click Start to begin the installation.
Once the installation is finished, click Finish to exit. It is not necessary to restart your computer;
select No at this point.
After installing the Pharos Database and the Pharos Principal Services on the first node, the next step is
to install only the Principal Services components on the second node. You do not need to install the
Pharos Database on the second node.
Installing Principal Services on the Second Node
To install Principal Services on the second node:
1. Go to the second node and move the resource group to this node. The second node is now your
active node.
2. Run setup.exe on this node.
3. On the Select Components screen, select the Principal Services role only.
4. The installation is generally the same as installing on the first node. However, the following
additional information is needed:
a. In the Virtual Server Name field, enter the Virtual Server Name of the cluster resource
group that the Pharos services will be part of. Pharos clients will use this name to access
the Pharos services.
b. In the Microsoft SQL Server Name field, enter the SQL Server name that the Pharos
Database is installed on.
c. Enter the Database Name, Database User Name and Password. In a default install, the
database name is set to “pharos”.
Copy the value of the User Name and Password entry from the following registry of the
first node:
[HKLM\Software\Pharos\Database Server\Database]@User Name
[HKLM\Software\Pharos\Database Server\Database]@Password
5. Click Browse to locate the registry file containing your license information. Then click Next to
continue.
6. Click Start to begin the installation.
7. Once the installation is finished, click Finish to exit. It is not necessary to restart your computer;
select No at this point.
Configuring the Pharos Principal Services as Cluster Resources
After installing the Pharos Database on the first node and Pharos Principal Services on the two nodes,
the next step is to add the Pharos Principal Services as a clustered service. A cluster configuration tool,
64
Planning and Installation Guide
Installing Server Components on a Cluster
ClusterConfiguration.exe, is provided to simplify the process of adding the Pharos Principal Services as a
cluster resource and adding this to the resource group.
The Cluster Configuration Tool will scan the cluster and prepare a task list. Clicking the “Start Tasks”
button in the tool will configure the Principal Service as a Cluster resource. There is no need to reboot
both nodes.
To configure the Pharos Principal Services using the Cluster Configuration Tool:
1. On the first node, browse to C:\ Program Files\Pharos\bin\cluster to run the
ClusterConfiguration.exe.
2. This tool will scan the cluster and prepare a task list as shown below. The Status column shows
“To Do”.
3. Ensure the correct cluster resource group is selected in the Resource Group combo-box.
4. Click the Start Tasks button. There is no need to reboot both nodes.
After configuring the Pharos Principal Services, the Status column for the Pharos Principal Services on
both nodes should be “Done”.
Validating the Installation
You can validate the installation by checking the status of the cluster group. To do this:
1. Open the Failover Cluster Management Console and navigate to the resource group.
2. Verify that the following cluster resources have a status of “Online”:
 Pharos Database Service
 License Service
65
Planning and Installation Guide
Installing Server Components on a Cluster
 Online Service
3. To test fail-over, right click on the resource group and select “Move Group”. The resources will
be moved to the other node. If successful, all resources should be shown as “Online”.
Installing Other Pharos Services
Before You Begin
Prepare the cluster as specified in the “Preparing Cluster for Installation” section on page 62.
In addition, make sure that the physical node you are installing on is the active node and the other
physical node of the cluster is running.
If this cluster will also be running the Database and Principal Services in addition to the Print Services,
SignUp Services, etc., first complete the installation process covered in the “Installing Database and
Principal Services” section on page 63.
Installing Print Service, SignUp Service, EDI Service and Web Services
After installing the Pharos Database and the Pharos Principal Services (on this cluster or another server –
standard or clustered), the next step is to install the other Pharos components on both nodes.
To install the Print Service, SignUp Service, EDI Service and/or Web Services:
1. Run setup.exe on the currently active node, i.e. this node should own the resource group that
the Pharos services will be part of.
2. If you installed the Database and Principal Services already on this cluster, the installer will
detect that these components have already been installed on the computer.
3. Select one or more of the following Pharos components to install:
a. Print Services
b. SignUp Services
c. Print Center
d. EDI Service
e. Web Services
f. PayPal IPN Processor Service
4. Enter the Virtual Server Name of the
Note: You must specify the shared
cluster resource group that the Pharos
disk location or use any shared
services will be part of.
storage location on both nodes for
5. If the Database and Principal Services are
the Application Data directory;
already installed on the cluster, these
otherwise print jobs will be not be
Pharos components need to be installed
available if you fail over to the other
under the same virtual server/resource
node.
group as the Pharos Principal Services.
6. Enter the TCP/IP Host Name of the
computer that houses the Pharos Database
Service.
66
Planning and Installation Guide
7.
8.
9.
10.
Installing Server Components on a Cluster
a. If the Database and Principal Services are already installed on this cluster, enter the
virtual server name of this cluster.
b. If the Database and Principal Services are installed on a separate server, enter the host
name of that server.
Enter the Application Data Directory. It is the location where print jobs (spool files) will be
temporarily stored.
If you have installed the EDI service, enter a password for the Pharos EDI Server. Make sure to
keep a record of this password as it may be needed when configuring external devices and
clients.
Click Start to begin the installation.
Once the installation is finished, click Finish to exit. It is not necessary to restart your computer;
select No at this time.
Note: If you installed the 'Print Center Services' component, you should manually stop the
'Pharos Systems PayPal IPN Processor' service to avoid an unnecessary delay in the next
step. This will no longer be necessary once the cluster is fully configured.
11. Open the second node and fail over the resource group to this node.
12. Repeat steps 1- 8 on the second node.
Configuring the Print Server and SignUp Server as Cluster Resources
After installing the Pharos Print Server, SignUp Server and Web Components on the two nodes, the next
step is to add these services as cluster services. You can use the Cluster Configuration tool to simplify
the process of adding the Pharos Services as cluster resources and adding these to the resource group.
The Web Components require some manual configuration. Refer to the section “Configuring Web
Components” on page 68.
To configure the Print Server and/or SignUp Server using the Cluster Configuration Tool:
1. Browse to C:\ Program Files\Pharos\bin\cluster to run the ClusterConfiguration.exe. This tool
will scan the cluster and prepare a task list.
2. Ensure that the Configure Pharos Print Server and SignUp Server radio-button is selected.
3. Click the Start Tasks button. This will add Pharos Print Services and SignUp Services to the
selected cluster group.
4. Reboot both nodes to finish installation.
Validating the Installation
The Print Services and/or SignUp Service should be working at this point. Open the Failover Cluster
Management console and navigate to the Application or Service that contains the Pharos components.
You should be able to see the following services with a
status of “Online”:
Note: All print drivers need to be
 Pharos Print Service
installed on both physical nodes of
 Pharos Popup Service
the cluster and on the virtual node.
67
Planning and Installation Guide


Installing Server Components on a Cluster
Pharos LPD Service
Pharos SignUp Service
Initiate a failover by moving the resource group to the
other node, to verify that the Print Services and the
SignUp Service are installed properly.
Configuring Web Components
Note: Only network printers, not
local printers, can be added to the
clustered Print server.
Note: Ensure that IIS is not
configured as a cluster resource.
Microsoft Internet Information Services (IIS) is not
managed as a cluster resource by Microsoft Failover
Clustering. The Uniprint Suite web components still work
by running multiple instances of IIS. Since only the active node will own that network name resource,
effectively only one IIS instance will serve requests at a time.
For the instructions below, the example path names assume that the drive letter assigned to the disk
resource is S:.
Create the Shared Folder
For the Uniprint web page to function, the installation packages must be stored on the shared disk
resource to ensure they are available regardless of which node is active.
To do this, run the following command from a command prompt in the active node:
xcopy /E C:\Inetpub\wwwroot\Uniprint S:\Inetpub\wwwroot\Uniprint
Configure Uniprint to Use the Shared Folder
Once you have created the shared folder, open the Pharos Administrator. Click on the Packages >
Packages Global Settings context. Change the Package Build Location to:
\\<your Virtual Server Name>\S$\Inetpub\wwwroot\Uniprint
Configure IIS to Use the Shared Folder
Apply the following steps to both nodes:
1. On the active node, open IIS Manager by running inetmgr.exe.
2. Under “Web Sites”, expand the “Default Web Site”. Then right-click on the Uniprint virtual
directory and select Managed Application > Advanced Settings.
3. On the Advanced Settings, change the local path to S:\Inetpub\wwwroot\Uniprint and click
Apply. Now the Uniprint Website can be accessed using the virtual network name.
4. Fail-over the resource group to the other node.
68
Planning and Installation Guide
Installing Server Components on a Cluster
5. Repeat steps 1 – 3 on the second node.
If you want to prevent direct access to web server using the physical server name (i.e. the hostname of
the physical node), perform the following on each node:
1. Open IIS Manager by running inetmgr.exe.
2. Under “Web Sites”, right-click on the “Default Web Site” and select Properties.
3. On the Web Site tab, change the IP address to bind to the virtual server IP address only. Now
only the virtual server can respond to requests.
SSL Certificates
To apply SSL certificates to the web site (e.g. to secure EDI communications), an SSL certificate request
must be generated from each node. The SSL certificate must use the virtual server name and not the
name of the physical node. For more information on requesting an SSL certificate, please refer to the
“Setting up SSL” section on page 82.
Once the SSL certificates have been applied, you can verify the certificate name on each node:
1. Open IIS Manager by running inetmgr.exe.
2. Under “Web Sites”, right-click on the “Default Web Site” and select Properties.
3. On the Directory Security tab, click View Certificate to verify that the server certificate is using
the Virtual Server Name of the cluster resource group.
69
Planning and Installation Guide
Installing SignUp Clients
Installing SignUp Clients
The SignUp Client is installed using the SignUpClientInstaller.exe install package. You can obtain the
SignUp Client install package in two ways:

Open the Packages > Client Installers context in the Pharos Administrator. Select the SignUp
Client Installer. This section contains a description of the SignUp client install package and where
to find it. Simply click on the Package Location path to open a Windows Explorer window to that
location.

Browse to the location Program Files\Pharos\Client Installers directory of all Pharos
Administrator computers.
OR
The SignUp Client install package can be installed manually using a simple wizard or automatically using
the command line (i.e. the required installation information is supplied as parameters).
To install the SignUp Client:
1. Run the SignUpClientInstaller.exe install package on the computer and then click Next on the
Welcome screen.
2. Enter the network name of the server on which you installed the Pharos Database and click
Next.
3. Select the Branch that this computer should belong to and click Next. You can add additional
branches using the Pharos Administrator.
4. Select the Computer Type and Computer Group that this computer should belong to and click
Next.
You can add additional computer types and computer groups using the Pharos Administrator.
5. Enter a Display Name and Description for the computer and then click Next.
The display name and description are displayed to the end user when they reserve the
computer. The information is intended to help them to find the correct computer.
6. Check the installation details and click Start.
7. The SignUp Client installation will start. Once the installation is complete, click Finish.
8. You will be asked to restart the PC. Click OK to allow the installer to reboot the computer.
Once the SignUp Client is installed, it will control access to the computer. A Computer entry for the
computer is automatically created in Pharos Administrator. You can view and edit the computer details
on SignUp > Computers context.
70
Planning and Installation Guide
Installing SignUp Clients
Command Line Options
The SignUp Client install package can be run from the command line. The following parameters can be
specified:
Parameter
Description
Instructs the installer to run in silent mode. No dialogs are
shown to the user and default values are used, unless
specified by other command line options.
/s
Note: As of 8.3, a command line install is treated
as silent (regardless of whether the /s parameter
is specified or not).
/d "server"
Host name of the Pharos Database Server. This value must
always be specified.
/n "portnumber"
Port number of the Pharos Database Server. Defaults to port
number “2355” if not specified.
/b "branch"
The name of the Branch that the computer belongs to.
/g "group"
The name of the Computer Group that the computer belongs
to.
/t "type"
The name of the Computer Type that the computer belongs
to.
/dn "displayname"
The computer’s Display Name. This is the name that will be
visible to users of the SignUp system, and does not have to be
the computer’s host name.
/ds "description"
The computer’s description, which should include information
on where the computer is located.
After installing a SignUp client:
After installing a SignUp client using the command line, complete the following steps:


Check the result of the install (whether Success or Fail) in the Result.txt log file found in the
\Pharos\Temp folder.
Check the SignUpClientInstall.log file found in the \Pharos\Bin folder for details of installation
errors, if any.
71
Planning and Installation Guide

Installing SignUp Clients
Restart your computer to complete installation.
All parameters are optional, except for /d. If no Branch, Computer Group or Computer Type is specified,
the installer will select defaults from the Pharos Database after connecting to the Database Server. All
values must be specified inside double quotes.
72
Planning and Installation Guide
Installing Popup Clients
Installing Popup Clients
The Popup Client is installed using Pharos install packages. Install packages automate the process of
setting up Pharos Popups on workstations.
Installing Popup Clients involves creating one or more install packages and deploying them on the
workstations.
As well as installing the Uniprint client application(s), they set up one or more Pharos Queues as printers
on the workstation. Each install package can also include:


An uninstaller to allow the end user to remove the package at any time.
An updater service that automatically connects to the Uniprint server to check for updates and
changes. If an update is detected, the new files are downloaded and applied.
Standard install packages are self-contained and can be simply copied and run on each workstation.
“Lite” versions of the install packages are also available, which are smaller executables that detect the
operating system and any existing components, and then download only those components that are
needed.
Once the Popup Client is installed, users can easily submit print jobs to the Uniprint server. In addition,
the system can be configured to request additional information from the user each time they print.
Pre-requisites
Before creating Pharos install packages, ensure that the following pre-requisites are met:


Make sure that all Queues are using the correct drivers.
If you plan to use "Lite" packages or the "Automatic Update" feature, you must specify the
Package Download and Update Location in the Packages > Packages Global Settings context.
The Package Download and Update Location is the URL of the web site that modules will be
downloaded from.
Creating Install Packages
Install packages are created in Pharos Administrator. The process of creating and deploying install
packages involves the following steps:
1. Specify the global properties of the install
packages.
2. Add a Custom Module (optional).
3. Add a Package Definition.
4. Build packages based on the definitions.
Note: For detailed information on how
to create and deploy install packages,
see the Online Help.
73
Planning and Installation Guide
Installing Popup Clients
Specifying the global properties of the Install Package
Before creating install packages, you need to specify where they will be stored and how they will be
accessed. The Packages > Packages Global Settings context contains settings that affect how the install
packages are generated and distributed. For example, the website or network location that users will be
able to download Packages from, and where updates will be retrieved from.
Adding Optional Custom Modules
Pharos install packages can also run user-created modules to add custom functionality. For example, a
custom module could be used to install additional applications along with the Pharos software. A
custom module can be an executable, a batch file or a self-extracting zip file.
Contact Pharos Support for assistance in creating custom modules.
Adding Package Definitions
Package definitions are set up in Pharos Administrator on the Packages > Package Definitions context.
Once defined, packages are built by using the Build Package action available in this context.
Building Packages
When packages are built, the package creator utility performs a number of checks – if any issues are
found, an error or warning will be displayed. In addition, the creator utility checks what operating
systems and platforms are supported by the print drivers associated with the selected Queues. It will
collect these print driver files and incorporate them into the package.
For each Package Definition, the following files are created:



Full packages for each supported operating system (based on both the operating systems
supported by Uniprint and the operating systems supported by the print drivers).
One Lite package.
Modules for all components and operating systems included in the full packages.
In addition, a “manifest” containing details of all modules and packages is created. This XML document,
called Manifest.xml, is used by the package updater to detect updates and changes. It is formatted with
an XSL style sheet, and can be viewed in a web browser.
Deploying Install Packages
Once created, packages can be distributed by a variety of means. It is recommended that they are made
available from a shared location, so that users can download and install the packages relevant to them
without any assistance. This shared location may be a network share or a web site.
If packages are made available on a web site, several options are available for presenting the packages
to users:
74
Planning and Installation Guide




Installing Popup Clients
You can write your own web pages, containing links to the package files.
Users can be given access to the Manifest.xml file, which contains links to all available packages.
The Pharos Print Map Builder can be used to create a series of web pages containing links to Lite
packages. The Map Builder is installed with Pharos Administrator; it can be opened by clicking
the Pharos Print Map Builder action on Packages > Package Definitions context.
Users can be given access to the Uniprint Web Site, which contains links to all available packages
and maps. The Uniprint Web Site is installed from the main installers.
75
Planning and Installation Guide
Installing Pharos Stations
Installing Pharos Stations
You can install Pharos Stations using the PharosStationInstaller.exe install package. You can obtain the
Pharos Station install package in two ways:

Navigate to the Packages > Client Installers context in the Pharos Administrator. Select the
Pharos Station Installer section, which contains a description of the install package and where to
find it. Simply click on the Package Location path to open a Windows Explorer window to that
location.

Browse to the location Program Files\Pharos\Client Installers directory of all Pharos
Administrator computers.
OR
Run the package executable on each computer on which you want to install the Pharos Station
component. In addition, you can run the package executable on computers that already have the Pharos
Station component to upgrade those computers. The Pharos Station install package can be installed
manually using a simple wizard or automatically using the command line (i.e. the required installation
information is supplied as parameters).
Pre-requisites
In addition to a supported operating system, the computer must have following pre-requisite:

Microsoft .NET Framework 4.0
Before You Begin
A Pharos Station record must already be configured for the computer that you are installing on, i.e.
there must be a Pharos Station entry in the Pharos Database. The network name of the computer must
match the network name of the Pharos Station entry.
Installing the Pharos Station
To install the Pharos Station component on a computer:
1. Run the PharosStationInstaller.exe install package on the computer and click Next at the
Welcome screen.
2. Enter the network name of the machine on which you installed the Pharos Database Service and
click Next.
3. Check the installation details and click Start. The Pharos Station installation will start.
4. Once the installation is complete, click Finish.
5. You will be asked to restart the PC. Click OK to allow the installer to reboot the computer.
76
Planning and Installation Guide
Installing Pharos Stations
Once the Pharos Station is installed, you can start it from the Start menu at Programs > Pharos. Any
changes to the Pharos Station's configuration are made in Pharos Administrator on the Release Stations
context.
Command Line Options
The Pharos Station install package can be run from the command line. The following parameters can be
specified:
Parameter
Description
/s
Instructs the installer to run in silent mode. No dialogs are
shown to the user and default values are used, unless
specified by other command line options.
/d "server"
Host name of the Pharos Database Server. This value must
always be specified.
/n "portnumber"
Port number of the Pharos Database Server. Defaults to port
number 2355 if not specified.
Name of the Pharos Station color scheme to use. The
following schemes are available:
/c "colorscheme"

"Pharos Vx3" - the default Pharos scheme

"Blue Sky" - a color scheme in shades of blue

"Brain Food" - a library-themed color scheme in
shades of orange

"Building Blocks" - a color scheme in shades of yellow

"Expedition" - a color scheme in shades of brown

"Explore!" - a children's scheme in shades of green

"Hit the Books" - an education-themed scheme in
shades of gray and brown

"Mist" - a color scheme in shades of gray and light
blue

"Print Control" - a corporate-themed scheme in blue
All parameters are optional, except for /d. All values must be specified inside double quotes.
77
Planning and Installation Guide
Installing Pharos Remote
Installing Pharos Remote
You can install Pharos Remote using the RemoteInstaller.exe install package. Pharos Remote is basically
a light-weight Pharos Administrator; it only includes contexts required for user and print job
management such as Users, Alerts, Transactions, Output Management Overview, Queued Jobs and
Printed Jobs.
You can obtain Pharos Remote install package in two ways:


By navigating to the Packages > Client Installers context in the Pharos Administrator. This
context contains a description of the install package and where to find it. Simply click on the
Package Location path to open a Windows Explorer window to that location.
Browse to the location Program Files\Pharos\Client Installers directory of all Pharos
Administrator computers.
Pre-requisites
Microsoft .NET Framework 4.0 must be installed before installing Pharos Remote.
Installing Pharos Remote
To install the Pharos Remote application on a computer:
1. Run the RemoteInstaller.exe install package on the
Note: If you installed the web-based
computer and click Next at the Welcome screen.
Remote application from Uniprint
2. Enter the Database Server Host Name of the
8.0, the Uniprint 9.0 upgrade will
machine on which you installed the Pharos
remove this web-based Remote.
Database Service and click Next.
3. Click the Start button to begin the installation. The
Pharos Remote installation will start.
4. Once the installation is complete, click Finish.
5. You will be asked to restart the computer. Click OK to allow the installer to reboot the
computer.
After Pharos Remote is installed, you can start Pharos Remote from the Start menu at Programs >
Pharos > Pharos Remote on the computer.
78
Planning and Installation Guide
Installing Pharos Reports
Installing Pharos Reports
Pharos Reports is installed using the main installers on the Pharos disk image.
To install the Pharos Reports component on a computer:
1. Access the Pharos disk image from the computer on which you want to install the Pharos
Reports component.
2. If the installers do not start automatically, run setup.exe in the root directory of the disk image.
3. Select Install Pharos from the main splash screen.
4. Click Next at the Welcome screen.
5. If any other Pharos components are installed on this computer, they will be listed. Click Next.
6. Leave the install directory as the default and click Next.
7. Select "Additional Components" and click Next.
8. Select "Reports" and click Next.
9. Enter the network name of the machine on which you installed the Pharos Database Service and
click Next.
10. Check the installation details and click Start. The Pharos Reports installation will commence.
11. Click Finish once the installation is complete.
Once Pharos Reports is installed, you can start it from the Start menu under Programs > Pharos Reports.
79
Planning and Installation Guide
Installing Pharos Print Center
Installing Pharos Print Center
The Pharos Print Center Web and the Print Center Services are installed using the main installers on the
Pharos disk image.
Installing the Print Center Web
Pre-requisites
In addition to a supported operating system, the computer must have following pre-requisites:

Microsoft IIS 6.0 or later, plus ASP, ASP.NET 4.5 and .NET Extensibility 4.5
To install the Pharos Print Center component on a computer:
1. Access the Pharos disk image from the computer on which you want to install the Pharos Print
Center component.
2. If the installers do not start automatically, run setup.exe in the root directory of the disk image.
3. Select Install Pharos from the main splash screen.
4. Click Next at the Welcome screen.
5. If any other Pharos components are installed on this computer, they will be listed. Click Next.
6. Leave the install directory as the default and click Next.
7. Select Print Center Web and click Next.
8. Check the installation details and click Start. The Pharos Print Center Web installation will
commence.
9. Click Finish once the installation is complete.
Note: The Pharos Print Center Web is dependent on the Print Center Services (Pharos API). If you would
like to install the Print Center Web separate from the Pharos API, please refer to the “Technote Pharos
Print Center Deployment Strategy” document. You can find this document in the Documentation folder
under the Technotes subfolder.
Installing the Print Center Services (Pharos API)
Pre-requisites
In addition to a supported operating system, the computer must have following pre-requisites:


Microsoft .NET Framework 4.5
Microsoft IIS 6.0 or later
80
Planning and Installation Guide
Installing Pharos Print Center
Note: Pharos Print Center Services (Pharos API) requires Print Services to be installed on the same
machine.
1. Access the Pharos disk image from the computer on which you want to install the Pharos Print
Center Services (Pharos API).
2. If the installer does not start automatically (e.g. if you are accessing the disk image from a
network share), double-click on setup.exe from the root directory of the disk image. The
Pharos splash screen appears.
3. Click <Next> at the Welcome screen.
4. Any Pharos components (e.g. Database, Principal Services) already installed on this machine
will be displayed. Click Next to continue.
5. At the Select Components screen, select Print Center Services (Pharos API).
6. Check the installation details displayed and click Start. The installation will commence. When it
is done, click Finish.
Once Pharos Print Center is installed, you can start it from the Start menu under Programs > Pharos >
My Print Center.
81
Planning and Installation Guide
Setting up SSL
Setting up SSL
Certain Pharos components, in particular the Pharos External Device Interface (EDI), use HTTP to
communicate with each other. This communication can be secured with SSL encryption. Setting up
encryption for secure communications requires the installation of certificates, which are supplied as a
free service from Pharos Systems.
When to Use SSL
The following Pharos components communicate via
HTTP, which can be secured with SSL:


Services, terminals, and iMFPs communicating
with the Pharos EDI Service
Client web browsers accessing the SignUp Nerve
Center
Note: Where a service
communicating with the EDI is on the
same machine as the EDI, secure
communications are not required (as
no data is transmitted over the wire).
Setting up Encryption
To secure these communication paths with SSL, you must perform the following steps:
1.
2.
3.
4.
Install the Pharos CA certificate on all computers that will access the server.
Request a server certificate for the server component from Pharos Support.
Install the server certificate on the server.
Direct the relevant components to use SSL
Installing the Pharos CA Certificate
The Pharos CA certificate is required to verify the server certificate during any SSL session (i.e. when
communicating with the server). The Pharos CA certificate is publicly available—you can find it on the
Pharos disk. This certificate must be installed on all clients that will be accessing the server. For example,
when securing communication with the Pharos EDI Server, the CA certificate must be present on all
terminals or computers running software that will contact the EDI. The Pharos Omega terminals and
Pharos integrated Multifunction Printers (iMFPs) come with the CA certificate already installed.
To install the Pharos CA certificate on a computer:
1. Access the Pharos disk image from the computer on which you want to install the Pharos CA
certificate.
2. Browse the disk image and open the server\edi.net folder. The Pharos CA certificate is called
PharosCACertificate.crt.
3. Double-click the certificate. If prompted, select Open.
4. Click Install Certificate on the dialog that opens. This starts the Certificate Import Wizard.
5. Click Next on the opening screen.
82
Planning and Installation Guide
Setting up SSL
6. Select Place all certificates in the following store on the Certificate Store screen and click
Browse.
7. Select the store Trusted Root Certification Authorities > Local Computer and click OK. (You may
need to check the Show physical stores box to see this store.)
8. Click Next.
9. Click Finish.
Requesting a Server Certificate
To obtain a certificate from Pharos Systems, you must generate a certificate request using Microsoft
Internet Services Manager and send it to Pharos Systems. The certificate request is simply a text file
containing information about your server in an encoded format.
Requesting a Server Certificate using IIS 6.0
To generate a certificate request using IIS 6.0:
1. Open the Internet Services Manager (Control Panel > Administrative Tools).
2. Right-click the Web site on which you want to enable encryption (e.g. “Default Web Site”), and
click Properties.
3. Click the Directory Security tab, and then click Server Certificate to start the Web Server
Certificate Wizard.
4. Click Next to start the wizard, and select Create a new certificate.
5. Click Next, and select Prepare the request now, but send it later.
6. Click Next, and give your certificate a name. You may want to match it with the name of the
Web site. Now, select a bit length; the higher the bit length, the stronger the certificate
encryption.
7. Click Next, and type your Organization and Organizational Unit. These values do not need to
match any Active Directory entries.
8. Click Next, and then enter the common name.
Note: Server certificates are specific to the common name that they have been issued to, so it is
important that the common name is correct. The common name must be the same as the Web address
you will be accessing when connecting to the secure site. Common names are typically composed of Host
+ Domain Name and will look like "servername" or "servername.domain". If the certificate is used on a
cluster, the common name should the Host + Domain Name of the virtual server name of the resource
group that contains the Pharos services.
9. Click Next, and type your country, state, and city or locality.
10. Click Next, and select a location and file name to save your request to.
11. Click Next twice, and then click Finish to close the wizard.
This places the text file (called certreq.txt by default) into the location you specified in step 10. The
request can now be emailed to Pharos Systems at support@pharos.com.
83
Planning and Installation Guide
Setting up SSL
Requesting a Server Certificate using IIS 7.0
Microsoft Windows Server 2008, 2008 R2, 2012 and 2012 R2 use Internet Information Services (IIS) 7.0.
With this new version of IIS, there are new methods of requesting and installing SSL certificates. The
following section shows instructions on how to obtain a Server Certificate using IIS 7.0.
To generate a certificate request using IIS 7.0:
1. Open the Internet Services (IIS) Manager (Start Menu > Programs > Administrative Tools).
2. Right-click the server on which you want to enable encryption and then click Server Certificates
(from IIS).
3. In the Server Certificates Actions pane, select Create Certificate Request. This opens the
Request Certificate dialog.
4. In the Common name field, enter the name of your certificate. You may want to match it with
the name of the Web site.
Note: Server certificates are specific to the common name that they have been issued to, so it is
important that the common name is correct. The common name must be the same as the Web
address you will be accessing when connecting to the secure site. Common names are typically
composed of Host + Domain Name and will look like "servername" or "servername.domain". If the
certificate is used on a cluster, the common name should the Host + Domain Name of the virtual
server name of the resource group that contains the Pharos services.
5. Enter values to the rest of the fields:
a. Organization
b. Organizational Unit
c. City/locality
d. State/province
e. Country/region
These values do not need to match any Active Directory entries.
6. Click Next.
7. Select the Cryptographic Service Provider.
8. Select a bit length; the higher the bit length, the stronger the certificate encryption. Click Next.
9. Specify the file name and the location of the certificate request.
10. Click Finish.
This places the text file (called certreq.txt by default) into the location you specified in step 9. The
request can now be emailed to Pharos Systems at support@pharos.com.
84
Planning and Installation Guide
Setting up SSL
Installing the Server Certificate
Once the request is received and verified, Pharos Systems will generate your certificate and send it to
you.
Using IIS 6.0
To install the certificate on your server using IIS 6 or lower:
1. Open the Internet Services Manager.
2. Right-click the Web site on which you want to enable SSL, and then click Properties.
3. Click the Directory Security tab, and then click Server Certificate… to start the Web Server
Certificate Wizard again.
4. Click Next, and select Process the pending request and install the certificate.
5. Click Next, and enter the path and file name of your certificate.
6. Click Next twice, and then click Finish to complete the wizard.
7. Click the Directory Security tab, click Edit under Secure Communications and on the dialog that
opens, make sure that the default “Ignore client certificates” option is selected and click OK.
8. Click the Web Site tab, and make sure that the SSL Port text box is populated with the port you
would like SSL to run on. The default (and recommended) port is 443.
9. Click OK to close the Web site Properties dialog box.
10. Open the Certificates Console by opening Microsoft Management Console (enter “mmc” at a
command prompt).
11. Select Add/Remove Snap-in from the File menu and click Add.
12. Select Certificates and click Add.
13. Select Computer account and click Next.
14. Select Local Computer and click Finish.
15. Click Close and then click OK.
16. The server certificate will have been installed in the Personal folder. Select the certificate and
select Copy from the Action menu.
17. Go to the Trusted People folder and paste a copy of the certificate there.
18. Close the console.
The certificate is now installed on your web server and ready for use by all client components.
Note: Double-clicking on the certificate file in Windows Explorer and clicking Install Certificate on the
dialog that appears starts a Web Server Certificate Wizard. However, this wizard does not install the
certificate on your server; it merely places the certificate in a “store” where it can be accessed by
applications. To actually install the certificate on your web server, you must go through the Internet
Services Manager.
85
Planning and Installation Guide
Setting up SSL
Using IIS 7.0
To install the certificate on your server using IIS 7.0:
1. Open the IIS Manager.
2. Right-click the Server on which you want to enable SSL, and then click Server Certificates (from
IIS).
3. In the Server Certificates Actions Pane, add a certificate to your server.
4. On the Default Web Site, check that you have added https to your Bindings list.
5. On the Sites list, select Pharos EDI.
6. Double click SSL Settings and tick the "Require SSL" checkbox.
7. Click Apply.
Directing the System to Use SSL
Once both the CA certificate and the server certificate have been installed where required, SSL can be
activated by informing the clients to connect to the server.
Pharos EDI
To direct clients to contact the EDI Server using SSL, configure them to connect to the server using the
URL:
https://<server>/PharosEdi/EdiService.asmx
where <server> is the host name of the web server that the Pharos EDI is installed on. This should be the
host name specified in the common name of the certificate.
SignUp Nerve Center
If you want to secure communication between users’ web browsers and the SignUp Nerve Center, you
must instruct users to browse to the following URL (note the https):
https://[server]/SignUp/
86
Planning and Installation Guide
Supporting Legacy EDI Addresses in IIS7
Supporting Legacy EDI Addresses in IIS7
Starting with Uniprint 8.0, the default EDI Service address was changed to point to the EdiService.asmx
file. Some older network terminals and iMFPs use a hard coded EDI service address to connect to the
EDI, e.g. pedi.wsdl, pedi.asmx and pediservice.asmx. In order to support these terminals, a redirection
has been added to the EDI Service so that connections to old EDI Service addresses will be automatically
redirected to EDIService.asmx.
A third-party URL rewriter is used to redirect requests to the EDIService.asmx. This redirection process is
handled by the Internet Information Server (IIS).
The Pharos installer can automatically setup this redirection process for both IIS5 and IIS6. However, the
Pharos installer cannot setup this process for IIS7 (Windows Server). By default, IIS7 runs in Integrated
Mode which is not compatible with the third party URL rewriter.
In order for the URL rewriter to run on IIS7, you can do one of the following:


Change the Application Pool
Allocate a separate Application Pool
Changing the Application Pool
When the Pharos installer detects IIS7, it will disable the URLRewriteModule in the configuration file.
Manual configuration is necessary to enable URL redirection.
Note: Switching from Integrated Mode to Classic Mode can potentially break other websites and
services hosted on the same machine.
To manually enable URL rewriting, you will switch the Pharos EDI virtual directory from
'DefaultAppPool' to 'Classic .NET AppPool'. Use the following steps:
1. Enable the URLRewriteModule
2. Change the Application Pool
3. Test the connection
Step 1- Enable the URLRewriteModule
1. Open the configuration file web.config from \inetpub\wwwroot\PharosEdi.
2. Locate <httpModules> in the configuration file, and uncomment the following section to enable
URL rewriting.
3. Save the configuration file.
The <httpModules> will look like the following:
<httpModules>
<!--<add name="UrlRewriteModule" type="UrlRewritingNet.Web.UrlRewriteModule,
87
Planning and Installation Guide
Supporting Legacy EDI Addresses in IIS7
UrlRewritingNet.UrlRewriter"/>-->
</httpModules>
After removing the comments, the <httpModules> section should look like this:
<httpModules>
<add name="UrlRewriteModule" type="UrlRewritingNet.Web.UrlRewriteModule,
UrlRewritingNet.UrlRewriter"/>
</httpModules>
Step 2 -Change the Application Pool
1. Open Internet Information Services (IIS) Manager by running inetmgr.exe or by selecting Start
Menu >All Programs > Administrative Tools.
2. Expand the Sites node and expand the Default Web Site node. A list of all the websites appear.
3. Right click on the PharosEDI website, and then select Manage Application > Advanced Settings.
This opens the Advanced Settings dialog.
4. In the Advanced Settings dialog, change the Application Pool property from 'DefaultAppPool' to
'Classic .NET AppPool' and then click OK.
Note: Ensure that the Managed pipeline mode of the Classic.NET AppPool is set to Classic.
To verify the Managed pipeline mode, In the Applications Pool, right click on the Classic.NET AppPool
and click Basic Settings, this opens the Edit Application Pool. Verify that the Managed pipeline mode
property is set to Classic.
Step 3- Test Connection
Open a web browser and type one of following URLs, depending on the address that the terminal
requires. This process is used to test if redirection works.


http://localhost/PharosEdi/pedi.asmx
http://localhost/PharosEdi/pedi.wsdl
If the .wsdl does not get through, you need to check the IIS handler mapping:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Open IIS manager by running inetmgr.exe.
Expand the Sites node and expand the Default Web Site node. A list of all the websites appear.
Click on the PharosEDI website, and click Handler Mappings.
In the Actions Pane, select Add Script Map. This opens the Add Script Map dialog.
In the Request path field, type*.wsdl
In the Executable field, enter %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
In the Name field, type a name for the script map, for example wsdl
Click OK.
Test the redirection by typing this on a web browser http://localhost/PharosEdi/pedi.wsdl. This
should open the EDI Service web page.
88
Planning and Installation Guide
Supporting Legacy EDI Addresses in IIS7
Moving the EDI Server to a separate application pool
By default, all IIS web applications run with the default application pool called DefaultAppPool. In this
section, you will be creating a separate application pool and moving the EDI server to that application
pool.
One advantage of isolating an application pool is that you can configure the application pool with special
settings. Moreover, creating a separate application pool prevents other sites from affecting other sites
in the application pool.
Note: Both IIS 6 and IIS7 support application isolation.
Creating an application pool
To create an application pool:
1. Open Internet Information Services (IIS) Manager by running inetmgr.exe or by selecting Start
Menu >All Programs > Administrative Tools.
2. Expand the server node and then select Application Pools. This opens the Application Pools
page.
3. Right click on the Application Pools and then select Add Application Pool.
4. In the Name field, enter a name for the new application pool, for example PharosEDIPool.
5. In the Managed pipeline mode list, select Classic.
6. Click OK. This adds the new application pool to the Web Server.
Moving the Pharos EDI to the created application pool
After creating a separate application pool, the next step is to move the Pharos EDI website to this
application pool.
To move the Pharos EDI to the new application pool:
1. Expand the Default Web Site node and select PharosEDI website.
2. Right click on the PharosEDI website, and then select Manage Application > Advanced Settings.
This opens the Advanced Settings dialog.
3. In the Advanced Settings dialog, change the Application Pool property to the newly added
application pool and then click OK.
89
Planning and Installation Guide
Uninstalling
Uninstalling
The Pharos uninstall program (uninst.exe) is installed with most Pharos components, and is available
from the Start menu at Program Files > Pharos. It is also available on the Pharos disk image in the setup
directory.
To remove Pharos components from a computer:
1. Run the uninstaller from the Start menu, or run the uninstaller from the setup directory on the
Pharos disk image.
2. Click Next at the Welcome screen.
3. Select the component(s) to uninstall (click Select All to check all boxes at once) and click Next.
4. Specify the location of the installed Pharos files and click Next.
5. If you are uninstalling the Pharos Database: Enter the SQL Server administrator logon and
password and click Next.
6. Check the uninstall details and click Start. This will begin the uninstallation process.
7. Click Finish to complete the uninstallation.
8. Depending on which components were uninstalled, you may be asked to restart the computer.
Click OK to allow the uninstaller to reboot the computer.
90
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising