Product Setup

Important: If this is a product upgrade, review all prerequisites described in Before Upgrading.

To install Enterprise Server, log into your computer with Administrator (or Domain Administrator if you are in an Active Directory environment) permissions, and follow the steps below.

  1. Download the IBM Aspera product installer.

    Use the credentials provided to your organization by Aspera to access:

    If you need help determining your firm's access credentials, contact your Aspera account manager.

  2. For product upgrades, ensure you have prepared your machine to upgrade to a newer version.
    Although the installer performs your upgrade automatically, Aspera highly recommends completing the tasks described in Before Upgrading. If you do not follow these steps, you risk installation errors or losing your configuration settings.
  3. Open the installation package and select the setup type.
    Important: On 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 Run as administrator. You may be asked to enter the administrator's password to allow the installer to make changes to your computer.

    Follow the on-screen instructions. After the license agreement screen, select the desired setup type. If you are upgrading from a previous version, the installer will skip this step.

    Note: If your system has an existing SSH service installed (such as Cygwin), select the Custom setup type and clear SSH Server to avoid conflicts. For assistance, contact Technical Support.
    Setup Type Description
    Typical Install the standard Enterprise Server, including an SSH Server (OpenSSH).
    Custom Select the features and the path to install.
    Complete Install all features, including an SSH Server (OpenSSH) and the Connect Server web UI (for Connect Server, a web-based transfer server). Note that the Connect Server web UI cannot be used unless you have a Connect Server license. To upgrade Enterprise Server to Connect Server, contact your Aspera account manager to obtain the license.
  4. For a Custom setup, select features to install and the installation path.
    If you wish to configure your own SSH Server for FASP transfers, deselect SSH Server so that the OpenSSH Service is not installed. Select Connect Server Web UI only if you have a Connect Server license .
    Custom setup type - select features

    Select the destination folder for the installation or use the default filepath. Under Install this application for, select 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.

    Custom setup type - select features
  5. Set up the Aspera service account.
    The Aspera service account runs services for Aspera products, including:
    • Aspera Central
    • OpenSSH Service (optional)
    • Aspera NodeD
    • Aspera Sync

    By default, the user name is svcAspera.

    Note: User names for 3.X are case sensitive.

    A local account (such as the default svcAspera) is all that is required to run Aspera services if your machine is not joined to a Windows domain. If your machine is joined to a domain, if you need to provision Active Directory accounts, or if transfer users store files remotely, refer to the following table for the type of service account to use:

    Requirement Type of Service Account User
    Provision local transfer users only. Local account. Domain account with local admin privileges can be used, but is not required.
    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.
    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. Additional actions may required. Please see the aspera knowledgebase or contact your Aspera account manager for assistance.

    Local accounts: If a local account does not already exist, enter new credentials and click Next. If the account already exists (for example, if it was 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, see Managing the Aspera Service Account.

    Set up the Aspera service account.

    Domain accounts: If the server is configured to accept a 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 in your Domain Controller first. The username for a domain account must be in the form See the example below.

    Set up the Aspera service account.
    Note: If you intend to use this Enterprise Server node with Console, the Aspera service account (svcAspera, by default) must be set up as a transfer user on this node. If you have installed these products by upgrading from a previous installation of Connect or Enterprise Server, a transfer user corresponding to the service account is created automatically. However, if you are performing a "clean" install (not an upgrade from a previous installation), only the service account is created, not the corresponding transfer user. In this case, create the transfer user manually using the Connect/Enterprise Server GUI.
  6. Install the license.
    Launch the application to add or update the license. Click: Start Menu > All Programs > Aspera > Enterprise Server > Enterprise Server.

    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. The license information appears in the window. Verify that it is correct and click Close.

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

  7. 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 or Downgrading.
    "Error 1721" The installer may be having difficulty removing the previous installation (2.2.1). For details, see Uninstall Version 2.2.1 for Upgrade.