Upgrading Notes

Refer to the Globalscape Knowledgebase topic #11194 for more information about upgrading EFT.

Upgrading notes for v8.0.6:

  • In EFT v8.0.6, the installer includes SQL Server Express 2019; Upgrades will continue to use SQL 2017 Express as we do not upgrade SQL Express via our installer

  • When upgrading to v8.0.6, EFT will convert the reply behavior for File Uploaded rules from synchronous to asynchronous by default. This may affect the flow of existing File Uploaded rules. If needed, you can return to the legacy synchronous reply behavior by setting the Advanced Property 'WaitOnFileUploadEventCompletionBeforeSendingResult" to true.​

  • Upgrade can fail when multiple actions (>100+) exist in a single event rule. Setting up event rules like this can exceed transfer storage size limit and prevent importing event rules with a "big body." Workaround is to separate the event rules to have fewer actions or to increase EFT computer power. (Globalscape Professional Services can assist you in optimizing your event rules for better performance with their EFT Automation Assessment.)

  • The EFT installer does not detect the App Data directory if the previous version was installed from a command-line (Silent Installation). You must upgrade using the same method.

Upgrading notes for v8.0.5:

  • Upgrade 8.0.0.38 to 8.0.5.12 fails due to database upgrade functions. The workaround is a version-stepped upgrade.

    Copy the \web\ folder from the EFT installation folder to the cluster share (%ClusterShare%)

  • Upon upgrade, the file structure of the EFT client location, C:\Program Files (x86)\Globalscape\EFT Server Enterprise\web\public\EFTClient\shadowfax\wtc\assets, has changed to C:\Program Files (x86)\Globalscape\EFT Server Enterprise\Web\Shadowfax\wtc\assets (\public\EFTClient\ no longer exists) and the admin-configuration.json file has new parameters.

  • Upon upgrade, the TLS Settings dialog box may be blank due to the changes in SSL between versions.

  • If used in a previous version, the advanced property UserAgentHeaderSkipOTP will need to be updated in the JSON file to add brackets around the value, even if only one value is specified: "UserAgentHeaderSkipOTP": ["value"] Until the brackets are added, the advanced property will fail to load.​​

  • In the WTC, the Progress icon continues to spin, even while an upload is paused

  • In the ​​WTC, the Password Reset functionality is not available for AD​ or LDAP

  • After an upgrade of HA primary node, the modified theme.json file is not moved to the shared folder

  • Twilio verification test option requires +1 before it can successfully send a test

  • For the Acceleration module, pre EFT v8.0.4 scClient is NOT backward compatible with the DMZ Acceleration library with a trial expiry date of 11Jan21 (DMZ 3.5.0.24) and later. So, if a customer who's already using an older (pre 3.5.0.24) DMZ wishes to trial Acceleration using scClient, they will need to update the FAST dll in DMZ AND update their scClient on the EFT server.

  • Upgrading to this version will convert all event rule actions set to run in synchronous mode, to asynchronous mode. This potentially can impact the logic/flow of client event rules after upgrade. In particular, the On User Login event rule can prevent users from logging in after upgrade, if it contains actions that get converted to sync mode and the action takes some time to complete. The current list of actions that support asynchronous mode are listed below. These actions will convert to synchronous mode.

    • Execute command

    • Execute Advanced Workflow

    • Send notification email

    • Call event rule subroutine

  • When you upgrade from an earlier version, your event rules will have been changed to the new naming of the actions. For example, the Copy/Move Action from earlier versions is now the Protocol: Upload action.

Upgrading from EFT v7.4.x to EFT v8.x

The following changes upon upgrading from v7.4.x to v8.x should be noted:

  • EFT Insight

    • EFT v8.0.x works with EFT Insight v1.0.7.4550 or later

  • Advanced Workflow Engine

    • The Advanced Workflow tasks in versions prior to v8 were stored on EFT in the form of AML files. In v8 and later, they are stored in the SQLite database files. If you are using the Task Action in AWE, which is an AWE task that is calling another AWE task, you will need to export the AML files to a location that EFT can access.

  • WTC/Workspaces

    • Customizations in the v7.4.x client interface do not carry over upon upgrade to v8.x. You should back up everything BEFORE upgrading, then you can apply your custom logo, theme.json file, and any customizations after the upgrade.

    • Some portals were not updated with the new look and feel. Those changes are expected in subsequent releases.

    • In v8.0.0 and 8.0.1, the send portal does not provide an option to select files in your Workspace; you can only select files on the hard drive. In v8.0.2, you can select Workspace files.

    • EFT v8.x does not support UPLOADS from CAC-authenticated users when using Chrome or Edge browsers. Firefox (and possibly other browsers) will work.

  • Administration Interface

    • The Site > General tab and Server > General tab (anywhere that Last modified by is displayed) will report Last modified by as "EFTUpgrade" after upgrading

    • The Site > Workspaces tabs have been consolidated into the Site > Web tab

    • On the Server > General tab, the Server configuration settings box is not editable. EFT configuration is now stored in a database file.

    • Removed email address from User > General tab

    • Optional permission on Server > administration tab to give administrator accounts permission to manage personal data for users

    • Added User Account Details Template on Site > Security tab to apply GDPR-related privacy settings to all user accounts on a Site

    • Added ability to resize SSH Key Manager dialog box and Advanced Workflow dialog box

  • SSH keys

    • Upon upgrade from 7.4.x to 8.x, ALL SSH keys are moved into each Site-specific key manager

    • The SFTP private key is pulled from the key manager

    • Upon upgrading to v8.0.4, EFT will enable the following ciphers:

      • aes256-gcm@openssh.com

      • aes128-gcm@openssh.com

      • rijndael-cbc@lysator.liu.se

      • aes192-ctr

      • aes192-cbc

  • OpenPGP

    • OpenPGP key pairs are defined and managed on a Site instead of the Server

    • PGP keyring (pubring.pgp and secring.pgp) are stored in SiteConfig<GUID>.db

    • At EFT server service startup, a PGP folder is created in the \ProgramData\Globalscape\EFT folder

    • Upon upgrading from a 7.4.x version to EFT v8, ALL PGP keyrings are cloned into each Site keyring

    • Upon upgrading a legacy server, keyrings are cloned into each site keyring.

    • Added "Sites" combo box to OpenPGP Keyring dialog box; Removed "Sites" combo box from OpenPGP Key Generation wizard; Removed OpenPGP Settings dialog box.​

  • VFS

  • Advanced Properties

    • Non-default registry settings are moved to AdvancedProperties.json

    • EFT caches all Advanced Properties on service startup and purges legacy Advanced Properties from the registry

    • The following registry keys have been removed from the Advanced Property list

      • AppDataPath

      • DefaultCfgPath

      • Cluster and SharedFolder; these two are located in Cluster.json now

  • HA Configuration

    • In EFT v8.x and later, you have the option to store logs on the cluster shared drive; the log naming convention now allows for that

  • EFT Configuration - Upon upgrade, EFT settings are transitioned from SiteConfig<GUID>.db and ServerConfig.db

    • These Server-level settings are now stored in SiteConfig<GUID>.db

      • General Tab

      • administration Tab

      • Security Tab

      • SMTP Tab

      • Logs Tab

      • HA Tab

      • CIC Tab

    • These Site-level settings are now stored in SiteConfig<GUID>.db

      • General Tab

      • Connections Tab

      • Security Tab

      • Gateway Tab

    • EFT will request administrator credentials on Server Config Restore. If credentials are invalid, restoration will fail.

    • Restore from previous versions of EFT are forbidden. EFT now only supports restoration from the same version of EFT.

  • ODBC

    • When upgrading from 7.4.x to 8.0.x, the ODBC schema has changed. If you are using ODBC as the authentication database, then you will need to consult with Globalscape Support so we can assist with the manual process necessary to get EFT updated and running.

  • LDAP

    • LDAP search timeout now applies also to search timeout. The default value is 60 seconds.

  • SFTP

    • When you create a Site, you are able to specify the use of SFTP and browse for a key. After the Site is created and you click on SFTP config (on the Site > Connections tab), you cannot browse the file system to find a key. Instead, you are taken to the SSH Key Manager.

  • Content Integrity Control (CIC) Action

    • Upon upgrade, legacy server level CIC profiles will be cloned into each Site. CIC profiles are now site-level

  • Remote Agents

    • When upgrading a GA EFT Server 7.4.13.15 to the latest 8.0 EFT Server, Remote Agents will not auto-update to the new version. You need to have the patched Remote Agent msi and executable before you can update to the latest 8.0 agents. You will need to enroll the agents with the patched versions before proceeding.