Instant InfoSystems. Open Text Fax Server (RightFax) Preinstallation Guide. January 20, 2011

Transcription

1 Instant InfoSystems Open Text Fax Server (RightFax) Preinstallation Guide January 20, 2011 Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 1 of 15

2 Table of Contents Introduction... 3 Hardware Requirements and Supported Software... 3 Service Accounts... 5 Domain Account... 5 SQL Account... 6 IUSR Account... 6 Dialogic Brooktrout Fax Board... 6 T1/PRI Ordering... 7 T1/Robbed Bit Signaling (RBS) Ordering Fax Over IP (FoIP)... 9 Firewall Ports RightFax Connector for Exchange RightFax Connector for Exchange RightFax Connector for SharePoint RightFax Post Installation Considerations Time Sync Issues Fax aging Microsoft SQL and Open Text Fax Server (RightFax) Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 2 of 15

3 Introduction This guide provides prerequisites and system requirements to support an installation of Rightfax 9.4 Server. Hardware Requirements and Supported Software Open Text Fax Server (RightFax) Supported Virtual Platforms Virtual Operating VMware ESX server or later Systems VMware ESX server 3.5 or later VMware ESX server 4.0 or later VMware ESX server 4.1 or later VMware ESXi server or later VMware ESXi server 3.5 or later VMware ESXi server 4.0 or later VMware ESXi server 4.1 or later Microsoft Hyper-V Server 2008 R2 or later CAUTION It is recommended to dedicate a virtual machine to each fax server. Of course, no virtual fax server can contain fax board hardware. Sending and receiving fax documents requires FoIP or dialing rules to route faxes to and from a physical server that contains one or more fax boards i.e., a Remote DocTransport. When utilizing a virtual machine for each fax server the Media Access Control (MAC) address on the network interface controller (NIC) should to be set to static. If a virtual RightFax server is recovered without this setting licensing may be lost causing a potential outage of the fax server. Open Text Fax Server (RightFax) Supported Operating Systems and Software Operating Systems Windows Sever 2003, Standard Edition x86, Service Pack 2 or later Windows Sever 2003 R2 Standard Edition x86, Service Pack 2 or later Windows Server 2003, Enterprise Edition x86, Service Pack 2 or later Windows Sever 2008 R2, Standard Edition x64** Windows Sever 2008 R2 Enterprise Edition x64** Windows Server 2008, Standard Edition x86 and x64** Windows Server 2008, Enterprise Edition x86 and x64** Windows Cluster Services Terminal Services Windows 2003 Microsoft Windows 2003, Enterprise Edition x86, Service Pack 2 or later cluster services Supports active-passive clustering Active-active clustering is not supported Internet Browsers Microsoft Internet Explorer 6.0 Service Pack 1 or later ** Feature Pack 1 for Open Text Fax Server, RightFax Edition Version 9.4 is required for x64 support. The software runs in 32-bit emulation mode on x64 systems. A separate version 9.4 installation program for x64 systems is available in the Open Text Knowledge Center. Download and install the x64 installation program for Open Text Fax Server, RightFax Edition version 9.4, and then install Feature Pack 1. Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 3 of 15

4 CAUTION With Windows Server 2008, Microsoft does not support server-side document conversion. To support server-side document conversions, set up a remote WorkServer on a Windows 2003 server, then install Microsoft Office 2003 and install the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available at no cost from Microsoft. Office 2007 PowerPoint documents with watermarks have problems converting. Office 2007 Excel documents using the column feature (a new feature in Office 2007) have problems converting. CAUTION With RightFax 9.4, port 1052 and 1053 are no longer supported. Port 1052 and 1053 were used by the API and many application integrations in previous versions of RightFax but is no longer available in version 9.4. If you have used the COM API, older FaxUtil client or any communications to RightFax via 1052/1053 then you will need to update your configuration to support ports and Microsoft SQL Server Operating Systems SQL 2005 Standard Edition SQL 2005 Enterprise Edition SQL 2008 Standard Edition SQL 2008 Enterprise Edition SQL Server 2005 Express Edition Hardware Open Text follows the minimum hardware requirements specified by Microsoft at the following links: sysreqs/2000/default.asp Most installations will need additional memory and processor speed than the minimum. Open Text Fax Server (RightFax) Hardware Requirements Minimum Computer/processor: 2.6 GHz or higher Pentium IV-compatible CPU Memory: 1 GB RAM Hard disk: 10 GB free space. Installed programs require 1.2 GB* CPU: Single and dual CPU systems Optical drive: DVD drive Display: SVGA (800 x 600) or higher resolution monitor Keyboard: Required Recommended Computer/processor: 3.6 GHz or Higher Pentium IV compatible CPU Memory: 2 GB RAM Hard disk: 10 GB free space. Installed programs require 1.2 GB* CPU: Dual CPU systems Optical drive: DVD drive Display: SVGA (1024 x 768) or higher resolution monitor Keyboard: Keyboard and mouse Active-active clustering is not supported *Hard disk minimum requirements do not include space for storage of document images. To calculate needed disk space, Open Text recommends using an estimate of 35kb per page. Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 4 of 15

5 Open Text Client Applications Supported Operating Systems and Software Operating Systems Windows XP Professional Service Pack 2 or later, x86 and x64 versions Windows Vista x86 and x64 versions Windows 7, x86 and x64 versions ** Requires RF9.4 FP1 Internet Browser Requirement Internet Explorer 6.0, Service Pack 1 or later, is required for RightFax Web Access and Enterprise Fax Manager Web Edition Supported Systems Microsoft Exchange Exchange Server 2003 Service Pack 1 or later Exchange Server 2007 Exchange Server 2010 ** Requires RF9.4 FP1 Microsoft Outlook Outlook 2000 Outlook XP Outlook 2003 Outlook 2007 IBM Lotus Domino Notes Client and Domino Server Lotus Domino Web Access Lotus Notes R6.5.1 Lotus Notes R7 Lotus Notes R8 Lotus Domino Web Access 8 Service Accounts There are several accounts that may need to be setup for RightFax 9.4 to be installed and configured. Domain Account The RightFax server will have at least one domain account with Full Local Admin permissions to all Servers running the RightFax software, including the application servers and any Remote Board servers. This account will need to have access to network folders, printers, Exchange File Share for the RightFax connector and obtain information from Active Directory. The following RightFax Services will run under the corresponding account: o RightFax Server Module o RightFax Database Module o RightFax DocTransport Module o RightFax Workserver Module o RightFax Server o RightFax Gateway for Exchange o RightFax Remoting o Captaris Sync Module o Captaris Conversion engine o RightFax Integration Module ( RightFax Automated Fax only) Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 5 of 15

6 SQL Account Open Text Fax Server (RightFax) Preinstallation Guide If a SQL account is preferred over a Domain Account for SQL access, the SQL Permissions required for this account are provided below. o Create database o Create table o Create procedure o Create view o Create rule o Create default The second account is used by and during Setup to run SQL stored procedures and subsequently by RightFax services requiring a SQL connection. To execute stored procedures, Setup will create a new RightFax database role (called DB_executer) and will assign this account to the role. IUSR Account For anonymous access to web services on the RightFax server, the IUSR account has to be enabled. This account will only be required on a RightFax server where the WebUtil and XML/JAVA integration will be used. If we are unable to use the Windows IUSR account, a new account will need to be created and used to allow Anonymous access authentication. Dialogic Brooktrout Fax Board The Dialogic 1034 line of fax boards require a full-length PCI-X or PCI-E slot. Cards designed for PCI-X will not work in a PCI-e slot and visa versa, so it is important to make sure you are ordering the correct card. As a general rule, newer computers use PCI-E slots while older computers use PCI-X. PCI-X is often confused with PCI-Express. PCI-Express is commonly abbreviated as PCI-E or PCIe. While they are both high-speed computer buses for internal peripherals, they differ in many ways. The first is that PCI-X is a parallel interface that is directly backward compatible with all but the oldest (5-volt) standard PCI devices. PCI-e is a serial bus that offers no compatibility with older buses. When purchasing certain products for your system, you may be given the choice between PCI-X and PCI-E versions of a card. Cards designed for PCI-X will not work in a PCI-E slot and visa versa, so it is important to make sure you are ordering the correct card. The most obvious visible difference between PCI-E and PCI-X is that PCI-X has two separators in it while PCI-e only has one. Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 6 of 15

7 PCI-X PCI-e Note: PCI-X Slot has two separators Note: PCI-e has a single separator. This is a x16 PCI-e slots come in a variety of physically different sizes referred to by the maximum lane count they support, ie. x1, x2, x4, x8, x16 and x32. A PCI-e card will fit into a slot of its size or bigger, but not into a smaller PCI-e slot. So the FORM Factor (Length) is also very important when ordering a fax card. Brooktrout 1034 Boards support 4x or larger connectors. T1/PRI Ordering When you order T1-PRI service from the telco or service provider, provide the following information: Product Manuf: Product Name: Signal Protocol (or 'trunk type'): Frame Mode: Line Coding: Clock Master: Dialogic Corporation (formerly: Brooktrout Technology) Dialogic Brooktrout TR1034+yxH-T1 Fax Board (where 'x' denotes the number of channels active on the card, ie: 4, 8, 16, 24 and "y" denotes for 'P' for PCI and 'E' for PCIe) Common Channel Switching Extended Super Frame B8ZS The switching device providing the PRI line to the Brooktrout TR1034 Fax Board must act as NETWORK / Clock Master, or pass master clock signal seamlessly from PSTN. The Brooktrout TR1034 Fax Board(s) must act as TERMINAL end / User Side. # of Channels: 24 (23 "B" channels plus one "D" channel, commonly written "23B+D") B Channel Provisioning: B Channel Service: D Channel Service: Packet Handlers: Channel Service: Compatible Switch Types: Circuit-Switched Voice & Data Voice; as fax is considered voice, the line would be configured as though voice calls were being placed over it. Signaling only with the D-channel on channel 24 of the T1-PRI line. No packet handlers other than the D-channel. 64Kbps clear channel service end-to-end for every call. Your telco or service provider needs to tell you the type of switch that is providing the PRI line to the Brooktrout TR1034 Fax Board; the list of supported switch types is in the Brooktrout configuration tool. Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 7 of 15

8 Compatible Variant Types: Called Party Number: Your telco or service provider needs to tell you the program variant programmed on the PRI line; the list of supported variant types is in the Dialogic Brooktrout configuration tool. This is what the ISDN world calls 'DID' or 'DNIS'. Normally the last 4 digits of the number dialed; required for inbound routing. Please confirm with your telco or service provider the number of CPN digits it will be providing to you on inbound calls. NOTE: If the total number of digital channels on the Brooktrout TR1034 Fax Board(s) will not allow for all 23 B-channels to be utilized (for instance, if you are using a Brooktrout TR1034+P/E4, 8, or 16H-T1 Fax Board, where 'x' denotes number of activated channels on the board), you will need to tell to your telco or service provider which B-channels you will be using. Then, the telco or service provider will not direct traffic to B-channels that are not mapped to functioning Brooktrout TR1034 Fax Board channels. This is sometimes called a 'fractional PRI' or 'partial PRI ' line. T1/Robbed Bit Signaling (RBS) Ordering Ordering T1 Robbed Bit Signaling (RBS) Service for a Dialogic Brooktrout TR1000 Media Board or Dialogic Brooktrout TR1034 T1 Fax Board: Product Manuf: Dialogic Corporation (formerly: Brooktrout Technology) Product Name: Signal Protocol (or 'trunk type'): Frame Mode: Line Coding: Clock Master: # of Channels: 1-24 Dial Tone: Dialogic Brooktrout TR1034+yxH-T1 Fax Board (where 'x' denotes the number of channels active on the card, ie: 4, 8, 16, 24 and "y" denotes for 'P' for PCI and 'E' for PCIe) E&M Wink (generally used) or E&M Immediate (note 2) Extended Super Frame (ESF)(generally used) or Super Frame (SF) / D4 B8ZS (generally used) or AMI The switching device providing the PRI line to the Brooktrout TR1034 Fax Board must act as NETWORK / Clock Master, or pass master clock signal seamlessly from PSTN. The Brooktrout TR1034 Fax Board(s) must act as TERMINAL end / User Side. Optional CSU: NONE on-board. (note 3) DNIS Digits: Wall Jack Required: Connector on TR1034 Board: DTMF (generally used) or Pulse USOC-RJ-48C See note 4 below Note 1: Additional information on 'T1 Service Type': When using a Brooktrout TR1034 Board, the type of T1 line that must be supplied is a Robbed-Bit Signaling (RBS) T1 line, which also may be described as an A/B signaling T1 line, or an E&M tie trunk. This type of signaling is in-band, meaning the signaling information is carried on the same channel as the traffic. The physical connection must be a 4-wire connection; no other type of physical connection is Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 8 of 15

9 supported by the Brooktrout TR1034 Board. Open Text Fax Server (RightFax) Preinstallation Guide Note 2: Additional information on 'Signal Protocol': The Brooktrout TR1034 Board needs the signal protocol to be consistent across all T1 channels, in both directions. By 'E&M', it is meant that the signaling bits do whatever the A-bit does. Note 3: Additional information about 'CSU': The FCC requires an external CSU/DSU device to be installed on any T1 digital line supplied directly from your local telephone service provider. Note 4: Connecting the Brooktrout TR1034 Board to T1 Telephone Service Connecting the Brooktrout TR1000/TR1034 Board to T1 Telephone Service If your telco or service provider or PBX support personnel are not familiar with the Brooktrout TR1034 Board, and thus are not sure how to treat it, you may tell them to view the Brooktrout TR1034 Board as a PBX. The telco or service provider should set up a 'tie trunk', or 'tie line', from its side to the Brooktrout TR1034 Board, just as if it were setting up a line to a PBX. The service must be 'tie line' or 'tie trunk'. Offpremise 'extensions', or 'stations', are not supported. Cable note: Although standard CAT-5 (unshielded) cable will work in many situations, Shielded Twisted Pair (STP) cabling can be used to provide protection against electrical interference, particularly on longer cable runs. Additional information on signal regeneration, and CSUs: The cable length between the last signal regeneration point on the T1 circuit and its termination point (the connector on the Brooktrout TR1034 Board) determines whether you must connect the Brooktrout TR1034 Board to an external CSU (Channel Service Unit) or directly to a T1 circuit. If the last point of signal regeneration on the T1 circuit is less than 500 feet in cable length from the Brooktrout TR1034 Board, you do not need to connect the Brooktrout TR1034 Board to a CSU. If the cable length from the Brooktrout TR1034 Board to the last point of signal regeneration exceeds 500 feet (even if installed behind an in-house PBX system), you must connect the Brooktrout TR1000/TR1034 Board to an external CSU device and the CSU to the T1 circuit. Fax Over IP (FoIP) If you are installing RightFax and utilizing Fax over IP (either SR140 or the N port of the TR1034) then please review the checklist. If you have not received the checklist, please let your technical contact at Instant InfoSystems know. Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 9 of 15

10 Below is the list of interoperable devices. If you do not have (or plan to have before installation) one of the following products then please let Instant InfoSystems know immediately. Dialogic Brooktrout Tested FoIP Interoperability Firewall Ports The following ports are required for proper operation of the SR140/TR1034 FoIP boards and troubleshooting assistance: Port 5060 SIP signaling port Port 80 TCP port for Dialogic troubleshooting assistance using Copper Conferencing s Raindance application. Port 1157 TCP port for Dialogic troubleshooting assistance using Copper Conferencing s Raindance application. Port 8080 TCP port for HTTP (license activation - required for automatic registration via Internet; otherwise, manual registration via Dialogic Website is required) Port 1719 H.323 gatekeepers Port 1720 H.323 signaling port Ports to UDP ports for FoIP traffic (configurable) RightFax Installation Media Prior to installation/upgrade of the RightFax software the customer should download the RightFax 9.4 media, all applicable connectors/modules and subsequent updates: Feature Pack 1 (FP1), Service Release 3 (SR3) from OpenText Knowledge Center Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 10 of 15

11 RightFax Connector for Exchange 2003 Open Text Fax Server (RightFax) Preinstallation Guide The RightFax Connector for Exchange requires both a gateway service (installed in RightFax server) and a connector service (installed on Exchange server). The gateway service requirements will fall under the RightFax Server requirements. Below are the requirements for the connector services. Requirements Exchange Server 2003 Service Pack 1 or later Microsoft.NET Framework 2.0 Microsoft Visual C runtime components Microsoft Windows Installer 3.1 Supported Microsoft Windows Operating Systems Windows Server 2003 Standard x86 Windows Server 2003 R2 Standard x86 Windows Server 2003 Enterprise x86 Schema Modifications During setup, RightFax design elements are inserted into the Active Directory schema. These changes are minor and can be viewed before you run setup at: Because setup writes to Active Directory, the Windows account used to install the connector must belong to the following groups: Domain Admins, Enterprise Admins, and Schema Admins. This only required for the 2003 version of the connector. RightFax Connector for Exchange The RightFax Connector for Exchange requires both a gateway service (installed in RightFax server) and a connector service (installed on Exchange server). The gateway service requirements will fall under the RightFax Server requirements. Below are the requirements for the connector services. Requirements Microsoft Exchange 2007 Server configured for the Hub Microsoft.NET Framework 2.0 Microsoft Visual C runtime components Microsoft Windows Installer 3.1 Supported Microsoft Windows Operating Systems Windows Server 2003 Standard x64 Windows Server 2003 R2 Standard x64 Windows Server 2003 Enterprise x64 RightFax Connector for SharePoint 2007 RightFax Server prerequisites Microsoft Windows Server 2003 Access to an SQL Server 2005 database Administrator privilege on the local machine Microsoft.NET Framework 3.0 RightFax Server Version 9.3 and most current Service Release or Feature Packs English Only Support SharePoint Server Microsoft Windows Server 2003 Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 11 of 15

12 prerequisites IIS 6.0 Administrator privilege on the local machine Microsoft.NET Framework 3.0 Microsoft SharePoint Server 2007 with most recent updates English Only Support Configuration prerequisites The RightFax Connector for SharePoint 2007 deploys two distinct pieces of software: one that you install on the RightFax server to communicate with SharePoint, and one that you install on the SharePoint server to communicate with RightFax. CAUTION: You must install RightFax and SharePoint on different physical computers. Captaris does not support any configuration in which both products, or both pieces of the Connector software, are on the same computer. Some of our customers have deployed a "single computer" configuration for testing, demonstrations, etc. in the past. Despite this acknowledgement that such configurations might well exist among our customers, Captaris recommends that you use the RightFax Connector for SharePoint 2007 only in a "dual server" configuration. We do not support the "single server" configuration. RightFax Post Installation Considerations Time Sync Issues (VMware or later) The RightFax application checks the time of its host server with that of the SQL server to ensure accurate recording of data in the SQL database. If the discrepancy between the two is greater than 5 minutes, RightFax produces errors and shuts down the Server Module, disabling the RightFax server. VMware time sync and Windows Time Services do not see the other, so there is risk of overcorrecting time, causing a large time drift to occur. Windows Time Services on the guest are normally set to obtain their time data from domain controllers. By enabling the time sync through the VMware Tools installed on the guest OS, it will look to the host clock for its time data and thus avoid the time sync issue. Fax Aging Policy The RightFax software (Enterprise edition) includes the ability to automatically set the amount of time a fax is kept (automatic fax aging) in the RightFax database. By default this setting is set to no aging and faxes are kept for an indefinite period of time. For RightFax Business edition users the automatic aging box in Enterprise Fax Manager is grayed out. Business edition users of RightFax can enable the automatic fax aging policy by upgrading to the Enterprise Edition. Fax aging can also be completed manually using commands. For more information on fax aging contact the Support Help Desk or your Account Manager. Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 12 of 15

13 Microsoft SQL Licensing Guidelines Excerpt from Open Text Knowledgebase. Article Number: MICROSOFT SQL LICENSE DEFINITIONS Microsoft has three licensing models available that may apply to a RightFax 9.3 deployment. Information about these models, in their entirety, can be found at In summary, the three models are: Processor Licensing Model This is a model by which a license can be acquired that covers any CPU that runs a SQL Server. By using this model, additional licensees for users and devices that connect are not required. Server plus Device CALs A device Client Access License (CAL) is a license for a device that connects to a SQL Server. In this licensing scenario, one license is acquired for the SQL Server, and additional licenses are acquired for any number of devices that will connect to SQL. Devices can be defined as a user's laptop, home PC, etc. In many instances, once you exceed a certain number of device CALs, it is more logical to acquire a processor license. Server plus Device licensing may apply to a RightFax scenario. See section below titled, Captaris guidelines in regard to Microsoft SQL licensing for more details. Server plus User CALs A user CAL is a license for users that connect to a SQL server. In this licensing scenario, one license is acquired for the SQL Server, and additional licenses are acquired for any number of users that will connect to SQL. In many instances, once you exceed a certain number of user CALs, it is more logical to acquire a processor license. Server plus User licensing may apply to many RightFax scenarios. See section below titled, Captaris guidelines in regard to Microsoft SQL licensing for more details. CLARIFICATIONS AND DEFINITIONS OF RIGHTFAX RELEVANT TO MICROSOFT SQL RightFax is a Windows 32-bit client server faxing application. Using Microsoft definitions, the RightFax Server application is a "multiplexer" in which it manages requests from all of its connected clients and services that the server then passes through to SQL. (Source: Microsoft: SQL Server 2005 Licensing; section on "Multiplexing: Use of Middleware, Transaction Servers, and Multitiered Architectures" at df9c5c2/SQLServer2005Licensingv1.1.doc In the context of Microsoft licensing, a multiplexer does not require a CAL, whether user or device, unless a client application such as Enterprise Fax Manager (EFM) or FaxUtil are run on the same machine as the RightFax multiplexer. Otherwise, in the instances where the RightFax multiplexer is on a selfcontained server machine, and the administrators use FaxUtil or EFM from a separate machine like a desktop, then that RightFax system does not require a CAL and can be regarded as a multiplexer. Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 13 of 15

14 The RightFax product has many client applications such as FaxUtil, RightFax Web Access, EFM, Fax Reporter and Print-to-Fax (the RightFax printer driver). End-users and administrators may use these client applications to connect to SQL via RightFax, and they are typically deployed on other machines across an enterprise such as user's desktops and laptops. These are considered clients that access the RightFax database in SQL, and in the event of non-cpu licensing, are eligible for a CAL. Whether that CAL is device-based or user-based is relative to how the customer wishes to license it, depending on their usage compared to the Microsoft guidelines. Furthermore, RightFax utilizes various server services to perform processing and job tasks. There are many RightFax services such as the Workserver, DocTransports, RPC services, BoardServers and queue handlers. Some of these services may be installed remotely, such as DocTransports and Workservers. These services, whether installed locally or remotely, are not considered device or user clients for Microsoft licensing, because some of these services connect to SQL for purposes of processing their own data via the multiplexer RightFax Server and in fact, these services are connecting to SQL directly. And finally, there is a new feature introduced in RightFax 9.3 in which the DocTransport service communicates to the RightFax database directly. A new "Receive Queue" now resides in SQL to process received faxes from remote BoardServers (remote doctransports). This is not considered a "client" or a "device" in the context of Microsoft licensing because this service connects to SQL for purposes of processing its data; no device or user clients are connecting. Therefore, DocTransports do not require individual device or user CALs. CAPTARIS GUIDELINES IN REGARD TO MICROSOFT SQL LICENSING Guidelines about the Processor Licensing Model Because RightFax is defined as a multiplexer and it can have a variety of users and devices connecting to it, this is the most highly recommended licensing option. According to Microsoft, "This licensing model is most appropriate for applications that are accessible through the Internet and for internal applications with a high client-to-server ratio." In this scenario, a CPU is typically setup to run SQL Server 2005 or One of the databases on that server is the RightFax database. The RightFax application server software is installed on a separate server machine and connects to its database residing on the SQL server machine. The CPU license will cover all RightFax client and device connections without the need for additional user or device. Guidelines about the Server plus Device CAL Licensing Model This is an unlikely scenario for RightFax due to the complex nature of a typical deployment. However, a scenario may exist where there is a low number of end-user accounts for a specific RightFax application within a company. Or, there are a low number of devices such as server machines or desktops, laptops, etc., connected to RightFax. Example scenario: Twelve workers are sharing two desktop machines in a productivity environment. There is one RightFax Server machine and one machine for SQL 2000 Standard edition. The RightFax Administrator runs EFM from the same machine as the RightFax Server. Licensing option: A server plus a three device CAL license would license them for their SQL server plus the two desktop machines. Since they are running EFM on the same machine as the RightFax Server, it too now requires a CAL. This totals three device CALs and a server and is an appropriate model to use Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 14 of 15

15 for this scenario where customers, according to Microsoft, "do not need access beyond the firewall and who have relatively low CAL-to-server ratios." Another RightFax scenario that may fit a "server plus device" licensing model is a production fax or backoffice faxing business application. In this scenario, there may be a very limited number of users, because the main objective is to automate a back-office host application (mainframe, legacy, ERP, etc.), and that in itself is the only "user" or "device" that connects to RightFax. Guidelines about the Server plus User CAL Licensing Model This may be an unlikely scenario; however the distinction in this model is "users" versus "devices". In this example, a user may need to log in to RightFax from a desktop machine, a laptop while working remotely, or from a home computer using Remote Web Access, for example. The user requires flexibility to access RightFax from any device or location and, therefore, the user CAL follows the user, no matter where he connects from. Similar to the restrictions mentioned in the above section about "device" CALs, an organization may have a low number of end-users who need to log in to RightFax from many devices. Example Scenario: A company has a RightFax Server on its own server machine and five FaxUtil users who access from desktops. This includes the administrator who is not running FaxUtil or EFM on the same machine as the RightFax Server. Licensing option: One server plus five user CALs. A CAL is not required for the RightFax Server program, because it has no client program running and remains a pure multiplexer. Note: There are economies of scale that determine the best approach. Microsoft processor licensing quickly becomes the obvious choice when the number of users or devices exceeds a point at which a CPU license would make sense. Microsoft SQL and Open Text Fax Server (RightFax) Open Text has created a great whitepaper explaining the interaction between RightFax and SQL Server. Please see the attached PDF for more details. If you have not received the PDF file then please you re your IIS contact to forward a copy to you. (For reference, the PDF name is RightFax-SQL and Microsoft SQLServer.pdf ) Instant InfoSystems 2301 W. 190th St. Torrance, CA Toll Free: InstantInfoSystems.com Page 15 of 15