Release Notes: Aspera for Microsoft SharePoint 1.6.2

Product Release: January 9, 2017

Release Notes Updated: January 9, 2017

Welcome to this release of IBM Aspera for Microsoft SharePoint. Aspera for SharePoint 1.6.2 is a maintenance release that features bug fixes and various other improvements.


  • Aspera for SharePoint now supports ADFS authentication and single sign-on.
  • When you enter a path in LocalDirectory, the folder is now created if it does not already exist.
  • Aspera for SharePoint now supports content protection on your transfer server, for server-side encryption at rest (EAR).
    To configure server-side encryption, add the following to your aspera.conf file:
    After updating aspera.conf, you must
    1. Restart asperanoded and asperacentral.
    2. Add (or re-add) this transfer server node to Aspera for SharePoint.
    Once this configuration is in place, when you upload files or folders to SharePoint, you also enter the passphrase for encryption. On the transfer server node, the files are saved with the .aspera-env extension, indicating that they are encrypted. This is true of both the Insert as Link and the Insert as File content types. When users download the content, they must enter the passphrase to decrypt it.
    Note: When content_protection_required is enabled on your transfer server, you can perform an Aspera download of *.aspera-env files, but you cannot perform a direct download of these encrypted files.


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-101 - The Transfer Rate field now uses Mbps as its unit of measure. (It previously used bps.)

ASSP-100 - The Transfer Rate field now includes a label to show what unit of measure it uses.

ASSP-87 - When you uploaded a file to a nested folder as a file content type (rather than as a link), the upload action failed.

ASSP-86 - When a SharePoint Document Library is mapped to a local folder on a transfer server node, download actions failed.

ASSP-84 - When you toggled from the Insert as file to Insert as link content types, then synced the transfer server node with the SharePoint Document Library, duplicate files were created in nested folders.

ASSP-79 - You can now correctly drag-and-drop a file to download it from SharePoint with Aspera Drive.

ASSP-65 - A bug has been fixed that caused duplicate files to appear on the transfer server node and in the SharePoint Document Library. Now, if the SharePoint Recycle Bin is enabled, when you delete a file or folder, it is moved to a hidden folder on the transfer server node. If you restore the deleted content from the SharePoint Recycle Bin, it is restored from that hidden folder.

#31803 - If you changed the name of a Document Library in SharePoint, this disrupted the mapping between that Document Library and the Aspera transfer server node.


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 plug-in, version 3.5 or higher.
  • Optional: IBM Aspera Drive 1.3.5 or higher.


Windows: AsperaSharePointApp-ML-
md5: c1b92456b9d1335958300611a16cf52e
sha1: 54ca44cb70d468cb2e753af13e09b9330602f461
md5: 385c13822aba20eb846f37be9c176cf1
sha1: 9ee1ce9f5039facb5902635e77d733c4ccade71f


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-124 - If you change a folder on the transfer server node (such as by renaming or moving it), then sync the transfer server node with the SharePoint Document Library, the changed folder persists in the Document Library (it appears as an empty folder). To avoid this issue, before performing a sync, ensure that the Document Library contains only the content you want to sync.
  • 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-59 - Users with view-only permissions can download files from Drive.
  • 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.
  • #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. To fix this issue, do the following: Go to Site Settings > Site Actions > Manage Site Features and deactivate the Minimal Download Strategy option.
  • #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