ExtraFax 9.5.5 Requirements on Domino 14

Link:  http://www.extracomm.com/Extracomm/FAQ.NSF/FAQs/7aaa814112edde0a48257de1002adfaa
Apply to:  ExtraFax for Domino

Last Modified Date:  05/23/2024


Description

There are important considerations that need to be understood when running ExtraFax 9.5.5 on the HCL Domino 14 platform with Dialogic Brooktrout Fax devices:

HCL Software has made some important changes as it relates to how Domino 14 operates on the Windows Server Platform. As part of the "ongoing work to continuously improve security for Domino", HCL has updated the Windows installer to configure Domino to run using a non-admin user ID by default. Most notably, starting in Domino 14, the Domino Windows service will now use "NT Authority\Local Service" non-admin user ID instead of using a "Local System" account, which was considered the standard Windows service configuration for Domino prior to Domino 14

Question?:

Are you using the new default configuration in Domino 14 where the Domino Windows service is running using a non-admin ID OR is your Domino 14 server Windows service still starting using a "Local System" account instead?

Scenario 1: Using "Local System" account with the Domino 14 Windows service:

If your organization has chosen NOT to adopt the new default Domino 14 Windows Service - Security configuration that is uses "NT Authority\Local Service" non-admin ID and instead your organization will continue to run the Domino 14 server using a Windows service that is configured to run using a "Local System" account, there are no special considerations that you need to be aware of when running ExtraFax 9.5.5 on Domino 14 with Dialogic Brooktrout Fax devices.

Scenario 2: Using "NT Authority\Local Service" non-admin ID with the Domino 14 Windows service:

If your organization has chosen to adopt the new default Domino 14 Windows Service - Security configuration that is uses "NT Authority\Local Service" non-admin ID, ExtraFax 9.5.5 when using Dialogic Brooktrout fax devices will need some configuration adjustments as documented below:

1) In addition to installing ExtraFax 9.5.5 using the standard installation procedure, ExtraFax 9.5.5 must be configured to use the ExtraFax Port server. The ExtraFax Port server can be downloaded at this link. Install the ExtraFax Port server on the same server OS, where Domino 14 and ExtraFax 9.5.5 are installed. Using the ExtraFax Port server is an absolute requirement for Dialogic Brooktrout Fax devices to continue functioning with ExtraFax 9.5.5, when used on a Domino 14 server that uses the new default Windows service configuration that is set to use a non-admin ID.

2) It is recommended that the ExtraFax Port server Windows service startup type be set to "Automatic". By default the ExtraFax Port server Windows Service startup type is set as "Manual". Note that if ExtraFax Domino task is running, however the Windows ExtraFax Port Server service is not running, ExtraFax will be unable to send/receive faxes using Dialogic Brooktrout Fax devices.


3) In the ExtraFax Post Office database(extrafax.nsf), configure each of the Port Configuration/Port Control documents for Dialogic Brooktrout devices to use a Remote port as seen in the example below. In the Location field, select the Remote option and in the Network Address field: for optimal performance, specify the server localhost loopback address of 127.0.0.1, along with the Port field set to: 1238. Please verify the Windows Server OS firewall settings to ensure that the connection is not blocked in order to allow the ExtraFax Port server connection to be established successfully.


4) When using this configuration, in order to monitor Port/Channel level activity, be sure to use the ExtraFax Log viewer that is installed in the ExtraFax Remote Port server Windows - Start menu instead of using the ExtraFax 9.5.5 - ExtraFax Log Viewer Windows Start menu option.

If you have any additional questions about running ExtraFax 9.5.5 on Domino 14, that were not answered in this FAQ, please don't hesitate to reach out to our support team via email: [email protected]