This document contains the speaker bio and presentation for Noorez Khamis on the topic of SharePoint architecture best practices. The speaker is a SharePoint architect with over 14 years of experience designing and implementing SharePoint solutions. The presentation covers a wide range of architectural topics for SharePoint including hardware requirements, deployment models, scaling, security, services, and tools like PowerShell. It provides guidance on choosing the right approach for various scenarios.

1. NoorezKhamis
Twitter:@nkhamis
Blog:http://www.khamis.net

2. GOLDRAFFLESILVER
PLATINUM

3. Speaker Bio
• Noorez Khamis aka “Rez”
• SharePoint Architect
• Microsoft MVP
• About me:
• SharePoint Solutions Architect (currently at Toyota Canada)
• 14+ years in managing, leading, designing and implementing SharePoint business solutions
across a wide variety of verticals
• Involved in hundreds of projects spanning entire SharePoint spectrum including enterprise
scale document and records management systems
• Active blogger and involved in GTA SharePoint community
• MBA, MCTS, MCDBA, MCSD, MVP
twitter: @nkhamis blog: Rez’s SharePoint Blog Spot -
http://www.khamis.net

4. So what’s this session about
anyways?







5. Key takeaways






6. Agenda











8. Understand the breadth of SharePoint







9. Experience and practice






10. Know your users











11. Communication skills are necessary







12. Know yourself










14. Looks like small changes at
first glance












 Urlremainsintactwithrenameandmoveacrosssitecollections


15. Hardware Requirements
Memory Processor Disk
Single Server Foundation
(Integrated or Standalone
Database)
SP 2013: 8 GB
SP 2016: ?
SP 2013: x64 1x4 cores
SP 2016: ?
SP 2013: 80 GB (OS)
SP 2016: ?
Single Server
(Integrated or Standalone
Database)
*Development
Environment/Evaluation
SP 2013: 10 GB*, 24 GB
SP 2016: 16-24 GB
*Min services for Dev
SP 2013: x64 1x4 cores
SP 2016: x64 1x4 cores
SP 2013: 80 GB (OS)
SP 2016: 80 GB (OS)
Web / Application Servers
*Pilot, Production, Servers in
a Farm
SP 2013: 12 GB
SP 2016: 12 – 16 GB
SP 2013: x64 1x4 cores
SP 2016: x64 1x4 cores
SP 2013: 80 GB (OS)
SP 2013: 80 GB (OS)
Want a full list? Go to my blog post: http://www.khamis.net/Blog/Post/267/SharePoint-2013---Hardware-and-Software-Requirements-and-Prerequisites

16. Prerequisites
Windows Management Framework 3.0
Application Server Role
Web Server (IIS) Role
Microsoft .NET Framework 4.5.2
Update for the .NET Framework 4 (KB2898850)
Microsoft SQL Server 2012 Native Client
Microsoft Identity Extensions
Microsoft Sync Framework Runtime v1.0 SP1 (x64)
Windows Server AppFabric 1.1
Windows Identity Foundation v1.1
Microsoft Information Protection and Control Client
Microsoft WCF Data Services
Windows Management Framework 3.0
Microsoft .NET Framework 4.5.2
Update for the .NET Framework 4 (KB2898850)
Windows Server AppFabric 1.1
Microsoft Information Protection and Control Client
Microsoft WCF Data Services
64-bit edition of SQL Server 201x
64-bit edition of Microsoft SQL Server 2014
Service Pack 1

17. Deployment Requirements
SharePoint
2010
SharePoint
2013
SharePoint
2016
Workgroup Supported Unsupported Unsupported
Domain
Controller
Supported for SBS
Only for Developer
Installation
Only for Developer
Installation
Client OS Developer Installation Unsupported Unsupported
Dynamic
Memory in VMs
Unsupported Unsupported Unsupported
Windows Web
Server
Supported Unsupported Unsupported
Source: SPC 2012

18. Increased List
Threshold >5000
List Threshold
Content database
sizing into TB’s
Content
Database Size
MaxFile Size
increases to 10GB
and removed
character
restrictions
MaxFile Size
100,000 site
collections per
content database
Site Collections
per Content
Database
2x increase in
Search scale to 500
million items
Indexed Items

19. Upgrade 14.5 mode site collections to 15
mode
Attach SharePoint 2013 databases to
SharePoint 2016
Upgrade
Migrate content to SharePoint 2016
Migration

21. Understand your client before doing
anything….








22. At the top of mind for any
SharePoint Architect





 Why?  Flexibility, Boundaries & Limitations

23. Boundaries and Limitations
More Info:
http://www.khamis.net/Blog/Post/260/S
harePoint-2010-vs--SharePoint-2013-
Boundaries-and-Limits-Comparison
Limit Name SharePoint 2010 Maximum
Value
SharePoint 2013 Maximum
Value
Web application limits
Web application Not Published 20 per farm
Content database 300 per Web application 500 per Web application
Zone 5 per Web application 5 per Web application
Managed path 20 per Web application 20 per Web application
Solution cache size 300 MB per Web application 300 MB per Web application
Site collection (sites and sub-sites) 250,000 per Web application 250,000 per Web application
Web server and application server
limits
Application pools 10 per Web server 10 per Web server
Content database limits
Number of content databases 300 per Web application 500 per farm
Content database size (general usage
scenarios)
200 GB per content database 200 GB per content database
Content database size (all usage
scenarios)
4 TB per content database 4 TB per content database
Content database size (document
archive scenario)
No explicit content database
limit
No explicit content database
limit
Content database items 60 million items including
documents and list items
60 million items including
documents and list items
Site collections per content database 2,000 recommended
5,000 maximum
5,000 recommended
10,000 maximum

24. How SharePoint 2013 can
help with scaling












25. Structured Technical Analysis








26. SDLC and ALM Planning and System Setup












28. Office 365 vs On-Premises










29. Physical vs Virtual








 http://download.microsoft.com/download/0/0/1/001ADCCC-A45B-47E3-8DA4-
ED51E3208021/Best_Practices_for_Virtualizing_and_Managing_SharePoint_2013.pdf

30. App Model vs Traditional – Choose wisely
Farm Solutions
• Full trust solutions
• Access to file systems
• Classic model from 2007
• Deploy to the GAC
• Access to the 14 Hive
• DLL’s and .NET Managed Code
Sandbox Solutions
• Declarative elements
• Partially trusted code with limited API
support
• DLL’s and .NET Managed Code
• No access to server
Apps
• New Apps model
• Deployed from corporate catalog or
office market place
• Manage permission and licenses
specifically
• Preferred option
• No server code!
---------------- Solutions Model -------------------- ------ App Model ------
Provider
Hosted
Auto
Hosted
SharePoint
Hosted
X

31. Why did Microsoft go down
the “App Route”?












32. Extensive CSOM and REST API Coverage


And more..BCS
AnalyticsWorkflow
eDiscoveryPublishing
TaxonomySocial
Sharing
Search

33. External Access for Extranet and Internet Sites






 http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC333
Want more information? http://technet.microsoft.com/en-us/library/cc263513(v=office.14).aspx

34. Source: http://www.wictorwilen.se/

36. Security concepts
• Use the principle of least privileges
• Minimum permissions that are required for users to complete authorized
tasks
• SQL/SharePoint/Other managed, app pool and service accounts, roles
• Concept also applies to privileges within your SharePoint webs as well
• Security Hardening
• Service applications enabled per server role, ports, web.config, SQL, SMTP,
Managed Accounts and auto password change
• Map your authorization and access to your Logical
Architecture
• Could just be a spreadsheet, define groups and accounts that have access to
which libraries and lists
Want more information? http://technet.microsoft.com/en-us/library/hh377941(v=office.15).aspx

37. Understand capabilities and benefits of Claims





38. Securing vs Targeting










40. Virtual Machine and SQL
Server Optimization











Want more information? http://technet.microsoft.com/en-us/library/hh292622(v=office.15).aspx

41. Services running in multi-server
environment





 http://www.microsoft.com/en-
us/download/confirmation.aspx?id=37001
 http://www.microsoft.com/en-
us/download/details.aspx?id=30367

42. Querying methods in SharePoint 2013












43. Caching

 http://blobcache.codeplex.com/











45. Consider Host Named Site Collections






46. Folders vs Metadata

Advantages of folders Disadvantages of folders
Segregation Harder to find specific items/more
clicks
Permissions URL length increased
Default metadata Hard to navigate through folder levels
Easily transitioning from file shares Folder metadata lacking
Scaling Can lose a document in wrong folder
Windows Explorer friendly No breadcrumb
Play nice with document sets Tricky to iterate through
Easier to migrate Filtering and sorting drawbacks

47. Versioning



49. PowerShell is your friend – Learn it!





 http://autospinstaller.codeplex.com/

50. Highly Available and Disaster
Recovery Environments






51. Consider Remote Blob Storage
for your deployment








53. Consider Add-ons











54. 
 www.khamis.net

55. Thank you!
Toronto Enterprise Collaboration User Group
Change Management, Governance, SharePoint, Office 365, Yammer,
PowerBI, etc
http://www.meetup.com/TSPBUG/
Toronto SharePoint Business Users Group
http://www.meetup.com/TorontoSPUG/
Saturday July 9, 2016
See you next year!