New Users: while you are reading this topic, we suggest that you start the following download:
http://cdn.copia.com/files9/COPIAINSTALL9.exe. Note that all cdn.copia.com links are case-sensitive. Install this file in your folder C:\Program Files (x86)\Copia and run it from there.
Then, when you reach Installation Management below, click on the COPIAINSTALL9 link.
For a new install where you want to setup the COPIA share on a separate Windows file server, so this first, using COPIAINSTALL9; otherwise run COPIAINSTALL and then the server installer CopiaServerInstall91xxxx.exe on your first or only server node as desribed in the next paragraphs.
When you run COPIAINSTALL9 and have used it to set up the COPIA share and the CopiaFacts license, you can use Check For Updates in COPIAINSTALL9 to find the current CopiaFacts release and download it, and also to download the installer for your chosen FoIP interface.
 | Some customers have secure evironments which block the view of available downloads in COPIAINSTALL9. Please contact Copia Support for direct download links for the current release. These will have the form: |
CopiaServerInstall910vvv.exe Copia Server
CopiaClientInstall910vvv.exe Copia Workstation Client
These filenames (case sensitive) follow the URL http://cdn.copia.com/files9/NETBIN/
These installers (and the FoIP interface installers) MUST be downloaded to your COPIA share in the NETBIN foldert and MUST be run from COPIAINSTALL9.exe.
Delails and links for the VoIP and and hardware installers are in the Hardware and IP Ports topic.
Preparing for CopiaFacts Installation
Please check ALL the following items before you start to install CopiaFacts for the first time:
•Go to the System Overview topic and check the Hardware, Operating System and Network requirements to run CopiaFacts components.
•For machines where you will be running CopiaFacts server components, we recommend setting up a user named CopiaFacts with local administrator privileges and using this account to run the installation and the server applications.
•You should normally allocate an e-mail address for this 'CopiaFacts' user, to be used as the sender address for system administrative notifications and also as the default 'envelope sender' for e-mails sent from the system.
•For machines where you will be running CopiaFacts server components, you will need to install BOTH the CopiaServerInstall installer AND the appropriate drivers for IP Ports (for example TE-Systems XCAPI drivers) or hardware.
•For larger systems using a separate file server, you will need to set up a COPIA share on this machine, which needs to be available to all accounts running CopiaFacts software. DO THIS FIRST. Copia refers to this as the application data area and there is normally a FAXFACTS and a NETBIN folder in the root of the COPIA share. If you are running a workgroup, then each user must be a user on this machine.
•If your file server on which the COPIA share will reside is a Windows machine, use COPIAINSTALL9 to set up this share and its NETBIN and FAXFACTS sub-folders. If it is a file server which is not a Windows Server, follow the instructions for Advanced Configuration Features. DO THIS FIRST, before running any other installers.
•If you will be running COPIAFACTS and FFEXTERN in Windows Service mode, follow the instructions for installation of CFMSG as the services communication service, preferably as a on the fileserver where the COPIA share is located.
•Make sure that you turn off indexing by Windows on the drive containing the COPIA share. It can severely impact performance if Windows creates full-text index entries for every short-lived transaction file. You can do this from the Explorer properties dialog for the drive.
•We recommend configuring your server to warn on disk space low. If you do not enable clean-up using CFHK, lack of space on disk can cause CopiaFacts to start reporting multiple failures. This link describes a way to do this.
•If you will be using multiple channels of e-mail on any machine running a COPIAFACTS server, we recommend that the machine should have a dedicated, externally-visible IP address. You will need to use EMSETUP to configure e-mail parameters after installation.
•Users of the CopiaFacts SMTP Gateway will need to have port 25 opened for incoming e-mail. or 465 / 587 when TLS is configured. You will also normally need a new domain name such as fax.mycompany.com, and to set up an MX record in your DNS settings pointing to the machine running the Gateway. This will then allow you to accept incoming mail to for example 6417416000@fax.mycompany.com and have it forwarded by CopiaFacts to 6417416000 as a fax.
•If you plan to convert Word, Excel or Powerpoint documents to fax, you will require a copy of Microsoft Office (or LibreOffice) to be installed on each machine which is to be used for document conversions. These conversions no longer require the Document Converter print drivers and default to saving the document as PDF and then using the built-in PDF converter. You can optionally include the print drivers (if available for your operating system) if you prefer to use this conversion method, or if you wish to use Acrobat for PDF conversions instead of the built-in converter to convert PDF documents to faxable format.
•The CopiaFacts installation programs have now joined many other CopiaFacts programs in no longer supporting Windows versions earlier than Windows 10 or Server 2012 operating systems. As a result installation on these insecure operating systems is no longer possible.
•Please read all the Important Links in the next section below.
Important Links
Please read and make a note of the following topics, either in the CHM or on-line:
•The Quick Reference topic for learning about basic fax operations.
•Sending E-Mail for basic e-mail tasks.
•The System Reliability topic for advice on backup and housekeeping tasks.
•The OMACHECK utility to monitor system components and notify problems.
•The white paper on CopiaFacts Security Issues.
•Checking for Updates with the COPIAINSTALL9 utility.
•Checking on-line for details of the latest changes and enhancements.
Installation Management
Copia provides only one Installation Management program for version 9:
•COPIAINSTALL9 manages Internet installs and downloads from the Copia CloudFront content delivery network (CDN) site.
•To revert to an earlier release, please download COPIAINSTALL version 8.3 from http://cdn.copia.com/files83/COPIAINSTALL.exe
Follow the links above for a description of these installation processes.
Installers
There are two separate installers which are installed or downloaded, and then run, by the Installation Managers (xxx below indicates the build number):
•CopiaServerInstall91xxxx.exe installs CopiaFacts Server components, such as COPIAFACTS, Document Converter, SMTP Gateway, Services, etc. An option in this installer can be selected to install CopiaFacts administration tools only: this is specifically for use by the site administrator to install software on his or her own machine.
•CopiaClientInstall91xxxx.exe installs CopiaFacts desktop client components and print drivers, viewer, status viewer etc. However you should normally not run this directly: instead use CopiaClientInstall9.exe as described in the topic Installation Notes - Client. This installer cannot be used when your CopiaFacts license includes the 'Thin Client' option. which you must therefore ask Copia to remove if it is no longer needed. The terminal services print driver interfaces are no longer supportrd in version 9 of CopiaFacts.
If your security policies prevent you from downloading using the COPIAINSTALL9 program, you can use another means of downloading and copy the required installers to the local COPIA\NETBIN folder. The source path to use is http://cdn.copia.com/files9/NETBIN/ followed by the name of the installer above, for example http://cdn.copia.com/files9/NETBIN/CopiaServerInstall910355.exe for server components build 9.1.0.355. The pathname is case-sensitive,
The installers will be downloaded by COPIAINSTALL9 to the NETBIN folder in your COPIA share. You can run the installer directly from there if you wish to install on multiple machines, or use the COPIAINSTALL9 or COPIACLIENTINSTALL9 managers to run the installers from there.
You should also download installers (from the 'downloads list') for the fax ports or voice ports (or hardware) that your installation requires. There is no need to download all of these installers. Download links are also available in the Hardware and IP Ports topic, but later versions may be available in the COPIAINSTALL9 list.
To install selected administration tools only, on an administrator workstation, run the Server installer and select Administration Tools Only from the installer task list.
In each case the installer filename will be followed by the six-digit version number of the principal component contained in the installer. Release-candidate builds of the installers will have a _PW suffix on the filename, and will require a password. Ignore these builds unless you have been advised to use them by Copia support.
| If you run one of these installers manually, you must run it from the NETBIN folder. Do not copy the installer elsewhere before running it. |
Upgrades
We recommend not upgrading your CopiaFacts system every time you see that a new build is available. If your system is working correctly and you do not need new features from the new build, there is no need to upgrade. However you should schedule updates at convenient intervals to ensure that you have the latest fixes and features.
Before installing an upgrade, consult the latest on-line version of Appendix M and review the changes to see if you are affected by any fixes or changes since the release you are using.
Also check the release notes which will highlight any changes which might alter current operations.
| More customers are now using a virtual machine to run a CopiaFacts server. If you are using a VM, always ensure that you have made a backup or snapshot before installing an upgrade. |
It is good practice to run regular virus and malware checks on all machines, including nodes running CopiaFacts software. However the CopiaFacts command and control files in the COPIA share are text files which cannot contain viruses, and continuous monitoring of them is not desirable.
| We strongly recommend excluding the FAXFACTS folder in the COPIA share, and its subfolders, from scanning by an antivirus utility. This folder should contain no executable modules, and examining the large numbers of files which are often found below this folder can severely impact performance. |
If you operate a bureau and clients upload files such as DOC or PDF directly to subfolders below the FAXFACTS folder, you may wish to selectively enable scans of such folders. But if your antivirus utility requires user intervention on detection of a suspect file, you may find that automated conversions are blocked by this.
Malware can cause excessive CPU utilization, sometimes in programs other than the malware, and can block or divert IP ports. So it remains important to make regular scans at times of low traffic.
From time to time we encounter false positives with specific anti-virus utilities, which will be noted here. If your AV reports a potential problem with a CopiaFacts application, we suggest using VirusTotal.com which will submit the file to a large number of AV checkers and allow you to confirm that it is genuine. You should not be concerned by a browser reporting for example that a file is 'infrequently downloaded and may be unwanted'.
| We are currently aware of a false positive reported by a small number of anti-virus utilities in the BladeWare 2.4.18.0 MSI installer. This may trigger when the CopiaFacts installer for BladeWare SIP installs or runs their MSI installer. You would need to whitelist the TEMP folder into which the MSI is extracted, and probably also the Commetrex\openmedia folder under Program Files (x86) in which the DLL falsely detected as malware should be installed. |
