- Create a reusable SharePoint 2013 build and configuration guide
- Implement SharePoint and Office Web Apps Server in a consistent manner using the scripts I will provide throughout this blog post series.
- Farm Topology and Prerequisites (This article)
- SharePoint Installation, Configuration and Basic Service Applications Deployment
- User Profile, Search and Distributed Cache Service Applications Deployment
- Office Web Apps Server farm Implementation and Configuration
- Leave adequate memory for the Hyper-V partitions - For SharePoint products virtual machines, we recommend 4 GB of RAM or more for host computer operations.
- Use a minimum of two physical network adapters - For better network management and performance, dedicate one adapter to virtual machine network traffic and use the other adapter for virtualization host network traffic.
- Do not oversubscribe the CPU on the virtualization host computer - Review the supported ratio of virtual processors per logical processor and avoid oversubscribing the host computer CPU. The optimum virtual processor:logical processor ratio is 1:1. For more information, see Configure the processors for the virtual machines in Deployment guide for SharePoint 2013 eBook.
- Do not cross Non-uniform memory access (NUMA) boundaries - Hyper-V spans NUMA nodes to assign physical memory to a virtual machine; however, this does reduce performance on the virtual machine. For more information, see Configure the memory for the virtual machines in Deployment guide for SharePoint 2013 eBook.
- Do not use snapshots in a production environment - Do not use snapshots for the virtual machines in a SharePoint products production environment. When you create a snapshot, Hyper-V creates a new secondary drive for the virtual machine. Write operations occur on the new drive and read operations occur on both drives, which has the same net affect as a differencing disk. Every snapshot that you add reduces disk performance further.
- Do not use dynamic memory - The reason is that this implementation of dynamic memory does not work with every SharePoint feature. For example, Distributed Cache and Search do not resize their caches when the allocated memory for a virtual machine is dynamically changed. This can cause performance degradation, especially when assigned memory is reduced.
Setup user account
|The Setup user account is used to run the following:|
|SVC_SPFarm||The server farm account is used to perform the following tasks:|
|SVC_SPSvc||A generic services account for grouped Service Applications|
|SVC_SPSvcPool||Application Pool Identity for SharePoint Web Services Default application|
|SVC_SPWeb||Application Pool Identity for the main web application|
|SVC_SPUPA||The User Profile Service account is used to run the following:|
|SVC_SPSearch||This is the Windows Service account for the SharePoint Server Search Service. This setting affects all Search Service Applications in the farm.|
|SVC_SPSrchPl||Search Admin Web Service application pool|
Search Query and Site Settings Web Service application pool
|SVC_SPSrchCrl||Windows user credentials for the Search service application to use to access content when crawling|
|SVC_SPFabric||AppFabric Caching service|
|SVC_SPOWAPool||Office Web App Application pool account|
|SVC_SPOWASvc||Office web application Services Pool|
|SVC_SPSecStr||Secure Store application Pool account|
- All SharePoint servers would require an additional drive to host Data, Log and Index flies.
- An additional VHD is required
- Bring the disk online
- Format the drive as NTFS, label: Data
- Ensure that the following are implemented:
- Remote Registry Service started (or Automatic - Trigger Start) on all servers
- Inbound firewall rules enabled on all SharePoint servers: (Please see SharePoint 2013 Ports, Proxies and Protocols - An Overview of Farm Communications for more information)
- ICMP v4
- ICMP v6
- Central Administration port number on the servers hosting the Central Admin Site only. It is recommend to use SSL for the central administration site.
- Distribution Cache port 22233 on the Distribution Cache Servers only
- Ensure that the Install account has SQL securityadmin and dbcreator roles and is member of local administrator group on all SharePoint servers
- Ensure that the Farm account is a member of local administrators group on the server hosting the User Profile Service Synchronisation Service. This is only required during the User Profile Synchronisation Configuration defined in post #3 User Profile, Search and Distributed Cache Service Applications Deployment. These permissions are only required while configuring User Profile synchronisation Settings. However, when a backup of the User Profile application is initiated, the synchronization service provisions the User Profile application again. During the course of provisioning the User Profile application, the farm account must stop and start the synchronization service. To do this, the farm account must be a member of the Administrators group on the computer that is running the synchronization service.
- Ensure that the Farm account is able to logon locally on the server hosting the User Profile Service Synchronisation Service (Please see Plan account permissions).