Implementation Details

This is Step 1 in my SharePoint 2013 Setup Guide

SharePoint Server

The following table lists and describes the typical service accounts I use in the SharePoint farm. The SharePoint farm account holds the highest privilege in the SharePoint farm. All services that require elevated privilege run as this account. All other services run as one of the remaining lower-privilege accounts.

Service Account Name Description
SP-Farm SharePoint Farm Account Main service account for the SharePoint farm
SP-AppPool SharePoint Application Pool (IIS) Account Default account to run the IIS application pool
SP-Search SharePoint Search Content Access Account Default account for the search service to use to access content
SP-ServiceApp SharePoint Service Application Account Default account used to run service applications and web services application pool

Note: Please see this TechNet article for more details on the service accounts: http://technet.microsoft.com/cc263445

Note: Please see this TechNet article for more details on account permissions: http://technet.microsoft.com/cc678863

The following table lists and describes all of the servers in a sample SharePoint farm.

Server Name Description
SHAREPOINT1 SharePoint server web front-end
SHAREPOINT2 Load-balanced SharePoint server web front-end
SHAREPOINT3 SharePoint application server
SHAREPOINT4 SharePoint application server
OFFICE1 Office Web Apps server – shared with Lync 2013 & Exchange 2013
OFFICE2 Office Web Apps server – shared with Lync 2013 & Exchange 2013
UAG1 Load-balanced Forefront UAG server
UAG2 Load-balanced Forefront UAG server
SQL1 SQL Server – active node for SharePoint farm
SQL2 SQL Server – passive node for SharePoint farm

SQL Server Database List

The following table lists and describes the databases that SharePoint provisions for the farm.

Database Name Description
SP_AppManagementService Apps for SharePoint Management Service
SP_BDCService Business Data Connectivity Service
SP_Config SharePoint farm configuration
SP_Content_CentralAdmin SharePoint Central Administration web application
SP_Content_DefaultWebApp1 SharePoint default web app content database #1
SP_Content_DefaultWebApp2 SharePoint default web app content database #2
SP_Content_DefaultWebApp3 SharePoint default web app content database #3
SP_Content_DefaultWebApp4 SharePoint default web app content database #4
SP_Content_DefaultWebApp5 SharePoint default web app content database #5
SP_MachineTranslationService Machine translation service application
SP_ManagedMetadataService Managed metadata service application
SP_SearchService Search service application
SP_SearchService_AnalyticsReportingStore Search service – analytics
SP_SearchService_CrawlStore Search service – crawl
SP_SearchService_LinkStore Search service – links
SP_SecureStoreService Secure Store (stores encrypted passwords and other strings)
SP_StateService State service (manages session state information)
SP_SubscriptionSettingsService Subscription Settings service application
SP_UsageAndHealthDataCollection Usage and health data collection
SP_UserProfileService_Profile User Profile – Profiles
SP_UserProfileService_Social User Profile – Social
SP_UserProfileService_Sync User Profile – Sync
SP_WordAutomationService Word Automation service application

Content databases store all of the content and site information for a site collection. A SharePoint site collection can live in one and only one content database. Data for site collections cannot span content databases. A site collection may belong to any content database that belongs to the same web application. A web application can have one or more content databases. You may dedicate a content database to a single site collection if you desire, or you can allow multiple site collections to share a content database (the default).

When you provision multiple content databases, SharePoint will use a round-robin method to select which database to associate with a site collection when creating new site collections.

Language Packs

Installing language packs for SharePoint 2013 and Office Web Apps will provide language support for documents in these languages when users use the search engine to search for content stored in these languages or when these users open the document and render it as a web page using Office Web Apps. Installed language packs will also provide the option to create sites in one of the alternate languages and to toggle a site to view menus in an alternate language

Next, you are ready to address your SharePoint 2013 farm’s prerequisites.

Advertisements