|Configuring for Other Aspera Products|
These steps are described in detail below.All steps must be performed with administrator permissions.
The transfer server that you use with Aspera for SharePoint must be installed on a host separate from your Microsoft SharePoint environment hosts.
To create a new system user sharepoint on your Windows system, go to Control Panel > User Accounts. After adding the sharepoint user, change the user's password.
Then log back in as administrator and continue the steps below.
The Aspera-provided key file is located in:C:\Program Files [(x86)]\Aspera\Enterprise Server\var\aspera_tokenauth_id_rsa.pub
> cd user_profile_folder > md .ssh
In Windows Explorer, right-click the .ssh folder, and select Properties > Security. Set permissions to read, write, and execute (full control).
The aspera.conf file is found in the following location:C:\Program Files [(x86)]\Aspera\Enterprise Server\etc\aspera.conf
Below is a typical aspera.conf file. Yours may differ, particularly if you have installed other Aspera products. Modify the following settings, as necessary:
<central_server> <persistent_store>enable</persistent_store> </central_server> ... <user> <name>sharepoint</name> <authorization> <transfer> <in> <value>token</value> </in> <out> <value>token</value> </out> </transfer> <token> <encryption_key>gj5o930t78m34ejme9dx</encryption_key> </token> </authorization> <file_system> <access> <paths> <path> <dir_allowed>true</dir_allowed> </path> </paths> </access> ... </user> ... <server> <server_name>server_ip_or_name</server_name> </server>
After any change to aspera.conf, you must restart the asperacentral and asperanoded services. To restart these services, go to Control Panel > Administrative Tools > Services, right-click Aspera Central and Aspera NodeD, and click Restart.
Enabled settings: connect, mobile, cargo, node, proxy, http_fallback_server, group_configuration, shared_endpoints, desktop_guiIf the list includes connect, you have a Connect Server-enabled license.
You can also check the license from the Connect Server desktop client GUI. Click Tools > License and confirm that the Connect Clients Enabled field is set to Yes.
When you update your Connect Server license (see Updating the Product License), you must reload the asperanoded service afterwards by running the following command:
> "C:\Program Files [(x86)]\Aspera\Enterprise Server\bin\asnodeadmin.exe" --reload
> asnodeadmin.exe -a -u node_sharepoint -p node_password -x sharepoint
> asnodeadmin.exe --reload
> asnodeadmin.exe -l
The output for this command should resemble the following:
List of node user(s): user system/transfer user acls ==================== ======================= ==================== sharepointnode sharepoint  spnode aspera_user_1