Setting Policies for OpenSSH User

Setting local security policies (post-Aspera product installation) for the user who runs OpenSSH

Your Aspera transfer product's installer includes the implementation of an SSH Server (OpenSSH) for user authentication and for the setup of transfer sessions. Alternatively, you can opt not to install OpenSSH (i.e., you click the Custom button within the installer and then de-select the option for the SSH Server), and choose to set it up post-install, instead. If you choose to set up OpenSSH, post-Aspera product installation, then you must create a user account to run the SSH service, and assign the proper permissions. You can set up the SSH service user account and associated permissions automatically using the script asuser-services.bat, which can be found in the following location:

Platform Location
32-bit Windows C:\Program Files (x86)\Aspera\Point-to-Point\bin\
64-bit Windows C:\Program Files\Aspera\Point-to-Point\bin\

You may also set up the SSH service user account manually, although you must also manually assign the proper permissions. You may do so through Administrative Tools > Local [Security] Policy > Local Policies > User Rights Assignment. The SSH user account must be made a member of the local Administrators group and then granted the following rights:

Important: If your clients need to access network resources (e.g., transferring files to or from a Windows share), then you must create a domain account that has proper access to these resources; otherwise, you may create a local account.