See how Microsoft Consulting Services can help you
Contact Microsoft Services
Contact The SharePoint Guys
Apply for a job at Microsoft Consulting Services
MCS Solution Dev
The Deployment Guys
MSDN UK Newsletter
MSDN UK Team Blog
TechNet UK Newsletter
TechNet UK Blog
This is the first in a series of posts where I will talk about my involvement in the TAP (Technology Adoption Program) and more specifically a project I was involved in to implement the SharePoint 2013 platform and Office Web Apps Server farm. I will be sharing my findings and experience that will hopefully help you to:
The series is broken down into the following articles that I will write:
This post will focus on providing an overview of the overall farm topology, the end to end build sequence from preparation to testing, recommended service accounts and the prerequisites.
The following diagram illustrates the high level overview of the steps required to implement and configure the SharePoint and Office Web Apps Server farms. The Office Web Apps server farm requires dedicated hardware and is no longer implemented as a SharePoint service application.
The server farm topology will have multiple tiers and each tier will have redundant server instances, this is the most common topology that provides an efficient physical and logical layout to support scaling out or scaling up, and provides better distribution of services across the member servers.
It is important to adopt an iterative design approach to analyse the architecture model, to verify that the model identifies all the elements that are required for the farm solution.
The Plan for monitoring in SharePoint 2013 TechNet article provides great introduction on tools and scenarios on how to best use them.
Redundant member servers are hosted on different Hyper-V hosts and Anti-Affinity helps to eliminate single points of failure. It is worth noting that the Deployment guide for SharePoint 2013 eBook, provides great detailed information regarding recommended practices when implementing SharePoint 2013 on a virtualised platform such as:
The following service accounts are what I have used to create the farm. This list may vary for your implementation depending on Server resources management versus least privilege security recommendation, required service applications and in general what works for your implementation based on the organisations security guidelines and policies.
Setup user account
The Setup user account is used to run the following:
The server farm account is used to perform the following tasks:
A generic services account for grouped Service Applications
Application Pool Identity for SharePoint Web Services Default application
Application Pool Identity for the main web application
The User Profile Service account is used to run the following:
This is the Windows Service account for the SharePoint Server Search Service. This setting affects all Search Service Applications in the farm.
Search Admin Web Service application pool
Search Query and Site Settings Web Service application pool
Windows user credentials for the Search service application to use to access content when crawling
AppFabric Caching service
Office Web App Application pool account
Office web application Services Pool
Secure Store application Pool account
Now we are ready to implement SharePoint and configure the basic services. Look out for part two for detailed step by step scripted deployment and configuration of the farm.