Aspera Drive 1.2.0 Release Notes
Aspera Drive 1.2.0 Release Notes

Aspera Drive 1.2.0 Release Notes

  • Product Release Date: Jan. 13, 2015
  • Release Notes Updated: Jan. 13, 2015

WHAT'S NEW

Welcome to this release of Aspera Drive. Drive 1.2.0 includes new features for integration with Microsoft Azure.

This release provides the following new features:
  • Install for all users - The installer program for Drive now includes an advanced option that lets you install Drive for all users. Each user, however, can have his or her own settings.
  • SSL certificate validation - Drive now validates SSL certificates. If the server's certificate is not valid, Drive asks you whether it should trust the server.
  • Improved support for cloud storage - Drive 1.2.0 offers an improved workflow for adding accounts that use cloud storage, and several bug fixes around Azure SAS.
    Note: If you need to generate Azure SAS URLs, there are several tools you can use. For example, you can download the open-source tool Azure Storage Explorer. See https://azurestorageexplorer.codeplex.com/ for futher information.

    Note, however, that earlier versions of Azure Storage Explorer may generate URLs that expire after one hour. If you use Azure Storage Explorer, Aspera recommends version 6 or higher.

ISSUES FIXED IN THIS RELEASE

  • When you configure an Azure account, the account-setup wizard now includes cloud-specific fields. Furthermore, the account-setup wizard now verifies that Drive can browse files in storage before continuing.
  • If your transfer server is running Aspera Enterprise server 3.5, you can now enable TLS without adjusting your aspera.conf file.
  • Proxy support has been fixed.
  • When you use Drive with Shares, you can now delete more than 200 files at the same time.

KNOWN ISSUES

  • #20513 - When you use Drive with Faspex to send a package to a dropbox, the dropbox name will not appear in the autocomplete options. Instead, you must type the dropbox name manually.
  • #22789 - When a directory is renamed, then renamed again to its original name, the correct name may not appear in all Explorer windows.
  • #23230 - Aspera Drive cannot send packages to some valid Faspex usernames if those usernames contain the following special characters:

    < > ; ( ) &

  • #24193 - On Mac OS X, when you right-click a file for the first time after Drive has been installed, the Send to Faspex option is not available. However, it is available on subsequent attempts.
  • #25913 - During a sync scheduled in Aspera Drive, even if files on the Shares server are changing (that is, are in the process of being downloaded), Aspera Drive nevertheless attempts to sync those files, resulting in file errors and conflicts.
  • #26641 - Drive does not allow drag-and-drop of files from the remote server when the files have the same name but different case (for example, aspera1 and Aspera1).
  • #26725 - On Mac OS X, an initial sync of a large number of files results in high CPU usage.
  • #27153 - If the host is unreachable while Aspera Drive is sending a Faspex package, Drive shows a "Not responding" error. The "Not responding" state persists for approximately one minute.
  • #27277 - If a user's account is configured to check for updates from an update server that uses the "Check for updates" feature, when that user first attempts an automatic update from Drive 1.1.1 to Drive 1.2.0, the update fails with an error message:
    Failed to run update. Mount location not found:
    /tmp/AsperaDrive
    If the user attempts the automatic update a second time, the update succeeds.

    Then, when the user manually opens the upgraded application for the first time, the Drive icon may appear to be missing. However, the application does open successfully and the icon is then displayed correctly.

  • #27587 - Temporary files that applications (such as Microsoft Office) create are excluded from sync transactions because they can cause conflicts. The affected files are those with names of the form ~$* or ~*.tmp.
  • #27961 - If you updated your Windows installation between August 12 and October 14, 2014 (Microsoft Security Update KB2918614), you cannot install Drive system-wide as a domain user. The system produces the error message The profile for the user is a temporary profile. To address this, you must either
    • Uninstall Microsoft Security Update KB2918614.

      or

    • Install update KB3000988.
  • #28181 - On Mac OS X, some configurations experience issues in syncing files with S3 storage.

SYSTEM REQUIREMENTS

Windows

On your Aspera Drive client:

  • Windows 7 or 8

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or higher with a Sync-enabled license.

Mac

On your Aspera Drive client:

  • OS X 10.8, 10.9, or 10.0.

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or later with a Sync-enabled license.

PACKAGE INFORMATION

Windows: AsperaDrive-1.2.0.98091.msi:
md5: 2a4e6524289fed47fd432cec32424c74
sha1: de321b7be65d7bdc5a7d54b224c87779bc33b210
Mac OS X: AsperaDrive-1.2.0.98091.dmg:
md5: 2a1451b49f50c78597ad809a6cefebb4
sha1: 40fbbff7e19ce079739272bec4f384543902d7e9

PRODUCT SUPPORT

For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.