Microsoft Windows SharePoint Services uses a database to store configuration and site mapping information for your server computer, the virtual servers (virtual server: A virtual computer that resides on an HTTP server but appears to the user as a separate HTTP server. Several virtual servers can reside on one computer. Each virtual server can have its own domain name and IP address.) on your server computer, and for servers in a server farm (server farm: A centralized grouping of network servers maintained by an enterprise or, often, an Internet service provider (ISP). A server farm provides a network with load balancing, scalability, and fault tolerance.). This database is called the configuration database. You need one configuration database for your server farm, whether your server farm is one server computer with everything on it, or several server computers.
If you install Windows SharePoint Services on a single server using Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE), the configuration database is created for you.
Installing Windows SharePoint Services in a server farm environment, or on a server running Microsoft SQL Server, does not create the configuration database. The installation ends by opening the Configure Administrative Virtual Server page. You can use this page to configure the SharePoint Central Administration virtual server and select the configuration database. You may also use the command line utility stsadm.exe to perform these tasks.
Note Microsoft Windows Server 2003 R2 adds the Windows SharePoint Services role to the Configure Your Server Wizard and Manage Your Server. Installing Windows SharePoint Services by using either method will perform a typical installation. To perform a server farm installation you must use the Windows Components Wizard.
Using HTML Administration to Create or Connect to a Configuration Database
When you install Windows SharePoint Services without installing WMSDE, the setup program ends by opening Central Administration and displaying a page where you specify the application pool (application pool: In Internet Information Services (IIS), a group of one or more URLs served by a worker process.) to use for administration tasks. After you specify the application pool, the security account and NTLM or Kerberos authentication for the Security Configuration, you are taken to the Set Configuration Database Server page where you specify whether to use existing domain accounts or use Active Directory directory service to create user accounts, and create the configuration database. For more information about account types, see "Managing Users and Cross-Site Groups" in the Windows SharePoint Services Administrator's Guide.
Create a configuration database after setting up Windows SharePoint Services
When Setup finishes, you are taken to the Configure Administrative Virtual Server page.
- In the Application Pool section, select Use an existing application pool or Create a new application pool.
- If you selected Use an existing application pool, select the application pool to use.
- If you selected Create a new application pool, under Application pool name, type a name for the application pool, and under Select a security account for this application pool, select either predefined or configurable.
- Predefined security accounts (network service, local service, local system) are configured to work with Kerberos authentication.
- If you select Configurable, and the Security Configuration is set to Kerberos authentication, you must configure the account as a Service Principal Name (SPN). Be sure to specify an account that is a member of the Security Administrators and Database Creators roles for the SQL Server database. For more information, refer to the Microsoft Knowledge base article 832769: How to configure a Windows SharePoint Services virtual server to use Kerberos authentication.
- It is recommended that you use a dedicated account for this account, rather than a user's logon account. Also, it is recommended that you use the same account for each application pool that hosts the same content.
- Once the above steps have been completed, click OK.
You will see the Application Pool Changed page which prompts you to restart IIS.
- To restart Internet Information Services (IIS) from a command prompt, type iisreset which will stop and restart IIS.
- After IIS has been restarted, on the Application Pool Changed page, click OK.
- On the Set Configuration Database Server page, in the Configuration Database section, enter the server name and database name to use.
- Under Database connection type, select Use Windows authentication (more secure, recommended) or Use SQL authentication (less secure).
- If you selected Use SQL authentication (less secure), you must also type the database account user name and password.
- If you selected Use Windows authentication, select one of the following options:
- If the user accounts you want to use for your site already exist in the Active Directory directory service, select Users already have domain accounts. Do not create active directory accounts.
- If you want Windows SharePoint Services to automatically create user accounts in the Active Directory directory service, select Automatically create active directory accounts for users of this site.
Note For Windows SharePoint Services to automatically create accounts, the application pools must have proper permissions on the Active Directory directory service. For more information, see “Preparing the Domain Controller” in Separate Active Directory Directory Service Organization Unit Deployment.
- If you selected Automatically create active directory accounts for users of this site, you must fill in the Active Directory Domain and Organization Unit information.
- Click OK.
If you already have a configuration database for your server farm, you can use the Set Configuration Database Server page to connect to the existing configuration database. You must connect to the configuration database whenever you add a server to a server farm, and before you can extend (extend: To apply Windows SharePoint Services to a virtual server.) any virtual servers on that server.
Connect to a configuration database
- Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
- Under Server Configuration, click Set configuration database server.
- In the Configuration Database section, enter the server name and database name for the existing configuration database.
- Under Database connection type, select Use Windows authentication (recommended security level) or Use SQL authentication (less secure).
- If you selected Use SQL authentication (less secure), type the database account user name and password.
- Select the Connect to existing configuration database check box.
- Click OK.
Using the Command Line to Create or Connect to a Configuration Database
You use the same operation on the command line to create or connect to a configuration database. The setconfigdb operation allows you to perform either action, depending on the parameters you include. The setconfigdb operation takes the following required parameters: databaseserver (ds), databaseuser (du), and databasepassword (dp). (Note that the -du and -dp parameters are only required if you are using SQL Server authentication; they are not used with Windows authentication.) In addition, you can use the following optional parameters: connect, databasename (dn), and hh, which specifies that you are in server farm mode.
To create a new configuration database and specify a name for the database, you would use the following syntax:
stsadm -o setconfigdb -ds <database server> -dn <database name>
-du <database user> -dp <database user password> -hh
For example, to create a new configuration database called "config1" at http://mydomain, on the Sql_02 database server, using Windows authentication, you would type:
stsadm -o setconfigdb -ds mydomain -dn config1
To connect to an existing configuration database, you would use syntax similar to the following:
stsadm -o setconfigdb -connect -ds <database server>
-dn <database name> -du <database user>
-dp <database user password>
After you have set up the configuration database, you can begin extending virtual servers. For more information, see Extending Virtual Servers.
For more information about using the setconfigdb operation, see Command-Line Operations.