Please read the following information before upgrading. Several of the caveats below could adversely affect the success of your upgrade if not heeded.
If you are upgrading from EFT Standard edition to EFT Enterprise, you may have to update the path to the .aud file in the Authentication Options dialog box for each Site. Refer to Globalscape Authentication or Changing and Testing LDAP Authentication Options for instructions, depending on the authentication type. When the EFT service starts, it looks for a .cfg file. If the .cfg file is not found, corrupted, or not compatible, EFT creates a new .cfg file in the default location. If the .cfg file is corrupted or the wrong version, the bad .cfg file is backed up and an error is written to the Event log. The .cfg file points to the Sites' .aud files. EFT searches for the .aud file near the ftp.cfg file if the path to the .aud file appears to be incorrect. You cannot edit the .cfg file. (If you have installed the previous version for the sole purpose of upgrading, you must create at least a Server object in the administration interface to create a .cfg file before you can upgrade.)
If you are adding any modules, you may receive a new activation serial number. If so, then it may be necessary to activate the software when you start it for the first time.
Contact the Sales team to obtain a new registration serial number or to determine your eligibility for an upgrade. If you are moving an EFT from one computer to another, contact the Globalscape customer service team or your account manager so that we can adjust your account on our activation and registration server. Activation on the new computer will not be possible until the adjustment is made. If you want to test or verify an update prior to introduction into your production environment, do not use your production serial number for testing purposes.
If you are upgrading a cluster, refer to Installing or Upgrading EFT in a Cluster.
If you are upgrading from Secure FTP Server, refer to: Upgrading Secure FTP Server v3.3 to EFT Server v6.x
DMZ Gateway: If you are also upgrading DMZ Gateway, upgrade DMZ Gateway first, then upgrade EFT.
If you will be upgrading the ARM database, refer to Upgrading the EFT Database, Upgrading Large Databases, and ARM Database Schema Change Tracking for important information. A new process is used to upgrade the ARM database. Refer to Upgrading the EFT Database for details.
When upgrading from versions prior to EFT v6.4, if you upgrade the SQL Server ARM database with the installer, the default schema name is changed to dbo.
COM API resources including SFTPCOMInterface.DLL and associated files are saved in C:\Program Files\Common Files\Globalscape\SFTPCOMInterface so that they can be shared with other Globalscape applications, such as the Secure Ad Hoc Transfer module and Mail Express, ensuring that each application is using the same DLL.
Any scripts that use the v6.2 COM API for Timer Events must be updated to the new API.
The IP Access/IP Ban has increased functionality, and the COM interface has been modified to match the new functionality.
When upgrading the WTC, workstations might receive a Java error, but then the WTC will load and be functional. Refer to KB article#10654 for details.
When upgrading, the \web\custom\ and \web\public\ folders are backed up and renamed with the date and time (e.g., \customBackup_9-28-2010_16-18\ and \publicBackup_9-28-2010_16-18\). The new versions of the files may have some updated content, so rather than overwriting the new files with your old files, you should manually copy your customizations to the new files after upgrading. This applies to any edits for the per-Site and per-Server login pages, Web Transfer Client (WTC) interface, Plain-Text Client (PTC), Account Management interface, and AS2 Management interface.
New functionality has been added to the Web Transfer Client (WTC) and the Plain Text Client (PTC). End users will need to clear their browser cache: refer to KB http://kb.globalscape.com/KnowledgebaseArticle10654.aspx for more information.
The Folder Monitor Event Rule trigger was improved to provide better reliability for the handling of file events. The current Folder Monitor algorithm uses more resources (threads) than the v6.2 algorithm. EFTs with more than 250 Folder Monitor Rules should use the v6.2 algorithm, which uses fewer resources. The 6.2 Folder Monitor algorithm can be selected via a registry key.
The Event Rule file Copy/Move wizard provides control for overwrite options. The overwrite options were set in earlier versions using registry keys. Any associated registry keys will now be ignored and you should update your Event Rule Actions with the desired overwrite option.
EFT supports PORT mode when using the SOCKS protocol to the outbound gateway/proxy. Event Rules that were configured for SOCKS PORT mode in v6.2, will switch from acting as a PASV mode connection to a PORT mode connection in later versions.
During the upgrade, if a non file-trigger rule contains an %FS.FILE_NAME% variable, it will be converted to %SOURCE.FILE_NAME% and a WARNING will record the change in the EFT.log. Refer to Variables (List) for more information about the %SOURCE.FILE_NAME% variable.
In cases where ASCII strings with >127 characters were used for RADIUS in the prior version, there is some risk of loss of fidelity when converting to UTF-8 (depending on the code page) for v6.5. You may need to re-enter values, disable and then re-enable RADIUS, or restart the Site to refresh the values.
If a Site uses the LDAP Authentication Manager, and if the users are allowed to change their passwords, LDAP calls are used to make the password changes. In v6.2, Active Directory calls were used to make the password changes. With the switch to LDAP in v6.3 and later, LDAP over SSL should be used to protect the password changes. LDAP over SSL can be difficult to configure, so the registry setting in http://kb.globalscape.com/KnowledgebaseArticle10659.aspx allows you to continue using the Active Directory API for the password changes, which also provides security for the communication path.
If NTLM v2 proxy authentication support is needed, the default HTTP client must be changed from the Apache HTTP client to the Java JSE HTTP client. The JSE HTTP client does not properly set the Content-Length for files > 2GB, so a custom X-Header is used to communicate the file size. Any HTTP proxy that is in the path between the browser and EFT must properly pass the custom X-Header. Refer to Accessing EFT Through a Proxy for details.
FTP requires UPLOAD permission in addition to APPEND to resume a partial file transfer.
It is a good idea to read the Release Notes before you begin.
To upgrade the software
Document the administrator user name and password for the existing product. If you are also upgrading the database files, you will need the ARM database name, username, and password.
Close the administration interface and stop the EFT service.
As a precaution, back up the existing installation directories and any other files you may have installed elsewhere. If you are upgrading EFT Enterprise, run a backup and save that backup file in an easily accessed location or removable media.
Launch the installer. The Choose an installer page appears.
Click EFT or EFT Enterprise. The installer loads the required components, then the Welcome page appears.
Click Next. The license agreement appears.
Scroll or page down to review the agreement, then click I Agree to continue. The license agreement is also saved in the EFT installation folder as "license.txt" if you want to read or print it later.
The installer will detect the existing installation of EFT.
Click Upgrade to upgrade the existing configuration and copy your existing Sites, users, etc. to the new installation. (If you are upgrading a cluster, refer to Installing EFT in a Cluster. If this is a new installation, refer to Installing the Server, Administrator, and Modules.)
Click Next. If a message appears stating that the SFTPCOMInterface.dll will be upgraded, click OK to dismiss the message.
Click Next. The Choose Components page appears.
To upgrade EFT and the Admin Interface, leave both check boxes selected. (To upgrade only the administration interface (for remote management of the server), clear the EFT check box and refer to Installing the Administration Interface Remotely.)
Click Next. The Choose Install Location page appears.
Keep the default location or click Browse to specify an alternate location.
Click Next. The Configuration data path page appears.
Keep the default location or click Browse to specify an alternate location.
Click Next. The Choose Start Menu Folder page appears.
Keep the default location, click an alternate location, or type a name to create a new folder, then click Next.
Click one of the following options:
If you do not want to configure auditing and reporting, click Skip auditing and reporting configuration, and then click Next and the selected components will be updated. Go to step 24.
If you want to configure auditing and reporting, click Configure auditing and reporting, and then click Next.
If you are using a local SQL Server Express database, the wizard will find the database and prompt you to upgrade it. When using a SQL Server or Oracle database, a page appears in which you can provide the database connection information and credentials. The installer will test the database connection, if configured, then the Confirm Database Upgrade page appears.
Review the information in the dialog box, or click View to review the information in a text editor.
If there are any errors to repair, you can repair them on the database now, and then click Reanalyze to retest.
After all requirements for upgrade have passed, click Install.
The wizard will upgrade the database and the specified EFT components. On the final page of the wizard, select the check boxes as needed:
Start the administration interface - If you do not want to open the interface, clear the check box. You can also open the interface from the Start menu.
Create a desktop shortcut - An administration interface shortcut is created on the desktop by default. If you do not want to create a shortcut, clear the check box.
Show version history - If you want to read the release notes, select the Show Version History check box. If you want to read it later, the release notes file, notes.txt, is installed in the EFT installation directory.
Show installation log - If you want to review the installation log now, select the check box. If you want to review it later, it is saved in a temporary folder, C:\Program Files\GlobalSCAPE\EFT Server Enterprise (or EFT Server)\Installer.log.
Start the EFT Service - Clear the check box if you do not want to start the service yet. Select the check box if you want to start the service when you click Finish. The service is configured to start automatically when the computer starts. If you do not want the service to start automatically, you will have to configure it in Windows to start manually.
The EFT service Log On as account will be set to Local System account by default. If necessary, you can edit this in the service's Properties dialog box, on the Log on tab. (Start > Run > services.msc.)