Before you can allow your internal users to send and receive e-mail file attachments using the Secure Ad Hoc Transfer (SAT) module, there are a few configuration options to consider. Review the topics below for details.
|
|
The help file, adhoc.chm can be found in the SAT installation folder (e.g., C:\Inetpub\EFTAdHoc). For the release notes, refer to notes.txt in the EFT Server installation folder or the GlobalSCAPE support page http://www.globalscape.com/eft/sat_history.aspx. |
Receiving Notification when Recipient Uploads a File - The SAT module default installation handles the process of notifying your recipients when a file is sent. In addition, temporary accounts are disabled automatically one week after account creation. You must configure EFT Server to remove expired temporary accounts from EFT Server (including their home folder and any files contained within) automatically, and to receive notifications for files uploaded by recipients.
|
|
EFT Server basic edition has no Timer Event Rule functionality. You cannot configure EFT Server basic edition to alert you on upload notifications of SAT users. If you send a SAT e-mail to a user, then that user uploads something back to you, there is no way to configure the “return upload” notification to let you know your temporary user has uploaded something for you to pick up. This functionality relies on a Timer Rule that is only available with EFT Server Enterprise. Nor can you configure EFT Server basic edition to remove expired SAT temporary accounts automatically. The removal of the temporary accounts is triggered by the Timer Event running a script. The script is still available in EFT Server basic edition and you can run it manually to clean up expired accounts, but there is no Timer Event to have this happen automatically. You could also run the script using the Log Rotated Event so that the script is run daily, weekly, or monthly, depending on how often the log is rotated. For more information about logs, refer to the EFT Server help topic "Log Settings." |
Using the PCI Module with the Secure Ad Hoc Transfer Module - If you are using the HS module and the SAT module with EFT Server, you should create a separate, non-PCI DSS Site that is used only for the SAT module. Alternately, you can disable the features that are not compatible, but that would take the Site out of compliance with the PCI DSS.
Enforcing Strong (Complex) Passwords - If your Site's complex password settings require more than 20 characters, you must configure the EFTAdHoc Settings Template to override the Site's password settings so that complex passwords for SAT temporary users contain fewer than 20 characters.
Sending Large Files - If you expect to transfer large files, e.g., 1 GB or larger, we strongly recommend that you install EFT Server on the same computer as IIS and, in edit settings in the SAT configuration file.
SAT module configuration - Refer to Secure Ad Hoc Transfer's Configuration File for details of editing the configuration file.
You must configure your SMTP server to allow the computer on which the SAT module is installed to relay. Refer to the following Web links for details:
Allowing application servers to relay off Exchange Server 2007 (Microsoft Exchange Team Blog)
How to troubleshoot mail relay issues in Exchange Server 2003 and in Exchange 2000 Server (Microsoft KB article ID 895853)
Activating Secure Ad Hoc Transfer - When you first install the Secure Ad Hoc Transfer module, you are given the choice of installing a Full or Trial version. The trial version is not time limited, but file sender operations are limited to ten per IIS session and one file at a time. Follow the instructions in Activating Secure Ad Hoc Transfer to activate the full version.
Troubleshooting Errors in the Secure Ad Hoc Transfer Module. Refer to the topics in this chapter for the resolution to common errors.
Perform the steps below in the order listed:
Review the system requirements, deployment methods, and installation prerequisites.
