This Readme file provides late-breaking or other information that supplements the RightFax documentation. Feature packs are the means by which RightFax product updates are distributed from the Captaris Web site. A feature pack may contain new product features, updates for system reliability, program compatibility, performance improvements, and more. All feature packs are cumulative. Each contains new features plus all the features from previous feature pack releases.
This document describes the current update to this version of the RightFax server and client software. It provides installation instructions, descriptions of the new features, a brief description of problems fixed with this release, and some updates and corrections made to the documentation.
By the time you receive this software, updates to other RightFax software may be available. To obtain updates, go to http://www.captaris.com/support.
This feature pack should be installed on all version 9.0 RightFax servers, remote BoardServer computers, IIS servers, Exchange Connector servers, Gateway servers, and client computers on your network. The Feature Pack 1 installation will determine the components that have been installed on each of these computers and upgrade them accordingly. This Feature Pack installation will only upgrade existing installations of the RightFax 9.0 server and client applications. It cannot be used for new installations of any server or client applications. To update your software, Microsoft Windows Installer patches your existing RightFax installation by replacing existing files with updated files and installing new files.
Important: Before running this upgrade, if you have one or more Brooktrout TR1034 fax boards installed, you must confirm that the file bos_btcall.cfg in the \RightFax\RFBoard folder is not set to read-only. If it is, remove the read-only attribute from this file prior to installing the service pack. Running the service pack installation with this file set to read-only will fail to properly update the file and the fax boards will not operate.
Follow these steps on each of your organization's 9.0 RightFax servers, remote BoardServer computers, IIS servers, Gateway servers, and client computers.
Download either the North American or International version of the upgrade ZIP file, depending on which of these installations you ran for the core 9.0 software, and extract the files. Each ZIP file includes three update executables: the client/server update, the SOAP server installation (described here), and the administrative utilities update (described here). The North American client/server update file is called RPS SP1 Patch North American.exe. The International client/server update file is called RPS SP1 Patch International.exe. Save this file to a location on your network accessible by all RightFax server and client computers on which it will be run.
Log on to the RightFax computer as an administrator.
Run the update program from its location on the network.
At the introductory screen, click Update. A status bar indicates the progress of the installation.
When the installation is complete, click Finish.
The SOAP client/server installation lets RightFax users use the Print-to-Fax feature from any computer with an Internet connection. The SOAP server must be installed on an IIS server running version 9.0 of RightFax Web Access. The SOAP client then accesses RightFax through that server. This provides RightFax functionality to home-office or other remote employees who do not have direct access to your organization's network. There are two components to the SOAP installation: install the SOAP server on the IIS computer running RightFax Web Access, and then install the SOAP client on the remote client computers.
Update the RightFax Web Access installation on the Web Access IIS server according to the instructions in the section Installing Feature Pack 1 on RightFax Servers and Client Computers.
Log on to the Web Client IIS server as an administrator.
Navigate to the SOAP server installation file RightFax SOAP Server.exe that you extracted from the downloaded ZIP file (described here).
At the introductory screen, click Next.
Read and select the option to accept the terms of the license agreement. Click Next.
Click Install to begin the installation. A status bar indicates the progress of the installation.
When the installation is complete, click Finish.
When you install the SOAP server on the Web Access IIS server, the SOAP client installation file RightFax Client for the Web.exe is installed in the Program Files\RightFax\WebApps\WebUtil\Client Install folder. You must send this file via e-mail, copy it to a removable storage medium, or otherwise make it available to the remote clients. Follow these steps on each remote computer to install the SOAP client:
Run the RightFax SOAP client installation file RightFax Client for the Web.exe.
At the introductory screen, click Next.
Enter the Web address of the SOAP server (e.g., www.MyCompany.SOAPServer.com) and the machine name of the RightFax server when prompted. Click Next.
Click Install to begin the installation. A status bar indicates the progress of the installation.
When the installation is complete, click Finish.
After you install the RightFax SOAP client, a RightFax tray icon will appear in the computer's Start bar. Users can access RightFax Print-to-Fax features through the shortcut menu from this icon. Users can also print documents directly to the RightFax Fax Printer (a new printer type that the client installation adds), which prompts for fax addressing information and transmits the document via the RightFax server.
The RightFax Administrative Utilities are installed separately from other RightFax server and client components. Follow these steps to update the RightFax Administrative Utilities on all computers where they are already installed.
Log on to the computer with the RightFax Administrative Utilities installed.
Navigate to the file Administrative Utilities SP1.exe that you extracted from the downloaded ZIP file (described here).
At the introductory screen, click Update. A status bar indicates the progress of the installation.
When the installation is complete, click Finish.
The RightFax Client Installs folder lets you store the RightFax client installation files on your network so that you can easily run all new RightFax client installations from that location. The installation files in this folder should be used for all new client installations. Existing clients should be upgraded by running the Feature Pack 1executable file directly on each client computer.
Follow these steps on the server where the version 9.0 RightFax Client Installs folder resides (described in the RightFax Installation Guide):
Download either the North American or International version of the upgrade executable, depending on which of these installations you ran for the core 9.0 software. The North American download file is called RPS SP1 Patch North American.exe. The International download file is called RPS SP1 Patch International.exe. Save this file to a temporary location of your choice, e.g., the C:\temp folder.
Open a command prompt and navigate to the existing client installs folder where the file RightFax Product Suite.msi is located.
At the command prompt,
enter:
"C:\temp\RPS SP1 Patch
North American.exe
" /V"/a RightF~1.msi
(for the North American upgrade)
or
"C:\temp\RPS SP1 Patch
International.exe
" /V"/a RightF~1.msi
(for the international upgrade)
Once the installer window is displayed, follow the on-screen prompts to update the client installs to Feature Pack 1. If the installer fails to display or if you receive an error message, verify the path to the temporary folder where you saved the upgrade executable file.
After the RightFax client installs folder on your network has been upgraded, it should be used for new client installations only. If you want to upgrade existing RightFax client installations, you should run the RPS SP1 Patch North American.exe or RPS SP1 Patch International.exe file directly on each client computer.
After you upgrade the RightFax server to version 9.0 Feature Pack 1 (described in the section Installing Feature Pack 1 on RightFax Servers and Client Computers), the Notes update file NGPatch.NSF is copied into the \RightFax\Gateway folder. The steps for applying this update to the Notes Gateway depends on the type of installation you already have. To upgrade Notes, follow only the steps under the heading listed below for your specific installation type.
Caution: If you left files in the temp directory after your last installation, those files must be removed or a different temp directory specified during the install in order for the databases to be updated correctly.
Note: In a clustered Notes environment, documents that are sent while a node is failed over are held in the MAIL.BOX of the server to which the client is connected. When the node on which the Notes Gateway is installed is returned to service, outbound messages are processed according to the settings on the Connections document.
To ensure the previous version files are deleted during the upgrade when running the 9.00 installer and 9.01 installer back-to-back, you should take the following steps
Complete the 9.0 installer.
Close the Notes client from which the installer is being run.
On the Domino server console, type "dbcache flush." This will not delete any data, but will free up connections that are currently in use but are still cached.
Re-open the Notes client and continue with the 9.01 Installer.
For update instruction for your specific Notes Gateway
configuration, click the appropriate setting:
Copy NGPatch.NSF from the \RightFax\Gateway folder on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
Run the Lotus Notes client and open the RightFax 9.01 installer database file NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or select
a different, empty folder.
Follow the instructions in the RightFax Lotus Notes Module Guide for completing the installation after the last step of the installer has run.
On the RightFax server, run the RightFax E-mail Gateway program from Windows Control Panel. This opens the E-mail Configuration dialog box.
Click the Copy Notes Database button.
When you receive a message that the database has been successfully copied, click OK to close the message, and then click OK to close the E-mail Configuration dialog box.
Run Enterprise Fax Manager and stop the RightFax E-mail Gateway Module service.
Copy NGPatch.NSF located in the \RightFax\Gateway folder on the RightFax server and NGInstal.NSF in the \Lotus\Notes\Data directory on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
Run the Lotus Notes client and open the RightFax 9.00 Installation Database NGInstal.NSF to upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide for information on running this installation. When the installation is complete, do not set any configuration options for version 9.0.
Run the Lotus Notes client and open the RightFax 9.01 Installer database NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or select
a different, empty folder.
If applicable, delete the file RF80SYNC.NSF from the Lotus\Domino\Data\RIGHTFAX folder on the Domino server.
Follow the instructions in the RightFax Lotus Notes Module Guide for completing the installation after the last step of the installer has run.
On the RightFax server, run the RightFax E-mail Gateway program from Windows Control Panel. This opens the E-mail Configuration dialog box.
Click the Copy Notes Database button.
When you receive a message that the database has been successfully copied, click OK to close the message, and then click OK to close the E-mail Configuration dialog box.
Run Enterprise Fax Manager and stop the RightFax E-mail Gateway Module service.
Copy NGPatch.NSF located in the \RightFax\Gateway folder on the RightFax server and NGInstal.NSF in the \Lotus\Notes\Data directory on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
On the Lotus Notes Client
machine, run Notes Designer and uncheck the Prohibit
checkbox on the Design tab of
the following element properties:
MAIL50.NTF
Forms:
New
RightFax Fax
RightFax
Connections
RightFax
User Options
Folders:
Real-time
Fax Status
RightFax
Settings
Agents:
(RightFAX
Convert Picklist Names to FAX Addresses)
SubForms:
(RightFAX
Autoforward Profile)
(RightFAX
Autoforward Warning)
(RightFAX
Send Options)
Script
Libraries:
(RightFAX
Script Library)
...Other:
Icon
"Using
Database" Document
"About
Database" Document
EFM SYNC:
Folders:
Real-Time
Fax Status
RightFax
Settings
...Other:
Icon
"Using
Database" Document
"About
Database" Document
ICD ROUTER
...Other:
Icon
"Using
Database" Document
"About
Database" Document
Run the Lotus Notes client and open the RightFax 9.00 Installation Database NGInstal.NSF to upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide for information on running this installation. Complete the upgrade configurations for version 9.0 according to the instructions in the RightFax Lotus Notes Module Guide.
Run the Lotus Notes client and open the RightFax 9.01 Installer database NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or select
a different, empty folder.
If applicable, delete the file RF80SYNC.NSF from the Lotus\Domino\Data\RIGHTFAX folder on the Domino server.
Follow the instructions in the RightFax Lotus Notes Module Guide for completing the installation after the last step of the installer has run.
Copy NGPatch.NSF from the \RightFax\Gateway folder on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
Run the Lotus Notes client and open the RightFax 9.01 installer database file NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or specify
a different, empty folder
After completing step 10 in the installation, view the install log
by clicking the button in the top left of the Installer window, and confirm
that the previous install files were successfully deleted. If not, you
must manually delete these files before continuing with the installation.
Re-send the Connections document to each person listed in the EFM Sync database.
Instruct each user to run the Update from their mail file to download the updated Fax Factory, and then open the User Options document from within the Fax Factory database and Save and Close the document to update the remaining mail elements.
On the RightFax server, run the RightFax E-mail Gateway program from Windows Control Panel. This opens the E-mail Configuration dialog box.
Click the Copy Notes Database button.
When you receive a message that the database has been successfully copied, click OK to close the message, and then click OK to close the E-mail Configuration dialog box.
Run Enterprise Fax Manager and stop the RightFax E-mail Gateway Module service.
Copy NGPatch.NSF located in the \RightFax\Gateway folder on the RightFax server and NGInstal.NSF in the \Lotus\Notes\Data directory on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
Run the Lotus Notes client and open the RightFax 9.00 Installation Database NGInstal.NSF to upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide for information on running this installation. When the installation is complete, do not set any configuration options for version 9.0.
Run the Lotus Notes client and open the RightFax 9.01 Installer database NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or specify
a different, empty folder
After completing step 10 in the installation, view the install log
by clicking the button in the top left of the Installer window, and confirm
that the previous install files were successfully deleted. If not, you
must manually delete these files before continuing with the installation.
If applicable, delete the file RF80SYNC.NSF from the Lotus\Domino\Data\RIGHTFAX folder on the Domino server.
Follow the instructions in the RightFax Lotus Notes Module Guide for completing the installation after the last step of the installer has run.
Re-send the Connections document to each person listed in the EFM Sync database.
Instruct each user to run the Update from their mail file to download the updated Fax Factory, and then open the User Options document from within the Fax Factory database and Save and Close the document to update the remaining mail elements.
On the RightFax server, run the RightFax E-mail Gateway program from Windows Control Panel. This opens the E-mail Configuration dialog box.
Click the Copy Notes Database button.
When you receive a message that the database has been successfully copied, click OK to close the message, and then click OK to close the E-mail Configuration dialog box.
Run Enterprise Fax Manager and stop the RightFax E-mail Gateway Module service.
Copy NGPatch.NSF located in the \RightFax\Gateway folder on the RightFax server and NGInstal.NSF in the \Lotus\Notes\Data directory on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
On the Lotus Notes Client
machine, run Notes Designer and uncheck the Prohibit
checkbox on the Design tab of
the following element properties:
EFM SYNC:
Folders:
Real-Time
Fax Status
RightFax
Settings
...Other:
Icon
"Using
Database" Document
"About
Database" Document
ICD ROUTER
...Other:
Icon
"Using
Database" Document
"About
Database" Document
Run the Lotus Notes client and open the RightFax 9.00 Installation Database NGInstal.NSF to upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide for information on running this installation. Complete the upgrade configurations for version 9.0 according to the instructions in the RightFax Lotus Notes Module Guide.
Run the Lotus Notes client and open the RightFax 9.01 Installer database NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or select
a different, empty folder.
After completing step 10 in the installation, view the install log
by clicking the button in the top left of the Installer window, and confirm
that the previous install files were successfully deleted. If not, you
must manually delete these files before continuing with the installation.
If applicable, delete the file RF80SYNC.NSF from the Lotus\Domino\Data\RIGHTFAX folder on the Domino server.
Follow the instructions in the RightFax Lotus Notes Module Guide for completing the installation after the last step of the installer has run.
Re-send the Connections document to each person listed in the EFM Sync database.
Instruct each user to run the Update from their mail file to download the updated Fax Factory, and then open the User Options document from within the Fax Factory database and Save and Close the document to update the remaining mail elements.
Copy NGPatch.NSF from the \RightFax\Gateway folder on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
Run the Lotus Notes client and open the RightFax 9.01 installer database file NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or specify
a different, empty folder
On the RightFax server, run the RightFax E-mail Gateway program from Windows Control Panel. This opens the E-mail Configuration dialog box.
Click the Copy Notes Database button.
When you receive a message that the database has been successfully copied, click OK to close the message, and then click OK to close the E-mail Configuration dialog box.
Run Enterprise Fax Manager and stop the RightFax E-mail Gateway Module service.
Copy NGPatch.NSF located in the \RightFax\Gateway folder on the RightFax server and NGInstal.NSF in the \Lotus\Notes\Data directory on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
Run the Lotus Notes client and open the RightFax 9.00 Installation Database NGInstal.NSF to upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide for information on running this installation. When the installation is complete, do not set any configuration options for version 9.0.
Run the Lotus Notes client and open the RightFax 9.01 Installer database NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or specify
a different, empty folder
If applicable, delete the file RF80SYNC.NSF from the Lotus\Domino\Data\RIGHTFAX folder on the Domino server.
Follow the instructions in the RightFax Lotus Notes Module Guide for completing the installation after the last step of the installer has run.
On the RightFax server, run the RightFax E-mail Gateway program from Windows Control Panel. This opens the E-mail Configuration dialog box.
Click the Copy Notes Database button.
When you receive a message that the database has been successfully copied, click OK to close the message, and then click OK to close the E-mail Configuration dialog box.
Run Enterprise Fax Manager and stop the RightFax E-mail Gateway Module service.
Copy NGPatch.NSF located in the \RightFax\Gateway folder on the RightFax server and NGInstal.NSF in the \Lotus\Notes\Data directory on the RightFax server to the Notes client machine's \Lotus\Notes\Data folder. View the file properties of NGPatch.NSF on the Notes client machine and ensure that it is not set to read-only. If so, remove the read-only attribute.
On the Lotus Notes Client
machine, run Notes Designer and uncheck the Prohibit
checkbox on the Design tab of
the following element properties:
EFM SYNC:
Folders:
Real-Time
Fax Status
RightFax
Settings
...Other:
Icon
"Using
Database" Document
"About
Database" Document
ICD ROUTER
...Other:
Icon
"Using
Database" Document
"About
Database" Document
Run the Lotus Notes client and open the RightFax 9.00 Installation Database NGInstal.NSF to upgrade from version 8.7 to version 9.0. See the RightFax Lotus Notes Module Guide for information on running this installation. Complete the upgrade configurations for version 9.0 according to the instructions in the RightFax Lotus Notes Module Guide.
Run the Lotus Notes client and open the RightFax 9.01 Installer database NGPatch.NSF.
Click the Begin/Resume
Installation button. Complete the database installation according
to the instructions in the RightFax
Lotus Notes Module Guide but do not make any changes to the existing
configuration settings.
Important: When you reach the step that specifies the path to
the TEMP folder, ensure that the specified folder is empty, or select
a different, empty folder.
If applicable, delete the file RF80SYNC.NSF from the Lotus\Domino\Data\RIGHTFAX folder on the Domino server.
Follow the instructions in the RightFax Lotus Notes Module Guide for completing the installation after the last step of the installer has run.
Added Support for SQL 2000 Enterprise Edition both standalone and in clustering environments. See RightFax Installation Guide Pages 9-10.
Added support for the following Eicon fax boards:
Eicon Diva Server PRI/E1/T1-8
Eicon Diva Server PRI/T1-24
Eicon Diva Server Analog-4P
Eicon Diva Server Analog-8P
Added support for up to four Brooktrout TR1034 boards per chassis for all supported TR1034 models. See RightFax Fax Board Guide pages 34-35.
Up to eight Eicon boards can be installed per chassis.
RightFax now supports up to 120 channels per DocTransport/BoardServer module. See RightFax Administrator's Guide page 49.
The SOAP client/server installation lets RightFax users use the Print-to-Fax feature from any computer with an Internet connection. The SOAP server is installed on an IIS server on your network, and then the SOAP client then accesses RightFax through that server. This provides RightFax functionality to home-office or other remote employees who do not have direct access to your organization's network. See Installing the SOAP Server and Client Applications for instructions on installing this new feature.
Added support for ANSI code page 1256 (Arabic) to support Arabic characters in fax documents. See RightFax Installation Guide pages 10-11.
Added support for several additional annotation types in the RightFax Web Access fax viewer. See the RightFax Web Access online help.
Fax failure message are now handled in the domain of the mail router and its DELIVERY FAILURE message. More details are now provided in fax failure messages.
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
46928 |
BoardServer |
When using Least-Cost Routing rules with the "Send via Fax Server" option, FaxUtil reports "unknown error," but the fax sends correctly. |
This error message no longer appears. |
|
47673 |
BoardServer |
Dialing rules strip non-dialable characters such as - and ( ) in phone numbers instead of correctly stripping digits and ignoring the non-dialable characters. |
The dialing rules now correctly ignore non-dialable characters and strip only the phone number digits. |
|
47719 |
BoardServer |
On Business Integration servers with only one channel enabled, all outbound faxes fail with the status "Scheduled to be Sent" or "Waiting to be Sent." |
Faxes now send as expected on servers with this configuration. |
|
47954 |
BoardServer |
When the Human-Answered Fax feature is configured to switch to voice mode when the phone is answered, "Unknown error reported by fax board" is reported. |
The Human-Answered Fax feature now correctly switches to voice mode. |
|
47965 |
BoardServer |
The TTI line was not being properly added to outbound faxes when using a Brooktrout TruFax 200 uPCI fax board. |
When using a Brooktrout TruFax 200 uPCI fax board, TTI lines are now correctly added to outbound faxes as expected. |
|
46695 |
Database Module |
RightFax 9.0 and RightFax Workflow Wizard 1.5 displaying incompatibility issues. |
RightFax 9.0 and RightFax Workflow Wizard 1.5 now functioning compatibly. |
|
46734 |
Database Module |
Unable to log into fax server after 2 AM maintenance time. |
Corrected maintenance issue allowing RightFax logon as expected. |
|
47130 |
Database Module |
Daily maintenance deletes all fax image files on RightFax 9.0 Business servers. |
Corrected. Daily maintenance no longer deletes fax image files. |
|
47544 |
Database Module |
Billing codes not displaying correctly or searchable through FaxUtil. |
Corrected. Billing codes now display as expected. |
|
48048 |
Database Module |
Under specific circumstances, sending multiple faxes simultaneously causes SQL deadlock errors in RightFax. |
Corrected so that deadlocking errors no longer appear under test conditions. |
|
46828 |
DBPurge.exe |
In DBPurge.exe, there is no specific option to purge GenMailMsg. |
An option to purge GenMailMsg has been added to DBPurge.exe. |
|
47818 |
DBPurge.exe |
Dbpurge.exe fails to purge work requests. |
Work requestes can now be purged with DBPurge.exe. |
|
47795 |
Enterprise Fax Manager |
Enterprise Fax Manager version 9.0 stops unexpectedly when attempting to configure a WorkServer module on a version 8.x RightFax server. |
Enterprise Fax Manager version 9.0 now allows you to configure a WorkServer module on a version 8.x RightFax server. |
|
46868 |
Exchange Connector |
Microsoft Outlook stops unexpectedly when receiving a fax into Outlook with both the RightFax 9.0 client and McAfee 8.0i Enterprise installed. |
Corrected. Microsoft Outlook operated as expected when both of these applications are installed. |
|
43438 |
FaxAge.exe |
Faxage.exe reports that it is not a valid win32 program. |
Corrected. FaxAge.exe runs as expected. |
|
32217 |
FaxUtil |
Spanish help for embedded codes mistranslated. |
The help translation was corrected. |
|
32218 |
FaxUtil |
Spanish help for "Hold for Preview" feature mistranslated. |
The help translation was corrected. |
|
46135 |
FaxUtil |
The "Refuse Distributions" option for members of groups that had the option could not be enabled, gave error message. |
The "Refuse Distributions" option can now be toggled without error message. |
|
46687 |
FaxUtil |
The option View > New Faxes displays a blank screen. |
This option now correctly displays only faxes that have not been viewed. |
|
46985 |
FaxUtil |
When FaxUtil fax list is opened, the oldest fax is always highlighted, despite settings. |
The fax that is highlighted upon opening FaxUtil is now correctly determined by display settings. |
|
47457 |
FaxUtil |
After upgrading to version 9.0 faxes with the status "duplicate" will not open in FaxUtil. |
Duplicate faxes now open as expected. |
|
47094 |
GammaLink Adapters |
PDF attachments using fine mode (200 x 200 dpi ) are received at 200 x 100 dpi when sent through GammaLink fax boards. |
Fine mode setting corrected on GammaLink fax boards. |
|
45104 |
Notes Client |
Faxes sent via iNotes leave multiple entries in the fax send log. |
Each sent fax now logged only one time. |
|
46588 |
Notes Client |
Misaddressed faxes that are corrected and resent retain the status "in process" in the fax send log. |
These faxes are now updated in the send log as "sent." |
|
46809 |
Notes Client |
After upgrading from 8.x to 9.0, administrators are not able to edit some synchronized user accounts because complete user account name not synched. |
The complete user name is now synchronized and editing is possible. |
|
47821 |
Notes Client |
Unable to change the Notes mail integration by using the Update Mail Integration button in the connections document. |
This feature now lets you update the Notes Mail Integration type. |
|
44421 |
Notes Gateway |
Failed fax notifications do not work when sending to multiple addresses. |
Corrected. Failed fax notifications now work as expected. |
|
46522 |
Notes Gateway |
E-mail messages submitted to the RightFax Mail Router with multiple fax recipients results in multiple History.txt files being appended to the fax send logs in the EFM Sync database. |
Only one History.txt file appended as expected. |
|
47728 |
Notes Gateway |
With a Minimal Mail Integration, when synchronizing users from Notes to RightFax the Notification Address/Info field is empty. |
This field now populates correctly during synchronization with the Minimal Notes Integration. |
|
46824 |
SAP |
SAP Gateway sends unusable notification information. |
Notifications through the SAP Gateway corrected. |
|
46234 |
SecureDocs |
A secure PDF sent via Certified Delivery can be opened without a password. |
Corrected. Password now required on secured PDFs. |
|
47777 |
SecureDocs |
Sending SecureDocs from Outlook only creates empty SecureDoc recipient mailboxes . |
SecureDocs mailboxes now correctly populated with the sent document. |
|
1195 |
Server Module |
Autoforward feature does not copy the fax history. |
The fax history is now included with documents forwarded with the autoforward feature. |
|
46285 |
Server Module |
Cannot send a fax through the HPFAX queue if the user account does not already exist. |
A new RightFax user account is now created automatically based on the user's NT login. |
|
47478 |
SMTP Integration |
SMTP Gateway strips all attachments from outbound faxes. |
Attachments now retained as expected when sent via SMTP Gateway. |
|
47611 |
SMTP Integration |
E-mail messages submitted through the SMTP Gateway do not word-wrap. |
E-mail messages submitted through the SMTP Gateway now word-wrap as expected. |
|
46167 |
Web Access |
Attempting to view an SMS message through Web Access causes error message. |
Corrected. SMS messages can now be viewed through Web Access. |
|
46236 |
Web Access |
Web Access fails to check a RightFax user's permission settings. |
Web Access now restricts user activity based on the RightFax permissions settings. |
|
46890 |
Web Access |
E-mail notifications of documents received into Web Access include incorrect hyperlink to document. |
Corrected hyperlink to correctly point user to their received document. |
|
47044 |
Web Access |
Some text in the localized versions of Web Access was mistranslated. |
Translations corrected. |
|
47738 |
Web Access |
Forwarding a fax to a new destination through Web Access drops all body pages and sends only the cover page. |
Forwarded faxes now include body pages as expected. |
|
47814 |
Web Access |
Zooming and scrolling in the Web Access fax viewer frame causes faxes to become unviewable until next login. |
Image display errors corrected. |
|
47886 |
Web Access |
Web Access gives authentication error when accessing localized SQL database. |
Corrected collation error. |
|
46570 |
WorkServer Module |
Active Directory synchronization does not work with more than one Organizational Unit. |
Active Directory synchronization now supports more than one Organizational Unit. |
|
46574 |
WorkServer Module |
Group membership changes are ignored when synchronizing with Active Directory. |
Group membership changes are now retained when synchronizing with Active Directory. |
|
47297 |
WorkServer Module |
After enabling Telephony Server Routing on multiple WorkServers, all outbound faxes are stuck "In Conversion" or "In FCS Conversion." |
Corrected. Enabling Telephony Server Routing on multiple WorkServers no longer prevents outbound faxing. |
|
47789 |
WorkServer Module |
PDF conversion causes WorkServer error (LGSD:Library Already Loaded ). |
Corrected. PDF conversion no longer prompts WorkServer error message. |
|
47963 |
WorkServer Module |
FileNet OEM WorkServers do not convert HTML cover sheets. |
FileNet OEM WorkServers now convert HTML cover sheets as expected. |
The following software fixes were released for RightFax 8.7 Service Pack 3, and are also incorporated into RightFax 9.0 Feature Pack 1:
|
Captaris Tracking Number |
Module |
Problem |
Solution |
|
39839 |
Alerting |
Fax channel monitoring reports error when last channel is selected. Monitors incorrect channels numbers. |
Fax channel monitoring correctly monitors fax channels. |
|
41470 |
BoardServer |
When analog TR1034 fax boards are in use, the BoardServer does not correctly process DTMF digits for routing. |
The BoardServer now processes DTMF digits for routing. |
|
41767 |
BoardServer |
The BoardServer module crashes if a dialing rule to disallow sending is listed after but matches the pattern of a previous rule. |
The described behavior no longer occurs. Dialing rules are executed as expected. |
|
42097 |
BoardServer |
The file Callctrl.cfg includes incorrect syntax for the num_rings parameter. |
This parameter has been corrected in Callctrl.cfg. |
|
43357 |
BoardServer |
Running the BoardServer module in debug mode through EFM pushes CPU usage to 100%. |
Debug error corrected. |
|
44160 |
BoardServer |
ECM setting for Brooktrout boards stays enabled even if disabled in the BoardServer configuration application. |
ECM setting now reads correct setting from the BoardServer configuration application as expected. |
|
40068 |
Brooktrout TR1034 |
When restarting a RightFax server installed on a Compaq machine (e.g. DL380 G3), running Compaq's Surveyor utility with Windows 2003 Server, and Brooktrout TR1034 fax boards installed, the server hangs. |
Hang on reboot problem resolved. |
|
41948 |
Brooktrout TR1034 |
TR1034 boards configured for PRI-E1 have the pcm_law parameter configured incorrectly. |
This parameter is now correctly configured as "alaw" instead of "mulaw." |
|
41951 |
Brooktrout TR1034 |
Deactivating one or more channels on the TR1034 (PRI) is not reflected correctly in callctrl.cfg. |
This value is now correctly written to Callctrl.cfg. |
|
42242 |
Brooktrout TR1034 |
TR1034 analog channels report as "Offline Permanently" when in the same machine as digital TR1034 boards configured as PRI-ISDN. |
TR1034 analog channels now function properly when in the same machine as digital TR1034 boards configured as PRI-ISDN. |
|
42841 |
Brooktrout TR1034 |
TR1034 will not dial more than 24 digits. |
Corrected. Unlimited dialing characters supported. |
|
44021 |
Brooktrout TR1034 |
TR1034 BRI boards fail to receive faxes via the Siemens HiPath PBX. |
TR1034 BRI boards now correctly receive faxes via the Siemens HiPath PBX. |
|
44089 |
Brooktrout TR1034 |
Frequent channel reset failures on inbound faxes when running one or more TR1034+P4-4L boards with RightFax 8.7 FP1 with IBM Series 235. |
Channel reset problem resolved. |
|
44220 |
Brooktrout TR1034 |
DTMF routing for a fax channel with the option "Initial Speech" set requires users to wait for the entire voice greeting to end before the system will accept entered digits. |
Routing digits can now be entered at any time during the voice prompt. |
|
44271 |
Brooktrout TR1034 |
Eccdlld.dll file not found error when running voice.exe for the TR1034 board. |
Voice.exe now finds eccdlld.dll as expected. |
|
37114 |
ChgUser.exe |
When running ChgUser.exe and the NONTSECURITY keyword is used in the command line, the "Stamp Pages of Received Faxes with Audit Stamp" option is enabled in the user record. |
The NONTSECURITY keyword in ChgUser.exe no longer automatically enables the "Stamp Pages of Received Faxes with Audit Stamp" option. |
|
41293 |
E-mail Gateways |
After a Satellite Server is bumped, the cc:Mail, MS Mail, Groupwise, and SMTP E-mail Gateways are unavailable for install. |
Bumping a Satellite Server now makes these e-mail Gateways available. |
|
42833 |
Embedded Codes |
After upgrading from RightFax 7.2 to RightFax 8.7, some embedded codes (such as NEWDEST) inappropriately generate a fax cover sheet. |
Embedded codes no longer inappropriately generate fax cover sheets. |
|
42217 |
Enterprise Fax Manager |
Selecting the option "Disallow Fax Annotation" also disables the ability to print, forward, route, and more. |
Selecting the option "Disallow Fax Annotation" no longer affects other user permissions. |
|
35668 |
Exchange Gateway |
The option to "Break up Large Faxes" sends faxes above the specified page limit. |
The option to "Break up Large Faxes" now correctly sends faxes at the specified page limit. |
|
42103 |
Exchange Connector |
Faxes routed to e-mail via the Exchange connector use full path to the attachment for the file name, which made the file unreadable by certain devices. |
Faxes routed to e-mail via the Exchange connector no longer include the full path in the file name. |
|
44119 |
Exchange Connector |
Exchange 5.5 displays warnings for every processed fax if you have Message Tracking enabled on the connector. |
Problem fixed. Warning messages no longer appear. |
|
44963 |
Exchange Connector |
Microsoft Exchange System Manager crashes when adding a user that is not in the Users container on the Delivery Restrictions tab. |
This action no longer crashes Microsoft Exchange System Manager. |
|
41685 |
Fax Control |
Print-to-Fax on a file with a long file name (150 characters or higher) fails. |
Print-to-Fax on files with long file names (150 characters or higher) work as expected. |
|
41973 |
Fax Control |
JPEG files converted to fax format appear small and compressed. |
JPEG files now convert to fax format as expected. |
|
45057 |
Fax Control |
When using the Quick Fax/Broadcast feature, users can change phonebook entries even when not assigned this permission. |
Quick Fax/Broadcast feature now correctly blocks users from changing phonebook entries if they are not assigned this permission. |
|
30461 |
Fax Reporter |
In Fax Reporter, the Folder column in the Faxes table is not populated correctly. |
Folder column in the Faxes table now reports folder names as expected. |
|
31869 |
Fax Reporter |
FaxReporter misreports scheduled send time in the FaxSendDateTime column if a fax was delayed. |
Delayed faxes now correctly report the scheduled send time in the FaxSendDateTime column. |
|
42209/ |
Fax Reporter |
Fax Reporter data does not refresh if the network protocol is set to TCP/IP and then changed to either Named Pipes or Automatic Selection. |
Fax Reporter data now correctly refreshes if network protocol setting is changed. |
|
41543 |
Fax Server |
"Fax not viewed or printed" notifications are always sent to the Group Administrator when users route faxes to an E-mail Gateway, even if option for no notifications is selected. |
The option for to disable notifications to the Group Administrator now works as expected. |
|
44243 |
Fax Server |
Applying Tracks patch 40069 causes files to be routed in 8.3.3 file format instead of an 8.3 format. |
Applying Tracks patch 40069 now correctly causes files to be routed in 8.3 format. |
|
42494 |
Fax Status |
Fax Status application crashes when viewing the status of a fax channel transmitting at V.34. |
Fax Status application no longer fails when viewing v.34 transmissions. |
|
41673 |
FaxUtil |
Odd-sized tiff images, when sent as file attachments, fail to convert. |
Attached tiff images convert as expected. |
|
41682 |
FaxUtil |
FaxUtil will not run if no RightFax server name was specified during client installation. |
Leaving the RightFax server name blank during installation no longer causes FaxUtil to fail. |
|
41742 |
FaxUtil |
After closing the Phonebook window, faxes appear to lose their corresponding filter information (sent/received, to/from/file, etc.). Deleting one of these faxes causes FaxUtil to appear to perpetually delete faxes. |
The described behavior no longer occurs and deleting faxes works as expected. |
|
41822 |
FaxUtil |
FaxUtil folders default to the order they were created, even if alphabetical order is specified. |
FaxUtil folders now correctly display in alphabetical order. |
|
41890 |
FaxUtil |
FaxUtil lists the same fax repeatedly after opening the Fax Viewer, forwarding to new number, and then using the phonebook to select a recipient. |
Corrected so that no duplicate fax entry is displayed. |
|
43987 |
FaxUtil |
FaxUtil lists the same fax repeatedly after opening the Fax Viewer, forwarding to new number, and then using the phonebook to select a recipient. |
Corrected so that no duplicate fax entry is displayed. |
|
44707 |
FaxUtil |
Faxes that are in the "Needs Approval" status will not go back to that status after printing. Status stays as "Printing" indefinitely. |
After printing a fax in the "Needs Approval" state, fax returns from status "Printing" to status "Needs Approval." |
|
44833 |
FaxUtil |
Attached text files that contain tab characters do not word wrap correctly on conversion to fax format. |
You can now customize the maximum number
of characters per line. Navigate to the registry key HKEY_LOCAL_MACHINE |
|
45841 |
FaxUtil |
When attempting to send a fax to an Outlook 2003 MAPI phonebook contact, FaxUtil generates a Dr. Watson error. Occurs only when an Outlook 2003 client has "Use cached exchange mode" enabled. |
Error no longer occurs. |
|
43661 |
FileNet Connector |
The connector fails to process jobs from multiple source servers. |
The connector now supports job processing from multiple servers as expected. |
|
41854 |
Human-Answered Fax |
Selecting the option "Always start each call in voice mode" causes the fax board to automatically hang up after 12 seconds on outbound calls. |
Selecting the option "Always start each call in voice mode" no longer causes the fax board to automatically hang up. |
|
42503 |
Human-Answered Fax |
The Human-Answered Fax feature, using TR1034 analog boards with the "Always start" option enabled, reports status "OK" when dialing times out without an answer. |
Faxes now correctly report status "No answer at fax number." |
|
42534 |
Human-Answered Fax |
The Human-Answered Fax feature, using TR1034 analog boards with the "Always start" option enabled, reports status "OK" when a busy signal is encountered. |
Faxes now correctly report status "Busy." |
|
32530 |
ImpUser.exe |
The last entry in a .csv file fails to import unless a carriage return follows. |
Fixed so that carriage return is no longer required. |
|
33203 |
ImpUser.exe |
All users exported from RightFax and re-imported using ImpUser .exe have "Delete After Routing" option enabled. |
ImpUser.exe now correctly retains "Delete After Routing" setting. |
|
41750 |
Mimesend |
Mimesend fails to send to all recipients if any single recipient in a particular group has a bad e-mail address. |
Mimesend now ignores only the bad e-mail addresses and sends to all others as expected. |
|
41611 |
Notes Gateway |
Under certain circumstances, user synchronization between Notes and RightFax was incorrectly synching changes to Notes users with the RightFax server when synchronization was specifically set to only flow from RightFax to Notes. |
Corrected directional synchronization error. |
|
37666 |
ODBCSync.exe |
When synching a new user into a group whose name contains a space, the new user is not created in RightFax. |
RightFax now correctly reformats the group name, replacing spaces with underscore characters, and adds the user to the new group. |
|
39682 |
ODBCSync.exe |
When synching a new user whose name contains a space, the new user created with an underscore replacing the space as expected, but re-running ODBCSync.exe will generate arror and fail to update these users. |
Importing user names with spaces no longer generates error and updates as expected. |
|
40310 |
ODBCSync.exe |
RightFax IDs that have been created with ODBCSync.exe and had a source ID more than 21 characters long fail to update when re-running ODBCSync.exe. |
Importing user names with more than 21 characters no longer generates error and updates as expected. |
|
41814 |
Outlook Advanced Form |
The "Delay Send" option on the Outlook Advanced form shows the Date field twice instead of Date and Time. |
The "Delay Send" option on the Outlook Advanced form now correctly shows Date and Time fields. |
|
43610 |
Outlook Advanced Form |
Some faxes appear blank when viewed with the Outlook Advanced Form with Outlook 2003. |
All faxes now display as expected. |
|
43913 |
Outlook Advanced Form |
Outlook 2003 terminates unexpectedly when opened minimized and custom user variables exist with Outlook Extensions installed. |
Outlook 2003 no longer terminates when minimized and then closed. |
|
45705 |
Outlook Advanced Form |
Outlook hangs when receiving a fax in Outlook with McAfee 8.0i enterprise installed. |
Outlook no longer hangs on receiving a fax. |
|
31969 |
|
PostScript documents that contain the PostScript command "setpagedevice" fail conversion to fax format for transmission. |
The PostScript command "setpagedevice" is now processed correctly and does not cause fax conversion failure. |
|
41573 |
|
Adobe 6 PDF images acquired using TWAIN scanners shrink to 1/3 original size. |
Adobe 6 images now attach at full size. |
|
41676 |
|
Compressed PDF file fails conversion. |
Compressed PDF files convert as expected. Requires SSA NativeDocControl PDF,2 for WorkServer. |
|
42263 |
|
PDFs with embedded Asian fonts convert incorrectly to fax format. |
Asian fonts now convert to fax format as expected. |
|
42693 |
|
The -d switch for Pssplit.exe does not cause debug information to write to the screen or event viewer. |
The -d switch for Pssplit.exe now correctly outputs debug information. |
|
43227 |
|
Converting a document that contains a barcode font to PDF using NativeDocControl fails to properly convert the barcode. |
Corrected. The font is properly converted when corresponding .TTF file is located in the Worksrv\Fonts folder. |
|
43377 |
|
PDF images generated on the HP4100 have stripes running through the image. |
Problem corrected. PDF images convert as expected. |
|
44108 |
|
PDFs created from documents with graphic images in the header or footer convert with poor image quality. |
Graphic conversion corrected to retain image quality. |
|
34653 |
PhnPrint.exe |
PhnPrint.exe commands that specify multiple users but only supply some of the users' passwords outputs data as though no passwords had been supplied. |
PhnPrint.exe now recognizes a partial list of passwords and outputs data accordingly. |
|
42555 |
PhnPrint.exe |
Level 2 output for PhnPrint.exe does not output all expected data fields. |
Level 2 output for PhnPrint.exe corrected so that it now outputs all expected data fields. |
|
35199 |
Production |
The Mailsend.exe -o switch converts all recipient e-mail address to ASCII, causing mail transmission failure. |
Mailsend.exe -o switch preserves recipient e-mail addresses correctly and mail transmits as expected. |
|
37199 |
Production |
Bumping a Business Server with the Integration Module enables no production fax channels. |
The production fax channels are now correctly enabled when a Business Server with Integration is bumped. |
|
41396 |
Production |
MapText.exe image preview does not work. |
MapText.exe image preview works as expected. |
|
42954 |
Production |
When PORTLSTN.exe is enabled in the Integration Module control panel application, a Dr. Watson error is reported when the Integration Module service is stopped. |
Corrected issue. Dr. Watson error no longer occurs. |
|
43168 |
Production |
Running NOTIFY.exe to add a new integration channel causes a Dr. Watson error when the Integration Module service is stopped. |
Corrected issue. Dr. Watson error no longer occurs. |
|
34724 |
Rescue.exe |
Running Rescue.exe causes all faxes that are currently waiting for transmission because a delay time was specified to fail to send. |
Rescue.exe now correctly preserves delayed faxes. Delayed faxes transmit at the specified time as expected. |
|
41840 |
SAP |
The ProgID parameter in the saprfc.ini file is always reset to servername.sapgate when closing configuration. |
The ProgID parameter now retains its correct setting when closing configuration. |
|
41894 |
SAP |
All faxes sent via SAPOffice are sent as high priority. |
Faxes sent via SAPOffice now send with normal priority unless otherwise specified. |
|
44203 |
SAP |
SAPGate strips out data beginning with "<who". |
SAP no longer strips invalid SAP embedded code text. |
|
44227 |
SAP |
If you add DefaultUserID as a Reg_SZ value to HKLM\Software\RightFax\SAP\SAP#\ and send a fax through that SAP Gateway, it will not send from the user specified in that key, but will send using the Default user ID instead. |
Registry setting now correctly read by SAP connector. |
|
12459 |
SecureDocs |
Non-US regional settings cause an inability to log in to SecureDocs . |
Corrected date formatting to allow login with non-US regional settings. |
|
43116 |
SecureDocs |
Under certain circumstances, user administration through SecureDocs fails. |
Corrected error so that user administration works as expected. |
|
41270 |
SMTP Gateway |
Submitting an e-mail to the SMTP Gateway that has embedded HTML in the body with embedded images causes the Gateway to stop unexpectedly. |
The SMTP Gateway now correctly processes HTML-referenced images. |
|
42990 |
SMTP Gateway |
A fax with an attachment that is sent through the SMTP Gateway and fails conversion is incorrectly deleted from FaxUtil. |
The behavior in this circumstance is now configurable in the registry. To retain these faxes in FaxUtil with a "failed" status, navigate to the registry key HKEY_LOCAL_MACHINE\Software\Rightfax\Faxserver and set AutoDeleteFailedGatewayFaxes to 0. To retain the functionality as described, set AutoDeleteFailedGatewayFaxes to 1. |
|
43282 |
SMTP Gateway |
Fax conversion error notifications are returned to the sender via e-mail, even if all notification options are disabled. |
This behavior is now configurable in the registry. To disable these notifications, navigate to the registry key HKEY_LOCAL_MACHINE\Software\Rightfax\Faxserver, add a new DWORD registry called NoGatewayNotify, and set the data for this new value to 1. |
|
46915 |
Standalone Fax Connector |
Standalone Fax Connector does not work with TR1034 analog boards. |
Connector now dials out as expected. |
|
40288 |
Web Client |
Attaching notes in Web Client loses all characters after 80 if manual carriage returns are not entered. |
You can now customize the maximum number
of characters per line. Navigate to the registry key HKEY_LOCAL_MACHINE |
|
35216 |
WorkServer |
WorkServer archiving of outbound documents fails when sending to an e-mail address. |
Faxes sent to e-mail addresses are now archived as expected. |
|
41911 |
WorkServer |
Autoprinting inbound faxes to an HP LaserJet 4si prints only a single black line. |
HP LaserJet 4si printers now autoprint correctly. |
|
43699 |
WorkServer |
Conversion of some JPEG images results in poor image quality, especially when converting colors to grayscale. |
You can now customize the threshold setting when converting JPEG images to grayscale. Navigate to the registry key HKEY_LOCAL_MACHINE\Software\Rightfax\Workserver, add a new DWORD registry called RFThresh, and set the data for this new value to an appropriate setting from 3-255. The default value used is 128. Increase this value to darken color images. To change the registry value, stop all WorkServers, change the registry value on the server, then restart the WorkServers. |
|
44398 |
WorkServer |
WorkServer fails to create TIFF-G4 for certain received faxes when routing to network directory. |
Problem corrected. TIFF-G4 created as expected. |
New versions of the RightFax documentation have been updated for RightFax 9.0 Feature Pack 1. Although the Feature Pack installation will not make any changes to the guides in your RightFax\Docs folder, the new versions of the documentation are available for download from the same Web page where you downloaded the Feature Pack installation. All of the updated guides that have changes listed in this section are available for download.
|
Chapter |
5, "Configuring the DocTransport and BoardServer Modules" |
||
|
Section |
"Running DocTransport and BoardServer Services on Remote Computers" |
||
|
Page |
74 |
||
|
Error |
The documentation fails to mention that running remote DocTransport and BoardServer modules over a WAN is a supported configuration. |
||
|
Resolution |
A note regarding this support has been included in the Administrator's Guide. |
||
|
Chapter |
10, "Creating Signatures" |
||
|
Section |
"Adding a Signature to a file" |
||
|
Page |
123 |
||
|
Error |
The documentation fails to mention that signature files are not supported in PostScript documents. |
||
|
Resolution |
A note regarding this support issue has been included in the Administrator's Guide. |
||
|
Chapter |
22, "Creating, Sending, and Deleting Faxes" |
||
|
Section |
"Using International Character Sets" |
||
|
Page |
235 |
||
|
Error |
Instructions necessary to ensure that international character sets appear properly on RightFax cover pages incomplete. |
||
|
Resolution |
Information on this subject has been updated and clarified and relocated to the RightFax Installation Guide. |
||
|
Chapter |
26, "Working with the RightFax Database and Administrative Utilities" |
||
|
Section |
"Changing the Connection to the SQL Server" |
||
|
Page |
270 |
||
|
Error |
The instructions for changing the SQL connection string omit two additional steps. |
||
|
Resolution |
The SQL connection string must also be changed in the DocTransport module and in the registry. Instructions for this are in the Administrator's Guide updated for version 9.0 Feature Pack 1 on page 270. |
||
|
Chapter |
1, "Activating and Configuring the RightFax Microsoft Exchange Module" |
||
|
Section |
Adding and Configuring the RightFax Microsoft Exchange Module Service |
||
|
Page |
9 |
||
|
Error |
Microsoft Exchange imposes a sending limit of about 100 documents during a MAPI session. The workaround to bypass this limit is not documented. |
||
|
Resolution |
The following workaround has been added to the Microsoft Exchange Module Guide: Edit the Windows registry and navigate to HKEY_LOCAL_MACHINE\Software\RightFax\Gateway. Add a new DWORD value called “AvoidServerLimits” and set its value to 1. |
||
|
Chapter |
Various |
||
|
Section |
Various |
||
|
Page |
Various |
||
|
Error |
Documentation for configuring Echange 5.5 is included in the guide, although support for Exchange 5.5 was dropped in RightFax version 9.0. |
||
|
Resolution |
All references to Exchange 5.5 have been removed from the Guide |
||
|
Chapter |
3, Installing the RightFax Server Software |
||
|
Section |
Running a silent install of the RightFax server software |
||
|
Page |
31 |
||
|
Error |
The list of required settings in the ServerProperties.txt file for upgrades omitted three required properties. |
||
|
Resolution |
The following settings are also required for upgrades: IS_SQLSERVER_PASSWORD, IS_SQLSERVER_SERVER, IS_SQLSERVER_USERNAME. |
||
|
Chapter |
3, Installing the RightFax Server Software |
||
|
Section |
Running Silent Installs of the Server and Fax Board Drivers |
||
|
Page |
34 |
||
|
Error |
The example batch files for silently installing Microsoft Windows Installer and the RightFax server included a command to run instmsiw.exe, but this is no longer required. |
||
|
Resolution |
All references to instmsiw.exe have been removed from the sample batch files. |
||
|
Chapter |
Various |
||
|
Section |
Various |
||
|
Page |
Various |
||
|
Error |
The 9.0 version of the documentation omitted a new document type {{type SMS}}. |
||
|
Resolution |
This document type lets you send a specified message to an SMS-compatible device. The FCL code for this document type follows: {{type SMS}} |
||
|
Chapter |
1, Installing the Lotus Notes Module |
||
|
Section |
Activating and Configuring the Lotus Notes Module |
||
|
Page |
7 |
||
|
Error |
The documentation omits some inportant information about failovers in Domino cluster environments. |
||
|
Resolution |
If you are running the Lotus Notes module in a clustered Domino server environment, note that faxes that are sent during a failover of the node used to install the RightFax gateway will sit in the MAIL.BOX of the node being used by the Notes clients. When the node used to install the RightFax Gateway is returned to service, those faxes will be processed according to your Domino Connections document configuration. Please see your Domino documentation for instructions on configuring your Connections document. |
||
|
Chapter |
1, Installing the Lotus Notes Module |
||
|
Section |
Installing the Databases for Full Notes Mail Integration |
||
|
Page |
11 |
||
|
Error |
The documentation did not mention an additional required step during upgrades from version 8.x to 9.0. |
||
|
Resolution |
Because the name of the EFM Sync database file was changed between version 8.x and 9.x, the administrator must resend the Connections document to each fax user in the EFM Sync database, after upgrading from version 8.x. |
||
|
Chapter |
3, Using the RightFax Lotus Notes Module |
||
|
Section |
Introduction text |
||
|
Page |
39 |
||
|
Error |
The documentation fails to mention sending requirements for certified delivery and SecureDocs documents. |
||
|
Resolution |
Sending RightFax messages of type "Document" (for Certified Delivery) requires that the recipient have an SMTP e-mail address, and sending RightFax messages of type "SMS" requires that the recipient have a cell phone number. Either of these may be picked from from the Domino Directory or from the Personal Address Book. If the required information is not present, the user will not appear in the address of the memo once the Addressing dialog box has been closed. |
||
|
Chapter |
3, Using the RightFax Lotus Notes Module |
||
|
Section |
Introduction text |
||
|
Page |
39 |
||
|
Error |
The documentation did not mention that prioritization of outbound faxes is controlled by the Domino prioritization settings. |
||
|
Resolution |
The priority setting on faxes sent from the Notes client uses the Domino prioritization settings. If a fax is sent with low priority, and the Domino server is configured to send low priority messages at midnioght (the dafault Domino setting), then the fax will not be delivered to the RightFax server until midnight. |
||
|
Chapter |
2, "Installing the SecureDocs Module" |
||
|
Section |
Understanding the Installation Process |
||
|
Page |
8 |
||
|
Error |
The documentation states that a separate SecureDocs component must be selected when the RightFax server is installed. |
||
|
Resolution |
The SecureDocs software on the RightFax server is installed automatically with all server installs, and only requires that its functionality be licensed and activated. |
||
©2005 Captaris. All rights reserved.