Introduction

Downloading and installing SharePoint prerequisites

Downloading and installing the SharePoint binaries

Downloading and installing the lastest SharePoint updates

Downloading and installing the required language packs (optional, necessary if you want the SharePoint interface to be presented in a language other than English)

Configuring the SharePoint farm using SharePoint Products and Configuration Wizard

Downloading the SharePoint installation package, click here for more details

Installing SharePoint and configuring the SharePoint farm

SharePoint 2010

SharePoint 2013

SharePoint 2016

SharePoint 2019 (to learn more about all the new features in SharePoint 2019, click here)

1 SharePoint 2016 Server

1 Database Server

Managed Accounts and Pre-Installation Requisites

Name Description Local Rights Domain Rights sp_farm The server farm account is used to perform the following tasks: -Configure and manage the server farm. -Act as the application pool identity for the SharePoint Central Administration Web site. -Run the Microsoft SharePoint Foundation Workflow Timer Service. SecurityAdmin and DB_Creator rights on the SQL Instance Domain User sp_admin The server farm account is used to perform the following tasks: -Setup -SharePoint Products Configuration Wizard Local Administrator on all the SharePoint Servers. SysAdmin, SecurityAdmin and DB_Creator rights on the SQL Instance. Must be na account with permissions to add rules to the local firewall. Domain User sp_pool The Pool account is used to run the Web Application Pools None Domain User sp_services The Services Account is used to run the Service Application Pool None Domain User sp_crawl The Default Content Access Account for the Search Service Application None Domain User sp_search Service Account to run the SharePoint Search “Windows Service” Local Administrator and SysAdmin rights on the SQL instance Domain User sp_mysitepool Used for the My Sites Web Application None Domain User sp_userprofilesync The User Profile Synchronization Account None Replicating Directory Changes permission on the domain. wf_service WorkFlow Manager Service Account Local Administrator and SysAdmin rights on the SQL instance. Domain User sp_portalsuperuser Object Cache Service Account. The goals of the object cache are to reduce the load on the computer on which SQL Server is running, and to improve request latency and throughput. These user account must be properly configured to ensure that the object cache works correctly. None. SharePoint: Must be an account that has Full Control access to the Web application. Domain User sp_portalsuperreader Object Cache Service Account. The goals of the object cache are to reduce the load on the computer on which SQL Server is running, and to improve request latency and throughput. These user account must be properly configured to ensure that the object cache works correctly. None. SharePoint: Must be an account that has Full Read access to the Web application. Domain User

To avoid problems executing the AutoSPInstaller script, ensure that the passwords of the above accounts do not contain any special characters (ex: $,%,&,/. etc)

The above table contains a proposal to name the accounts for the SharePoint installation. If you choose to use different names, ensure that the account names do not exceed 20 characters since NETBIOS names have a limit of 20 characters

Download AutoSPInstaller PowerShell script

Creating the AutoSPInstaller configuration file

SharePoint version to install

The SharePoint product key

The Farm Account and all Managed Accounts and their credentials

The database instance that will support the SharePoint environment

The web applications we want to create (ex: Intranet. My Site, etc)

The service applications we want to enable and their configurations

Outgoing email settings for the farm

Database names: this is extremely useful since it allows us to have complete control over the names of all the databases that will be created during the SharePoint farm configuration and avoid having databases with unclear names containing GUIDs which is the default behavior if we configure the farm using SharePoint Products Configuration Wizard (PSConfig)

Installing SharePoint

Managed accounts credentials will be validated. If any of the credentials is incorrect, the script will stop

SharePoint prerequisites will be installed

SharePoint will be installed

SharePoint language packs will be installed

SharePoint updates will be installed

Configuring the SharePoint Farm

Create all managed accounts

Configure IIS and SharePoint ULS log file paths

Create the configured web applications (ex: Intranet, My Site)

Configure the service applications

Configure outgoing email settings for the farm

Multi-Server Installation

What is your farm topology and the number of servers you want to consider (WFEs, Application Servers and Database Servers)

Which services and service applications will be provisioned for each server

Will you be using MinRoles or will you use a custom installation where you will be manually selecting the services and service applications that will be provisioned for each server?

Front-end

Application

Distributed cache

Search

Custom

Single-server farm

Front-end with Distributed Cache (merge of Front-end and Distributed cache MinRoles). available with Feature Pack 1 update or later

Application with Search (merge of Application and Search MinRoles). available with Feature Pack 1 update or later

Use Remote Installation

Install SharePoint individually in each SharePoint server

AutoSPInstaller Input File Configuration for Multi-Server Installation Notes when not using MinRoles

< Custom Provision=” false ” />

Provision=” ” /> <SingleServerFarm Provision=”localhost ” />

< Custom Provision=” localhost ” />

Provision=” ” /> <SingleServerFarm Provision=”false” />

<ServerRoles> <Custom Provision="localhost" /> <WebFrontEnd Provision="false" /> <WebFrontEndWithDistributedCache Provision="false" /> <SingleServerFarm Provision="false" /> <Search Provision="false" /> <Application Provision="false" /> <ApplicationWithSearch Provision="false" /> <DistributedCache Provision="false" /> </ServerRoles>

Remote Installation

Install SharePoint individually in each SharePoint server

SharePoint bits must be installed on all servers but farm configuration must only be done once all servers have the SharePoint bits installed . You may Install the SharePoint bits (all steps before the “Configuring the SharePoint Farm” in this post) in all servers at the same time but you must stop the installation process once you are asked to continue with farm configuration

. You may Install the SharePoint bits (all steps before the “Configuring the SharePoint Farm” in this post) in all servers at the same time but you must stop the installation process once you are asked to continue with farm configuration After the SharePoint bits are installed on all servers, you may proceed to the “Configuring the SharePoint Farm” section of this post BUT this must be done server by server, one at a time, sequentially . The AutoSPInstaller configuration file will determine what services and service applications are going to be provisioned on each server: When you run the farm configuration in the first server, the farm will be created and the services and service applications that are configured to run on that server will be provisioned When you run the farm configuration on the other servers, each server will be added to the farm and the services and service applications that are configured to run on that server will be provisioned

. The AutoSPInstaller configuration file will determine what services and service applications are going to be provisioned on each server:

Related Articles