Uniprint Planning & Installation Prerequisites

Version 14
Visibility: Open to anyone

    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

     

    COMPONENT

    DESCRIPTION

    Pharos Database

    The Pharos Database is central to all Pharos products - all configuration and transaction data information is stored here.

    Principal Services

    The core group of services required for all Uniprint Suite installations. These services include:

    • Pharos Database Server
    • Pharos License Server
    • Pharos Online Services
    • Pharos Logging Service

    These components must be installed on a server machine.

    Print Services

    Print Services comprise the following four services.

     

    • Print Server – The component that handles costing and billing of print jobs. It also controls copy- related 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.

    SignUp Services

    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.

    EDI ServiceThe External Device Interface (EDI) Service provides a suitable protocol for approved, external devices and integration to connect to the Uniprint Suite installation. Pharos Network Terminals and Pharos iMFPs require the Pharos EDI.
    Web ServicesWeb 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. 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.
    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 Payment Notification Processor – This service is responsible for processing approved PayPal transactions. It will credit the Pharos user accounts based on the details provided by PayPal.
    Pharos Systems Updater Service The component that downloads updates for Pharos software to maintain stability and aid in deployment of new features. Updater Service will be installed with every Uniprint Server component and as well as with Pharos Administrator.

     

     

    Client Components

     

     

    COMPONENT

    DESCRIPTION

    Pharos Popup Client

    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. 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 duration as part of SignUp.

    Pharos Station

    Pharos Stations are dedicated user stations that allow end-users to (1) collect and pay for printing, (2) manage their account, and (3) create and manage computer reservations.

     

    Administrative Components

     

     

    COMPONENT

    DESCRIPTION

    Pharos Administrator

    The Pharos Administrator is the main user interface used to configure, manage and maintain the Pharos system. Pharos Administrator is installed with all Pharos Services, but it can also be installed standalone for remote management of the Pharos system.

    Pharos Remote

    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.

    Pharos Reports

    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.

     

    Web Components

     

     

    COMPONENT

    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.

    Print Center Web

    This is the website component that allows users to release print jobs from laptops and traditional desktops to any Pharos controlled device. This can be extended by integrating the standard Print Center web with MobilePrint 2.1. 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

     

     

    COMPONENT

    DESCRIPTION

    Network Terminal

    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 the 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.

     

     

    Which Pharos Server Components Should I 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 lists 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

    COMPONENT

    Uniprint (Including Secure Release Here, Informed Print, and Third-Party Charging)

    • Pharos Database
    • Principal Services
    • Print Services
    • EDI Service
    • Web Services (optional)

    Off-The-Glass

    • Pharos Database
    • Principal Services
    • Print Services
    • EDI Service
    • Web Services (optional)
    SignUp
    • Pharos Database
    • Principal Services
    • SignUp Services
    • Web Services (optional)
    MobilePrint
    • Pharos Database
    • Principal Services
    • Print Services
    • Print Center Services (Pharos API)
    Pharos Print Center
    • Pharos Database
    • Principal Services
    • Print Services
    • Print Center Web
    • Print Center Services (Pharos API)

     

    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

    COMPONENTS

    NUMBER OF SERVERS

    Small

    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

    A single server can be used for all Pharos services

    Medium

    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

    1 server for SQL Server, Pharos Database and Pharos Principal Services

     

    1 server for all other services (including Print Services and SignUp Services)

    Large

    A large environment is defined as having one or more of the following characteristics:

     

    • 100+ output devices (i.e. printers and MFPs)
    • 50,000 + full time equivalent students
    • 500 – 2,500 SignUp Client computers

    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.

                 

    Determining the 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 HereTM 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.

     

    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.

    Determining the 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:

     

    Take into consideration the following factors:

     

    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

    • The amount of space for indexes a factor of 2
    • 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 prerequisites 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 = 1900 MB

    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 4 GB of disk space for the Database.

     

     

    Single Server Running All Pharos Services

     

    The minimum requirements for a single server running all Pharos Services:

     

     

     

    COMPONENT

    DESCRIPTION

    CPU

    2 or more processors

    Memory

    4 GB RAM (Microsoft® SQL Server is on the same server). If running newer versions of operating systems, such as Windows Server 2012 R2, Pharos recommends 8 GB of RAM.

    Disk Space

    Program Files(x86) 246 MB

     

    Database – For a site with 10,000 students generating 5,000 transactions per day (keeping 12 months’ worth of data), the Database requires approximately 4 GB 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:

     

      • 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:

     

    • 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.
    • 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):

     

    COMPONENT

    PRINCIPAL SERVER

    (with SQL SERVER)

    PRINT SERVER

    CPU

    2 or more processors

    Quad Core processor

     

    Memory

    4 GB RAM (Microsoft® SQL Server is on the same server).

     

    If running newer versions of operating systems, such as Windows Server 2012 R2, Pharos recommends 8 GB of RAM.

    3+ GB RAM

     

    Disk space

    Program Files – Allow 200 MB for software disk space.

     

    Database – Refer to the "Database Sizing" section on page 18.

    Program Files(x86) – Allow 300 MB for software disk space.

     

    Application Data – On a site generating 5,000 print jobs per day, allow 5 GB 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:
      • Database
      • Application Data
      • 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

     

    • 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 System 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 60.

     

    OPERATING SYSTEM

    EDITION

    32-BIT SUPPORT

    64-BIT SUPPORT

      Windows Server 2012 R2

    Standard, Enterprise

    NAYes

      Windows Server 2012

    Standard, Enterprise

    NA

    Yes

      Windows Server 2008 R2

    Standard, Enterprise

    NA

    Yes
      Windows Server 2008Standard, EnterpriseYesYes
      Windows VistaBusiness, Enterprise, UltimateYesYes
      Windows 7Enterprise, Professional, UltimateYesYes
      Windows 8Windows 8 (Basic), Pro, EnterpriseYesYes
      Windows 8.1Windows 8.1 (Basic), Pro, EnterpriseYesYes

     

    Prerequisites

     

    Ensure that the following prerequisites are installed before installing the Uniprint Suite server components.

     

     

    PREREQUISITE

     

    DESCRIPTION

    Microsoft® Windows Installer 3.1 or laterWindows 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.

    Microsoft® .NET Framework 4.0, and 4.5

    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, 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 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.

     

    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.

     

     

    Additional Prerequisites for Pharos EDI Services, Print Center, and Web Components

    PREREQUISITE

    DESCRIPTION

    Microsoft Internet Information Services (IIS) 7.0 or later

    The following Pharos components require Microsoft Internet Information Services.

    • Pharos EDI service
    • Pharos Web Components
    • Pharos Print Center Web
    • Pharos Print Center Services (Pharos API)

     

     

    Additional Prerequisites for Windows Server 2008, 2008 R2, 2012, and 2012 R2


    If you are installing Pharos Uniprint on Windows Server 2008, 2008 R2, 2012, or 2012 R2, you need to install the following prerequisites in addition to the standard prerequisites.

     

    • 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
      • Static Content

     

    • Application Development
      • ASP .NET
      • .NET Extensibility
      • ASP
      • ISAPI Extensions
      • ISAPI Filters

     

    • Management Tools
      • IIS Management Console
      • IIS Management Scripts and Tools
      • Management Service
      • IIS6 Management Compatibility (including all components under this tree).

    Windows Server 2012, Windows Server 2012 R2

    • Web Server (IIS)
      • Common HTTP Features
        • Static Content (not required for EDI server)
        • Default Document
      • Security
      • 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 andASP.NET 4.5)
        • ISAPI Filters (Must be included for ASP.NET 4.5)

     

    • Management Tools
      • IIS Management Console
      • IIS 6 Management Compatibility (required for IIS 6 Scripting Tools)
      • IIS 6 Scripting Tools (required for IIS 6 Scripting Tools)

     

    Requirements for Administrative Components


    Hardware requirements for the Uniprint Suite administrative components (Pharos Administrator, Pharos Remote, Pharos Station, and Pharos Reports) are the same as the processor, memory, and disk space requirements of the Windows operating system.

     

    Operating System Requirements

     

    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 2008Standard, EnterpriseYesYes
      Windows VistaBusiness, Enterprise, UltimateYesYes
      Windows 7Enterprise, Professional, UltimateYesYes
      Windows 8Windows 8 (Basic), Pro, EnterpriseYesYes
      Windows 8.1Windows 8.1 (Basic), Pro, EnterpriseYesYes

     

    Requirements for Administrative Components


    Ensure that the following prerequisites are installed before installing the administrative components.

     

    PREREQUISITES

    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 laterPharos 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.
    Microsoft® .NET Framework 4.0 Microsoft .NET Framework 4.0 should be present on any computer running Pharos Administrator, Pharos Remote, Pharos Station, and Pharos Reports.

     

    *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.

     

    Requirements for Client Components


    The following table lists the hardware requirements for all the Uniprint Suite client components, including 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 2008Standard, EnterpriseYesYes
      Windows VistaBusiness, Enterprise, UltimateYesYes
      Windows 7Enterprise, Professional, UltimateYesYes
      Windows 8Windows 8 (Basic), Pro, EnterpriseYesYes
      Windows 8.1Windows 8.1 (Basic), Pro, EnterpriseYesYes
      Mac OS X10.6-10.8NANA

     

    Supported SignUp Client Platforms

     

    The SignUp Client supports the following platforms:

     

    OPERATING SYSTEM

    EDITION

    32-Bit Support

    64-Bit Support

      Windows 8.1

    Windows 8 (Basic), Pro, Enterprise

    YesYes

      Windows 8

    Windows 8 (Basic), Pro, Enterprise

    Yes

    Yes

      Windows 7

    Home Basic, Home Premium, Business, Enterprise, Professional, Ultimate

    Yes

    Yes
      Windows VistaHome Basic, Home Premium, Business, Enterprise, UltimateYesYes
      Mac OS X10.6-10.8NANA