The Connect Server Web UI requires Internet Information Service (IIS) 6, or IIS 7 with the IIS 6 Compatibility component. Depending on your version of Windows, IIS may not be installed by default. Please refer to the table below for instructions on installing/enabling IIS for your specific Windows OS. Note that Windows 7, 8 and 2008 require installation of IIS 7 with the IIS 6 Compatibility component. You will also need to ensure that ASP, ASP.NET, and Basic Authentication services are installed.

OS	Instructions
Windows 7, 8 and Vista	NOTE: Requires installation of IIS 7 with the IIS 6 Compatibility component. In Windows 7 and 8, go to the Control Panel > Programs > Turn Windows features on or off . (Fig: Windows 7 and 8) In Windows Vista, go to the Control Panel > Programs and Features > Turn Windows features on or off (located in the left panel). (Fig: Windows Vista) In the Turn Windows features on or off window, turn on the following features and click "OK": Place a check next to Internet Information Services and then expand the tree. Expand the Web Management Tools tree and place a check next to IIS 6 Management Compatibility. Then, expand the IIS 6 Management Compatibility tree and place a check next to each IIS 6 component. Within World Wide Web Services > Application Development Features , place a check next to ASP and ASP.NET. Note that if you are running Windows 8, you can select either .NET 3.5 or .NET 4.5. Within World Wide Web Services > Common HTTP Features , place a check next to Static Content. Within World Wide Web Services > Security , and place a check next to Basic Authentication. (Fig: Windows 8) Your computer may take a few minutes to configure itself. You can verify a successful installation by navigating to "Administrative Tools." In Windows 7 and 8, go to Control Panel > System and Security > Administrative Tools . In Windows Vista, go to Control Panel > Administrative Tools . Within "Administrative Tools," you should see the following features: Internet Information Services (IIS) 6.0 Manager (or IIS6 Manager on Windows Vista) Internet Information Services (IIS) Manager (or IIS Manager on Windows Vista)
Windows 2008	IMPORTANT NOTE: Requires installation of IIS 7 with the IIS 6 Compatibility component. Go to Administrative Tools > Server Manager > Roles > Add Roles . In the Add Roles Wizard, check Web Server (IIS). Upon checking it, a pop-up window will appear, which requires you to identify features that are required for the Web Server. Click the Add Required Features button in the pop-up window and click Next. Read the information on the following screen and then click Next again to proceed with adding required features. Add the following role services as required features by checkmarking the appropriate boxes and click Next when finished. ASP.NET ASP Basic Authentication IIS 6 Management Compatibility (entire tree) Once you read the confirmation message and click install, your server will take a few minutes to configure itself. You can verify a successful installation by navigating to your "Role Summary." Go to the Administrative Tools > Server Manager > Roles > Web Server (IIS) > Role Services .
Windows XP and Windows 2003	Go to the Control Panel > Add or Remove Programs > Add/Remove Windows Components (located in the left panel). For Windows XP, in the Windows Components Wizard window, place a checkmark next to Internet Information Services (IIS), and click Next. (Fig: Windows XP) For Windows 2003, in the Windows Components Wizard window, place a checkmark next to Application Server, and click Next. (Fig: Windows 2003) Your computer may take a few minutes to configure itself. You can verify a successful installation by going to Control Panel > Administrative Tools (located in "Classic View" in Windows XP). Here, you should see the Internet Information Services (IIS) Manager. (Fig: Windows XP) (Fig: Windows 2003)

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.

Although the Aspera Connect Server installer performs your upgrade automatically, we highly recommend 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.

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

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:

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). Check the Connect Server Web UI only if you have a Connect Server license and you have installed IIS, as described in Step 1, above.

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.

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

• Aspera Central
• (Optional) OpenSSH Service
• Aspera NodeD
• Aspera HTTPD
• 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:

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. On Windows XP 32-bit, instead of creating a user account, you may check the option Run Aspera services as a local SYSTEM account to run these services by the local user "SYSTEM."

If the local account does not already exist, enter new credentials and click Next. If the account exists (e.g. created through 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.

During IIS installation, a default Web site configuration is created on your Web server (e.g. "Default Web Site (ID:1)"). You may have elected to use this default directory to publish your Web content, or you may have created a directory at a file system location of your choice. In this step, select the website (default or other) that you created for the Connect Server Web UI.

When installation is finished, launch the application to add or update the license. Go to Start Menu > All Programs > Aspera > Enterprise Server > Enterprise Server .

If this is a fresh install, an Enter License window will appear. You may click the 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 will appear in the window. Verify that it is correct and click Close.

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

For instructions on generating an Internet Server Certificate for IIS 6 (Windows XP, 2003) or IIS 7 (Windows Vista, 2008, 7), please refer to the topic Generate an Internet Server Certificate (IIS).

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:

At this point, your Aspera transfer product is installed; however additional steps are required to configure the Web UI. Please continue to the Chapter "Connect Server Web UI Setup" and review the topics contained herein.