This setup guide walks you through the steps to install and configure a SharePoint 2013 farm and an Office Web Apps 2013 farm.

I have included a range of topics from preparing for the farm deployment through the deployment itself, including the following topics:

A checklist I use to help organize and prepare for the farm build
All the implementation details I like to decide on before the build
The prerequisites to prepare for a SharePoint farm build
The install and configuration steps for SharePoint
The Windows Firewall rules to enable intra-farm communication
The install and configuration for Office Web Apps
A checklist I use to guide next steps once the farm is deployed

Preparation/Preflight Checklist

Order SSL certificate for URL domain(s)
Procure and configure hardware load balancing (if load balancing)
Provision virtual servers – Windows 2012 (preferred) or Windows 2008 R2 SP1+
Install and configure Forefront UAG
Install SSL certificate on servers
Create DNS entries for domains to resolve to Forefront/load balancer
Copy setup media to servers

Copy SharePoint 2013 setup files to SharePoint servers
Copy SharePoint 2013 Language Packs to SharePoint servers
Copy KB2554876, KB2708075, KB2759112, KB2765317 to SharePoint servers
Copy Office Web Apps 2013 setup files to Office Web Apps servers
Copy Office Web Apps Language Packs to Office Web Apps servers

Provision SQL Server 2012 (preferred) or SQL Server 2008 R2
Provision service accounts in Active Directory and grant permissions

Grant SP Farm service account local Administrator on SharePoint servers
Grant SP Farm “Replicate Directory Changes” AD permissions (see note)
Grant SP Farm SQL Server permissions – DB Creator and Security Admin

Identify SharePoint 2013 and Office Web Apps 2013 product keys
Identify outbound e-mail server details

An SMTP address for SharePoint outbound email (for alerts, etc.)
An e-mail address for the “From” or “Reply To” address in system e-mails

Note: Please see this TechNet article for the steps on how to grant AD permissions: http://technet.microsoft.com/hh296982

Farm Implementation Details and Prerequisites

Install and Configure

Next Steps Checklist

SQL DBA to configure database backup schedule
Networking/Infrastructure resource configure routing and load-balancing rules
System Center administrator to configure system monitoring
Operations team to plan for regular patching and maintenance
Build an FAQ community support SharePoint site to log common end-user questions
Document SharePoint support information and resources

Implementation Details

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.

SharePoint Farm Prerequisites

Before attempting the SharePoint 2013 software installation on any servers, complete the prerequisites listed in the following sections on each server to prepare the environment.

Minimum Hardware and Software Requirements

All servers, including the SQL Server, in a SharePoint farm require 64-bit processors and a 64-bit operating system. The minimum operating system that SharePoint supports is Windows Server 2008 R2 with SP1 or above. SharePoint also supports Windows Server 2012. The minimum database server that SharePoint supports is SQL Server 2008 R2. SharePoint also supports SQL Server 2012.

SharePoint is a memory intensive application more than anything else. Hence, the officially Microsoft supported minimum hardware requirements for a SharePoint server is a server with 8GB of RAM. However, Microsoft’s recommended minimum is 12GB of RAM. SharePoint also depends heavily on the server’s processor and requires a minimum of 4 CPUs.

Microsoft recommends a minimum of 80GB of disk space for the system drive (C:). I recommend adding a data drive (D:) that you will use to store the SharePoint log files as well as any SharePoint index files for search. These files can quickly grow and consume significant disk space, and as such, I prefer to separate them to avoid starving the system drive of available space and affecting system availability.

Microsoft does not support SharePoint farms with servers distributed across multiple data centres. Every SharePoint server and SQL Server that belongs to the same SharePoint farm must be located in the same data centre. This is due to the amount of intra-farm communications between servers and the supported network latency.

Note: For details on the minimum supported requirements, please see this TechNet article:http://technet.microsoft.com/cc262485

SharePoint Server Prerequisites

Before you can install SharePoint 2013, there are a number of prerequisite updates and server configurations you will need to complete in order to prepare the server to host SharePoint. For the majority of the prerequisites, Microsoft has provided a tool and they have included it with the SharePoint 2013 installation media on the DVD image.

Add the SharePoint farm service account to the local administrator group on the server. This account will require local administrator access to administer select services for the SharePoint farm, most notably the SharePoint User Profile Synchronization service application.

Before you run the Microsoft SharePoint Products Preparation Tool, check for server updates on Microsoft Update and install any available updates to ensure the server is up-to-date.

Once you have finished applying the available updates and patches to the server, you are ready to run the Microsoft SharePoint Products Preparation Tool. This tool will install and configure the following:

Web Server (IIS) role
Application Server role
Microsoft .NET Framework version 4.5
SQL Server 2008 R2 SP1 Native Client
Microsoft WCF Data Services 5.0
Microsoft Information Protection and Control Client (MSIPC)
Microsoft Sync Framework Runtime v1.0 SP1 (x64)
Windows Management Framework 3.0 which includes Windows PowerShell 3.0
Windows Identity Foundation (WIF) 1.0 and Microsoft Identity Extensions (previously named WIF 1.1)
Windows Server AppFabric
Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)

To run the Microsoft SharePoint Products Preparation Tool and install the prerequisites, run the prerequisiteinstaller.exeprogram included with the SharePoint 2013 setup media.

Important: The Microsoft SharePoint Products Preparation Tool will require internet access.

After you complete the Microsoft SharePoint Products Preparation Tool, you must also install the following Microsoft updates:

After applying all the prerequisites, you can check for updates on Microsoft Update once more to ensure you patch the newly added prerequisite components with any available updates.

Note: For more information on the SharePoint 2013 prerequisites, please see this TechNet article: http://technet.microsoft.com/ff686793

SQL Server Prerequisites

SharePoint does not require any special SQL Server setup. A SharePoint farm consumes its database services from a SQL Server using standard data connection strings and SQL stored procedures.

The only permissions that SharePoint will need a DBA to explicitly set are the SQL Server DB Creator and Security Admin server permissions for the SharePoint Farm account. SharePoint will use these permissions to provision each of its databases and it will assign the SharePoint Farm account as the DBO for those databases. For all other accounts, SharePoint will assign any database permissions they require using the least privilege principle.

Note: For more information on configuring SQL Server security for SharePoint 2013, please see this TechNet article: http://technet.microsoft.com/ff607733

Next, you are ready to begin installing SharePoint on your servers.

SharePoint 2013 Server Installation

To start, logon to the server using the SharePoint farm account. Running the install and configuration wizard under this account will ensure the process provisions databases on SQL Server with the main SharePoint farm account as the database DBO.

Run the SharePoint 2013 setup media.
On the SharePoint 2013 Start page, click Install SharePoint Server.
On the Enter Your Product Key tab, enter your product key, and then click Continue.
On the Read the Microsoft Software License Termstab, review the terms, select the “I accept the terms of this agreement” check box, and then click Continue.
On the Choose the installation you want tab, clickServer Farm.
On the Server Type tab, click Complete.
On the File Location tab, accept the default location or change the installation path, and then click Install Now.
When the Setup program is finished, a dialog box prompts you to complete the configuration of your server. Clear the Run the SharePoint Products and Technologies Configuration Wizard now check box.
Click Close to finish Setup.

After installing the SharePoint 2013 server software, you are ready to install any additional add-ins and updates. You can also install any language packs your farm requires. To install the language packs, run the setup media for each of the language packs you want in the farm.

If applicable, install the latest service pack Microsoft has released for SharePoint 2013 and then apply the latest service pack Microsoft has released for SharePoint 2013 language packs.

Finally, check for updates on Microsoft Update in the server’s control panel.

Next, you are ready to configure your farm

SharePoint 2013 Farm Configuration

Before you start, verify that you are logged on and running as the SharePoint farm account.

Important: The initial server that you run the wizard on to create a new farm will be the default server name to access the SharePoint Central Administration site. For example, if the initial server is SHAREPOINT1, then Central Admin will be http://sharepoint1:15000

If you are ready, run the SharePoint 2013 Products Configuration Wizard located on the Windows Start menu and follow these steps to create a farm:

On the Welcome to SharePoint Products page, clickNext.
In the dialog box that notifies you that some services might have to be restarted during configuration, clickYes.
On the Connect to a server farm page, click Create a new server farm, and then click Next.
On the Specify Configuration Database Settings page, do the following:

In the Database server box, type the name of the computer that is running SQL Server.
In the Database name box, type a name for your configuration database, or use the default database name.
In the Username box, type the user name of the SharePoint farm account in DOMAIN\user name format.
In the Password box, type the service account’s password.

Click Next.
On the Specify Farm Security Settings page, type a passphrase, and then click Next.
Note: Although a passphrase resembles a password, it is usually longer to improve security. It is used to encrypt credentials of accounts that are registered in SharePoint 2013. Ensure that the passphrase contains at least eight characters and at least three of: uppercase letters; lowercase letters; numbers; non-alphabetic characters.
On the Configure SharePoint Central Administration Web Application page, do the following:

Select the Specify port number check box and type15000 as the port number for the SharePoint Central Administration web application.
Click either NTLM or Negotiate (Kerberos).
Specify the port for the Central Administration Web Application

Click Next.
On the Completing the SharePoint Products Configuration Wizard page, click Next.
On the Configuration Successful page, click Finish.
The Central Administration website will open in a new browser window. On the Help Make SharePoint Better page, click No, I don’t wish to participate and then click OK.
On the Initial Farm Configuration Wizard page, clickCancel.

The SharePoint Configuration Wizard will have provisioned a database for the Central Administration site using a system generated database name. You can rename this database by dismounting it from the SharePoint web application, renaming it in SQL Server Management Studio, and then mounting it back to the SharePoint Central Administration web application. The following PowerShell provides the steps on this process.

$db = Get-SPContentDatabase –WebApplication “http://sharepoint1:15000”
Dismount-SPContentDatabase $db
## Rename the database in SQL Server Management Studio
Mount-SPContentDatabase "[Name]" -DatabaseServer "[Server]" –WebApplication “[Web App]”

At this point, verify that all of the farm’s database names match your desired naming convention.

Now you have created the SharePoint farm. Next, use PowerShell to provision the SharePoint Usage and Health Data Collection service application in order to name the database according to the preferred naming convention.

$UsageService = Get-SPUsageService
New-SPUsageApplication –Name “[Name]” -DatabaseServer “[Server]” -DatabaseName “[DB Name]” –UsageService $UsageService

Next, use PowerShell to provision the SharePoint State service application in order to name the database according to the preferred naming convention.

New-SPStateServiceDatabase -Name "SP_StateService" | New-SPStateServiceApplication -Name "State Service" | New-SPStateServiceApplicationProxy -DefaultProxyGroup

Next, use PowerShell to provision the SharePoint Subscription Settings service application in order to name the database according to the preferred naming convention.

$Account = New-SPManagedAccount

$AppPool = New-SPServiceApplicationPool –Name “SP_ServiceApplicationsDefaultAppPool” -Account $Account
$App = New-SPSubscriptionSettingsServiceApplication –ApplicationPool $AppPool –Name “Subscription Settings Service” –DatabaseName “SP_SubscriptionSettingsService”
New-SPSubscriptionSettingsServiceApplicationProxy –ServiceApplication $App

Next, use PowerShell to provision the SharePoint Search service application in order to name the database according to the preferred naming convention.

$AppPool = Get-SPServiceApplicationPool –Identity “SP_ServiceApplicationsDefaultAppPool”
$ServerName = (Get-ChildItem env:computername).Value
$ServiceAppName = “Search Service”
$DatabaseName = “SP_SearchService”
Start-SPEnterpriseSearchServiceInstance $ServerName
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $ServerName

$App = New-SPEnterpriseSearchServiceApplication -Name $ServiceAppName -ApplicationPool $AppPool -DatabaseName $DatabaseName
New-SPEnterpriseSearchServiceApplicationProxy -Name “$ServiceAppName Proxy” -SearchApplication $App

$clone = $App.ActiveTopology.Clone()
$Instance = Get-SPEnterpriseSearchServiceInstance
New-SPEnterpriseSearchAdminComponent –SearchTopology $clone -SearchServiceInstance $Instance
New-SPEnterpriseSearchContentProcessingComponent –SearchTopology $clone -SearchServiceInstance $Instance
New-SPEnterpriseSearchAnalyticsProcessingComponent –SearchTopology $clone -SearchServiceInstance $Instance
New-SPEnterpriseSearchCrawlComponent –SearchTopology $clone -SearchServiceInstance $Instance
New-SPEnterpriseSearchIndexComponent –SearchTopology $clone -SearchServiceInstance $Instance
New-SPEnterpriseSearchQueryProcessingComponent –SearchTopology $clone -SearchServiceInstance $Instance
$clone.Activate()

Next, configure the Outgoing e-mail server information by opening SharePoint Central Administration and following these steps:

In Central Administration, click System Settings.
On the System Settings page, in the E-Mail and Text Messages (SMS) section, click Configure outgoing e-mail settings.
On the Outgoing E-Mail Settings page, in the Mail Settings section, type the SMTP server name for outgoing e-mail (e.g. “mail.contoso.com”) in theOutbound SMTP server box.
In the From address box, type the e-mail address as you want it to be displayed to e-mail recipients, such as “sharepoint@contoso.com”
In the Reply-to address box, type the e-mail address to which you want e-mail recipients to reply to, if desired.
In the Character set list, select the character set that is appropriate for your language.
Click OK.
The outgoing e-mail settings specifying the SMTP server and from address

Creating a Web Application

Once you have created a farm, you can provision a web application to host SharePoint sites. Create a new web application by opening SharePoint Central Administration and following these steps:

On the Central Administration home page, clickApplication Management.
On the Application Management page, in the Web Applications section, click Manage web applications.
In the Contribute group of the ribbon, click New.
On the Create New Web Application page, in the IIS Web Site section, configure the settings for your new web application.
Create a new web application and specify its name
In the Security Configuration section, choose whether or not to Allow Anonymous access and whether or not to Use Secure Sockets Layer (SSL).
In the Claims Authentication Types section, select the authentication method that you want to use for the web application.
Note: Office Web Apps will require the Claims Authentication type instead of Classic.
In the Sign In Page URL section, choose the Default Sign In Page URL.
In the Public URL section, type the URL for the domain name for all sites that users will access in this web application.
In the Application Pool section, select the application pool if available or create a new one.
In the Database Name and Authentication section, choose the database server, database name, and authentication method for your new web application.
If you use database mirroring, in the Failover Serversection, in the Failover Database Server box, type the name of a specific failover database server that you want to associate with a content database.
In the Service Application Connections section, in the drop-down menu, click default.
In the Customer Experience Improvement Programsection, click Yes or No.
Click OK to create the new web application.

Note: For more information on creating web applications, please see this TechNet article:http://technet.microsoft.com/cc261875

After you create a web application, you might want to add additional content databases to distribute the site collections across rather than storing the content in a single content database. You can access the Content Databases page by clicking on the Application Management link in SharePoint Central Administration, and then clicking on the Manage Content Databases link.

The Manage Content Databases page

On this page, you can provision a new content database and add it to the web application by clicking on the Add a content database link at the top of the content database list. You can select which web application you wish to add a content database for by selecting the desired web application from the dropdown list in the upper right area.

Unless you explicitly specify a content database for a site collection by creating the site collection by using PowerShell, SharePoint will allocate site collections to content databases in a round-robin fashion. SharePoint will alternate between available content databases that have not yet reached the maximum number of site collections you set for a content database.

You can click on the name of an individual content database to view additional details about the database and to change any of its settings. The following lists and describes the main properties to set for a content database:

Database Read-Only: This option specifies whether the content database is in read-only mode or not. You can set a content database to read-only mode by clicking on the database name, and then modifying the Database Read-Only property setting.
Note: By setting a content database in read-only mode, users can continue to access their sites and the content stored within them, but they cannot apply edits or add any new content. This is a useful option when you want to perform certain types of maintenance.
Current Number of Site Collections: This value displays the number of site collections currently provisioned in the content database.
Site Collection Level Warning: This property sets the warning level for SharePoint to write a warning to the Windows Event when the number of site collections reaches the threshold.
Maximum Number of Site Collections: This property sets the maximum number of site collections for a content database. When this property is equal to or less than the current number of site collections property value, then SharePoint will not provision any more site collections in the content database. Setting the value to a lower number will not affect existing sites, and instead will only prevent SharePoint from provisioning future site collections in the content database.

If you want to remove a content database from a web application, click on the content database name, and then select Remove content database. This will not delete the content database in SQL Server, but will remove its association from the SharePoint web application.

You can move a content database from one SQL Server instance to another if you want to scale out your data tier. One option to perform this move is to remove the content database form the SharePoint web application, detach the content database in SQL Server, copy and attach it to the new SQL Server, and then add the content database back to the web application by specifying the new SQL Server name and the existing content database name.

The detach database option in SQL Server Management Studio

Creating the Managed Metadata Service Application

The Managed Metadata Service publishes a term store to store a collection of terms that you can use to organize and classify content. Term sets within a term store can organize a hierarchy of terms, which can serve as the bases for your enterprise taxonomy or controlled vocabulary. A term set can also capture a flat, non-hierarchical list of terms, which you can use as a predefine list of options for a field or as a list that users can add to, such as a list of keywords in a folksonomy.

In the following steps, I will walk you through the process for creating a Managed Metadata Service. Begin by opening SharePoint Central Administration.

Click on the Manage service applications link under the Application Management menu to navigate to the Manage Service Applications page. In the ribbon, on the Service Applications tab, click on the New dropdown button, and click on the Managed Metadata service application.

Create a new Managed Metadata Service Application

In the Create New Managed Metadata Service Application modal window, enter the application name and database information. The following figure provides an example of the Create New Managed Metadata Service Application modal window.

Enter the Managed Metadata Service Application details

Click the OK button to create the Managed Metadata service application.

With the Managed Metadata service application provisioned, you can begin to add metadata terms. First you will need to create a Term Group to organize and contain the Term Sets, and then within each Term Group, you can create a Term Set. Within each Term Set you can create a hierarchy of Terms.

SharePoint uses the Terms as metadata tags to associate with documents and other property fields. You can associate a Term Set to a field to limit or focus the options available to tag an item.

Note: For more information on Managed Metadata and how to plan for and configure an enterprise taxonomy, please see this MSDN article: http://msdn.microsoft.com/jj163949

Creating the User Profile Service Application

The User Profile service application stores information about users in a central location. It makes this information available within a SharePoint farm to support social computing features such as profile sites, tagging, microblogging, and the like.

Before you begin to create a User Profile service application, create a My Site host site collection and add a managed path to the web application that you wish to provision personal sites under. You will also need to provision a Managed Metadata service application instance as a prerequisite to the User Profile service application by following the steps I provided in the previous section. Complete the following steps to provision a User Profile service application.

Click on the Manage services on server link located in the System Settings menu group to navigate to theServices on Server page.
Click the Start link for the User Profile Service.
Click on the Application Management category link on the left Central Administration menu, and then click on the Manage service applications link located in theService Applications category to navigate to theManage Service Applications page.
In the ribbon in the Create group, click the Newdropdown and select the User Profile Service Application.

On the Create New User Profile Service Applicationmodal window, fill in the information for name, application pool, database, and My Site information. The following figure provides an example of The New User Profile Service Application modal window.
Enter the details for the User Profile Service Application

Click the Create button at the bottom of the modal window.
Return to the Services on Server page that you navigated to in Step 1.
Click the Start link for the User Profile Synchronization Service.
On the User Profile Synchronization Service page, select the User Profile service application and enter the service account password. The following figure provides an example of the User Profile Synchronization Service page.
Enter the account information for the synchronization service
Click the OK button.

Notice the layout of the Mange Profile Service administration page, with the administration menu in the middle and statistical information along the right column. The following figure provides an example of the Manage Profile Service administration page.

The User Profile Service settings page

Click the Manage User Properties link in the Peoplesection.
On the Manage User Properties page, edit the Mapped Attribute for each of these properties:

Picture
Direction: Export
Attribute: thumbnailPhoto
Description: Upload a picture to help others easily recognize you at meetings and events. Your picture will show up for contacts in Outlook and Lync as well as in different parts of SharePoint, but it may take a day or so to sync your changes with all of these systems.
SIP Address
Direction: Import
Attribute: msRTCSIP-PrimaryUserAddress
Work Email
Direction: Import
Attribute: mail

Return to the Manage Profile Service administration page.
Click on the Configure Synchronization Connectionslink under the Synchronization category.
On the Synchronization Connections page, click on theCreate New Connection button. Enter a Connection Name and select a Connection Type from the dropdown box. Enter the authentication information and remaining connection information. The following figure provides an example of the Add new synchronization connection page.
Add a user profile synchronization connection
Click the OK button at the bottom of the page.
Return to the Manage Profile Service administration page and click the Start Profile Synchronization link under the Synchronization category.
On the Start Profile Synchronization page, select between an incremental and full synchronization.
Click the OK button to begin importing and synchronizing profiles.

Configure Apps for SharePoint

In the Application Management section, click theManage service applications link.
On ribbon in the Service Applications tab, click theNew button and click App Management Service on the new service application menu.
Provide the details for the app management service and click OK.
On the left navigation menu, click System Settings and then click Services on Server.
Start the App Management Service and the Microsoft SharePoint Foundation Subscription Settings Service.
On the left navigation menu, click Apps.
On the Apps page, click Manage App Catalog.
Click Create a new app catalog site.
Click OK.
Provide the site information for the organization’s app catalog.
Click OK.
Click Configure App URLs.
Type the desired App domain and App prefix.
Click OK.

Finalizing the Server Configuration

Finally, to finish the basic setup of the SharePoint farm, start and stop the services for the farm. You can manage the services by clicking on Services on Server under the System Settings section in SharePoint Central Administration.

Note: For additional farm configuration steps for individual service applications you wish to include in the farm, please see this TechNet article: http://technet.microsoft.com/ee836142

Joining Additional SharePoint Servers to the Farm

After you create the new farm on the initial server, you can join additional servers to the farm by following a similar process by running the SharePoint Products and Technologies Configuration Wizard on the server. The only difference for this option is when the wizard prompts you, select to join an existing farm rather than create a new farm. Follow the wizard steps and provide the required farm information to join the server to the farm.

Note: For more information on adding a server to a farm, please see this TechNet article: http://technet.microsoft.com/cc261752

The following figure provides a screenshot of the SharePoint Products and Technologies Configuration Wizard at the step where you can select to join and existing farm.

The join an existing farm option on the SharePoint Configuration Wizard

The following figure provides a screenshot of the SharePoint Products and Technologies Configuration Wizard at the step where you can specify the database server and the SharePoint configuration database to join.

Specify the database server and name on the SharePoint Configuration Wizard

Note: You will follow this same process if you want to add an additional server and scale the SharePoint farm at a later time as well.

After you have added all of the servers to the farm, you can distribute the services that run on each server to allocate and distribute the load. You can manage the services by clicking Services on Server under the System Settings section in SharePoint Central Administration. You can switch servers by clicking the server name dropdown in the upper-left area of this page.

At the top of the table listing the services, click the Server dropdown and click Change Server, as illustrated in the following figure.

The Change Server option on the Services on Server page

Start and stop the services to match how you wish to allocate them for each server in the farm.

At this point, you should have provisioned all of the service applications and services that you desire in the farm. You should also have provisioned all of the initial databases that you desire in the farm and their naming convention should roughly resemble the following screenshot.

A sample SharePoint database list in SQL Server Management Studio

You can run a SQL script on the SQL Server to update the recovery model if you desire. The following script will change all of the SharePoint databases that have the “SP_” prefix and set their recovery model to Full.

EXEC sp_MSforeachdb 'IF ''?'' LIKE ''SP_%'' ALTER DATABASE ? SET RECOVERY FULL;'

Alternatively, you can set the recovery model through the database properties on the Options page.

Database options settings to change the recovery mode to Full

Configuring the Windows Firewall for SharePoint Farm Traffic

On each SharePoint 2013 Server, you will need to set a firewall rule to allow SharePoint intra-farm traffic and HTTP/HTTPS traffic. Alternatively, you can disable the Windows Firewall if you choose and if you have another firewall solution.

You can set the Windows Firewall rules by navigating to the Control Panel, then click System and Security, then click Windows Firewall, and finally click Advanced settings. In the Inbound Rules area, ensure that the server allows connections on port 80 (HTTP) and port 443 (HTTPS). Add the ports listed in the table below for the SharePoint 2013 inter-farm communication by following these steps:

In the Windows Firewall with Advanced Security window, click Inbound Rules.
In the Actions panel, click New rule…
In the New Inbound Rule Wizard window, select Portsas the Rule Type and click Next.
Select the appropriate choice between TCP and UDP, and enter the desired port(s) for the Specific local ports. Click Next.
Windows Firewall rule specifying the protocol and ports
Click Next. On the Profile screen, click Next.
On the Name screen, enter the desired name and clickFinish.
Windows Firewall rule specifying the rule’s name

Complete the above steps for each of the following rules.

Rule Name	TCP or UDP	Ports
SharePoint Web Traffic	TCP	80,443
SharePoint Search Index	TCP	16500-16519
SharePoint Farm Communication	TCP	32843,32844,32845
SharePoint Profile Synchronizing (TCP)	TCP	5725,389,88,53
SharePoint Profile Synchronizing (UDP)	UDP	389,88,53,464
SharePoint User Code Service	TCP	32846
SharePoint SMTP Service	TCP	25

Office Web Apps 2013 Server Install and Configuration

Installing Office Web Apps

Office Web Apps 2013 is a stand-alone server web application that provides capabilities to open and render a Microsoft Office Word, Excel, PowerPoint, or OneNote document as a web page. Microsoft SharePoint 2013, Exchange 2013, and Lync 2013 can share the rendering service to display Office documents in those applications as a web page. Additionally, when accessed from within a SharePoint 2013 farm, Office Web Apps also enables rich editing features for those documents.

Note: You cannot install Office Web Apps on the same server as SharePoint 2013

Please follow the server preparation process in the following sections for the appropriate server, either Windows Server 2008 R2 or Windows Server 2012.

Windows Server 2008 R2 Preparation

Start by installing the following prerequisite software for Windows Server 2008 R2:

Open a PowerShell command running as an Administrator and execute the following commands to install the required roles and services for Office Web Apps.

Import-Module ServerManager
## Run the following command as a single line
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support

Windows Server 2012 Preparation

To begin, open a PowerShell command running as an Administrator and execute the following commands to install the required roles and services for Office Web Apps.

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices

Office Web Apps Installation

Open and run the Office Web Apps setup.exe media to launch the setup wizard.

In the Office Web Apps Server 2013 Wizard, on the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and then selectContinue.
On the Choose a file location page, select the folder where you want the Office Web Apps Server files to be installed (for example, C:\Program Files\Microsoft Office Web Apps), and then select Install Now. Note that, if this folder does not exist, Setup will create it for you.
The Choose a file location screen on the Office Web Apps install wizard.
When Setup finishes installing Office Web Apps Server, choose Close.

After installing the Office Web Apps 2013 server software, you are ready to install any additional add-ins and updates. You can also install any language packs your farm requires. To install the language packs, run the setup media for each of the language packs you desire.

If applicable, install the latest service pack Microsoft has released for Office Web Apps 2013 and then apply the latest service packs Microsoft has released for Office Web Apps 2013 language packs.

Finally, check for updates on Microsoft Update in the server’s control panel.

Configuring Office Web Apps

This section describes how to configure an Office Web Apps farm and join servers to it.

Important: Low memory conditions can cause Office document previews to fail in Office Web Apps. Verify that any servers that run Office Web Apps have sufficient memory.

On the first server for the Office Web Apps farm, execute the following PowerShell command to provision the farm:

New-OfficeWebAppsFarm -InternalUrl "https://office1.contoso.com" -ExternalUrl "https://office.contoso.com" -SSLOffloaded –EditingEnabled

The SSLOffloaded command switch configures Office Web Apps for hardware load-balancing, where the load-balancing device manages the SSL certificate and then relays the request to an Office Web Apps server over HTTP unencrypted traffic. This improves the overall performance but does require a secure network between the load-balancer and the Office Web Apps servers.

The following image provides an example of the expected output from the PowerShell command.

PowerShell results from configuring an Office Web Apps farm

Critical: Before you can use the Office Web Apps farm, you must add your domain to the list of allowed hosts.

Run the following PowerShell command to add your domain to the list of allowed hosts, substituting your domain for “contoso.com.”

New-OfficeWebAppsHost -Domain contoso.com

Once you have provisioned an Office Web Apps farm and allowed your domain, you can join additional Office Web Apps servers to the farm. To join additional servers, install the Office Web Apps software by following the steps in the previous section and then execute the following PowerShell command.

New-OfficeWebAppsMachine –MachineToJoin “office1.contoso.com”

You can test the Office Web Apps configuration by navigating to this URL and verifying it displays a Web app Open Platform Interface (WOPI)-discovery XML file:

https://office.contoso.com/hosting/discovery
(replacing office.contoso.com with your OWA external domain)

Note: For more information on deploying and configuring Office Web Apps, please see this TechNet article: http://technet.microsoft.com/jj219455

Configuring the Windows Firewall for Office Web Apps Traffic

On each Office Web Apps 2013 Server, you will need to set a firewall rule to allow Office Web Apps inter-farm traffic and HTTP/HTTPS traffic. Alternatively, you can disable the Windows Firewall if you choose and if you have another firewall solution.

You can set the Windows Firewall rules by navigating to the Control Panel, then click System and Security, then click Windows Firewall, and finally click Advanced settings. In the Inbound Rules area, ensure that the server allows connections on port 80 (HTTP) and port 443 (HTTPS). Add the port for the Office Web Apps inter-farm communication by following these steps:

In the Windows Firewall with Advanced Security window, click Inbound Rules.
In the Actions panel, click New rule…
In the New Inbound Rule Wizard window, select Portsas the Rule Type and click Next.
Select TCP and enter “809” for the Specific local ports. Click Next.
Windows Firewall Port Rule for Office Web Apps communication
Click Next. On the Profile screen, uncheck Public and click Next.
On the Name screen, enter “Office Web Apps Inter-Farm Communication” and click Finish.

Configuring a SharePoint 2013 Farm for Office Web Apps

Logon to the SharePoint application server that hosts Central Administration and open the SharePoint 2013 Management Shell (PowerShell), running it as an administrator. Next, enter the following PowerShell command:

New-SPWOPIBinding -ServerName “office1.contoso.com”

Run the following PowerShell command to enabled OAuth over HTTP.

$config = (get-spsecuritytokenserviceconfig)
$config.allowoauthoverhttp = $true
$config.update()

Run the following PowerShell command to change the WOPI zone to external-https.

Set-SPWOPIZone –zone “external-https”

Finally, verify that Office Web Apps is working by navigating to a SharePoint 2013 document library and verify that you can open a document as a web page.

Note: For more information on how to configure a SharePoint 2013 farm to use Office Web Apps and for troubleshooting information, please see this TechNet article: http://technet.microsoft.com/ff431687

Next Steps Checklist

SQL DBA to configure database backup schedule
Networking/Infrastructure resource configure routing and load-balancing rules
System Center administrator to configure system monitoring
Operations team to plan for regular patching and maintenance
Build an FAQ community support SharePoint site to log common end-user questions
Document SharePoint support information and resources

@Rintu Mondal

Pages

Friday, 25 October 2019

SharePoint 2013 Farm Installation and Setup Guide

Implementation Details

SharePoint Farm Prerequisites

No comments:

Post a Comment