Release Notes: Aspera for Microsoft SharePoint 1.6.0

Product Release: September 29, 2016

Release Notes Updated: September 29, 2016


This release of Aspera for Microsoft SharePoint provides the new features, fixes, and other changes listed below.

  • Improved performance, including optimized streaming of large files.
  • Support for the SharePoint Recycle Bin.
  • Eliminated duplication of data between the Aspera transfer server node and the SharePoint Document Library.
  • Support for e-discovery workflows.
  • A setting for the desired transfer rate, from within Aspera for SharePoint.


Note: This release was developed using two different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.


ASSP-62 - You can now adjust the transfer rate when you download files from SharePoint. You set the transfer rate in Aspera for SharePoint's transfer server settings; and you can see the transfer rate being enforced in Aspera Connect's Transfer Monitor window.

ASSP-57 - When you uploaded a large number of files (more than ~200) to SharePoint, Aspera for SharePoint failed to upload the files and displayed an error.

ASSP-38 - With an Aspera transfer server on Microsoft Azure, Aspera for SharePoint did not allow you to add a storage account if its access key started with the + character.

#35529 - When you renamed or deleted a file in Drive, this change took effect in SharePoint, but was not immediately reflected in Drive.

#35478 - If you performed a direct download (SharePoint download) of a file, then also performed an Aspera download of the same file, two copies of the file were downloaded to the destination.


Aspera for SharePoint requires the following:

For your Microsoft SharePoint installation:
  • SharePoint Server 2013 that is
    • Running on Windows 2012 or 2012 R2.
    • An on-premise deployment or a cloud deployment in which you performed the installation and have remote desktop access to the virtual machines.
    • Provisioned to host SharePoint apps.
    • Configured to use Active Directory (Kerberos or NTLM).
  • IIS version 8.0 or higher.
  • A domain name and matching wildcard certificate. The domain name must be different than that used for your SharePoint farm. This certificate and domain must be configured on both the SharePoint server(s) and the Aspera for SharePoint remote web server (see below).
For the Aspera transfer server:
  • Windows 2012 or 2012 R2; or Linux.
  • IBM Aspera Enterprise Server 3.5.6 or higher, with a Connect-enabled license, configured as a node.
For data storage:
  • Physical storage or cloud storage (Azure or other cloud options).
For the Aspera remote web server and monitor service:
  • Windows Server 2012 or 2012 R2 (or cloud equivalent).
  • The server must be a member of the Active Directory domain.
  • A fully separate domain (not a subdomain) for the Aspera for SharePoint application, with
    • DNS set up.
    • Wildcard DNS set up.
  • A wildcard SSL certificate for the Aspera for SharePoint domain.
  • IIS version 8.0 or higher.
  • An Active Directory user account and password that is also a SharePoint Site Collection Administrator.
Note: The remote web server and monitor service can be installed on the same system as the Aspera transfer server, but for performance reasons, this is not recommended.
For the Aspera for SharePoint application:
  • The wildcard SSL certificate (see above).
For the client computers:
  • A SharePoint-supported browser (for full SharePoint functionality, Internet Explorer).
  • The IBM Aspera Connect web browser plugin, version 3.5 or higher.
  • Optional: IBM Aspera Drive 1.3.5 or higher.


Windows: AsperaSharePointApp-ML-
md5: f79f4c8ad365a1d292d437e618d9c842
sha1: b7f6b71a7ad3477931b408d091f04446c0e4dcc2
md5: 6636dde064ce7039b598daf593316852
sha1: 2e252f977263d67892c267275f90f26a04a348d7


Note: This release was developed using two different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.


  • If you need to house more than 5,000 files, you must make a small change to the SharePoint configuration. For instructions on raising the list view threshold, see one of these resources:
  • In order to use Aspera for SharePoint with IBM Aspera Drive, you must have Drive 1.3.5 or higher.
  • In some cases, after a very large number of file operations, an administrator may need to run an occasional sync operation. This is to reconcile cases in which a file has been changed (such as renamed) on the transfer server.
  • Some characters that are permitted in filenames on an Aspera transfer server are not permitted in SharePoint. Aspera for SharePoint supports the same set of characters as are supported in SharePoint.
  • If a user has checked out a file through SharePoint, that file cannot be renamed or deleted. (This is standard behavior in SharePoint; Aspera for SharePoint follows the same workflows.)
  • ASSP-74 - When you delete files from Drive, the deleted files are sent not to the site-level Recycle Bin, but to the administrator's Recycle Bin.
  • ASSP-32 - When you delete a Document Library that is mapped to an Aspera transfer server node, the deleted Document Library may still appear on the Transfer Server page. However, it is not possible to edit or otherwise act on it.
  • #31803 - If you change the name of a Document Library in SharePoint, this disrupts the mapping between that Document Library and the Aspera transfer server node. If you upload files after renaming a Document Library, you must perform a sync operation in order for both the Document Library and the transfer server node to reflect the same contents.
  • #30177 - Aspera for SharePoint failed silently for folders with these names:
    • Forms
    • *_files
    This was due to a limitation in Microsoft SharePoint. For more information, see


For on-line support resources for Aspera products, including raising new support tickets, 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.

Powered by Zendesk