Product Setup

Download the IBM Aspera product installer

Download the installer from the link below. Use the credentials provided to your organization by Aspera to access:

If you need help determining your firm's access credentials, contact Technical Support.

For product upgrades, ensure you have prepared your machine to upgrade to a newer version.

Although the installer for Aspera Point-to-Point performs your upgrade automatically, Aspera highly recommends completing the tasks identified in the topic Before Upgrading. If you do not follow these steps, you risk installation errors or losing your former configuration settings.

Warning: When upgrading from 2.7.X to 3.X on Windows, please be aware that user names for 3.X are case sensitive.

Open the installation package and select the setup type

After downloading, open the installation package and follow the on-screen instructions.

Important: On Windows Vista, Windows 7, or Windows 2008 with UAC (User Account Control) enabled, you must run the installer as an Administrator. To do so, right-click the installation package and select the option Run as administrator. You may be asked to enter the administrator's password to allow the installer to make changes to your computer.

After the license agreement screen, click the desired setup type. If you are upgrading from a previous version, the installer will skip this step.

The following setup options are available:

Setup Type	Description
Typical	Install the standard Point-to-Point Client, including an SSH Server (OpenSSH).
Custom	Select the features and the path to install.
Complete	(Same as the Typical setup type).

Note: If your system has an existing SSH service installed (such as Cygwin), select the Custom setup type and deselect SSH Server to avoid conflicts. For assistance, contact Technical Support.

Select features and install path (Custom setup type)

If you selected the custom setup type, you will see the two additional steps during installation, as follows:

Check the features to install. If you wish to configure your own SSH Server for FASP transfers, deselect the SSH Server (so that the OpenSSH Service is not installed).

Select the destination folder for the installation. Under Install this application for:, choose between Anyone who uses this computer (all users) to allow access for all system users, or Only for me to allow only your user account to use the application.

Set up Aspera service account

On Windows Vista, 2003, 2008, and 7, the installer prompts you to create or update an Aspera service account that runs the services for Aspera products. These services include the following:

Aspera Central
OpenSSH Service (optional)
Aspera NodeD
Aspera Sync

By default, the user name is svcAspera. If your machine is not joined to a Windows domain, then a local user (such as the default svcAspera) is all that is required to run Aspera services. If your machine is already joined to a domain, or you need to support requirements #2 and/or #3 below, then the type of account specified will vary. Please refer to the following table:

No.	Requirement	Type of Service Account User
1	Provision local transfer users only.	Local account. Domain account with local admin privileges can be used, but is not required.
2	Provision Active Directory accounts for transfer users (users who wish to transfer with your server are authenticated through Active Directory).	Domain account with local admin privileges.
3	Transfer users store files on a remote file system (not on your server machine), such as an SMB file share.	Domain account with local admin privileges. In some cases, additional actions are required to support this requirement. Please see the aspera knowledgebase or contact Aspera Technical Support for assistance.

If the server is configured to accept the domain user login, use a domain account that has been added to the local administrator's group to run the services. You must create this domain account on your Domain Controller first.

If the local account does not already exist, enter new credentials and click Next. If the account already exists (for example, if created for the previous installation), enter the account password and click Next. If the existing user's password you have entered is incorrect, or you wish to change the Aspera service user, refer to Updating Aspera Service Account.

If you are entering details for a domain account, then the user name must be in the form "username@fully.qualified.domain.name." Please refer to the example below.

Install the license

When installation is finished, launch the application to add or update the license. Go to:

Start Menu > All Programs > Aspera > Point-to-Point > Point-to-Point

If this is a fresh install, an Enter License window appears. Either click Import License File and select the license file, or Paste License Text to copy-and-paste the license file's content. When finished, the license information appears in the window. Verify that it is correct and click Close.

/opt/aspera/etc/aspera-license

When finished, save and close the file. To verify the license info, run the following command:

If you are updating your product license after the installation, see Updating the Product License.

(For upgrades) Check aspera.conf for errors

When upgrading your Aspera product to a newer version, it is recommended that you check the aspera.conf configuration file for errors. Run the following command in a Command window to validate aspera.conf:

Platform	Command
32-bit Windows	`"C:\Program Files\Aspera\Point-to-Point\bin\asuserdata" -v`
64-bit Windows	`"C:\Program Files (x86)\Aspera\Point-to-Point\bin\asuserdata" -v`

Troubleshooting

Problem	Description
Installer freezes	You may have another Aspera product running on your computer. To stop all FASP transfer-related applications and connections, see Before Upgrading.
"Error 1721"	If you are upgrading to the latest version and see "Error 1721" regarding the installer package, the installer may be having difficulty removing the previous installation (2.2.1). For details, see Uninstall Version 2.2.1 for Upgrade.