<< Click to Display Table of Contents >> Navigation: Preparing for FYI > Best Practices for Server Setup |
FYI Server is server class software and requires a powerful, designated server to ensure that performance is optimal. Some IT departments may try to host FYI Server on a virtual machine as opposed to a designated server in an effort to save money without allocating enough system resources. Unlike Concordance (where processing is performed on individual workstations), all processing for .FYI and FYI Reviewer users is done on the FYI Server. When implementing FYI Server, we recommend that you invest in the best server your organization can afford, that meets or exceeds what is stated in the system requirements.
FYI Server is not a web server and cannot work through a proxy server. FYI must have an open connection through a named port. |
When planning your server setup, there are a few things to consider beforehand. We recommend that you reference the Best Practices for Server Setup when planning your server configuration.
Best Practices for Server Setup: FYI Server |
|
---|---|
FYI Server |
|
Minimum |
Microsoft Windows Server 2016 |
Dual Xeon (HT) (hyper-threaded) processors User capacity is metered by the hardware Each Pentium CPU supports 25 concurrent users Each Xeon or hyper-threaded CPU supports 50 concurrent users |
|
4 GB RAM or higher |
|
100 MB available hard disk space |
|
Disk caching, fault tolerant RAID 1+ 0 array controller |
|
High-speed Internet connection, 1.5mbps or faster |
|
Best Practice |
Ample CPU + RAM dependant on the number of users and how they use it * Virtual machines are not recommended due to scalability limitations |
Failover Redundancy |
|
T3 or OC1 Internet Connections |
|
FYI Server Security |
|
Standard |
Behind Firewall |
Secure Access |
|
Best Practice |
Hardware Firewall |
Network/Server Monitoring |
|
24-hour Surveillance |
|
Fingerprint/Retina scan access |
|
FYI Server Backups |
|
Standard |
Incremental secure backups |
Best Practice |
Data Mirroring/Clustering (SQL Server) |
Disaster Recovery Plan |
|
Offsite Data Recovery |
|
Server Support |
|
Required Staff |
CCSA |
CCFA |
|
Project Manager |
|
Network Administrator |
|
Technical Support |
|
Best Practice |
24/7 Technical Support |
CCST |
|
Paralegals |
|
Print Job Clerks |
|
Project Managers Law Firm Experience, Previous Vendor Experience, and EDD/Processing Experience |
|
Database Administrators Active Directory Administrators Certified DBAs, Very Technically Savvy, Detail Oriented, and have Network Administration Experience |
|
FYI Server Setup |
|
Standard |
Be sure to have the recommended minimum hardware resources |
Best Practice |
Create a separate Microsoft Windows account for FYI that has network rights to run services |
Administrator rights are required to install the ActiveX control. If you do not have administrator rights, please see your System Administrator. |
|
Store active databases on the FYI Server itself to eliminate as much network latency as possible. |
|
Be sure your FYI Server is not on a Web server. |
|
Store the TIFF image files associated with your databases on the FYI Server to eliminate as much document and production latency as possible. |
|
FYI Reviewer Setup |
|
Standard |
On the Client: Allow ActiveX controls and add the trusted site. If you are using Internet Explorer 7 or 8, make sure that the Enable Protected Mode option is not selected as this may cause problems when accessing or printing images with FYI Reviewer. |
Best Practice |
Always have the user reinstall the ActiveX control when there is an update |
Concordance .FYI Setup |
|
Standard |
Provide the .fyi file to the client to allow them greater control over their data |
Best Practice |
Make sure that clients/users are using the latest version of Concordance, Concordance Native Viewer or Concordance Image (Opticon) |
We recommend that you do NOT allow access to the following menu items: •File > Modify •File > Reindex •File > Index •File > Administration •File > Begin Program •File > Edit Program •Edit > Validation •Edit > Delete and undelete |