Installing Desktop Client

To install Desktop Client, log into your computer with Administrator (or Domain Administrator if you are in an Active Directory environment) permissions.

1. Download the HSTS installer.
   Use the credentials provided to your organization by Aspera to access:

   https://downloads.asperasoft.com/en/downloads/2

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

2. For product upgrades, ensure you have prepared your system 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
3. Open the installation package and select the setup type.

   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 skips this step.

   Setup Type	Description
   Typical	Install the standard Desktop Client.
   Custom	Select the path to install.
   Complete	Same as the Typical setup.

4. For a Custom setup, configure the installation path and users.
   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.

   

5. Set up the Aspera service account.
   The Aspera service account runs services for Aspera products, including:

   • Aspera Sync

   By default, the user name is svcAspera. User names for Desktop Client 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 knowledge base 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.

   

   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, as in the following example:

   
6. Installation 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.