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? |
|
All Pharos Components |
Yes |
Servers are installed with a supported OS (Windows 2012 R2, 2016,2019, 2022). |
|
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. |
|
Servers have Web Server (IIS) role installed. |
|
|
|
Any computer running Pharos Print Center requires
The Sentry Print related services in the Pharos API require the following
Pharos recommends installing the IIS before the DotNET core hosting bundle. The DotNET Core hosting bundled on the CD image includes ASP.NET Core. If the bundle is installed without installing the IIS first, the ASP.NET Core doesn’t get configured resulting in some services not running correctly. |
|
Servers are live on the network and are able to access the Internet with a web browser. |
|
The 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 a 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. |
|
SQL Server for Pharos (often installed on Pharos Principal Server) |
Yes |
Supported SQL Server version with the latest Service Pack. |
|
NT and SQL (Mixed Mode) authentication are enabled. |
|
SQL Administrator (SA) account has been granted logon rights. |
|
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) |
Yes |
Every print server has printer drivers installed for all printing devices to be controlled by Pharos. |
|
The naming convention for Pharos print queues has been provided to the Installation Engineer. |
|
The naming convention for all “devices” and “release stations” has been provided to the Installation Engineer. |
|
Each Print Server has the Print Server Role installed. Note: Microsoft LPD Service should not be installed as that will conflict with Uniprint. (All supported OS). |
|
Printers |
Yes |
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) or port 9100 (RAW). |
|
Pharos PC Release Stations (if used) |
Yes |
PCs are in place and ready for software installation. |
|
Pharos iMFPs (if used) |
Yes |
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) |
Yes |
Card Readers are onsite and configured (if applicable). |
|
Test card(s) have been sent to Pharos for verification of card type and data |
|
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). |
|