Microsoft Office Tutorials and References
In Depth Information
In my case, I plan to give my SharePoint admin account the right to be a shell admin for the whole
farm in order to be able to use it, at will, to do work—making it my super-admin account (see
Chapter 14 for more about how that’s done). Initially, we will be doing a lot of work either in Central
Administration or with STSADM. Later in the topic, as you get the hang of using SharePoint, we
will begin to do more and more with PowerShell.
The following services are created by SharePoint and are generally required for proper
functioning. It might be handy to know what they are before you conduct your first installation.
SPAdminV4 (SharePoint Foundation 2010 Administration) This is the administrative
service for SharePoint. It runs on every SharePoint server locally and is in charge of checking
the configuration database for changes. It keeps track of what server on a server farm is
running what service and is used by SharePoint to access local resources per server. This service
runs as the WSSADMIN process in Task Manager.
SPTimerV4 (SharePoint 2010 Timer) This is the service in charge of actually
triggering and running jobs for SharePoint. Because it uses the farm account identity, it usually
doesn’t have administrative permissions on the local server; however, it does have
ownership permissions to do what it needs to do on both the configuration and content databases.
If it needs to do something administrative on the local machine, it calls on the SPAdminV4
account to do it. This service runs as the OWSTIMER process in Task Manager.
SPSearch4 (SharePoint Foundation Search V4) This is the Search service for SharePoint.
It runs on the SharePoint servers that are running the Search service. This service runs the
mssearch and mssdmn processes in Task Manager.
SPTraceV4 (SharePoint 2010 Tracing) This service also installs on each SharePoint server
locally. It is used for error tracking and analysis and controls the trace logs. This service runs
as the wsstracing process in Task Manager.
SPWriterV4 (SharePoint 2010 VSS Writer) This service integrates with SQL’s VSS writer
service, inherited from SPS 2003, and works with SharePoint’s backup and recovery
capabilities. It makes it possible to use Windows Volume Shadow Copy when doing backups. This
service runs as the SPWRITER process in Task Manager and starts only when necessary. So,
it’s not always running.
SPUserCodeV4 (SharePoint 2010 User Code Host) This service is specifically for
something called sandboxed solutions . Basically for developers, SharePoint now allows certain
controls and limits for running solutions. This service executes code in a “sandbox.” In the
past, solutions could unintentionally take up a lot of server resources because of unhandled
exceptions, abnormal process termination, and the like. So, now solutions that are installed
on the server farm, if they are scoped to be sandboxed solutions, can be managed (limited or
stopped) by this service. This service runs as the SPUCHostService process in Task Manager.
It is not always enabled by default.