Microsoft Office Tutorials and References
In Depth Information
As you can see in Figure 2.40, the administration service, which is critical for a server farm,
isn’t even enabled by default on a single-server install (which can cause issues later when you
are trying to do backups to an off-server location). Also note that all of the services are using
local service, local system, or network system accounts for their logon identities.
FIGURE 2.40
Windows
SharePoint Services in
the console
Just below the SharePoint services (you may need to scroll a little), you’ll also find the five
SQL services listed: SQL Server , SQL Server Agent, SQL Server Browser, and SQL Server
VSS Writer. There might also be a SQL Active Directory Helper if your server is member of a
Windows domain.
The most significant SQL service is, of course, the SQL Server service, which is started (which
means it’s running) and is using the local server’s Network Services account. As you can see, the
other services (variously set to disabled or automatic depending on whether they’re needed) also
use local service, local system, or network service accounts. There are no nonlocal accounts in sight.
After confirming that the SharePoint and SQL server services are listed, let’s move on to the
rest of the SharePoint components.
Knowing what services are running that relate to SharePoint, knowing that it’s OK if some
are not always on, knowing which ones must be running, and knowing what their service
accounts are all help you really understand the underpinnings of the product.
Feel free to close out of the Services console.
Confirming IIS Web Sites and Application Pools
When the prerequisites were installed, IIS was enabled, and you checked the console to see what
was available by default.
Now that SharePoint has installed, that has changed. If you open the IIS console (not the one
for IIS 6.0), open the icon for the server (double-click or click the plus sign), and then open the
Search JabSto ::




Custom Search