This is very common ask and keep update post, latest on top, and old just behind the latest information. Instead of create multiple post in different date, we combine all in one, easy for reference for the same edition and build history and feature implement along the release. WS_FTP Server Latest Build and Release the post date will keep change to reflect for the latest changes, despite it older portion of content is post previously, it will keep update the post date to make it relevant for customer and for those who want to access all the information in one post.
2018-Sep-20 WS_FTP Server 2018 (v8.6)
The following improvements were added to WS_FTP Server 2018 (8.6).
PostgreSQL update
PostgreSQL was updated from version 9.3 to 10.4.
The following vulnerabilities were closed by this update:
- CVE-2017-7546: Empty password accepted in some authentication methods
- CVE-2017-7547: The “pg_user_mappings” catalog view discloses passwords to users lacking server privileges
- CVE-2017-7548: lo_put() function ignores ACLs.
Open SSL update
OpenSSL was update from version 1.0.2k to 1.0.2p.
The following vulnerability was closed by this update:
- CVE-2018-0739: Constructed ASN.1 types could exceed the stack given malicious input with excessive recursion, resulting in a Denial of Service attack.
Visual Studio
The Visual Studio 2008 C++ Redistributable package is no longer installed with the WS_FTP Server installer.
System Requirements
Operating System
The Operating Systems detailed in the table are supported for the following WS_FTP Server configurations:
- Standalone
- Failover cluster using Microsoft Clustering Services
- Failover cluster using Microsoft Network Load Balancing
Operating System |
Edition |
Supported Versions |
---|---|---|
Windows Server 2016 |
|
|
Windows Server 2012 R2 |
|
|
Prior to WS_FTP Sever 2018 (8.6) Windows Server 2008 R2 (64-bit English) was supported. This server is no longer supported.
Windows Server Components Activated Automatically
The WS_FTP Server installer automatically activates certain components in your Windows Server installation. This is necessary because after installation, Windows Server does not turn on non-core operating system components. However, before installing WS_FTP Server, you should be sure that these changes conform to your organization’s security policies.
When you install WS_FTP Server, the install activates the following Windows Server roles:
- ISAPI Extensions
- Windows Authentication
- ASP
Database Platform
WS_FTP Server requires one of the database platforms listed in the following table.
The default database platform is PostgreSQL, however during installation, you can select Microsoft SQL Server as your database for configuration data.
Database Platform |
Version |
Notes |
PostgreSQL |
10.0 |
Default. Packaged in WS_FTP installer |
MS SQL Server (Enterprise and Standard)
|
2017 |
|
2016 |
|
|
2014 |
|
Prior to WS_FTP Server 208 (8.6) Microsoft SQL Server 2008 was supported. This SQL server is no longer supported.
Configuring the database for remote connections
By default, the Microsoft SQL Server database will only accept connections coming from the local system. To use a remote notification server, to allow multiple servers to share a data store, or to allow a remote Web Transfer Client connection, you have to enable remote connections.
Microsoft’s Knowledge Base (KB) provides the following information on remote connections:
“When you try to connect to an instance of Microsoft SQL Server 2005 from a remote computer, you may receive an error message. This problem may occur when you use any program to connect to SQL Server. For example, you receive the following error message when you use the SQLCMD utility to connect to SQL Server:
Sqlcmd: Error: Microsoft SQL Native Client: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.This problem may occur when SQL Server 2005 is not configured to accept remote connections. By default, SQL Server 2005 Express Edition and SQL Server 2005 Developer Edition do not allow remote connections.
For instructions, see the Microsoft KB article: How to Configure SQL Server 2005 to Allow Remote Connections.
Web Server
During installation, you can select Microsoft Internet Information Services (IIS) as your web server (instead of WS_FTP’s Web Server). If you opt to use IIS, WS_FTP Server requires the ASP .NET Web Server Role Service.
Prior to installing, the Microsoft Internet Information Services Web site on which you intend to install WS_FTP Server Manager must be configured to use a port that is not already in use. If another application, such as the Web server included with Ipswitch WhatsUp Gold, is operating on the same port as the Web site, you must take one of the following actions:
- change the port used by the existing application.
- configure the Web site to use a port that is not already in use.
The setup program makes the following changes to your IIS configuration:
- On the Web site, Web Services Extensions will be set to Allow ASP Pages.
- On the WSFTPSVR Virtual Directory, Enable Parent Paths will be enabled.
- On the WSFTPSVR Virtual Directory, Application Pooling will be set to the Medium/Pool level.
On 64-bit versions of Windows, if 32-bit applications are not allowed to run under IIS, a “Service Unavailable” error is displayed in the browser. To correct this, you must run the following command from the command line to enable 32-bit applications to access IIS:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
After running the command, you must restart IIS.
In some cases the install will display the error message Could not enable ASP. This typically occurs when Active Server Pages in the IIS Server Extension section have been enabled. To verify this:
- Right-click My Computer, then click Manage. The Computer Management console opens.
- Click Services and Applications > Internet Information Services > Web Service Extensions. The Web Service Extensions are displayed in the right-hand console window.
- Make sure that the Active Server Pages status is set to Allowed. If it is not, right-click Active Server Pages and select Allow.
- Close the Computer Management console.
If you specify a user other than the default user to serve as the run as user on the IIS virtual folder (if you are using Microsoft IIS as your web server), you may get a HTTP 401 error when you attempt to open the WS_FTP Server Manager. If this occurs, you must open the WSFTPSVR virtual folder in IIS and change the anonymous access user password to match the specified user’s password.
Framework and Accessibility
WS_FTP Server requires the Microsoft .NET Framework and other Microsoft packages for scripting and software accessibility. Microsoft .NET Framework 4.6 is included in the installation program.
Hardware
The minimum recommended hardware is the same as recommended for Windows Server 2008 R2. (For more information, see the Windows Server information on Microsoft’s web site.) If you are using a later version operating system, you should meet the hardware requirements for that system.
Component |
Requirement |
Processor |
Minimum: 1 GHz (x86 processor) or 1.4 GHz (x64 processor) Recommended: 2 GHz or faster |
RAM |
|
Hard Drive |
Hard drive capacity depends on how much data you plan to store. |
Virtualization Requirements
- VMware ESXi 4.0 (32-bit and 64-bit guest operating systems), ESXi 5.0, ESXi 6.0
- Microsoft Hyper-V 1.0 on Windows 2012; Windows 2008 64-bit (32-bit and 64-bit guest operating systems)
Server Manager
The WS_FTP Server Manager provides web-based administration from the local machine and also allows remote management of the server. WS_FTP Server Server Manager is a part of WS_FTP Server and is installed on the same machine.
Web Interface Requirements
See the Ad Hoc Transfer Plug-in for Outlook Requirements.
Web Transfer Client
The Web Transfer Module needs access to the file system on your FTP host or hosts so it can upload and download files. During the WS_FTP Server Web Transfer Client installation, you will specify a Windows user account with permissions to the top folder of each WS_FTP Server host (for each host for which you will enable WS_FTP Server Web Transfer Client). We recommend you create a Windows user account for use by the Web Transfer Module. Note that this Windows user account is used differently depending on the WS_FTP Server host settings and the user database configured for that host:
- If the host uses a Microsoft Windows or Microsoft Active Directory user database, configured to use Windows file permissions, the user account permissions take precedence, and this Windows account is not used.
- If the host has a host-level impersonation account, which is required if the host Top folder uses a UNC path, the host-level impersonation account takes precedence, and this Windows account is not used.
- If the host uses the WS_FTP Server or ODBC user database, and the host-level impersonation is not specified, this Windows account is used.
Ad Hoc Transfer Module
Before you install the Ad Hoc Transfer Module, verify that the WS_FTP Server computer has the following:
- The Ad Hoc Transfer Module needs access to the Package Storage root folder on your FTP host or hosts so it can store package files and make them available for download. During the Ad Hoc Transfer Module installation you will specify a Windows user account with permissions to the Package Storage folder.
- For the Ad Hoc Transfer Module to be available to recipients outside your internal network, you must install it in the WS_FTP Server and configure it with the appropriate DNS settings.
Requirements for the WS_FTP Server Web Transfer Client and Ad Hoc Transfer Module end user
The end user can use any computer with an operating system that can support the following:
- Microsoft Internet Explorer 9, 10 or 11 (Windows only); Mozilla Firefox 16 or later, Google Chrome 21 or later, Apple Safari 5 or later (Mac-only)
- Enabled Javascript support in the Web browser
- Enabled Cookie support in the Web browserBroadband connection to the Internet (recommended)
Requirements for the WS_FTP Server Web Transfer Client and the Ad Hoc Transfer Module on Windows Server 2008 R2 or 2012
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
- Static Content
- Default Document
- Directory Browsing
- HTTP Errors
Application Development
- ASP .NET
- .Net Extensibility
- ISAPI Extensions
- ISAPI Filter
Health and Diagnostics
- HTTP Logging
- Request Monitor
Security
- Request Filtering
Performance
- Static Content Compression
Management Tools
- IIS Management Console
The following list shows the Windows Server stand-alone features activated during WS_FTP Server install:
.Net Framework 4.5.2 Features
- .Net Framework 4.5.2
- XPS-Viewer
- WCF Activation (HTTP Activation, Non-HTTP Activation)
Remote Server Administration Tools
- Role Administration Tools (Web Server (IIS) Tools)
Windows Process Activation Service
- Process Model
- .Net Environment
- Configuration APIs
Additionally, the Web Transfer Module install process does the following:
- Runs servicemodelreg to install the WCF service model.
- Places the Web Transfer Module and the underlying web service in classic mode application pools.
Also, if HTTPS is not enabled on the site hosting the Web Transfer Module, the install will:
- Create a self-signed certification for the machine hostname
- Grant permissions to EVERYONE to read the folder where the certifications live
- Create an HTTPS binding on the website hosting the Web Transfer Module (if applicable)
- Attach the certificate to the HTTPS binding.
Ad Hoc Transfer Plugin
The following software must be installed on the machine on which you install the Ad Hoc Transfer Plug-in for Outlook. If the required software is needed by only one of the clients, it is noted as such.
- Microsoft Outlook 2016, 2013, 2010, 2007 (Outlook plug-in only)
- Supported Operating Systems:
- Windows 10 (32-bit and 64-bit)
- Windows 8.1 (32-bit and 64-bit)
- Windows 8 (32-bit and 64-bit)
- Windows 7 (32-bit and 64-bit)
- Microsoft Visual Studio 2010 Tools for Office Runtime (VSTOR 2010) Redistributable (all OS) (Outlook plug-in only)
- Microsoft Visual Studio 2010 Tools for the Microsoft Office System (version 4.0 Runtime) Language Packs (non-English OS) (Outlook plug-in only)
If you are running the installer live (not doing a silent install), the installer automatically installs the Microsoft Visual Studio redistributable programs. You do not need to download anything from Microsoft. If running a silent install, you must download and install these redistributable programs before running the install. See the Requirements in the Silent Install section.
On the last screen of the installer, you can select to View Install Log.
- Microsoft Internet Explorer 9, 10 or 11 (Windows only); Mozilla Firefox 16 or later, Google Chrome 21 or later, Apple Safari 5 or later (Mac-only)
- Enabled Javascript support in the Web browser
- Enabled Cookie support in the Web browser
Third Party Software
WS_FTP Server utilizes third-party open source software subject to the licenses described below.
WS_FTP Server |
||
---|---|---|
Library |
Version |
License |
PostgreSQL |
10.4 |
|
zlib |
1.2.11.0 |
|
OpenSSL |
1.0.2P |
|
Distributed 3rd Party Code |
|
|
Greta |
Last copyright 2002 |
|
Web Transfer Module |
||
Library |
Version |
License |
1.4.6 |
||
1.4.7 |
||
2.9.1 |
||
0.13.4 |
||
0.2.15 |
||
3.3.5 |
||
4.6.3 |
||
2.2.0 |
||
3.10.1 |
||
0.3.9 |
||
2.10.6 |
||
1.5.1 |
||
Ad Hoc Transfer Module |
||
Library |
Version |
License |
1.4.6 |
||
1.4.7 |
||
2.9.0 |
||
0.13.4 |
||
0.2.15 |
||
3.3.5 |
||
4.6.3 |
||
2.2.0 |
||
3.10.1 |
||
0.3.9 |
||
1.5.1 |
Upgrade Paths
Ipswitch Update Service is included in WS_FTP Server. Ipswitch Update Service automatically detects and notifies you of the availability of any updates released for any Ipswitch software installed on the computer.
You can manually check for updates by selecting Start > Programs > WS_FTP Server > Check for Updates from the Windows desktop of the computer where WS_FTP Server is installed.
Upgrade paths
WS_FTP Server 2018 (8.6) supports direct upgrade installations from the following versions:
- WS_FTP Server 2017 Plus (8.5)
- WS_FTP Server 2017 (8.0.1)
- WS_FTP Server 7.7.
Note: The upgrade paths are valid only on supported Operating Systems. For more information, see Operating System.
For detailed installation and configuration instructions, or activating a new or upgraded license, see the WS_FTP Server Installation and Configuration Guide.
Issues Fixed in This Release
The following issues were fixed in WS_FTP Server 2018 (8.6).
ID |
Category |
Fixed Issue Description |
---|---|---|
WSRVR-3595 |
Database, Security |
The user’s password format was updated to ensure that if a user’s password is truncated, incorrect, or corrupted the user cannot log on. Users can re-enter a truncated or incorrect password. If the password is corrupted, the Administrator can reset the password. |
WSRVR-3586 |
Notifications |
The Failed Upload error notification is now triggered if the data channel times out during an FTP upload. |
WSRVR-3547 |
Install |
To avoid security concerns, the Visual Studio 2008 C++ Redistributable package is no longer installed with the WS_FTP Server installer. |
WSRVR-3417 |
Listeners, SSL |
The list of supported ciphers was updated to remove unsupported ciphers and include an additional 6 ciphers. |
WSRVR-3378 |
AHT |
The download link for a package functions correctly when NET 4.7 is installed on the WS_FTP Server. |
WSRVR-3205 |
Database, Install, Upgrade |
The IPS_account is validated during the upgrade process, preventing a PostgreSQL failure. |
WSRVR-2763 |
Install, Permissions |
The method of assigning permissions was changed to ensure that users do not encounter issues that prevent them from using RDP. |
WSRVR-3657 |
Security |
LDAP users that are removed from the security group can no longer log on to the Web Transfer and Ad Hoc Transfer Modules. |
WSRVR-3533 |
Security |
PostgreSQL was updated from version 9.3 to 10.4. The following vulnerabilities were closed by this update:
|
WSRVR-3592 |
|
OpenSSL was updated from version 1.0.2k to 1.0.2p. The following vulnerability was closed by this update:
|
WSRVR-3787 |
SSH |
Creating an SSH Listener no longer results in a “Save Error” when the Disable CBC Mode Ciphers option is enabled. |
Known Issues in This Release
This section details known issues and workarounds in WS_FTP Server 2018 (8.6).
ID |
Category |
Known Issue Description |
---|---|---|
MICEN-3785 |
Licensing |
Users are unable to modify or update a license number after it is activated. The updated license number and associated functional changes are not implemented. To workaround this issue, reset the IIS. |
2017-Aug-20 WS_FTP Server 2017 Plus (v8.5)
What’s New: 2017 Plus (v8.5)
- OpenSSL update: 2017 Plus includes the move from OpenSSL 1.0.1t to OpenSSL 1.0.2k, which contains new security fixes described here: https://www.openssl.org/news/openssl-1.0.2-notes.html. The new OpenSSL (1.0.2k) will support a different set of ciphers from any upgraded version (1.0.1t or previous). Any new ciphers that were not part of the version from which they upgraded will be added to the available cipher list but will not be associated with a particular listener until the user manually adds them. Any ciphers that have been deprecated between OpenSSL versions will be removed from from both the available cipher list and the list of ciphers associated with a particular listener. OpenSSL 1.0.1 will no longer be supported starting with WS_FTP Server 2017 Plus.
- Additonal KEX algorithm support: SSH to include Diffie-Hellman-group14-sha256 and Diffie-Hellman-group-exchange-sha256.
- Ability to connect to a remote SQL Server database using TLS 1.2
- Improved logging for LDAP connection failures
Known Issues in WS_FTP Server 2017 Plus (8.5)
ID |
Category |
Issues |
---|---|---|
WSRVR-3314 |
Install |
Before installing WS_FTP Server on a Windows Server 2008 R2, you must pre-install .NET (4.0). |
WSRVR-3332 |
Install |
For PostgreSQL clean installs the “%” character cannot be used for usernames or passwords. For migrations 7.7 -> 8.5 where the username or password contain a “%” character, run the dbconfig tool to update services and connection strings. Select OK in the PostgreSQL Configuration dialogue. |
WSRVR-3483 |
Ad Hoc Transfer Module (potentially Web Transfer Module) |
WS_FTP does not support for Windows .Net 4.7. |
WSRVR-3531 |
Browsers |
Windows Server 2012 does not support Internet Explorer 10. Alternative browsers can be used, such as Chrome and Firefox. |
WS_FTP Server Requirements
Supported Operating Systems
For a standalone WS_FTP Server installation:
Operating System |
Edition |
Supported Versions |
Windows Server 2016 |
|
|
Windows Server 2012 R2 |
|
|
Windows Server 2012 |
|
|
Windows Server 2008 R2 |
|
|
For a WS_FTP Server failover cluster using Microsoft Clustering Services:
Operating System |
Edition |
Supported Versions |
Windows Server 2012 R2 |
|
|
Windows Server 2012 |
|
|
Windows Server 2008 R2 |
Enterprise |
|
For a WS_FTP Server failover cluster using Microsoft Network Load Balancing:
Operating System |
Edition |
Supported Versions |
Windows Server 2012 R2 |
|
|
Windows Server 2012 |
|
|
Windows Server 2008 R2 |
|
|
Windows Server Components Activated Automatically
The WS_FTP Server installer automatically activates certain components in your Windows Server installation. This is necessary because after installation, Windows Server does not turn on non-core operating system components. However, before installing WS_FTP Server, you should be sure that these changes conform to your organization’s security policies.
When you install WS_FTP Server, the install activates the following 2008 R2 Server roles:
- ISAPI Extensions
- Windows Authentication
- ASP
Database Requirements
- The default database for configuration data is PostgreSQL 9.3.11 (local only).
- During installation, you can select Microsoft SQL Server as your database for configuration data. If you choose this option, you must use one of the following versions:
- Microsoft SQL Server 2016 Express, Standard, or Enterprise versions (local or remote) (WS_FTP Server 2017 8.0.1 only)
- Microsoft SQL Server 2014 Express, Standard, or Enterprise versions (local or remote)
- Microsoft SQL Server 2012 or 2012 R2 Express, Standard, or Enterprise versions (local or remote)
- Microsoft SQL Server 2008 R2 Express, Standard, or Enterprise versions (local or remote)
Configuring the database for remote connections
By default, the Microsoft SQL Server database will only accept connections coming from the local system. To use a remote notification server, to allow multiple servers to share a data store, or to allow a remote Web Transfer Client connection, you have to enable remote connections.
Microsoft’s Knowledge Base (KB) provides the following information on remote connections:
“When you try to connect to an instance of Microsoft SQL Server 2005 from a remote computer, you may receive an error message. This problem may occur when you use any program to connect to SQL Server. For example, you receive the following error message when you use the SQLCMD utility to connect to SQL Server:
Sqlcmd: Error: Microsoft SQL Native Client: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.This problem may occur when SQL Server 2005 is not configured to accept remote connections. By default, SQL Server 2005 Express Edition and SQL Server 2005 Developer Edition do not allow remote connections.
For instructions, see the Microsoft KB article: How to Configure SQL Server 2005 to Allow Remote Connections.
Web Server Requirements
During installation, you can select Microsoft Internet Information Services (IIS) as your web server (instead of WS_FTP’s Web Server). If you choose this option, you need to have Microsoft Internet Information Services (IIS) 7.0 or later installed on your computer. If you opt to use IIS, WS_FTP Server requires the ASP .NET Web Server Role Service.
- Prior to installing, the Microsoft Internet Information Services Web site on which you intend to install WS_FTP Server Manager must be configured to use a port that is not already in use. If another application, such as the Web server included with Ipswitch WhatsUp Gold, is operating on the same port as the Web site, you must take one of the following actions:
- change the port used by the existing application.
- configure the Web site to use a port that is not already in use.
- The setup program makes the following changes to your IIS configuration:
- On the Web site, Web Services Extensions will be set to Allow ASP Pages.
- On the WSFTPSVR Virtual Directory, Enable Parent Paths will be enabled.
- On the WSFTPSVR Virtual Directory, Application Pooling will be set to the Medium/Pool level.
- On 64-bit versions of Windows, if 32-bit applications are not allowed to run under IIS, a “Service Unavailable” error is displayed in the browser. To correct this, you must run the following command from the command line to enable 32-bit applications to access IIS:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
After running the command, you must restart IIS.
- In some cases the install will display the error message Could not enable ASP. This typically occurs when Active Server Pages in the IIS Server Extension section have been enabled. To verify this:
- Right-click My Computer, then click Manage. The Computer Management console opens.
- Click Services and Applications > Internet Information Services > Web Service Extensions. The Web Service Extensions are displayed in the right-hand console window.
- Make sure that the Active Server Pages status is set to Allowed. If it is not, right-click Active Server Pages and select Allow.
- Close the Computer Management console.
If you specify a user other than the default user to serve as the run as user on the IIS virtual folder (if you are using Microsoft IIS as your web server), you may get a HTTP 401error when you attempt to open the WS_FTP Server Manager. If this occurs, you must open the WSFTPSVR
virtual folder in IIS and change the anonymous access user password to match the specified user’s password.
Framework and Accessibility Requirements
WS_FTP Server requires the Microsoft .NET Framework and other Microsoft packages for scripting and software accessibility. Microsoft .NET Framework 4.0 is included in the installation program.
Third Party Software
WS_FTP Server utilizes third-party open source software subject to the licenses described below.
WS_FTP Server |
||
Library |
Version |
License |
PostgreSQL |
9.3 |
|
zlib |
1.2.5 |
|
OpenSSL |
1.0.2K |
|
Distributed 3rd Party Code |
|
|
Greta |
Last copyright 2002 |
|
Web Transfer Module |
||
Library |
Version |
License |
1.4.6 |
||
1.4.7 |
||
2.9.1 |
||
0.13.4 |
||
0.2.15 |
||
3.3.5 |
||
4.6.3 |
||
2.2.0 |
||
3.10.1 |
||
0.3.9 |
||
2.10.6 |
||
1.5.1 |
||
Ad Hoc Transfer Module |
||
Library |
Version |
License |
1.4.6 |
||
1.4.7 |
||
2.9.0 |
||
0.13.4 |
||
0.2.15 |
||
3.3.5 |
||
4.6.3 |
||
2.2.0 |
||
3.10.1 |
||
0.3.9 |
||
1.5.1 |
Other Notes
- If
net.exe
has been removed from the computer on which you want to install WS_FTP Server, you must create a user account to serve as the WS_FTP Server account in Windows before installing. The account name must begin withIPS_
, and it is recommended that it be configured so that the password never expires.During the install, when you reach the Create User Accounts dialog, specify this username without the
IPS_
at the beginning.For example, if you created a Windows user account called
IPS_wsftpadmin
, enterwsftpadmin
for the username on the Create User Accounts dialog.Note: If you are upgrading a previous version of WS_FTP Server with hosts that use Windows NT user databases exclusively, the username you create must be
IPS_
plus the username of an existing Windows NT user that has system administrator privileges in WS_FTP Server. - If you select to install to a web site that uses a custom host header or port, the desktop shortcut created does not use the host header or port. To correct this, you must create a new shortcut using the correct host header and port.
- When creating a rule for Failed Login, Folder Action, Quota Limits, or Bandwidth Limits, the Group Search function does not work.
- When upgrading a host using an external (ODBC) user database, you must manually set permissions to the external database file after the upgrade completes.
When multiple hosts with firewall settings configured share a single listener, the firewall settings for the first of those hosts that a user logs into are applied to all of the hosts that share the listener and have firewall settings configured. Hosts that do not have firewall settings configured are not effected by this issue. We recommend that all hosts that are assigned to a common listener share the same firewall settings.
- If you create a virtual folder with the same name as a physical folder, the physical folder takes precedence for permissions purposes. A work around is simply to change the name of one of the 2 folders.
Hardware Requirements
The minimum recommended hardware is the same as recommended for Windows Server 2008 R2. (For more information, see the Windows Server information on Microsoft’s web site.) If you are using a later version operating system, you should meet the hardware requirements for that system.
Component |
Requirement |
Processor |
Minimum: 1 GHz (x86 processor) or 1.4 GHz (x64 processor) |
RAM |
|
Hard Drive |
Hard drive capacity depends on how much data you plan to store. |
Virtualization Requirements
- VMware ESXi 4.0 (32-bit and 64-bit guest operating systems), ESXi 5.0, ESXi 6.0
- Microsoft Hyper-V 1.0 on Windows 2012; Windows 2008 64-bit (32-bit and 64-bit guest operating systems)
WS_FTP Server Manager
The WS_FTP Server Manager provides web-based administration from the local machine and also allows remote management of the server. WS_FTP Server Server Manager is a part of WS_FTP Server and is installed on the same machine.
Web Interface Requirements
See the Ad Hoc Transfer Plug-in for Outlook Requirements.
WS_FTP Server Web Transfer Client and Ad Hoc Transfer Module Requirements
The WS_FTP Server Web Transfer Client and the Ad Hoc Transfer Module come bundled with the WS_FTP Server installer. If your license includes these modules, make sure your system can support these requirements.
WS_FTP Server Web Transfer Client Requirements
The Web Transfer Module needs access to the file system on your FTP host or hosts so it can upload and download files. During the WS_FTP Server Web Transfer Client installation, you will specify a Windows user account with permissions to the top folder of each WS_FTP Server host (for each host for which you will enable WS_FTP Server Web Transfer Client). We recommend you create a Windows user account for use by the Web Transfer Module. Note that this Windows user account is used differently depending on the WS_FTP Server host settings and the user database configured for that host:
- If the host uses a Microsoft Windows or Microsoft Active Directory user database, configured to use Windows file permissions, the user account permissions take precedence, and this Windows account is not used.
- If the host has a host-level impersonation account, which is required if the host Top folder uses a UNC path, the host-level impersonation account takes precedence, and this Windows account is not used.
- If the host uses the WS_FTP Server or ODBC user database, and the host-level impersonation is not specified, this Windows account is used.
Ad Hoc Transfer Module Requirements
Before you install the Ad Hoc Transfer Module, verify that the WS_FTP Server computer has the following:
- The Ad Hoc Transfer Module needs access to the Package Storage root folder on your FTP host or hosts so it can store package files and make them available for download. During the Ad Hoc Transfer Module installation you will specify a Windows user account with permissions to the Package Storage folder.
- For the Ad Hoc Transfer Module to be available to recipients outside your internal network, you must install it in the WS_FTP Server and configure it with the appropriate DNS settings.
Requirements for the WS_FTP Server Web Transfer Client and Ad Hoc Transfer Module end user
The end user can use any computer with an operating system that can support the following:
- Microsoft Internet Explorer 9, 10 or 11 (Windows only); Mozilla Firefox 16 or later, Google Chrome 21 or later, Apple Safari 5 or later (Mac-only)
- Enabled Javascript support in the Web browser
- Enabled Cookie support in the Web browserBroadband connection to the Internet (recommended)
Requirements for the WS_FTP Server Web Transfer Client and the Ad Hoc Transfer Module on Windows Server 2008 R2 or 2012
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
- Static Content
- Default Document
- Directory Browsing
- HTTP Errors
Application Development
- ASP .NET
- .Net Extensibility
- ISAPI Extensions
- ISAPI Filter
Health and Diagnostics
- HTTP Logging
- Request Monitor
Security
- Request Filtering
Performance
- Static Content Compression
Management Tools
- IIS Management Console
The following list shows the Windows Server stand-alone features activated during WS_FTP Server install:
.Net Framework 4.5.2 Features
- .Net Framework 4.5.2
- XPS-Viewer
- WCF Activation (HTTP Activation, Non-HTTP Activation)
Remote Server Administration Tools
- Role Administration Tools (Web Server (IIS) Tools)
Windows Process Activation Service
- Process Model
- .Net Environment
- Configuration APIs
Additionally, the Web Transfer Module install process does the following:
- Runs servicemodelreg to install the WCF service model.
- Places the Web Transfer Module and the underlying web service in classic mode application pools.
Also, if HTTPS is not enabled on the site hosting the Web Transfer Module, the install will:
- Create a self-signed certification for the machine hostname
- Grant permissions to EVERYONE to read the folder where the certifications live
- Create an HTTPS binding on the website hosting the Web Transfer Module (if applicable)
- Attach the certificate to the HTTPS binding
Ad Hoc Transfer Plug-in for Outlook Requirements
The following software must be installed on the machine on which you install the Ad Hoc Transfer Plug-in for Outlook. If the required software is needed by only one of the clients, it is noted as such.
- Microsoft Outlook 2016, 2013, 2010, 2007 (Outlook plug-in only)
- Supported Operating Systems:
- Windows 10 (32-bit and 64-bit)
- Windows 8.1 (32-bit and 64-bit)
- Windows 8 (32-bit and 64-bit)
- Windows 7 (32-bit and 64-bit)
- Microsoft Visual Studio 2010 Tools for Office Runtime (VSTOR 2010) Redistributable (all OS) (Outlook plug-in only)
- Microsoft Visual Studio 2010 Tools for the Microsoft Office System (version 4.0 Runtime) Language Packs (non-English OS) (Outlook plug-in only)
If you are running the installer live (not doing a silent install), the installer automatically installs the Microsoft Visual Studio redistributable programs. You do not need to download anything from Microsoft. If running a silent install, you must download and install these redistributable programs before running the install. See the Requirements in the Silent Install section.
On the last screen of the installer, you can select to View Install Log.
- Microsoft Internet Explorer 9, 10 or 11 (Windows only); Mozilla Firefox 16 or later, Google Chrome 21 or later, Apple Safari 5 or later (Mac-only)
- Enabled Javascript support in the Web browser
- Enabled Cookie support in the Web browser