1. Microsoft SharePoint Server 2016
Hiran Salvi
Senior Support Escalation Engineer
SharePoint & OneDrive

2. Why SharePoint Server 2016? Cloud-inspired infrastructure
Modernize your on-premises infrastructure to improve speed and scale, and enable new user experiences. SharePoint Server 2016 brings cloud and hybrid innovation to your datacenter so you can get the best of both worlds—speed and productivity for users, with flexibility and control for IT.
Based on learnings from Office 365, SharePoint 2016 delivers a reliable software-defined infrastructure foundation that’s proven at scale with best-in-class hybrid experiences.
Cloud-inspired infrastructure
New user experiences enable users to quickly and productively consume new apps and experiences across devices and screens.
New user experiences
Integrated data loss prevention and protection with built-in, cloud-connected compliance, security, and threat protection for both administrators and end users.
People-centric compliance

3. Cloud Born Cloud Scale and Performance with SharePoint Server 2016

4. Cloud Features with SharePoint 2016
Simple Sharing
Fast Site Creation
Site Folders
Large File Support
Simple Controls
Search
Durable Links
Mobile and Touch
Developer Experiences
Enhancements and Improvements

5. Future Proofing
Versions assume dependencies on latest system requirements
MinRole is the new normal for deployment topologies
Cloud is mainstream and closing in on on-premises

6. Farm Planning

7. Future Proofing Topology Planning
Design topology using MinRole roles
Mix Shared Roles with Dedicated Roles for flexible topology
Avoid using Custom Roles where possible
Role conversion is allowed
Caution: Distributed Cache needs special attention

8. MinRole
User services
sync client
OneNote
user profile
page
rendering
Excel
Services
sandbox
code
project
subscription
settings
Robot services
provisioning
timer jobs
search
SharePoint logic consolidated into a single machine reduces the number of discrete roles
Caching services
caching

9. MinRole & Topology Planning
Deploy 1+N of each role for High Availability
Select roles for the desired workloads and functions
Ensure minimum required roles are deployed

10. Role Guide
Dedicated Roles: Dedicated roles are optimized for performance and scalability and are typically used in large scale farms. They can also be used in medium scale farms with shared roles.
Server Role
Description
Front-end
Service applications, services, and components that serve user requests belong on a Front-end server. These servers are optimized for high performance.
Application
Service applications, services, and components that serve back-end requests, such as search crawl requests, belong on an Application server. These servers are optimized for high throughput.
Distributed Cache
Service applications, services, and components that are required for a distributed cache belong on a Distributed Cache server.
Search
Service applications, services, and components that are required for search belong on a Search server.

11. Role Guide
Shared Roles: Shared roles are optimized for fewer servers in a farm by combining dedicated roles together. They can also be used in medium scale farms with dedicated roles. Shared roles may require higher available system resources because they are running more services.
Server Role
Description
Front-end with Distributed Cache
Shared role that combines the Front-end and Distributed Cache roles on the same server. Make sure the server meets the system requirements for hosting a shared server role.
Application with Search
Shared role that combines the Application and Search roles on the same server. Make sure the server meets the system requirements for hosting a shared server role.

12. Role Guide
Special Roles: For special case scenarios, testing, development, and services that are not integrated with MinRole
Server Role
Description
Single-Server Farm
Service applications, services, and components required for a single-server farm belong on a server running the Single-Server Farm role. Use this role for development, testing, and limited production tasks.
Custom
Service applications, services, and components that you want to manage, instead of using MinRole to manage them, belong on a Custom server.

13. Site Collection Planning
Use one web application per farm to support all your site collections and sites
Keep your internally facing (intranet) SharePoint Server solution in a separate SharePoint Server 2016 farm from your externally facing (Internet) solution
Use host-named site collections instead of path-named site collections and place them in the default zone.
Use path-named collections when you need to use alternate access mappings (AAMs).
Site Collection Planning

14. Upgrade
Evaluate
Test
Backup

15. Evaluate Inventory SharePoint 2013 environment
Document the hardware and software in the SharePoint 2013 environment, where server-side customizations are installed and used, and the settings.
Automate process using SharePoint Migration Assessment Tool (link)

16. Test
Use SharePoint Migration Assessment Tool results to prepare test environment
Migrate Content from production to upgrade in test environment to confirm everything works as expected

17. Backup
Perform complete backup of services and content from 2013 environment
Document or export configuration of 2013 environment

18. Cloud Coexistence
There’s a new culture of work; one that is increasingly diverse, geographically distributed, and mobile, with an increasingly complex threat environment.

19. Scenarios and Benefits
Cloud Coexistence
MIGRATION TO THE CLOUD
Migrate at their own pace to the cloud with little or no disruption to existing service
Pilot Online Service with a subset of users
Scenarios and Benefits
MAINTAINING A HYBRID MODEL
Continue to maintain hybrid model providing services on- premises or online based on the organization needs
Continue to use existing customizations on-premises
Enrich traditional on-premises scenarios with cloud innovation

20. Information Protection
eDiscovery
Time Based Data Preservation
Data Loss prevention
Document Deletion Policies

21. Q&A