Migrating Watch Services on Upgrade

As of Connect Server version
3.7.1, Aspera Watches and Watchfolders are managed by the Aspera Watch Service Manager
(asperarund), which allows easy management of the asperawatchfolderd and
asperawatchd services. Most importantly, asperarund allows admins to
start services under different users without having to switch between the different
contexts.

If you upgraded from Connect Server
version 3.6.1, and you had the asperawatchd and asperawatchfolderd
services enabled and configured, you must manually migrate any services that are run
by a user other than svcAspera.

Scenario 1: User is "svcAspera"

If the user is svcAspera, the installer first stops the
asperawatchd and asperawatchfolderd services and removes them
from running services. The installer restarts the services using the following
command:

>asperawatchd --user svcAspera>asperawachfolderd --user svcAspera

Windows requires a password when running services as other users.
Enter the password when prompted.

Scenario 2: User is Not "svcAspera"

If the user is not svcAspera, the installer does not automatically
migrate the services. You must manually start the service under the user that was
running the asperawatchd and asperawatchfolderd services. Before
you perform the migration steps, confirm or set the following for the user running
the services:

a docroot in aspera.conf.

permissions to write to the default log directory if no directory is specified.