SharePoint 2013 my work log

Tags: SharePoint 2013, Installation

Scenario : 2 SharePoint Server and 1 SQL server

for the entire set up I have planed for 3 nos of 8 GB, 2 core VMs, All the servers are running in Windows Server 2012 R2 and the SQL server is having SQL Standard 2014 SP1

Step 1 : Create required accounts

I have created

Account Name Description Domain and Local Rights SQL rights needed
   

For SQL Servers

sql_admin SQL 2014. Admin (for SPS) SQL Admin on the SQL Server. Used to Install the SQL Server Domain User with Local Administrator on the SQL server box
sql_services SQL 2014. Services (for SPS) Account the SQL Instance is running as Domain User

Service account for

  • MSSQLSERVER
  • SQLSERVERAGENT

For SharePoint Servers

sps_Admin SharePoint 2013. Admin

The server farm account is used   to perform the following tasks:

  • Setup
  • SharePoint Products Configuration Wizard 

Domain User with Local Administrator on all the SharePoint Servers

  • securityadmin
  • dbcreator
  • public
  • Need to be SysAdmin on SQL when installing the Workflow Manager
  • This account must be a member of the db_owner fixed database role for the content databases database.
sps_Farm SharePoint 2013. Farm Admin

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.
  • User Profile service
       
Domain User but Local Admin during UPS provisioning, log on locally right

The server farm account is automatically added as a SQL Server login on the computer that runs SQL Server.

The account is added to the following SQL Server security roles:

  • dbcreator fixed server role
  • securityadmin fixed server role
  • db_owner fixed database role for all SharePoint databases in the server farm
sps_Search SharePoint 2013. Search Windows Service Service Account to run the SharePoint Search "Windows Service" Domain User
sps_Crawl SharePoint 2013. Search Service Application The Default Content Access Account for the Search Service Application Domain User
sps_WebAppPool SharePoint 2013. Web App The Pool account is used to run the Web Application Pools Domain User
sps_SerAppPool SharePoint 2013. Service App The Services Account is used to run the Service Application   Pool Domain User
sps_SuperReader SharePoint 2013. Cache Reader Domain User with Web application Policy Full read
sps_SuperUser SharePoint 2013. Cache User Domain User with Web application Policy Full   Control
sps_UserProfile SharePoint 2013. User Profile Service Account used by the User Profile services to access Active   Directory
  • Domain User
  • Replicate Directory Changes   permission on the domain.  Guide:   http://bit.ly/TSE7xs
  • Must be given in BOTH ADUC and ADSIEDIT
sql_ssas SQL 2014. Analysis Service Account that we run the SQL Server Analysis Service services   as Domain User -db_datareader
sql_ssrs SQL 2014. Reporting Service Account that we run the SQL Server Reporting Service Domain User
sps_excel SharePoint 2013. Excel Services Excel services unattended account. Domain User
sps_pps SharePoint 2013. Performance Point Service PerformancePoint Unattended account Domain User
sps_access SharePoint 2013. Access Services Access services   unattended account. Domain User -securityadmin
-dbcreator, 
-public

Rresources : 1, 2, 3

Step 2 : Install and Configure the SQL Server

Make "sql_admin" as one of the local admin, give permission gor RDP, login to the db server under "sql_admin" install SQL 2014 (with SP1) and when asked for the service account assign to "sql_services". Leave the configuration of SSRS and Analytic servce for later.

Once Installed, please provide or assign the above SQL rights to the accounts and change the "Max Degree of Parallelism" value from 0 to 1

Enable the TCP/IP client protocoal form "SQL Server Configuration Manager"

Create an alias to the instance for Sharepoint 2013 and test it.

Resources : 1,

Step 3 : Install SharePoint 2013 Binary and Run Configuration Wizard.

Make "sps_admin" as local admin and allow fro RDP, Login to the first server, where we are going to host CA and install the SharePoint 2013 binary, but not run the configuration wizard.

create ans SQL Alias and test it. Now lets create the base Database and Admin Content database using code. (am running this in PowerShell ISE)

******************************

CLS
& 'C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\CONFIG\POWERSHELL\Registration\SharePoint.ps1'

### Check for cliconfg enrtry 
#For x86: Get-ItemProperty HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo #For x64: Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo if($passphrase -eq $null) { $passphrase = (ConvertTo-SecureString "DisIt2014" -AsPlainText -force) } if($credentials -eq $null) { $credentials = Get-Credential } New-SPConfigurationDatabase -DatabaseServer "DISSPS2013" ` -DatabaseName "SharePoint_Config" ` -AdministrationContentDatabaseName "SharePoint_Admin_Content" ` -Passphrase $passphrase -FarmCredentials $credentials ## State Service Application New-SPStateServiceApplication -Name "State Service Application" Get-SPStateServiceApplication | New-SPStateServiceApplicationProxy -DefaultProxyGroup Get-SPStateServiceApplication | New-SPStateServiceDatabase -Name "State_Service_DB" Get-SPDatabase| Where-Object {$_.type -eq "Microsoft.Office.Server.Administration.StateDatabase"} | Initialize-SPStateServiceDatabase ## Usage and Health Data Collection New-SPUsageApplication -Name "Usage and Health Data Collection" $proxy = Get-SPServiceApplicationProxy| where {$_.TypeName-eq "Usage and Health Data Collection Proxy"} $proxy.Provision()

******************************

 Then Run the "SharePoint 2013 Product Configuration Wizard" to to finilize the CA on port XXXX

Resources : 1, 2, 3