Introduction › Server Requirements › Log On Account Conditions

Log On Account Conditions

The Arcserve RHA Engine service must satisfy certain account conditions for successful communication with other components. If these requirements are not met, scenarios may not run. If you lack the permissions required, contact your local IS team.

• It is a member of the Domain Admins group. If the Domain Admins group is not a member of the built-in domain local group Administrators you must use an account that is.
• It is a member of the local computer Administrators Group. If the Domain Admins group is not a member, add the account manually.
• For servers in a workgroup, use the Local System account. If you have used Redirect DNS redirection method in a HA scenario, then use the local administrator account.

  Note: In MS SQL server 2012, Local System (NT AUTHORITY\SYSTEM) is not automatically provisioned in the sysadmin server role. See Microsoft documents on how to provision the sysadmin server role to the NT AUTHORITY\SYSTEM account. Alternatively, use Administrator account to install and log in to the engine service.

• When your SQL servers are in a workgroup, enable "sa" account on Master and Replica server before you run the scenario.

• If the account does not have built-in administrator permissions on all SQL Server instances, add appropriate permissions.
• The account must be able to modify the SQL Master and Replica DNS A-Record.

Important! For a SharePoint Farm deployment, the SharePoint server's Farm Admin account must employ the same log on account conditions.