SharePoint 2016 Topology Planning

Scenario

• You are architecting an on-premises SharePoint 2016 Server Farm infrastructure deployment.

Steps

• If this is an upgrade, make sure you know what features were depricated
• Technet - Depricated Features
• Determine your server license requirements
• Enterprise or Standard
• Procure that license
• Determine if you need a scripted install or wizard install
• Scripted
• Utilize AutoSPInstaller (open source project) to create reusable installation scripts for easier re-provisioning of servers for multiple environments and disaster recovery scenarios
• More time to setup and initially more error-prone with greater possibility of misconfiguration and typos
• Wizard
• Simplified interface and best support from MS
• You should document in OneNote all settings chosen so you can reproduce exactly
• Determine if you can use MinRoles and decide which roles to use for which servers and how many servers you need
• MinRoles provide best practice configurations, are better supported by Microsoft, and are easier to redeploy using the wizard
• MinRoles cannot be used in certain large and specialized farm configurations
• Decide how many servers you need based on projected load and high availability requirements
• Decide which roles to use by reviewing them here: Technet - MinRole Planning
• Design SharePoint server topology using the roles and number of servers decided earlier
• Determine Hardware and VM Specs: Technet - Minimum Server Requirements
• Design SQL, Workflow Manager, and Office Online (previously Office Web Apps) server configurations
• SQL: Technet - SQL Planning
• Best on designated servers
• Workflow Manager: Technet - Install Workflow Manager
• Required to enable SharePoint 2013 workflows
• Latest SQL server version may not support WFM without additional patches
• Step by step guide
• Office Online Server: Technet - Planning Office Online Server
• Note that Excel Services is deprecated in 2016 and now requires an OOS deployment to work
• Requires designated servers