How to access repositories on non-trusted domain servers? How is Instance Configuration set during install to allow the LiteSpeedLocal and LiteSpeedCentral communicate when they reside in different domains?
WORKAROUND - STEPS USED TO SETUP REPORTING TO CENTRAL REPOSITORY:
1. Account that you define as Service Account is used for LiteSpeed Activity Service.This account must have access to the Local registry.
2.
you can specify account used for access to the Central repository on the Central Repository page.
If you select Windows Auth, the activity service will access the repository under its Service Account and this Service Account must have access to the repository as detailed below.
If you choose SQL authentication,the activity service will access the repository under thespecified SQL account and this account must have access to the repository as detailed below.
Please note that if SQL authentication is used the activity service account type does not matter.
Details of rights needed to update the repositories: (this information can also be used to further define the SQL rights if a customer decides not to use the “sysadmin” role.)
Example scenarios:
Computers are in a trusted domain.
Computers are in a trusted domain.
1. Domain service account with admin rights to both servers and repositories.
Computers are not in a trusted domain.
Computers are not in a trusted domain.
1. Local windows account with admin rights to both servers and repositories.
