Skip to content
English
Submit a Support Ticket
Contact us
  • There are no suggestions because the search field is empty.

SureSync MFT Internal Build

An MFT Internal Build is used to update your MFT environment with the latest fixes not yet available in an official public release.

SureSync MFT Installer

The full SureSync MFT Internal Build can be downloaded by clicking here.

File Name: SureSyncMFTSetup.exe

Version 2.0.32.03

To update to the internal build, simply run the installer on each machine in the environment with the Hub or the Communications Agent installed. The steps are the same as performing a regular SureSync MFT Update as outlined in the Updating SureSync MFT KB article.

Fixes in the 2.0.32 Internal Builds

2.0.32.04

  • When a Job is disabled, file action in progress may not be canceled. In that situation, the Job would attempt to completre the current active copy actions. This has been fixed in 2.0.32.4.
  • In a Delete Rule, if a File Mask was defined, a folder could be deleted incorrectly. Folders should only be deleted in a Delete Rule with a *.* definition. This has been fixed in 2.0.32.4.
  • In Enterprise Status, you can now multi-select multiple Jobs and enable/disable them as a group. You will be prompted to confirm the action on the first Job and then prompted if you would like to perform the same action on the others. If you multi-select Jobs that are in different statuses, you will have to select an action for each job. This has been fixed in 2.0.32.4.
  • The capability to export a license file from the Desktop has been added. This can be accessed via Licenses in the Ribbon bar and then clicking on the Export License button. This can be useful if you have one Desktop that has Internet access and others that do not. You can activate licenses via the one with the Internet access, export to the license and import it into the Desktops that do not. This has been fixed in 2.0.32.4.

2.0.32.03

  • Corrections have been made to the file locking driver load and unload processes. This has been fixed in 2.0.32.3.

2.0.32.02

  • In a rare timing situation related to path losses, a Foreign Key Constraint error could occur. This has been fixed in 2.0.32.2.

2.0.32.01

  • A deadlock could occur in the Hub service QueryJournalStatus.  A connection would have to drop, come back for a few seconds, and fail again while initializing to encounter the problem. This has been fixed in 2.0.32.1.