Product Setup

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

IBM Aspera Connect Server is a web-based file server that enables file access through a browser, and transfers files using the IBM Aspera Connect Browser Plug-in. Additionally, you can set up HTTP Fallback to establish HTTP- or HTTPS-based file transfers with clients that don't have FASP connectivity.

Note: On Windows, Connect Server uses Internet Information Service (IIS) authentication. If usernames use the extended character set, both the client and server machine must be set to use the same codepage, and the client must use IE 7 or later (other browsers don't support usernames using extended characters). For more information, see http://support.microsoft.com/kb/938418.

To install Connect 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. Install Windows Internet Information Service (IIS).
    The Connect Server web UI requires Internet Information Service (IIS) 7 with the IIS 6 Compatibility component. Depending on your version of Windows, IIS may not be installed. You also need to ensure that ASP, ASP.NET, and Basic Authentication services are installed. For instructions on installing and enabling IIS for your specific Windows OS, see the table below.
    OS Instructions
    Windows 7, 8, 10 Click Control Panel > Programs > Turn Windows features on or off.
    Turn Windows features on or off.

    In Turn Windows Features On or Off, select the following features and click OK:

    1. Select Internet Information Services and expand the file tree.
    2. Expand Web Management Tools and select IIS 6 Management Compatibility. Expand IIS 6 Management Compatibility and select all IIS 6 components. (Required)
    3. Expand World Wide Web Services and Application Development Features then select ASP and ASP.NET. If you are running Windows 8, you can select either .NET 3.5 or .NET 4.5. ISAPI Extensionand ISAPI Filters will automatically be selected.
    4. Expand Common HTTP Features under World Wide Web Services and select Static Content.
    5. Expand Security under World Wide Web Services and select Basic Authentication.

    Turn on IIS features.

    Click OK once all selections have been made. Your computer may take a few minutes to configure itself.

    Verify installation was successful by opening Control Panel > System and Security > Administrative Tools. You should see the following features:

    • Internet Information Services (IIS) 6.0 Manager
    • Internet Information Services (IIS) Manager
    IIS installed features.
    Windows Server 2012 R2, 2016 On the taskbar, click Server Manager to open the UI. Click Manage > Add Roles and Features.
    The manage button is located in the upper right corner of the Server Manager window

    Click Next to move on from the Before you begin landing page. On the Select installation type window, leave Role-based or feature-based installation selected, click Next, then select the destination server and click Next.

    In the list of Roles, select Web Server (IIS) and click Add Features in the pop-up window that appears, then click Next to enter the Features selector. Click Next to leave Features, then click Next to select role services to install.

    Expand Common HTTP Features and select Static Content (Default Document, Directory Browsing, and HTTP Errors should already be selected). Expand Security and select Basic Authentication(Request Filtering should already be selected).


    Select Static Content and Basic Authentication

    Expand Application Development and select .NET Extensibility 3.5 or .NET Extensibility 4.5. Click Add Features in the pop-up window. Select ASP and ASP.NET 3.5 or ASP.NET 4.5 (the same version as the .NET Extensibility) and click Add Features in the pop-up window. This automatically selects ISAPI Extensions and ISAPI Filters.


    Select Application Development features and IIS 6 Management Compatibility features

    Expand Management Tools and select IIS 6 Management Compatibility (IIS Management Console is already selected). Expand IIS 6 Management Compatibility and select all features. After you select IIS 6 Scripting Tools, click Add Features in the pop-up, and this automatically selects IIS 6 WMI Compatibility.

    Click Next to view a list of features selected then click Install to start the installation. Your server will take a few minutes to configure itself. On the Installation Results page, confirm that the installation completed successfully, then click Close.

    To confirm that IIS installed successfully, open a web browser, enter http://localhost in the address bar, and press Enter. If IIS was installed successfully, you see the default IIS Welcome page.

    Windows 2008 From the Control Panel, click Administrative Tools > Server Manager > Roles > Add Roles. Add a role.

    In the Add Roles Wizard, select Web Server (IIS). In the popup window that appears, click Add Required Features and click Next. Read the information on the following screen, then click Next.

    Add required features.

    Select the following role services:

    • ASP.NET
    • ASP
    • Basic Authentication
    • IIS 6 Management Compatibility (entire tree) (Required)

    Turn on IIS features.

    Click Next. Read the confirmation message and click Install. Your server will take a few minutes to configure itself.

    Verify that the installation was successful by viewing your Role Summary. Click Administrative Tools > Server Manager > Roles > Web Server (IIS) > Role Services and confirm that the features selected above appear in the Role Service pane.

    IIS installed features.
    Important: When you install the Connect Server web UI feature (as directed in the steps below), the Aspera installer automatically configures the following settings in IIS:
    • Disable Anonymous Authentication
    • Disable ASP.Net Impersonation
    • Enable Basic Authentication

    If you do not install the Connect Server web UI feature, then the settings will not be modified.

  2. Download the IBM Aspera product installer.
    Use the credentials provided to your organization by Aspera (not your personal Aspera ID) to access:

    http://downloads.asperasoft.com/en/downloads/4

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

  3. 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 or Downgrading. If you do not follow these steps, you risk installation errors or losing your configuration settings.
  4. 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.

    When installing Connect Server, you must select one of the following setup types:
    • Complete, which includes the web UI component.
    • Custom, along with the Connect Server web UI component.
    A Typical setup installs the standard Enterprise Server without web UI.
    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
    Custom Select the features and the path to install.
    Complete Install all features, including an SSH Server (OpenSSH) and the Connect Server web UI. IIS must already be installed on your Windows OS (see Step 1).
  5. 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 and you have installed IIS, as described in Step 1, above.
    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
  6. Set up the Aspera service account.
    The Aspera service account runs services for Aspera products, including:
    • Aspera Central
    • OpenSSH Service (optional)
    • Aspera NodeD
    • Aspera HTTPD
    • Aspera Sync

    By default, the user name is svcAspera. User names for Connect Server version 3.1.0 and later 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 username@fully.qualified.domain.name. See the example below.

    Set up the Aspera service account.
    Note: If you intend to use this Connect 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.
  7. Select a website for the Connect Server web UI
    During IIS installation, a default website configuration is created on your web server (for example, "Default Web Site (ID:1)"). You can use this default directory to publish your web content, or you can use a directory in a different location. In the Connect Server setup dialog, select the website (default or other) to use for the Connect Server web UI from the dropdown menu. Select the website to set up web UI.
    Note: If you are upgrading Connect Server from a previous version, Aspera recommends you select the same website on which your current web UI is running.
  8. 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.

  9. Configure SSL. (Optional)
    To generate an Internet Server Certificate for IIS 7, see Generate an Internet Server Certificate (IIS).
  10. Troubleshooting
    If the installer freezes during installation, another Aspera product might be running on your computer. To stop all FASP transfer-related applications and connections, see Before Upgrading or Downgrading.
  11. Set up your new Connect Server's web UI (or verify your web UI settings after an upgrade).
    Your IBM Aspera transfer product is now installed. Additional steps are required to configure the web UI, see Set up the Connect Server Web UI.