Adding an Administrative Account to a Windows Machine

The node machine that you add to IBM Aspera Console as a managed node must have a properly configured administrative account. The following instructions assume that you are logged into the node machine you want to add to Console.
Important: These instructions require that your Aspera service account (svcAspera, by default) be set up as a transfer user on the server. If the node's transfer product was installed by upgrading from a previous installation of IBM Aspera Enterprise Server or IBM Aspera Connect Server, a transfer user corresponding to the service account is created automatically. However, if it was 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 GUI. For more information on creating the transfer user, see the IBM Aspera Enterprise Server Admin Guide.
  1. Configure the node machine's firewall as described in System and Firewall Requirements.
  2. Configure the user's docroot settings.
    Click the Docroot tab. Select Override for Absolute Path. Leave the field blank to allow the user to override default docroots under the node- or group-level setting.
  3. Add a node user associated with the svcAspera system user.
    Console authenticates to the node machine using a Node API username and password. The following command creates a Node API user and password and associates it with the system user you created.
    > cd C:\Program Files (x86)\Aspera\Enterprise Server\bin
    > asnodeadmin.exe -a -u node_api_username -p node_api_passwd -x svcAspera --acl-set impersonation
    Adding, modifying, or deleting a node-user triggers automatic reloading of the user database and the node's configuration and license files. For more information on the Node API, see your transfer server's administrator guide.
    Note: If the transfer server on your node is running a transfer product before 3.5.5, the node is not recent enough to support setting the "impersonation" ACL. You must upgrade the node to 3.5.5+ or obtain a patch from Aspera Support.
  4. Verify that you correctly added the node user.
    > asnodeadmin.exe -l
    The output should look like the following:
                    user       system/transfer user                    acls
    ====================    =======================    ====================
               node_user                  svcAspera          [impersonation]
  5. Restart the Aspera Node API and Aspera Central services to load changed settings.
    Go to Control Panel > Administrative Tools > Services, right-click Aspera NodeD and select Restart. Do the same for Aspera Central.
Now that your node machine is configured for use with Console, open the Console interface and create a new managed node following the instructions in Creating a Managed Node in Console.