How to check an Enterprise Server, Point-to-Point, Client, or Connect Server installation for problems on Windows

by Brian Din

Summary

This article describes how to use asuser-check.cmd, a tool that checks some of the essentials for Enterprise Server, Connect Server, Point-to-Point, and Client 2.6.0 or higher for Windows to operate correctly.

This tool checks:

  • That the service account running each Aspera service has the necessary privileges granted and is part of the correct local administrators group. The services checked include the asperasync, sshd, asperacentral, and asperahttpd services, depending on the product installed.

  • That the sshd service has the proper file permissions to the key files. The list of files includes \etc*key*, \etc\passwd, \etc\group, \etc\docroot, and \var\log\sshd.log.

Location of this tool:

  • asuser-check.cmd is located in the product's bin directory at C:\Program Files (x86)\Aspera\<product>\bin

  • This tool should always be run from the bin directory.

Environment

  • Product: Enterprise Server, Connect Server, Point to Point, Aspera Client
  • Versions: 2.6.0 or higher
  • Operating System: Windows

 

Usage

The tool can be run with the following syntax:

asuser-check.cmd [ES|P2P|Client] [LocalAdministratorGroup]
  • By default, the script will run a check for Enterprise Server with the user assumed to be in the Administrators group

  • In order to only check a P2P or Client installation, specify "P2P" or "Client" as the first argument.

  • If the service account is not in the "Administrators" group, specify its group name as the second argument.

Examples

# asuser-check.cmd Client Administratores 
# asuser-check.cmd P2P

How to run

  1. Start a Command Prompt
  2. Change directory to C:\Program Files (x86)\Aspera\<product>\bin
  3. Run asuser-check.cmd as above
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk