In this File
New install program: We have released an updated install program for the Ad Hoc Transfer Module to be compatible with the WS_FTP Server 220.127.116.11 patch release. If you are doing a new installation of the module, you need to use version 18.104.22.168 or later of the install program.
Before installing Ad Hoc Transfer Module, you need the following:
The pre-installation checklist in the section, "Installing Ad Hoc Transfer Module," describes how to configure the requirements.
The end user can use any computer with an operating system that can support the following:
For installation requirements, see Installing the Ad Hoc Transfer Plug-in for Outlook.
The WS_FTP installer automatically activates certain components in your Windows Server installation (in addition to the ones activated by a normal Server install. Before installing WS_FTP Server, you should be sure that these changes conform to your organization’s security policies.
The following list shows features activated by the Ad Hoc Transfer Module install under the IIS7 role. Features shown as indented indicate a nested relationship with the non-indented feature above it.
Common HTTP Features
Health and Diagnostics
The following list shows the Windows Server stand-alone features activated during WS_FTP Server install:
.Net Framework 3.0 Features
Remote Server Administration Tools
Windows Process Activation Service
Additionally, the Web Transfer Module install process does the following:
Also, if HTTPS is not enabled on the site hosting the Web Transfer Module, the install will:
If you choose to install Ad Hoc Transfer Module, it should be installed on the same computer as WS_FTP Server. This section provides a pre-installation checklist and install procedure for installing Ad Hoc Transfer Module.
Ad Hoc Transfer Module installs an IIS web application to communicate with the WS_FTP Server database and Ad Hoc file system. Before you run the Ad Hoc Transfer Module installation, you need to install the prerequisite software and configure the WS_FTP Server computer.
For the installation requirements and procedure, see WS_FTP Server Release Notes.
You can download and install .NET Framework 3.0 from the Microsoft Download Center.
You need the Windows OS disk to install IIS. Go to Control Panel > Add or Remove Programs, then select Add/Remove Windows Components. Select Internet Information Services, then follow the on-screen instructions.
To install Ad Hoc Transfer Module:
- OR -
If you downloaded the software from our Web site, double-click the executable (.exe) file to begin the installation.
Read the license agreement. If you agree with its terms, select "I accept the terms of the license agreement," and click Next.WS_FTP Server host (for each host for which you will enable Ad Hoc Transfer Module). We recommend you create a Windows user account for use by the Ad Hoc Transfer Module.
Next, the Destination Folder dialog opens.
Next, the Impersonation Account for Web Transfer Module screen opens.
The Ad Hoc Transfer Module needs a Windows account to use for access to the Package Storage folder.
On the WS_FTP Server computer, you should have created a Windows account that has full access to the Package Storage folder of the WS_FTP Server host, as described in the pre-installation steps. Use that account username and password here.
Domain or Server. Enter either the valid Windows domain name of the WS_FTP Server computer, or the Windows computer name.
User name. Enter the applicable user name for the Windows account.
Password. Enter the password for the account.
This account username and password will also appear in the WS_FTP Server Manager, under Home > Modules > Ad Hoc Transfer Access Settings. If necessary, you can modify this account after completing the installation.
The installation program also configures the Ad Hoc Transfer web application to accept SSL connections on port 443. A self-signed certificate is installed. This allows your users to use HTTPS for secure transfers.
You need to enable web access for users that will use the Ad Hoc Transfer Client, and provide them the web address to log on, as described in the section, "Configuring Ad Hoc Transfer Module."
You need to refresh your WS_FTP™ Server 7.7, WS_FTP Server 7.7 with SSH, and WS_FTP Server 7.7 Corporate license. To refresh, from the Start menu, select Program Files > Ipswitch WS_FTP Server > Activate or Refresh WS_FTP Server License.
There are two ways that an end user can send files via Ad Hoc Transfer:
For browser access, Ad Hoc Transfer Module does not require installation on a user's computer. Your WS_FTP Server users can access the files in their accounts using any browser, and the address (URL) that you provide them.
Before a user can access the Ad Hoc Transfer Module, whether they use a browser or Outlook, you must make the following changes:
The Ad Hoc Transfer Access page shows all eligible users. These users can be from any of your WS_FTP Server hosts.
By default, the address is: http://<local_machine>:80/AHT
where <local_machine> is the domain name of the computer on which you installed the Web Transfer Client. If you specified a custom port (other than the default port 80) during install, you need to include the port in the address.
For example, if the local computer domain name is host1.wsftp.com, then the address your users need to log on to Ad Hoc Transfer is:
You should test this address before sending it out to users.
You can also launch the Ad Hoc Transfer Module from the WS_FTP Server program group (Programs > Ipswitch WS_FTP Server > WS_FTP Server Ad Hoc Transfer Client.)
If you add a user to the default host (specified in Server > Server Settings > System Details), the user will log onto the Add Hoc Transfer Client using their WS_FTP server user name and password. If you add a user to a host that is not the default host, the user must log onto the Ad Hoc Transfer Client using the host name, host separator, and username and password; for example: email@example.com
For installation instructions, see "Installing the Ad Hoc Transfer Plug-in for Outlook" and also "Silent Install for the Ad Hoc Transfer Plug-in for Outlook" in this guide.
C:\Program Files\Ipswitch\Ad Hoc Transfer\AHT\web.config
C:\Program Files (x86)\Ipswitch\Ad Hoc Transfer\AHT\web.config
C:\Program Files\Ipswitch\Ad Hoc Transfer\XFTWebService\web.config
C:\Program Files (x86)\Ipswitch\Ad Hoc Transfer\XFTWebService\web.config
For secure transfer, the Ad Hoc Transfer Module is installed with SSL capability, which runs on port 443. The installation creates an SSL certificate which is used when the user connects via HTTPS. You can enable secure transfer by changing the address used to log on to the Ad Hoc Transfer Module to use HTTPS, for example:
If you specified a custom port (other than the default port 443) during install, you need to include the port in the address.
We have issued a maintenance release of Ad Hoc Transfer Module and the Ad Hoc Transfer Plug-in for Outlook that provides the following enhancements and bug fixes:
To upgrade to this release, you need to install:
Your WS_FTP Server version (v 7.6) does not need to be updated.
When setting the values for maximum or default downloads per file, be aware that browser security settings can influence the download count. For example, if the Internet Explorer security setting Automatic prompting for file downloads is not enabled, when the recipient clicks on the web link to access files, and selects to download a file, Internet Explorer will pop up the following message and it will add 1 to the download count:
'To help protect your security, IE blocked this site from downloading files to your computer. Click here for options.'
For this reason, we recommend that you are generous when setting these values, and that you do not set these values to 1.
The same is true if you have multiple end users downloading a file. If the Internet Explorer security setting Automatic prompting for file downloads is not enabled, the download limit should be set to double the number of users who are intended to download the file.
Also, note that download counts shown in the package detail page and in log files will be affected.
In Windows Explorer, you can right click a file, select Send to > Mail Recipient, which opens the Outlook compose screen with the file attached. Ad Hoc Transfer does not support this functionality, so you will not see the Send Secure button.