Share via

Windows SharePoint Services 3.0 farm (Health model)

Applies To: Windows SharePoint Services 3.0


A server farm typically consists of a database server running either Microsoft SQL Server 2005 or Microsoft SQL Server 2000 SP3a or later, and one or more servers running Internet Information Services (IIS) and Windows SharePoint Services 3.0. In this configuration, the front-end servers are configured as Web servers. The Web server role provides Web content and services such as search.


The following is a list of all aspects that are part of this managed entity:

Name Description

Active Directory Integration (Health model)

When Windows SharePoint Services 3.0 is in Active Directory account creation mode, any user added to a site is automatically added to the Active Directory organizational unit identified for use by Windows SharePoint Services 3.0. When running in Active Directory account creation mode, every application pool that contains one or more sites must use an account that has permissions to create, read, and update accounts in the Active Directory organizational unit that the domain administrator configured for Windows SharePoint Services 3.0.

Backup and Restore (Health model)

When you back up a Web site, you back up the content database for the site, including all pages in the site, files in document libraries, files attached to lists, security and permission settings, and feature settings. The backup process creates a single file that contains all of this data. The restore process uses this file to restore the content database for the site. For more information about backup and restore, see Administering backup and recovery for Windows SharePoint Services 3.0 technology ( on TechNet.

Deployment and topology (Health model)

Several features of Microsoft Windows SharePoint Services 3.0 rely on scheduled background processes called timer jobs. Administrators can configure and schedule timer jobs by using Central Administration. When you use the Services on Server page in Central Administration to start or stop a service, a timer job is used to perform this action.

To improve the performance of Windows SharePoint Services 3.0, much of the data in the configuration database is kept in a local file-system cache, called the configuration data cache. Windows SharePoint Services 3.0 uses the timer service to keep this cache synchronized with the configuration database. Alternate access mapping is a feature of Windows SharePoint Services 3.0 that enables administrators to configure a load-balanced system by mapping an incoming URL to alternate URLs used by Windows SharePoint Services. Windows SharePoint Services enables administrators to create new SharePoint sites. Site owners and (depending on the site settings) site visitors can also create subsites.

Diagnostic system (Health model)

The Windows SharePoint Services Tracing (SPTrace) service is used by Windows SharePoint Services 3.0 to manage trace output of the call stack. When trace logging is enabled, administrators can specify the path used to store the trace logs. This log file is reused by many applications that are built on top of Windows SharePoint Services 3.0.

E-mail (Health model)

Microsoft Windows SharePoint Services 3.0 sends alerts and other administration messages by using an SMTP mail server. You can specify which SMTP server to use, and you can set the e-mail address to use for sending alerts and receiving replies for all sites, by using the Outgoing E-Mail Settings page in Central Administration.

Windows SharePoint Services 3.0 health model