Initial deployment administrative and service accounts (SharePoint Foundation 2010)
Published: May 12, 2010
This article provides information about the administrative and service accounts that are required for an initial Microsoft SharePoint Foundation 2010 deployment. Additional accounts and permissions are required to fully implement all aspects of a production farm.
To deploy SharePoint Foundation 2010 on a server farm, you must provide credentials for several different accounts.
The following table describes the accounts that are used to install and configure SharePoint Foundation 2010.
SQL Server service account
The SQL Server service account is used to run SQL Server. It is the service account for the following SQL Server services:
If you do not use the default SQL Server instance, in the Windows Services console, these services will be shown as the following:
Use either a Local System account or a domain user account.
If you plan to back up to or restore from an external resource, permissions to the external resource must be granted to the appropriate account. If you use a domain user account for the SQL Server service account, grant permissions to that domain user account. However, if you use the Network Service or the Local System account, grant permissions to the external resource to the machine account (domain_name\SQL_hostname$).
The instance name is arbitrary and was created when Microsoft SQL Server was installed.
Setup user account
The Setup user account is used to run the following:
If you run Windows PowerShell cmdlets that affect a database, this account must be a member of the db_owner fixed database role for the database.
Server farm account or database access account
The server farm account is used to perform the following tasks:
Additional permissions are automatically granted for the server farm account on Web servers and application servers that are joined to a server farm.
The server farm account is automatically added as a SQL Server login on the computer that runs SQL Server. The account is added to the following SQL Server security roles:
May 12, 2010