From: Subject: ReadMe.RFsp2 Date: Mon, 12 Apr 2010 17:05:00 +0100 MIME-Version: 1.0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Content-Location: file://C:\Documents and Settings\pwalker\Local Settings\Temp\Temporary Directory 1 for RF90SP2_Int.zip\International RPS\Readme.RF90SP2.htm X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 ReadMe.RFsp2

RightFax 9.0 Service Pack 2 Readme

This readme file provides late-breaking or other = information=20 that supplements the RightFax documentation. Service packs are the means = by=20 which RightFax product updates are distributed from the Captaris Web = site. A=20 service pack may contain updates for system reliability, program = compatibility,=20 performance improvements, and more. All service packs are cumulative. = Each=20 contains new fixes plus all the fixes from previous hot fix and service = pack=20 releases. =  

By the time you receive this software, updates to = other=20 RightFax software may be available. To obtain updates, go to http://www.captaris.com/support/downloads/rightfax/9/inde= x.html.

 

Important: = Before=20 installing any Service Pack or upgrading a RightFax server, you must = back up the=20 entire \RightFax directory structure, the fax board directory (usually = the=20 \RFBoard folder), and the SQL database for RightFax. To ensure that all=20 necessary files are properly backed up, stop all RightFax services = before=20 beginning the backup process.

Contents

  1. What=20 is Included in this Service Pack?

  2. Installing=20 Service Pack 2 on RightFax Servers and Client Computers

  3. Installing=20 Service Pack 2 Fax Board Drivers

  4. Updating=20 the RightFax Client Install Folder

  5. Updating=20 the RightFax Administrative Utilities

  6. Installing=20 the SOAP Server and Client Applications

  7. Updating=20 Lotus Notes Gateway Client Computers

  8. Software=20 Fixes in Service Pack 2

  9. Documentation=20 Additions and Corrections for Service Pack 2

  10. New=20 Product Features from Feature Pack 1

  11. Software=20 Fixes from Feature Pack 1

  12. Documentation=20 Additions and Corrections from Feature Pack 1

What is Included in this Service Pack?

Service Pack 2 for RightFax version 9.0 contains = numerous=20 updates to the core server components, fax board drivers, and client=20 installation files. In addition, all of the software fixes and new = features that=20 were available in Feature Pack 1 for RightFax 9.0 are also included in = this=20 Service Pack. Feature Pack 1 includes updates to the RightFax = administrative=20 utilities, Lotus Notes clients, and a new SOAP client/server = installation. If=20 you have already installed Feature Pack 1 for RightFax 9.0, you do not = need to=20 reinstall these features.

The Service Pack 2 installation will overwrite all = files=20 associated with the Service Pack, regardless of the dates and version = numbers of=20 those same files already installed on your server. In some cases, = problems that=20 were resolved with a patch or hotfix that was provided to you by the = Captaris=20 Support group may reoccur after you install this Service Pack. If you = installed=20 a patch or hotfix that resolved any of the following tracking reports, = you must=20 apply an updated version of the patch after installing Service Pack = 2:

For more information, or to request an updated = version of one=20 of these patches, contact Captaris Product Support Engineering at=20 ProductSupport@Captaris.com.

Contents of the Downloaded Service Pack ZIP File

The downloadable RightFax 9.0 Service Pack 2 ZIP = file extracts=20 four separate executable files:

<< Return=20 to ReadMe Contents

Installing Service Pack 2 on RightFax = Servers=20 and Client Computers

This service pack should be installed on all version = 9.0=20 RightFax servers, remote BoardServer computers, IIS servers, Exchange = Connector=20 servers, Gateway servers, and client computers on your network. The = Service Pack=20 2 installation will determine the components that have been installed on = each of=20 these computers and upgrade them accordingly. This Service Pack = installation=20 will only upgrade existing installations of the RightFax 9.0 server and = client=20 applications. It cannot be used for new installations of any server or = client=20 applications.

Important: = Before=20 running this upgrade, if you have one or more Brooktrout TR1034 fax = boards=20 installed, you must confirm that the file bos_btcall.cfg in the=20 \RightFax\RFBoard folder is not set to=20 read-only. If it is, remove the read-only attribute from this file prior = to=20 installing the service pack. Running the service pack installation with = this=20 file set to read-only will fail to properly update the file and the fax = boards=20 will not operate.

Follow these steps on each of your organization's = 9.0 RightFax=20 servers, remote BoardServer computers, IIS servers, Gateway servers, and = client=20 computers. If you are installing Service Pack 2 on a RightFax 9.0 = cluster,=20 follow the instructions for installing on a cluster here.

  1. If you have not already done so, back up the = entire=20 \RightFax directory structure, the fax board directory (usually the = \RFBoard=20 folder), and the SQL database for RightFax. To ensure that all = necessary files=20 are properly backed up, stop all RightFax services before beginning = the backup=20 process.

  2. Save the file RPS SP2=20 Patch North American.exe or = RPS SP2=20 Patch International.exe to a location on your network = accessible by all=20 RightFax server and client computers on which it will be run.

  3. Log on to the RightFax computer as an = administrator.

  4. Run the update program from its location on = the=20 network.

  5. At the introductory screen, click Update. A status bar indicates the = progress=20 of the installation.

  6. When the installation is complete, click Finish.

To Install Service Pack 2 on a RightFax 9.0 = Cluster

  1. Run Cluster Administrator and stop all = RightFax=20 services. Do not take the RightFax file share offline.

  2. Apply Service Pack 2 to the active node = according to the=20 instructions in the section above.

  3. Move the group containing the RightFax = services to the=20 next node without bringing them online.

  4. Apply Service Pack 2 to the new node according = to the=20 instructions in the section above.

  5. Apply Service Pack 2 to any remote = BoardServers and=20 WorkServers.

  6. From Cluster Administrator, bring the RightFax = services=20 back online.

<< Return=20 to ReadMe Contents

Installing Service Pack 2 Fax Board = Drivers

Follow these steps on the RightFax server if it has = fax boards=20 installed. If you use remote BoardServer computers, run the fax board = drivers=20 update on those computers as well.

Important: = When running=20 the Service Pack 2 fax board drivers upgrade, you must be logged in to = the=20 server using the same user ID as was used when the original base 9.0 fax = board=20 drivers were installed. If you are unable to log in with this user ID, = you must=20 re-run the base 9.0 fax board drivers installation using your own login=20 information before installing the Service Pack 2 update.

  1. When the installation of Service Pack 2 for = the RightFax=20 server is complete, remain logged on to the RightFax 9.0 server as an=20 administrator.

  2. Run the program RightFax Fax Board Driver SP2.exe = that you=20 extracted from the downloaded ZIP file.

  3. At the introductory screen, click Update. A status bar indicates the = progress=20 of the installation.

  4. When the installation is complete, click Finish.

<< Return=20 to ReadMe Contents

Updating the RightFax Client = Install=20 Folder

The RightFax Client Install folder lets you store = the RightFax=20 client installation files on your network so that you can easily run all = new=20 RightFax client installations from that location. The installation files = in this=20 folder should be used for all new client installations. Existing clients = should=20 be upgraded by running the Service Pack 2 executable file directly on = each=20 client computer.

Follow these steps on the server where the version = 9.0=20 RightFax Client Install folder resides (described in the RightFax Installation Guide):

  1. Save the file RPS SP2 Patch=20 North American.exe or RPS = SP2 Patch=20 International.exe to a location on your network accessible by = the=20 server where the Client Install folder is located.

  2. Open a command prompt and navigate to the existing = client=20 installs folder where the file RightFax=20 Product Suite.msi is located.

  3. At the command prompt, enter:

    "C:\temp\RPS SP2 Patch North American.exe " /V"/a=20 RightF~1.msi (for the North American upgrade)

    or

    "C:\temp\RPS SP2 Patch International.exe " /V"/a = RightF~1.msi=20 (for the international upgrade)

    (Where C:\temp is = the=20 location where you extracted the Service Pack executable file)
     

  4. Once the installer window is displayed, follow the = on-screen=20 prompts to update the client installs to Service Pack 2. If the = installer=20 fails to display or if you receive an error message, verify the path = to the=20 temporary folder where you saved the upgrade executable file.

  5. After the RightFax client installs folder on your = network=20 has been upgraded, it should be used for new client installations = only. If you=20 want to upgrade existing RightFax client installations, you should run = the=20 RPS SP2 Patch North = American.exe or=20 RPS SP2 Patch = International.exe file=20 directly on each client computer.

<< Return=20 to ReadMe Contents

Updating the RightFax=20 Administrative Utilities

Important: = This update=20 was released with Feature Pack 1 for RightFax 9.0. If you have already = installed=20 this update, you do not need to reinstall it for Service Pack 2.

The RightFax Administrative Utilities are installed = separately=20 from other RightFax server and client components. Follow these steps to = update=20 the RightFax Administrative Utilities on all computers where they are = already=20 installed.

  1. Log on to the computer with the RightFax = Administrative=20 Utilities installed.

  2. Navigate to the file Administrative Utilities SP1.exe = that you=20 extracted from the downloaded ZIP file.

  3. At the introductory screen, click Update. A status bar indicates the = progress=20 of the installation.

  4. When the installation is complete, click Finish.

<< Return=20 to ReadMe Contents

Installing the SOAP Server and Client = Applications

Important: = This feature=20 was released with Feature Pack 1 for RightFax 9.0. If you have already = installed=20 this feature, you do not need to reinstall it for Service Pack 2.

The SOAP client/server installation lets RightFax = users use=20 the Print-to-Fax feature from any computer with an Internet connection. = The SOAP=20 server must be installed on an IIS server running version 9.0 of = RightFax Web=20 Access. The SOAP client then accesses RightFax through that server. This = provides RightFax functionality to home-office or other remote employees = who do=20 not have direct access to your organization's network. There are two = components=20 to the SOAP installation: install the SOAP server on the IIS computer = running=20 RightFax Web Access, and then install the SOAP client on the remote = client=20 computers.

Installing the SOAP Server

  1. Update the RightFax Web Access installation on the = Web=20 Access IIS server according to the instructions in the section Installing=20 Service Pack 2 on RightFax Servers and Client Computers.

  2. Log on to the Web Client IIS server as an=20 administrator.

  3. Navigate to the SOAP server installation file = RightFax SOAP Server.exe that you = extracted=20 from the downloaded ZIP file.

  4. At the introductory screen, click Next.

  5. Read and select the option to accept the terms = of the=20 license agreement. Click Next.

  6. Click Install to=20 begin the installation. A status bar indicates the progress of the=20 installation.

  7. When the installation is complete, click Finish.

Installing the SOAP Client

When you install the SOAP server on the Web Access = IIS server,=20 the SOAP client installation file RightFax=20 Client for the Web.exe is installed in the Program Files\RightFax\WebApps\WebUtil\Client=20 Install folder. You must send this file via e-mail, copy it to a=20 removable storage medium, or otherwise make it available to the remote = clients.=20 Follow these steps on each remote computer to install the SOAP = client:

  1. Run the RightFax SOAP client installation file = RightFax Client for the = Web.exe.

  2. At the introductory screen, click Next.

  3. Enter the Web address of the SOAP server = (e.g.,=20 www.MyCompany.SOAPServer.com) and the machine name of the RightFax = server when=20 prompted. Click Next.

  4. Click Install to=20 begin the installation. A status bar indicates the progress of the=20 installation.

  5. When the installation is complete, click Finish.

Using the SOAP Client

After you install the RightFax SOAP client, a = RightFax tray=20 icon will appear in the computer's Start bar. Users can access RightFax=20 Print-to-Fax features through the shortcut menu from this icon. Users = can also=20 print documents directly to the RightFax Fax Printer (a new printer type = that=20 the client installation adds), which prompts for fax addressing = information and=20 transmits the document via the RightFax server.

<< Return=20 to ReadMe Contents

Updating Lotus Notes Gateway Client = Computers

Important: = This update=20 was released with Feature Pack 1 for RightFax 9.0. If you have already = installed=20 this update, you do not need to reinstall it for Service Pack 2.

After you upgrade the RightFax server to version 9.0 = Service=20 Pack 2, the Notes update file NGPatch.NSF is copied into the=20 \RightFax\Gateway folder. The steps for applying this update to the = Notes=20 Gateway depends on the type of installation you already have. To upgrade = Notes,=20 follow only the steps under the heading listed below for your specific =  installati= on=20 type.

Caution: If = you left=20 files in the temp directory after your last installation, those files = must be=20 removed or a different temp directory specified during the install in = order for=20 the databases to be updated correctly.

Note: In a = clustered=20 Notes environment, documents that are sent while a node is failed over = are held=20 in the MAIL.BOX of the server to which the client is connected. =  When the = node on=20 which the Notes Gateway is installed is returned to service, outbound = messages=20 are processed according to the settings on the Connections document.

To ensure the = previous version=20 files are deleted during the upgrade when running the 9.00 installer and = 9.01=20 installer back-to-back, you should take the following steps

  1. Complete the 9.0 installer.

  2. Close the Notes client from which the installer is = being=20 run.

  3. On the Domino server console, type "dbcache = flush." This=20 will not delete any data, but will free up connections that are not = currently=20 in use but are still cached.

  4. Re-open the Notes client and continue with the = 9.01=20 Installer.

For update instruction for your specific Notes = Gateway=20 configuration, click the appropriate setting:
 

To=20 Update the Full Notes Mail Integration for Existing 9.0 = Installations To=20 Update the Full Notes Mail Integration for Existing 8.7 = Installations To=20 Update the Full Notes Mail Integration for Existing 8.5 = Installations To=20 Update the Minimal Notes Mail Integration for Existing 9.0=20 Installations To=20 Update the Minimal Notes Mail Integration for Existing 8.7=20 Installations To=20 Update the Minimal Notes Mail Integration for Existing 8.5=20 Installations To=20 Update the No Notes Mail Integration for Existing 9.0 = Installations To=20 Update the No Notes Mail Integration for Existing 8.7 = Installations To=20 Update the No Notes Mail Integration for Existing 8.5 = Installations

To Update the Full Notes Mail = Integration=20 for Existing 9.0 Installations

  1. Copy NGPatch.NSF=20 from the \RightFax\Gateway folder on the RightFax server to the Notes = client=20 machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  2. Run the Lotus Notes client and open the RightFax = 9.01=20 installer database file NGPatch.NSF.

  3. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide.

    Important:    =20 When you reach the step that specifies the path to the TEMP folder, = ensure=20 that the specified folder is empty, or select a different, empty=20 folder.
     

  4. Follow the instructions in the RightFax Lotus Notes Module Guide = for=20 completing the installation after the last step of the installer has=20 run.

To Update the Full Notes Mail = Integration=20 for Existing 8.7 Installations

  1. On the RightFax server, run the RightFax E-mail = Gateway=20 program from Windows Control Panel. This opens the E-mail Configuration dialog = box.

  2. Click the Copy = Notes=20 Database button.

  3. When you receive a message that the database has = been=20 successfully copied, click OK = to close=20 the message, and then click OK to close=20 the E-mail Configuration = dialog=20 box.

  4. Run Enterprise Fax Manager and stop the RightFax = E-mail=20 Gateway Module service.

  5. Copy NGPatch.NSF=20 located in the \RightFax\Gateway folder on the RightFax server and = NGInstal.NSF in the = \Lotus\Notes\Data=20 directory on the RightFax server to the Notes client machine's=20 \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  6. Run the Lotus Notes client and open the RightFax = 9.00=20 Installation Database NGInstal.NSF to=20 upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide = for=20 information on running this installation. When the installation is = complete,=20 do not set any configuration options for version 9.0.

  7. Run the Lotus Notes client and open the RightFax = 9.01=20 Installer database NGPatch.NSF.

  8. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or select a different, empty = folder.
     

  9. If applicable, delete the file RF80SYNC.NSF from the=20 Lotus\Domino\Data\RIGHTFAX folder on the Domino server.

  10. Follow the instructions in the RightFax Lotus Notes Module Guide = for=20 completing the installation after the last step of the installer has=20 run.

To Update the Full Notes Mail = Integration=20 for Existing 8.5 Installations

  1. On the RightFax server, run the RightFax E-mail = Gateway=20 program from Windows Control Panel. This opens the E-mail Configuration dialog = box.

  2. Click the Copy = Notes=20 Database button.

  3. When you receive a message that the database has = been=20 successfully copied, click OK = to close=20 the message, and then click OK to close=20 the E-mail Configuration = dialog=20 box.

  4. Run Enterprise Fax Manager and stop the RightFax = E-mail=20 Gateway Module service.

  5. Copy NGPatch.NSF=20 located in the \RightFax\Gateway folder on the RightFax server and = NGInstal.NSF in the = \Lotus\Notes\Data=20 directory on the RightFax server to the Notes client machine's=20 \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  6. On the Lotus Notes Client machine, run Notes = Designer and=20 uncheck the Prohibit checkbox = on the=20 Design tab of the following = element=20 properties:

    MAIL50.NTF
    Forms:
    New RightFax = Fax
    RightFax=20 Connections
    RightFax User Options
    Folders:
    Real-time Fax=20 Status
    RightFax Settings
    Agents:
    (RightFAX Convert = Picklist=20 Names to FAX Addresses)
    SubForms:
    (RightFAX = Autoforward=20 Profile)
    (RightFAX Autoforward Warning)
    (RightFAX Send = Options)
    Script Libraries:
    (RightFAX = Script=20 Library)
    ...Other:
    Icon
    "Using=20 Database" Document
    "About Database" Document
    EFM SYNC:
    Folders:
    Real-Time Fax=20 Status
    RightFax Settings
    ...Other:
    Icon
    "Using = Database"=20 Document
    "About Database" Document
    ICD=20 ROUTER
    ...Other:
    Icon
    "Using = Database"=20 Document
    "About Database" Document

  7. Run the Lotus Notes client and open the RightFax = 9.00=20 Installation Database NGInstal.NSF to=20 upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide = for=20 information on running this installation. Complete the upgrade = configurations=20 for version 9.0 according to the instructions in the RightFax Lotus Notes Module = Guide.

  8. Run the Lotus Notes client and open the RightFax = 9.01=20 Installer database NGPatch.NSF.

  9. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or select a different, empty = folder.
     

  10. If applicable, delete the file RF80SYNC.NSF from the=20 Lotus\Domino\Data\RIGHTFAX folder on the Domino server.

  11. Follow the instructions in the RightFax Lotus Notes Module Guide = for=20 completing the installation after the last step of the installer has=20 run.

To Update the Minimal Notes = Mail=20 Integration for Existing 9.0 Installations

  1. Copy NGPatch.NSF=20 from the \RightFax\Gateway folder on the RightFax server to the Notes = client=20 machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  2. Run the Lotus Notes client and open the RightFax = 9.01=20 installer database file NGPatch.NSF.

  3. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or specify a different, empty = folder

    After=20 completing step 10 in the installation, view the install log by = clicking the=20 button in the top left of the Installer window, and confirm that the = previous=20 install files were successfully deleted. If not, you must manually = delete=20 these files before continuing with the installation.

  4. Re-send the Connections document to each person = listed in=20 the EFM Sync database.

  5. Instruct each user to run the Update from their = mail file to=20 download the updated Fax Factory, and then open the User Options = document from=20 within the Fax Factory database and Save and Close the document to = update the=20 remaining mail elements.

To Update the Minimal Notes = Mail=20 Integration for Existing 8.7 Installations

  1. On the RightFax server, run the RightFax E-mail = Gateway=20 program from Windows Control Panel. This opens the E-mail Configuration dialog = box.

  2. Click the Copy = Notes=20 Database button.

  3. When you receive a message that the database has = been=20 successfully copied, click OK = to close=20 the message, and then click OK to close=20 the E-mail Configuration = dialog=20 box.

  4. Run Enterprise Fax Manager and stop the RightFax = E-mail=20 Gateway Module service.

  5. Copy NGPatch.NSF=20 located in the \RightFax\Gateway folder on the RightFax server and = NGInstal.NSF in the = \Lotus\Notes\Data=20 directory on the RightFax server to the Notes client machine's=20 \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  6. Run the Lotus Notes client and open the RightFax = 9.00=20 Installation Database NGInstal.NSF to=20 upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide = for=20 information on running this installation. When the installation is = complete,=20 do not set any configuration options for version 9.0.

  7. Run the Lotus Notes client and open the RightFax = 9.01=20 Installer database NGPatch.NSF.

  8. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or specify a different, empty = folder

    After=20 completing step 10 in the installation, view the install log by = clicking the=20 button in the top left of the Installer window, and confirm that the = previous=20 install files were successfully deleted. If not, you must manually = delete=20 these files before continuing with the installation.

  9. If applicable, delete the file RF80SYNC.NSF from the=20 Lotus\Domino\Data\RIGHTFAX folder on the Domino server.

  10. Follow the instructions in the RightFax Lotus Notes Module Guide = for=20 completing the installation after the last step of the installer has = run.

  11. Re-send the Connections document to each person = listed in=20 the EFM Sync database.

  12. Instruct each user to run the Update from their = mail file to=20 download the updated Fax Factory, and then open the User Options = document from=20 within the Fax Factory database and Save and Close the document to = update the=20 remaining mail elements.

To Update the Minimal Notes = Mail=20 Integration for Existing 8.5 Installations

  1. On the RightFax server, run the RightFax E-mail = Gateway=20 program from Windows Control Panel. This opens the E-mail Configuration dialog = box.

  2. Click the Copy = Notes=20 Database button.

  3. When you receive a message that the database has = been=20 successfully copied, click OK = to close=20 the message, and then click OK to close=20 the E-mail Configuration = dialog=20 box.

  4. Run Enterprise Fax Manager and stop the RightFax = E-mail=20 Gateway Module service.

  5. Copy NGPatch.NSF=20 located in the \RightFax\Gateway folder on the RightFax server and = NGInstal.NSF in the = \Lotus\Notes\Data=20 directory on the RightFax server to the Notes client machine's=20 \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  6. On the Lotus Notes Client machine, run Notes = Designer and=20 uncheck the Prohibit checkbox = on the=20 Design tab of the following = element=20 properties:

    EFM = SYNC:
    Folders:
    Real-Time Fax=20 Status
    RightFax Settings
    ...Other:
    Icon
    "Using = Database"=20 Document
    "About Database" Document
    ICD=20 ROUTER
    ...Other:
    Icon
    "Using = Database"=20 Document
    "About Database" Document

  7. Run the Lotus Notes client and open the RightFax = 9.00=20 Installation Database NGInstal.NSF to=20 upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide = for=20 information on running this installation. Complete the upgrade = configurations=20 for version 9.0 according to the instructions in the RightFax Lotus Notes Module = Guide.

  8. Run the Lotus Notes client and open the RightFax = 9.01=20 Installer database NGPatch.NSF.

  9. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or select a different, empty = folder.

    After=20 completing step 10 in the installation, view the install log by = clicking the=20 button in the top left of the Installer window, and confirm that the = previous=20 install files were successfully deleted. If not, you must manually = delete=20 these files before continuing with the installation.

  10. If applicable, delete the file RF80SYNC.NSF from the=20 Lotus\Domino\Data\RIGHTFAX folder on the Domino server.

  11. Follow the instructions in the RightFax Lotus Notes Module Guide = for=20 completing the installation after the last step of the installer has = run.

  12. Re-send the Connections document to each person = listed in=20 the EFM Sync database.

  13. Instruct each user to run the Update from their = mail file to=20 download the updated Fax Factory, and then open the User Options = document from=20 within the Fax Factory database and Save and Close the document to = update the=20 remaining mail elements.

To Update the No Notes Mail = Integration for=20 Existing 9.0 Installations

  1. Copy NGPatch.NSF=20 from the \RightFax\Gateway folder on the RightFax server to the Notes = client=20 machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  2. Run the Lotus Notes client and open the RightFax = 9.01=20 installer database file NGPatch.NSF.

  3. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or specify a different, empty = folder

To Update the No Notes Mail = Integration for=20 Existing 8.7 Installations

  1. On the RightFax server, run the RightFax E-mail = Gateway=20 program from Windows Control Panel. This opens the E-mail Configuration dialog = box.

  2. Click the Copy = Notes=20 Database button.

  3. When you receive a message that the database has = been=20 successfully copied, click OK = to close=20 the message, and then click OK to close=20 the E-mail Configuration = dialog=20 box.

  4. Run Enterprise Fax Manager and stop the RightFax = E-mail=20 Gateway Module service.

  5. Copy NGPatch.NSF=20 located in the \RightFax\Gateway folder on the RightFax server and = NGInstal.NSF in the = \Lotus\Notes\Data=20 directory on the RightFax server to the Notes client machine's=20 \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  6. Run the Lotus Notes client and open the RightFax = 9.00=20 Installation Database NGInstal.NSF to=20 upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide = for=20 information on running this installation. When the installation is = complete,=20 do not set any configuration options for version 9.0.

  7. Run the Lotus Notes client and open the RightFax = 9.01=20 Installer database NGPatch.NSF.

  8. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or specify a different, empty folder

  9. If applicable, delete the file RF80SYNC.NSF from the=20 Lotus\Domino\Data\RIGHTFAX folder on the Domino server.

  10. Follow the instructions in the RightFax Lotus Notes Module Guide = for=20 completing the installation after the last step of the installer has=20 run.

To Update the No Notes Mail = Integration for=20 Existing 8.5 Installations

  1. On the RightFax server, run the RightFax E-mail = Gateway=20 program from Windows Control Panel. This opens the E-mail Configuration dialog = box.

  2. Click the Copy = Notes=20 Database button.

  3. When you receive a message that the database has = been=20 successfully copied, click OK = to close=20 the message, and then click OK to close=20 the E-mail Configuration = dialog=20 box.

  4. Run Enterprise Fax Manager and stop the RightFax = E-mail=20 Gateway Module service.

  5. Copy NGPatch.NSF=20 located in the \RightFax\Gateway folder on the RightFax server and = NGInstal.NSF in the = \Lotus\Notes\Data=20 directory on the RightFax server to the Notes client machine's=20 \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client = machine and=20 ensure that it is not set to read-only. If so, remove the read-only=20 attribute.

  6. On the Lotus Notes Client machine, run Notes = Designer and=20 uncheck the Prohibit checkbox = on the=20 Design tab of the following = element=20 properties:

    EFM = SYNC:
    Folders:
    Real-Time Fax=20 Status
    RightFax Settings
    ...Other:
    Icon
    "Using = Database"=20 Document
    "About Database" Document
    ICD=20 ROUTER
    ...Other:
    Icon
    "Using = Database"=20 Document
    "About Database" Document

  7. Run the Lotus Notes client and open the RightFax = 9.00=20 Installation Database NGInstal.NSF to=20 upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide = for=20 information on running this installation. Complete the upgrade = configurations=20 for version 9.0 according to the instructions in the RightFax Lotus Notes Module = Guide.

  8. Run the Lotus Notes client and open the RightFax = 9.01=20 Installer database NGPatch.NSF.

  9. Click the Begin/Resume=20 Installation button. Complete the database installation = according to=20 the instructions in the RightFax = Lotus Notes=20 Module Guide but do not make any changes to the existing = configuration=20 settings.

    Important:     = When you=20 reach the step that specifies the path to the TEMP folder, ensure that = the=20 specified folder is empty, or select a different, empty = folder.
     

  10. If applicable, delete the file RF80SYNC.NSF from the=20 Lotus\Domino\Data\RIGHTFAX folder on the Domino server.

  11. Follow the instructions in the RightFax Lotus Notes Module Guide = for=20 completing the installation after the last step of the installer has=20 run.

<< Return=20 to ReadMe Contents

Software Fixes in Service Pack 2
 

Captaris Tracking Number

Module

Problem

Solution

49365

API

Faxes=20 generated by the RightFax API with the faxInfo11.lExpiresIn = property=20 remain in fax board queue.

Corrected.=20 Faxes now expire at the interval specified.

42958

BoardServer

After=20 a failed transmission smart resume resends the entire = fax.

Smart=20 resume only sends pages that have failed or have yet to be=20 transmitted.

48240

BoardServer

When=20 the Human-Answered Fax feature is configured to switch to voice = mode when=20 the phone is answered, "Unknown error reported by fax board" is = reported.=20

The=20 Human-Answered Fax feature now correctly switches to voice mode.=20

48759

BoardServer

Malformed=20 SIP packets cause BoardServer module =  to crash=20 when configured for T.38 FOIP faxing. =  

Corrected.=20 BoardServer module no longer crashes.

49055

BoardServer

IRQ=20 settings above 9 =  for the=20 BoardServer module saving as one digit lower than was = specified.

IRQ=20 settings for the BoardServer module now save = correctly.

49111

BoardServer

The=20 Smart -Resume option on sent faxes failed and resent faxes sent = the entire=20 fax instead of only the unsent portion.

The=20 Smart-Resume option now resends only the unsent portion of failed = faxes as=20 expected.

49468

BoardServer

Faxes=20 sent using the RightFax API with an expired fax return value hang = in a=20 status of "waiting to be sent".

Corrected.=20 Faxes now send as expected.

49528

BoardServer

Attempting=20 to save dialing rules in a multi-BoardServer environment =  will = cause=20 dialing rules to be overwritten.

Corrected.=20 Dialing rules are no longer overwritten.

49681

BoardServer

CallXpress=20 IPK files fail to process correctly.

Corrected.

50109

BoardServer

Addresses=20 an issue with the Brooktrout SDK, T-1 (robbed-bit) lines and the = RightFax=20 BoardServer module that could cause a channel to answer with dead=20 air.

Corrected.=20 Channels now answer as expected.

50122

BoardServer

Fax=20 .IPK files will randomly fail to be parsed by the BoardServer=20 module.

Corrected.=20 Fax .IPK files are now processed as expected.

50126

BoardServer

Some=20 available fax channels remain idle during fax broadcasts using the = Production module.

Production=20 fax broadcasts now make use of all available channels as=20 expected.

50260

BoardServer

A=20 fax sent via a remote BoardServer machine may transmit twice under = certain=20 circumstances.

Corrected.=20 All faxes sent via remote BoardServers now transmit only once as=20 expected.

50759

BoardServer

Global=20 availability index for fax channels calculated incorrectly = resulting in=20 some available fax channels being left unused.

Availability=20 index now calculates correctly making all available fax channels=20 accessible.

50788

BoardServer

"Unknown=20 Error 4/500" on outbound faxes occur with TR1034 robbed-bit = digital fax=20 boards.

Corrected.=20 Error no longer occurs.

51003

BoardServer

BoardServer=20 not using all available fax channels resulting in unsent faxes = during=20 large-scale fax broadcasts.

Corrected.=20 Availability index now calculates correctly making all available = fax=20 channels accessible.

52067

BoardServer

Large-scale=20 SQL database activities performing more slowly than equivalent = activities=20 on previous proprietary RightFax database.

Corrected.=20 SQL database speed comparable to earlier versions of RightFax=20 database.

49395

Brooktrout=20
TR114

Attempting=20 to run voice.exe results in an error.

Corrected.=20 Voice.exe now runs as expected.

47177

Brooktrout=20
TR1034

Channels=20 cannot be re-mapped when using a T-1 (robbed-bit) line.

Corrected.=20 Channels can now be re-mapped.

49192

Brooktrout=20
TR1034

Outbound=20 faxes may report "OK" status and zero pages sent.

Corrected.=20 Outbound faxes send as expected.

49498

Brooktrout=20
TR1034

Configuring=20 Brooktrout TR1034 faxboards for T.38 faxing as per the 9.0 = FaxBoard guide=20 results in an error.

Boards=20 can now be configured for T.38 faxing.

49562

Brooktrout=20
TR1034

TR1034=20 fax boards configured for robbed-bit T-1 lines may generate an = 'unknown=20 error,' resulting in dead-air.

Corrected.=20 Faxes send as expected.

49687

Brooktrout=20
TR1034

Faxes=20 sent using a TR1034 faxboard are reported as successfully sent yet = no=20 pages are transmitted.

Corrected.=20 Transmission now occurs.

 

49821

Brooktrout=20
TR1034

1034=20 faxboards using T-1 lines with Human Answered Fax enabled result = in an=20 error

Corrected.=20 Enabling Human Answered Fax no longer produces an = error.

49880

Brooktrout=20
TR1034

Faxes=20 cannot be sent using T.38 with E-1 lines and Cisco routers = .

Corrected.=20 Faxes send as expected.

50110

Brooktrout=20
TR1034

TR1034=20 fax boards configured for robbed-bit T-1 lines may generate an = 'unknown=20 error,' resulting in dead-air.

Corrected.=20 Faxes send and receive as expected.

49824=20

Com=20 API

Users=20 lists sorted by 'UserID' are not returned to the correct sort = order =  when = loaded=20 from a fax server.

Corrected.=20 Users are now returned to the correct sort order.

50112

Com=20 API

After=20 applying feature pack 1, selecting the properties of a fax using a = client=20 application built on the 9.0 or earlier API results in an = error.

Corrected.=20 Fax properties can now be accessed as expected.

47727

Database=20 module

Running=20 DbUpgrader.exe fails to migrate folders and sub-folders created in = FaxUtil.

Corrected.=20 All folders are now migrated.

48747=20        "Err#1:=20 [Microsoft][ODBC SQL Server Driver] Connection is busy ..." = .

Corrected.=20 Logs no longer occur.

48927

Database=20 module

Fax=20 Reporter datasets return a maximum of 200 records.

Corrected.=20 All records are now returned.

49575=20        in a=20 destination table that is longer than 21 digits.

DocTransport=20 no longer crashes and dialing rule is applied.

49759=20            "Nee= ds=20 Approval", the status of the =  fax is=20 updated to "Printing" and never returns to "Needs Approval". =

Corrected.=20 Faxes now return to "Needs approval" =  status. 50025=20

FaxUtil

Error=20 231 occurs when submitting multiple print-to-fax jobs.

Corrected.=20 Faxes now send as expected

49578=20              {{notifyho= st}}=20 with the {{type print}} command.

Notifications=20 are now generated.

49459=20        through = an=20 e-mail gateway to fail.

Corrected.=20 Inbound faxes now route through e-mail gateways.

49367=20                 'From=20 Message' field is ignored when faxes are sent through the = 'Default' user=20 account.

Corrected.=20 Notifications are now sent on behalf of the address or account = configured=20 in the 'From Message' field.

50048

SMTP=20 Integration

HTML=20 conversions using the SMTP gateway produce blank pages, which are = dropped=20 and only a cover sheet is sent.

Corrected.=20 HTML conversion work as expected through the SMTP gateway. Note = that the=20 HTML conversion does not work when using Internet Explorer version = 6 SP1,=20 only versions prior to SP1.

48756=20        and 'To=20 Name' fields are populated using a Greek regional input = settings.

Text=20 is now legible.

48492=20             
 =20

<< Return=20 to ReadMe Contents

 =20

Documentation Additions and Corrections = for=20 Service Pack 2

New versions of the RightFax documentation have been = updated=20 for RightFax 9.0 Feature Pack 2. Although the Feature Pack installation = will not=20 make any changes to the guides in your RightFax\Docs folder, the new = versions of=20 the documentation are available for download from the same Web page = where you=20 downloaded the Feature Pack installation. All of the updated guides that = have=20 changes listed in this section are available for download.

RightFax 9.0 Administrators = Guide

Chapter

8, "Creating RightFax=20 Users"

Section

"Unprotected Mailbox"

Page

104

Error

The documentation fails to mention that the=20 unprotected mailbox user permission allows other users to = manipulate=20 delete faxes.

Resolution

A note regarding this has been included in = the Administrator's=20 Guide.

=09

 

 

 

 

Chapter

4, "Configuring the WorkServer=20 Modules"

Section

"Xerox = Configuration"

Page

39

Error

The guide states that information about = Xerox=20 Connector for RightFax 9.0 can be found in a PDF file on the = installation=20 CD.

Resolution

This documentation is not included on the = installation=20 CD. For information on this product, contact your RightFax=20 dealer.

=09

 

 

 

 

Chapter

4, "Configuring the WorkServer=20 Modules"

Section

"Telephony server = routing"

Page

33

Error

The guide fails to warn that enabling = telephony server=20 routing on a WorkServer disables all other WorkServer=20 activities.

Resolution

Any WorkServer that has telephony server = routing=20 enabled will be dedicated to telephony routing only and all other=20 WorkServer activities will be ignored. For this reason, you must = have=20 configured at least one WorkServer that is not assigned to perform = telephony routing and that performs all other required WorkServer=20 activities.

=09

 

 

 

 

Chapter

5, "Configuring the DocTransport and = BoardServer=20 Modules"

Section

N/A

Page

N/A

Error

No mention is included in the guide that the = BoardServer module must be initialized by the DocTransport module = or else=20 faxes will fail to schedule for = transmission.

Resolution

The BoardServer module should never be = stopped and=20 restarted manually. In all cases, you should stop and restart the=20 DocTransport module which will automatically also stop and = properly=20 reinitialize restart the BoardServer = module.

=09

 

 

 

 

Chapter

5, "Configuring the DocTransport and = BoardServer=20 Modules"

Section

"Running=20 DocTransport and BoardServer Services on Remote=20 Computers"

Page

75

Error

No mention is included in the guide that if = the DSN=20 for the SQL database has been changed on the main RightFax server = it must=20 also be changed on the remote = BoardServer.

Resolution

If you have changed the default DSN for the = SQL=20 connection on the main RightFax server, you must manually change = the DSN=20 on the remote BoardServer computer to match the DSN on the=20 server.

=09

 

 

 

 

Chapter

5, "Configuring the DocTransport and = BoardServer=20 Modules"

Section

"Running DocTransport and BoardServer Services = on Remote=20 Computers"

Page

74

Error

The documentation fails to mention that = running remote=20 DocTransport and BoardServer modules over a WAN is a supported=20 configuration.

Resolution

A note regarding this support has been = included in the=20 Administrator's=20 Guide.

=09

 

 

 

 

 RightF= ax 9.0=20 Fax Board = Guide

Chapter

3, "Brooktrout Digital Fax=20 Boards"

Section

"Download firmware to the Brooktrout=20 TR1034"

Page

16

Error

Step 1 instructs you to change to the = RightFax\RFBoard=20 folder.

Resolution

In step 1 you must change to the=20 RightFax\RFBoard\Boston = folder.

=09

 

 

 

 

RightFax 9.0 Installation = Guide

Chapter

3, "Installing the RightFax Server=20 Software"

Section

"To configure SQL Server for RightFax Web=20 Access"

Page

27

Error

Steps 1 and 2 instruct you edit a file = called=20 = Captaris.RightFax.RemotingService.exe.config.

<= /TR>

Resolution

If you have installed Feature Pack 1 for = RightFax 9.0,=20 this file name has been changed to=20 = RightFax.API.Remoting.Service.exe.config.

= =09

 

 

 

 

RightFax 9.0 Integration Module Guide =

Chapter

14, "Including the Same Files and Commands = in Many = Documents=20 "

Section

"Understanding Include=20 Files"

Page

83

Error

The documentation provides an incorrect = example of FCL=20 code-=20 =  {{font=20 times new roman 12}}.

Resolution

The example has been updated to include the = correct=20 syntax in the Integration = Module=20 Guide.

{{font "times new roman"=20 12}}

=09

 

 

 

 

Chapter

9, "Creating FCL=20 Documents"

Section

"Example FCL = Documents"

Page

52

Error

The documentation provides an incorrect = example of FCL=20 code-=20 =  {{font=20 times new roman 12}}.

Resolution

The example has been updated to include the = correct=20 syntax in the Integration = Module=20 Guide.

{{font "times new roman"=20 12}}

=09

 

 

 

 

New Product Features from Feature Pack = 1

Additional SQL Server Support

Added Support for SQL 2000 Enterprise Edition both = standalone=20 and in clustering environments. See RightFax Installation Guide Pages = 9-10.

Additional Fax Board Support

Added support for the following Eicon fax = boards:

  •    Eicon=20 Diva Server PRI/E1/T1-8

  •    Eicon=20 Diva Server PRI/T1-24

  •    Eicon=20 Diva Server Analog-4P

  •    Eicon=20 Diva Server Analog-8P

Added support for up to four Brooktrout TR1034 = boards per=20 chassis for all supported TR1034 models. See RightFax Fax Board Guide = pages=20 34-35.

Up to eight Eicon boards can be installed per = chassis.

RightFax now supports up to 120 channels per=20 DocTransport/BoardServer module. See RightFax Administrator's Guide page = 49.

Remote Print-to-Fax Client Using the SOAP = Protocol

The SOAP client/server installation lets RightFax = users use=20 the Print-to-Fax feature from any computer with an Internet connection. = The SOAP=20 server is installed on an IIS server on your network, and then the SOAP = client=20 then accesses RightFax through that server. This provides RightFax = functionality=20 to home-office or other remote employees who do not have direct access = to your=20 organization's network. See Installing=20 the SOAP Server and Client Applications for instructions on = installing this=20 new feature.

Support For Arabic Language Character Set

Added support for ANSI code page 1256 (Arabic) to = support=20 Arabic characters in fax documents. See RightFax Installation Guide = pages=20 10-11.

New Web Access Features

Added support for several additional annotation = types in the=20 RightFax Web Access fax viewer. See the RightFax Web Access online = help.

New Notes Features

Fax failure message are now handled in the domain of = the mail=20 router and its DELIVERY FAILURE message. More details are now provided = in fax=20 failure messages.

<< Return=20 to ReadMe Contents

Software Fixes from Feature Pack=20 1

 

Captaris Tracking Number

Module

Problem

Solution

46928

BoardServer

When=20 using Least-Cost Routing rules with the "Send via Fax Server" = option,=20 FaxUtil reports "unknown error," but the fax sends = correctly.

This=20 error message no longer appears.

47673

BoardServer

Dialing=20 rules strip non-dialable characters such as - and ( ) in phone = numbers=20 instead of correctly =  stripping = digits and ignoring the non-dialable characters.

The=20 dialing rules now correctly ignore non-dialable characters and = strip only=20 the phone number digits.

47719

BoardServer

On=20 Business Integration servers with only one channel enabled, all = outbound=20 faxes fail with the status "Scheduled to be Sent" or "Waiting to = be=20 Sent."

Faxes=20 now send as expected on servers with this = configuration.

47954

BoardServer

When=20 the Human-Answered Fax feature is configured to switch to voice = mode when=20 the phone is answered, "Unknown error reported by fax board" is = reported.=20

The=20 Human-Answered Fax feature now correctly switches to voice mode.=20

47965

BoardServer

The=20 TTI line was not being properly added to outbound faxes when using = a=20 Brooktrout TruFax 200 uPCI fax board.

When=20 using a Brooktrout TruFax 200 uPCI fax board, TTI lines are now = correctly=20 added to outbound faxes as expected.

46695

Database=20 Module

RightFax=20 9.0 and RightFax Workflow Wizard 1.5 displaying incompatibility = issues.=20

RightFax=20 9.0 and RightFax Workflow Wizard 1.5 now functioning compatibly.=20

46734

Database=20 Module

Unable=20 to log into fax server after 2 AM maintenance time.

Corrected=20 maintenance issue allowing RightFax logon as = expected.

47130

Database=20 Module

Daily=20 maintenance deletes all fax image files on RightFax 9.0 Business=20 servers.

Corrected.=20 Daily maintenance no longer deletes fax image files.

47544

Database=20 Module

Billing=20 codes not displaying correctly or searchable through FaxUtil. =

Corrected.=20 Billing codes now display as expected.

48048

Database=20 Module

Under=20 specific circumstances, sending multiple faxes simultaneously = causes SQL=20 deadlock errors in RightFax.

Corrected=20 so that deadlocking errors no longer appear under test=20 conditions.

46828

DBPurge.exe

In=20 DBPurge.exe, there is no specific option to purge = GenMailMsg.

An=20 option to purge GenMailMsg has been added to = DBPurge.exe.

47818

DBPurge.exe

Dbpurge.exe=20 fails to purge work requests.

Work=20 requestes can now be purged with DBPurge.exe.

47795

Enterprise=20 Fax Manager

Enterprise=20 Fax Manager version 9.0 stops unexpectedly when attempting to = configure a=20 WorkServer module on a version 8.x RightFax server.

Enterprise=20 Fax Manager version 9.0 now allows you to configure a WorkServer = module on=20 a version 8.x RightFax server.

46868

Exchange=20 Connector

Microsoft=20 Outlook stops unexpectedly when receiving a fax into Outlook with = both the=20 RightFax 9.0 client and McAfee 8.0i Enterprise installed.

Corrected.=20 Microsoft Outlook operated as expected when both of these = applications are=20 installed.

43438

FaxAge.exe

Faxage.exe=20 reports that it is not a valid win32 program.

Corrected.=20 FaxAge.exe runs as expected.

32217

FaxUtil

Spanish=20 help for embedded codes mistranslated.

The=20 help translation was corrected.

32218

FaxUtil

Spanish=20 help for "Hold for Preview" feature mistranslated.

The=20 help translation was corrected.

46135

FaxUtil

The=20 "Refuse Distributions" option for members of groups that had the = option=20 could not be enabled, gave error message.

The=20 "Refuse Distributions" option can now be toggled without error=20 message.

46687

FaxUtil

The=20 option View > New = Faxes displays=20 a blank screen.

This=20 option now correctly displays only faxes that have not been=20 viewed.

46985

FaxUtil

When=20 FaxUtil fax list is opened, the oldest fax is always highlighted, = despite=20 settings.

The=20 fax that is highlighted upon opening FaxUtil is now correctly = determined=20 by display settings.

47457

FaxUtil

After=20 upgrading to version 9.0 faxes with the status "duplicate" will = not open=20 in FaxUtil.

Duplicate=20 faxes now open as expected.

47094

GammaLink=20 Adapters

PDF=20 attachments using fine mode (200 x 200 dpi ) are received at 200 x = 100 dpi=20 when sent through GammaLink fax boards.

Fine=20 mode setting corrected on GammaLink fax boards.

45104

Notes=20 Client

Faxes=20 sent via iNotes leave multiple entries in the fax send = log.

Each=20 sent fax now logged only one time.

46588

Notes=20 Client

Misaddressed=20 faxes that are corrected and resent retain the status "in process" = in the=20 fax send log.

These=20 faxes are now updated in the send log as "sent."

46809

Notes=20 Client

After=20 upgrading from 8.x to 9.0, administrators are not able to edit = some=20 synchronized user accounts because complete user account name not=20 synched.

The=20 complete user name is now synchronized and editing is = possible.

47821

Notes=20 Client

Unable=20 to change the Notes mail integration by using the Update Mail = Integration=20 button in the connections document.

This=20 feature now lets you update the Notes Mail Integration = type.

44421

Notes=20 Gateway

Failed=20 fax notifications do not work when sending to multiple = addresses.

Corrected.=20 Failed fax notifications now work as expected.

46522

Notes=20 Gateway

E-mail=20 messages submitted to the RightFax Mail Router with multiple fax=20 recipients results in multiple History.txt files being appended to = the fax=20 send logs in the EFM Sync database.

Only=20 one History.txt file appended as expected.

47728

Notes=20 Gateway

With=20 a Minimal Mail Integration, when synchronizing users from Notes to = RightFax the Notification Address/Info field is empty.

This=20 field now populates correctly during synchronization with the = Minimal=20 Notes Integration.

46824

SAP

SAP=20 Gateway sends unusable notification information.

Notifications=20 through the SAP Gateway corrected.

46234

SecureDocs

A=20 secure PDF sent via Certified Delivery can be opened without a=20 password.

Corrected.=20 Password now required on secured PDFs.

47777

SecureDocs

Sending=20 SecureDocs from Outlook only creates empty SecureDoc recipient = mailboxes=20 .

SecureDocs=20 mailboxes now correctly populated with the sent = document.

1195

Server=20 Module

Autoforward=20 feature does not copy the fax history.

The=20 fax history is now included with documents forwarded with the = autoforward=20 feature.

46285

Server=20 Module

Cannot=20 send a fax through the HPFAX queue if the user account does not = already=20 exist.

A=20 new RightFax user account is now created automatically based on = the user's=20 NT login.

47478

SMTP=20 Integration

SMTP=20 Gateway strips all attachments from outbound faxes.

Attachments=20 now retained as expected when sent via SMTP Gateway.

47611

SMTP=20 Integration

E-mail=20 messages submitted through the SMTP Gateway do not word-wrap. =

E-mail=20 messages submitted through the SMTP Gateway now word-wrap as=20 expected.

46167

Web=20 Access

Attempting=20 to view an SMS message through Web Access causes error = message.

Corrected.=20 SMS messages can now be viewed through Web Access.

46236

Web=20 Access

Web=20 Access fails to check a RightFax user's permission = settings.

Web=20 Access now restricts user activity based on the RightFax = permissions=20 settings.

46890

Web=20 Access

E-mail=20 notifications of documents received into Web Access include = incorrect=20 hyperlink to document.

Corrected=20 hyperlink to correctly point user to their received = document.

47044
47045
47046
47051

Web=20 Access

Some=20 text in the localized versions of Web Access was mistranslated. =

Translations=20 corrected.

47738

Web=20 Access

Forwarding=20 a fax to a new destination through Web Access drops all body pages = and=20 sends only the cover page.

Forwarded=20 faxes now include body pages as expected.

47814

Web=20 Access

Zooming=20 and scrolling in the Web Access fax viewer frame causes faxes to = become=20 unviewable until next login.

Image=20 display errors corrected.

46570

WorkServer=20 Module

Active=20 Directory synchronization does not work with more than one = Organizational=20 Unit.

Active=20 Directory synchronization now supports more than one = Organizational=20 Unit.

46574

WorkServer=20 Module

Group=20 membership changes are ignored when synchronizing with Active=20 Directory.

Group=20 membership changes are now retained when synchronizing with Active = Directory.

47789

WorkServer=20 Module

PDF=20 conversion causes WorkServer error (LGSD:Library Already Loaded = ).

Corrected.=20 PDF conversion no longer prompts WorkServer error = message.

47963

WorkServer=20 Module

FileNet=20 OEM WorkServers do not convert HTML cover sheets.

FileNet=20 OEM WorkServers now convert HTML cover sheets as=20 = expected.

 

 =20

The following software fixes were released for = RightFax 8.7=20 Service Pack 3, and are also incorporated into RightFax 9.0 Feature Pack = 1:

 

Captaris Tracking Number

Module

Problem

Solution

39839

Alerting

Fax = channel=20 monitoring reports error when last channel is selected. Monitors = incorrect=20 channels numbers.

Fax = channel=20 monitoring correctly monitors fax channels.

41470

BoardServer

When = analog TR1034=20 fax boards are in use, the BoardServer does not correctly process = DTMF=20 digits for routing.

The = BoardServer now processes DTMF digits for = routing.

41767

BoardServer

The = BoardServer=20 module crashes if a dialing rule to disallow sending is listed = after but=20 matches the pattern of a previous rule.

The = described=20 behavior no longer occurs. Dialing rules are executed as=20 expected.

42097

BoardServer

The file=20 Callctrl.cfg includes incorrect syntax for the num_rings=20 parameter.

This = parameter has=20 been corrected in Callctrl.cfg.

43357

BoardServer

Running = the=20 BoardServer module in debug mode through EFM pushes CPU usage to=20 100%.

Debug = error=20 corrected.

44160

BoardServer

ECM=20 setting for Brooktrout boards stays enabled even if disabled in = the=20 BoardServer configuration application.

ECM=20 setting now reads correct setting from the BoardServer = configuration=20 application as expected.

40068

Brooktrout=20 TR1034

When = restarting a=20 RightFax server installed on a Compaq machine (e.g. DL380 G3), = running=20 Compaq's Surveyor utility with Windows 2003 Server, and Brooktrout = TR1034=20 fax boards installed, the server hangs.

Hang on = reboot=20 problem resolved.

41948

Brooktrout=20 TR1034

TR1034 = boards=20 configured for PRI-E1 have the pcm_law parameter configured=20 incorrectly.

This = parameter is=20 now correctly configured as "alaw" instead of = "mulaw."

41951

Brooktrout=20 TR1034

Deactivating one or=20 more channels on the TR1034 (PRI) is not reflected correctly in=20 callctrl.cfg.

This = value is now=20 correctly written to Callctrl.cfg.

42242

Brooktrout=20 TR1034

TR1034 = analog=20 channels report as "Offline Permanently" when in the same machine = as=20 digital TR1034 boards configured as PRI-ISDN.

TR1034 = analog=20 channels now function properly when in the same machine as digital = TR1034=20 boards configured as PRI-ISDN.

42841

Brooktrout=20 TR1034

TR1034=20 will not dial more than 24 digits.

Corrected.=20 Unlimited dialing characters supported.

44021

Brooktrout=20 TR1034

TR1034 = BRI boards=20 fail to receive faxes via the Siemens HiPath PBX.

TR1034 = BRI boards=20 now correctly receive faxes via the Siemens HiPath = PBX.

44089

Brooktrout=20 TR1034

Frequent = channel=20 reset failures on inbound faxes when running one or more = TR1034+P4-4L=20 boards with RightFax 8.7 FP1 with IBM Series 235.

Channel = reset=20 problem resolved.

44220

Brooktrout=20 TR1034

DTMF = routing for a=20 fax channel with the option "Initial Speech" set requires users to = wait=20 for the entire voice greeting to end before the system will accept = entered=20 digits.

Routing = digits can=20 now be entered at any time during the voice = prompt.

44271

Brooktrout=20 TR1034

Eccdlld.dll file=20 not found error when running voice.exe for the TR1034 = board.

Voice.exe = now finds=20 eccdlld.dll as expected.

37114

ChgUser.exe

When=20 running ChgUser.exe and the NONTSECURITY keyword is used in the = command=20 line, the "Stamp Pages of Received Faxes with Audit Stamp" option = is=20 enabled in the user record. =  

The=20 NONTSECURITY keyword in ChgUser.exe no longer automatically = enables the=20 "Stamp Pages of Received Faxes with Audit Stamp" = option.

41293

E-mail=20 Gateways

After a = Satellite=20 Server is bumped, the cc:Mail, MS Mail, Groupwise, and SMTP E-mail = Gateways are unavailable for install.

Bumping a = Satellite=20 Server now makes these e-mail Gateways = available.

42833

Embedded=20 Codes

After = upgrading=20 from RightFax 7.2 to RightFax 8.7, some embedded codes (such as = NEWDEST)=20 inappropriately generate a fax cover sheet.

Embedded = codes no=20 longer inappropriately generate fax cover = sheets.

42217

Enterprise Fax=20 Manager

Selecting = the=20 option=20 =  "Disallow = Fax Annotation" also disables the ability to print, forward, = route, and=20 more.

Selecting = the=20 option=20 =  "Disallow = Fax Annotation" no longer affects other user = permissions.

35668

Exchange=20 Gateway

The = option to=20 "Break up Large Faxes" sends faxes above the specified page=20 limit.

The = option to=20 "Break up Large Faxes" now correctly sends faxes at the specified = page=20 limit.

42103

Exchange=20 Connector

Faxes=20 routed to e-mail via the Exchange connector use full path to the=20 attachment for the file name, which made the file unreadable by = certain=20 devices.

Faxes=20 routed to e-mail via the Exchange connector no longer include the = full=20 path in the file name.

44119

Exchange=20 Connector

Exchange=20 5.5 displays warnings for every processed fax if you have Message = Tracking=20 enabled on the connector.

Problem=20 fixed. Warning messages no longer appear.

44963

Exchange=20 Connector

Microsoft = Exchange=20 System Manager crashes when adding a user that is not in the Users = container on the Delivery Restrictions tab.

This = action no=20 longer crashes Microsoft Exchange System = Manager.

41685

Fax=20 Control

Print-to-Fax on a=20 file with a long file name (150 characters or higher) = fails.

Print-to-Fax on=20 files with long file names (150 characters or higher) work as=20 expected.

41973

Fax=20 Control

JPEG = files=20 converted to fax format appear small and = compressed.

JPEG = files now=20 convert to fax format as expected.

45057

Fax=20 Control

When=20 using the Quick Fax/Broadcast feature, users can change phonebook = entries=20 even when not assigned this permission.

Quick=20 Fax/Broadcast feature now correctly blocks users from changing = phonebook=20 entries if they are not assigned this permission.

30461

Fax=20 Reporter

In=20 Fax Reporter, the Folder column in the Faxes table is not = populated=20 correctly.

Folder=20 column in the Faxes table now reports folder names as = expected.

31869

Fax=20 Reporter

FaxReporter=20 misreports scheduled send time in the FaxSendDateTime column if a = fax was=20 delayed.

Delayed=20 faxes now correctly report the scheduled send time in the = FaxSendDateTime=20 column.

42209/
44020

Fax=20 Reporter

Fax=20 Reporter data does not refresh if the network protocol is set to = TCP/IP=20 and then changed to either Named Pipes or Automatic = Selection.

Fax=20 Reporter data now correctly refreshes if network protocol setting = is=20 changed.

41543

Fax=20 Server

"Fax not = viewed or=20 printed" notifications are always sent to the Group Administrator = when=20 users route faxes to an E-mail Gateway, even if option for no=20 notifications is selected.

The = option for to=20 disable notifications to the Group Administrator now works as=20 expected.

44243

Fax=20 Server

Applying = Tracks=20 patch 40069 causes files to be routed in 8.3.3 file format instead = of an=20 8.3 format.

Applying = Tracks=20 patch 40069 now correctly causes files to be routed in 8.3=20 format.

42494

Fax=20 Status

Fax = Status=20 application crashes when viewing the status of a fax channel = transmitting=20 at V.34.

Fax = Status=20 application no longer fails when viewing v.34=20 transmissions.

41673

FaxUtil

Odd-sized = tiff=20 images, when sent as file attachments, fail to = convert.

Attached = tiff=20 images convert as expected.

41682

FaxUtil

FaxUtil=20 will not run if no RightFax server name was specified during = client=20 installation.

Leaving=20 the RightFax server name blank during installation no longer = causes=20 FaxUtil to fail.

41742

FaxUtil

After = closing the=20 Phonebook window, faxes appear to lose their corresponding filter=20 information (sent/received, to/from/file, etc.). Deleting one of = these=20 faxes causes FaxUtil to appear to perpetually delete = faxes.

The = described=20 behavior no longer occurs and deleting faxes works as=20 expected.

41822

FaxUtil

FaxUtil = folders=20 default to the order they were created, even if alphabetical order = is=20 specified.

FaxUtil = folders now=20 correctly display in alphabetical order.

41890

FaxUtil

FaxUtil = lists the=20 same fax repeatedly after opening the Fax Viewer, forwarding to = new=20 number, and then using the phonebook to select a recipient. =

Corrected = so that=20 no duplicate fax entry is displayed.

43987

FaxUtil

FaxUtil = lists the=20 same fax repeatedly after opening the Fax Viewer, forwarding to = new=20 number, and then using the phonebook to select a recipient. =

Corrected = so that=20 no duplicate fax entry is displayed.

44707

FaxUtil

Faxes = that are in=20 the "Needs Approval" status will not go back to that status after=20 printing. Status stays as "Printing" indefinitely.

After = printing a=20 fax in the "Needs Approval" state, fax returns from status = "Printing" to=20 status "Needs Approval."

44833

FaxUtil

Attached = text files=20 that contain tab characters do not word wrap correctly on = conversion to=20 fax format.

You=20 can now customize the maximum number of characters per line. = Navigate to=20 the registry key=20 HKEY_LOCAL_MACHINE
\Software\Rightfax\Workserver\WorkSrv#, = add a new DWORD = registry=20 called WordWrapTextLength, and set the data for this new value = to=20 the maximum number of characters per line (e.g. 76). After adding = this=20 registry value, Open the WorkServer configuration application and = select=20 the option Use PCL Converter for = Text=20 Files. Then, restart the services.

45841

FaxUtil

When = attempting to=20 send a fax to an Outlook 2003 MAPI phonebook contact, FaxUtil = generates a=20 Dr. Watson error. Occurs only when an Outlook 2003 client has "Use = cached=20 exchange mode" enabled.

Error no = longer=20 occurs.

43661

FileNet=20 Connector

The=20 connector fails to process jobs from multiple source = servers.

The=20 connector now supports job processing from multiple servers as=20 expected.

41854

Human-Answered=20 Fax

Selecting = the=20 option "Always start each call in voice mode" causes the fax board = to=20 automatically hang up after 12 seconds on outbound calls. =

Selecting = the=20 option "Always start each call in voice mode" no longer causes the = fax=20 board to automatically hang up.

42503

Human-Answered=20 Fax

The = Human-Answered=20 Fax feature, using TR1034 analog boards with the "Always start" = option=20 enabled, reports status "OK" when dialing times out without an = answer.=20

Faxes now = correctly=20 report status "No answer at fax number."

42534

Human-Answered=20 Fax

The = Human-Answered=20 Fax feature, using TR1034 analog boards with the "Always start" = option=20 enabled, reports status "OK" when a busy signal is encountered.=20

Faxes now = correctly=20 report status "Busy."

32530

ImpUser.exe

The=20 last entry in a .csv file fails to import unless a carriage return = follows.

Fixed=20 so that carriage return is no longer required.

33203

ImpUser.exe

All=20 users exported from RightFax and re-imported using ImpUser .exe = have=20 "Delete After Routing" option enabled.

ImpUser.exe=20 now correctly retains =  "Delete=20 After Routing" setting.

41750

Mimesend

Mimesend = fails to=20 send to all recipients if any single recipient in a particular = group has a=20 bad e-mail address.

Mimesend = now=20 ignores only the bad e-mail addresses and sends to all others as=20 expected.

41611

Notes=20 Gateway

Under=20 certain circumstances, user synchronization between Notes and = RightFax was=20 incorrectly synching changes to Notes users with the RightFax = server when=20 synchronization was specifically set to only flow from RightFax to = Notes.

Corrected=20 directional synchronization error.

37666=20

ODBCSync.exe

When=20 synching a new user into a group whose name contains a space, the = new user=20 is not created in RightFax.

RightFax=20 now correctly reformats the group name, replacing spaces with = underscore=20 characters, and adds the user to the new group.

39682

ODBCSync.exe

When=20 synching a new user whose name contains a space, the new user = created with=20 an underscore replacing the space as expected, but re-running = ODBCSync.exe=20 will generate arror and fail to update these users.

Importing=20 user names with spaces no longer generates error and updates as=20 expected.

40310

ODBCSync.exe

RightFax=20 IDs that have been created with ODBCSync.exe and had a source ID = more than=20 21 characters long fail to update when re-running = ODBCSync.exe.

Importing=20 user names with more than 21 characters no longer generates error = and=20 updates as expected.

41814

Outlook = Advanced=20 Form

The = "Delay Send"=20 option on the Outlook Advanced form shows the Date field twice = instead of=20 Date and Time.

The = "Delay Send"=20 option on the Outlook Advanced form now correctly shows Date and = Time=20 fields.

43610

Outlook = Advanced=20 Form

Some = faxes appear=20 blank when viewed with the Outlook Advanced Form with Outlook=20 2003.

All faxes = now=20 display as expected.

43913

Outlook=20 Advanced Form

Outlook=20 2003 terminates unexpectedly when opened minimized and custom user = variables exist with Outlook Extensions installed.

Outlook=20 2003 no longer terminates when minimized and then = closed.

45705

Outlook = Advanced=20 Form

Outlook = hangs when=20 receiving a fax in Outlook with McAfee 8.0i enterprise=20 installed.

Outlook = no longer=20 hangs on receiving a fax.

31969

PDF

PostScript=20 documents that contain the PostScript command "setpagedevice" fail = conversion to fax format for transmission.

The = PostScript=20 command "setpagedevice" is now processed correctly and does not = cause fax=20 conversion failure.

41573

PDF

Adobe 6 = PDF images=20 acquired using TWAIN scanners shrink to 1/3 original size. =

Adobe 6 = images now=20 attach at full size.

41676

PDF

Compressed PDF file=20 fails conversion.

Compressed=20 PDF files convert as expected. Requires SSA NativeDocControl PDF,2 = for=20 WorkServer.

42263

PDF

PDFs with = embedded=20 Asian fonts convert incorrectly to fax format.

Asian = fonts now=20 convert to fax format as expected.

42693

PDF

The -d = switch for=20 Pssplit.exe does not cause debug information to write to the = screen or=20 event viewer.

The -d = switch for=20 Pssplit.exe now correctly outputs debug = information.

43227

PDF

Converting=20 a document that contains a barcode font to PDF using = NativeDocControl=20 fails to properly convert the barcode.

Corrected.=20 The font is properly converted when corresponding .TTF file is = located in=20 the Worksrv\Fonts folder.

43377

PDF

PDF=20 images generated on the HP4100 have stripes running through the=20 image.

Problem=20 corrected. PDF images convert as expected.

44108

PDF

PDFs=20 created from documents with graphic images in the header or footer = convert=20 with poor image quality.

Graphic=20 conversion corrected to retain image quality.

34653

PhnPrint.exe

PhnPrint.exe=20 commands that specify multiple users but only supply some of the = users'=20 passwords outputs data as though no passwords had been = supplied.

PhnPrint.exe=20 now recognizes a partial list of passwords and outputs data = accordingly.=20

42555

PhnPrint.exe

Level=20 2 output for PhnPrint.exe does not output all expected data = fields.

Level=20 2 output for PhnPrint.exe corrected so that it now outputs all = expected=20 data fields.

35199

Production

The = Mailsend.exe =  -o switch = converts all recipient e-mail address to ASCII, causing mail = transmission=20 failure.

Mailsend.exe -o=20 switch preserves recipient e-mail addresses correctly and mail = transmits=20 as expected.

37199

Production

Bumping a = Business=20 Server with the Integration Module enables no production fax=20 channels.

The = production fax=20 channels are now correctly enabled when a Business Server with = Integration=20 is bumped.

41396

Production

MapText.exe image=20 preview does not work.

MapText.exe image=20 preview works as expected.

42954

Production

When=20 PORTLSTN.exe is enabled in the Integration Module control = panel=20 application, a Dr. Watson error is reported when the Integration Module=20 service is stopped.

Corrected=20 issue. Dr. Watson error no longer occurs.

43168

Production

Running=20 NOTIFY.exe to add a new integration channel causes a Dr. Watson = error when=20 the Integration Module service is stopped.

Corrected=20 issue. Dr. Watson error no longer occurs.

34724

Rescue.exe

Running = Rescue.exe=20 causes all faxes that are currently waiting for transmission = because a=20 delay time was specified to fail to send.

Rescue.exe now=20 correctly preserves delayed faxes. Delayed faxes transmit at the = specified=20 time as expected.

41840

SAP

The = ProgID=20 parameter in the saprfc.ini file is always reset to = servername.sapgate=20 when closing configuration.

The = ProgID=20 parameter now retains its correct setting when closing = configuration.=20

41894

SAP

All=20 faxes sent via SAPOffice are sent as high priority.

Faxes=20 sent via SAPOffice now send with normal priority unless otherwise=20 specified.

44203

SAP

SAPGate=20 strips out data beginning with "<who".

SAP=20 no longer strips invalid SAP embedded code text.

44227

SAP

If=20 you add DefaultUserID as a Reg_SZ value to=20 HKLM\Software\RightFax\SAP\SAP#\ and send a fax through that SAP = Gateway,=20 it will not send from the user specified in that key, but will = send using=20 the Default user ID instead.

Registry=20 setting now correctly read by SAP connector.

12459

SecureDocs

Non-US=20 regional settings cause an inability to log in to SecureDocs = .

Corrected=20 date formatting to allow login with non-US regional = settings.

43116

SecureDocs

Under=20 certain circumstances, user administration through SecureDocs=20 fails.

Corrected=20 error so that user administration works as expected.

41270

SMTP=20 Gateway

Submitting=20 an e-mail to the SMTP Gateway that has embedded HTML in the body = with=20 embedded images causes the Gateway to stop = unexpectedly.

The SMTP = Gateway=20 now correctly processes HTML-referenced = images.

42990

SMTP=20 Gateway

A=20 fax with an attachment that is sent through the SMTP Gateway and = fails=20 conversion is incorrectly deleted from FaxUtil.

The=20 behavior in this circumstance is now configurable in the registry. = To=20 retain these faxes in FaxUtil with a "failed" status, navigate to = the=20 registry key HKEY_LOCAL_MACHINE\Software\Rightfax\Faxserver

and=20 set AutoDeleteFailedGatewayFaxes to 0. To retain the functionality = as=20 described, set=20 AutoDeleteFailedGatewayFaxes to 1.

43282

SMTP=20 Gateway

Fax=20 conversion error notifications are returned to the sender via = e-mail, even=20 if all notification options are disabled.

This = behavior is=20 now configurable in the registry. To disable these notifications, = navigate=20 to the registry key = HKEY_LOCAL_MACHINE\Software\Rightfax\Faxserver,=20 add=20 a new DWORD registry called NoGatewayNotify, and set the data for = this new=20 value to 1.

46915

Standalone Fax=20 Connector

Standalone Fax=20 Connector does not work with TR1034 analog boards.

Connector = now dials=20 out as expected.

40288

Web=20 Client

Attaching = notes in=20 Web Client loses all characters after 80 if manual carriage = returns are=20 not entered.

You=20 can now customize the maximum number of characters per line. = Navigate to=20 the registry key=20 HKEY_LOCAL_MACHINE
\Software\Rightfax\Workserver\WorkSrv#, = add a new DWORD = registry=20 called WordWrapTextLength, and set the data for this new value = to=20 the maximum number of characters per line (e.g. 76). After adding = this=20 registry value, Open the WorkServer configuration application and = select=20 the option Use PCL Converter for = Text=20 Files. Then, restart the services.

35216

WorkServer

WorkServer=20 archiving of outbound documents fails when sending to an e-mail=20 address.

Faxes=20 sent to e-mail addresses are now archived as = expected.

41911

WorkServer

Autoprinting=20 inbound faxes to an HP LaserJet 4si prints only a single black=20 line.

HP=20 LaserJet 4si printers now autoprint correctly.

43699

WorkServer

Conversion of some=20 JPEG images results in poor image quality, especially when = converting=20 colors to grayscale.

You=20 can now customize the threshold setting when converting JPEG = images to=20 grayscale. Navigate to the registry key=20 HKEY_LOCAL_MACHINE\Software\Rightfax\Workserver, add a new DWORD = registry=20 called RFThresh, and set the data for this new value to an = appropriate=20 setting from 3-255. The default value used is 128. Increase this = value to=20 darken color images. To change the registry value, stop all = WorkServers, change the registry value on the server, then restart = the=20 WorkServers.

44398

WorkServer

WorkServer=20 fails to create TIFF-G4 for certain received faxes when routing to = network=20 directory.

Problem=20 corrected. TIFF-G4 created as = expected.

<< Return=20 to ReadMe Contents

Documentation Additions and Corrections = from=20 Feature Pack 1

New versions of the RightFax documentation have been = updated=20 for RightFax 9.0 Feature Pack 1. Although the Feature Pack installation = will not=20 make any changes to the guides in your RightFax\Docs folder, the new = versions of=20 the documentation are available for download from the same Web page = where you=20 downloaded the Feature Pack installation. All of the updated guides that = have=20 changes listed in this section are available for download.

RightFax 9.0 Administrators = Guide

Chapter

5, "Configuring the DocTransport and = BoardServer=20 Modules"

Section

"Running DocTransport and BoardServer Services = on Remote=20 Computers"

Page

74

Error

The documentation fails to mention that = running remote=20 DocTransport and BoardServer modules over a WAN is a supported=20 configuration.

Resolution

A note regarding this support has been = included in the=20 Administrator's=20 Guide.

=09

 

 

 

 

Chapter

10, "Creating = Signatures"

Section

"Adding a Signature to a=20 file"

Page

123

Error

The documentation fails to mention that = signature=20 files are not supported in PostScript=20 documents.

Resolution

A note regarding this support issue has been = included=20 in the Administrator's=20 Guide.

=09

 

 

 

 

Chapter

22, "Creating, Sending, and Deleting=20 Faxes"

Section

"Using International Character=20 Sets"

Page

235

Error

Instructions necessary to ensure that = international=20 character sets appear properly on RightFax cover pages=20 incomplete.

Resolution

Information on this subject has been updated = and=20 clarified and relocated to the RightFax=20 Installation Guide.

=09

 

 

 

 

Chapter

26, "Working with the RightFax Database and=20 Administrative Utilities"

Section

"Changing the Connection to the SQL=20 Server"

Page

270

Error

The instructions for changing the SQL = connection=20 string omit two additional steps.

Resolution

The SQL connection string must also be = changed in the=20 DocTransport module and in the registry. Instructions for this are = in the=20 Administrator's Guide updated for version 9.0 Feature Pack 1 on = page=20 270.

=09

 

 

 

 

RightFax 9.0 Microsoft Exchange Module Guide =

Chapter

1, "Activating and Configuring the RightFax = Microsoft=20 Exchange Module"

Section

Adding = and=20 Configuring the RightFax Microsoft Exchange Module=20 Service

Page

9

Error

Microsoft Exchange imposes a sending limit = of about=20 100 documents during a MAPI session. The workaround to bypass this = limit=20 is not documented.

Resolution

The following workaround has been added to = the=20 Microsoft Exchange Module Guide:

Edit the Windows registry and navigate to=20 HKEY_LOCAL_MACHINE\Software\RightFax\Gateway. Add a new DWORD = value called=20 AvoidServerLimits and set its value to = 1.

=09

 

 

 

 

Chapter

Various

Section

Various

Page

Various

Error

Documentation for configuring Echange 5.5 is = included=20 in the guide, although support for Exchange 5.5 was dropped in = RightFax=20 version 9.0.

Resolution

All references to Exchange 5.5 have been = removed from=20 the Guide

=09

 

 

 

 

RightFax 9.0 Installation Guide =

Chapter

3, Installing the RightFax Server=20 Software

Section

Running a silent install of the RightFax = server=20 software

Page

31

Error

The list of required settings in the=20 ServerProperties.txt file for upgrades omitted three required=20 properties.

Resolution

The following settings are also required for = upgrades:=20 IS_SQLSERVER_PASSWORD, = IS_SQLSERVER_SERVER,=20 IS_SQLSERVER_USERNAME.

=09

 

 

 

 

Chapter

3, Installing the RightFax Server=20 Software

Section

Running = Silent=20 Installs of the Server and Fax Board=20 Drivers

Page

34

Error

The example batch files for silently = installing=20 Microsoft Windows Installer and the RightFax server included a = command to=20 run instmsiw.exe, but this is no longer=20 required.

Resolution

All references to instmsiw.exe have been = removed from=20 the sample batch files.

=09

 

 

 

 

RightFax 9.0 Integration Module Guide =

Chapter

Various

Section

Various

Page

Various

Error

The 9.0 version of the documentation omitted = a new=20 document type {{type SMS}}.

Resolution

This document type lets you send a specified = message=20 to an SMS-compatible device. The FCL code for this document type=20 follows:

{{type SMS}}
{{sms ###-###-####}}
{{smsmsg = text}}

=09

 

 

 

 

RightFax 9.0 Lotus Notes Module Guide =

Chapter

1, Installing the Lotus Notes=20 Module

Section

Activating and=20 Configuring the Lotus Notes = Module

Page

7

Error

The documentation omits some inportant = information=20 about failovers in Domino cluster=20 environments.

Resolution

If you are running the Lotus Notes module in = a=20 clustered Domino server environment, note that faxes that are sent = during=20 a failover of the node used to install the RightFax gateway will = sit in=20 the MAIL.BOX of the node being used by the Notes clients. When the = node=20 used to install the RightFax Gateway is returned to service, those = faxes=20 will be processed according to your Domino Connections document=20 configuration. Please see your Domino documentation for = instructions on=20 configuring your Connections = document.

=09

 

 

 

 

Chapter

1, Installing the Lotus Notes=20 Module

Section

Installing the Databases for Full Notes Mail = Integration

Page

11

Error

The documentation did not mention an = additional=20 required step during upgrades from version 8.x to=20 9.0.

Resolution

Because the name of the EFM Sync database = file was=20 changed between version 8.x and 9.x, the administrator must resend = the=20 Connections document to each fax user in the EFM Sync database, = after=20 upgrading from version 8.x.

=09

 

 

 

 

Chapter

3, Using the RightFax Lotus Notes=20 Module

Section

Introduction = text

Page

39

Error

The documentation fails to mention sending=20 requirements for certified delivery and SecureDocs=20 documents.

Resolution

Sending RightFax messages of type "Document" = (for=20 Certified Delivery) requires that the recipient have an SMTP = e-mail=20 address, and sending RightFax messages of type "SMS" requires that = the=20 recipient have a cell phone number. Either of these may be picked = from=20 from the Domino Directory or from the Personal Address Book. If = the=20 required information is not present, the user will not appear in = the=20 address of the memo once the Addressing dialog box has been=20 closed.

=09

 

 

 

 

Chapter

3, Using the RightFax Lotus Notes=20 Module

Section

Introduction = text

Page

39

Error

The documentation did not mention that = prioritization=20 of outbound faxes is controlled by the Domino prioritization=20 settings.

Resolution

The priority setting on faxes sent from the = Notes=20 client uses the Domino prioritization settings. If a fax is sent = with low=20 priority, and the Domino server is configured to send low priority = messages at midnioght (the dafault Domino setting), then the fax = will not=20 be delivered to the RightFax server until=20 midnight.

=09

 

 

 

 

RightFax 9.0 SecureDocs Module Guide =

Chapter

2, "Installing the SecureDocs=20 Module"

Section

Understanding the Installation=20 Process

Page

8

Error

The documentation states that a separate = SecureDocs=20 component must be selected when the RightFax server is=20 installed.

Resolution

The SecureDocs software on the RightFax = server is=20 installed automatically with all server installs, and only = requires that=20 its functionality be licensed and = activated.

=09

 

 

 

 

<< Return=20 to ReadMe Contents

=A92005 Captaris. All rights = reserved.