Patr

oci

nadore

sPlatino

Oro

Plata

Séptimo Simposio Latinoamericano

SharePoint 2013 Deployment

Vladimir Medina PFE Microsoft@vladpoint

SharePoint Topologies Classic Three tiers topology

WFE, Apps, Backend News on topology

WFE Request Management Service

Apps services WAC on dedicated physical environment NEW Search Service should be deployed on dedicated physical environment

Topology configuration only via PowerShell SharePoint 2013 services could be consumed for SharePoint 2010 Farms

AppFabric Known as Distributed Cache Service or AppFabric Caching Service Dedicated physical environment recommended

Backend SQL 2012 AlwaysOn

SharePoint Topologies Virtualization

Plan to avoid oversubscription on hardware resources as Processor, RAM, Network, Disk NO dynamic configurations on RAM, Disk

Plan to reserve capacity for scale up (add resources to current VMs) and scale out (add new VMs)

Not only from production env lives SharePoint Farm Plan additional environments for development, testing, staging,

preproduction, disaster recovery, upgrade

PowerShellhttp://technet.microsoft.com/en-us/library/ee662539.aspxhttp://technet.microsoft.com/en-US/sharepoint/jj672838

SharePoint 2013 requirements Hardware

4-8 cores 12-24 Gb ram AppFabric 8-16 Gb recommended SQL 16+ Gb ram 80 GB disk for INSTALLATION ONLY + System + logs + index files + caches +

pagefile + data + free space (updates, memory dumps, etc.) 1 Gbps

Recommended limits 200 GB for content databases with read/write operations 4 TB for content databases with READ ONLY operations

Performance 15-25 ms disk transfer 10%+ free RAM memory Queues: 2 max Latency 1 ms

SharePoint 2013 requirements Software

Windows Server 2008 R2 SP1 – 2012 SQL 2008 R2 SP1 – 2012 .NET Framework 3.5 + 4.5 IIS 7.5 – 8

.NET extensibility Framework 4.5 ASP.NET 4.5 ISAPI Extensions

Application and Web server roles (configured via prerrequisites installer tool)

http://technet.microsoft.com/en-us/library/cc262485.aspx

Prerrequisites installer tool AppFabric 1.1 + CU1 SQL Server Native Client WCF Data Services 5.0 Information Protection and Control Client (MSIPC) Sync Framework Runtime 1.0 SP1 Windows Management Framework 3.0 Windows Identity Foundation 1.0 + Microsoft Identity

Extensions

SharePoint 2013 browsers support IE8 – IE10 Chrome Safari Firefox Additional Support to other browsers via Design Manager HTML 4 and ActiveX 32-bit required HTML 5 optional Mobile views: IE9+ – WinPhone 7.5+, Safari 4 – iOS 5+,

Android Browser – Android 4.0+http://technet.microsoft.com/en-us/library/cc263526.aspx

And more… WAC a.k.a. Office Web Applications Workflow Manager SMTP Reporting Services add-in, SSRS 2012 SP1 required for

SharePoint mode PowerPivot add-in Project Server 2013

ITPRO 104: Buenas Prácticas en la Migración a Project Server 2013

AppFabric or Distributed Cache Enabled as service on at least one server known as

Cache Host High Availability not supported by far Configurations into Config DB 10 “system caches” are created and managed by

SharePoint Customizations are not supported PowerShell cmdlets supported to monitor/access

Skydrive Pro & SharePoint Designer Groove – Workspace – Skydrive Pro Microsoft Sync Framework Web Services Office Document Cache SharePoint Designer 2010 can’t open SharePoint 2013

sites

Plan software boundaries Same as 2010

200 GB content databases 4 TB READ ONLY databases 100 GB site collection max size 50 MB file size, 2 GB max limit 5000 Items per list view 10 App pools per server

http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx

Logical Architecture best practices Same as 2010

Dedicated Web Applications with one or more content databases

Dedicated Content Databases for “BIG” Site Collections SharePoint Groups and AD groups to manage permissions Service accounts – managed accounts

http://technet.microsoft.com/en-us/library/cc262451.aspx

SQL Server deployment best practices Collation: Latin1_General_CI_AS_KS_WS Temp DB “best practices”

1:1 data files to cores Initial Size, pregrowth

Autogrowth: fixed mode Index fill factor: 80 Database location MAXDOP: 1 “required” High Availability on Backend Max memory setting

SharePoint deployment best practices… Wizards same as 2010

“Complete” role configuration “WFE” role deprecated

Command line + PowerShell still more flexible way to deploy Farm Setup.exe /config + config.xml file PsconfigUI steps using powershell:

new-spconfigurationdatabase + install-sphelpcollection + initialize-spresourcesecurity + install-spservice + install-spfeature + new-spcentraladminstration + install-spapplicationcontent

Connect-spconfigurationdatabase + install-sphelpcollection + initialize-spresourcesecurity + install-spservice + install-spfeature + install-spapplicationcontent

also… Web Applications

Claims authentication is default and required Clasic authentication still available only via PowerShell, NOT

RECOMMENDED Service Applications

New-SP<servicename>ServiceApplication New-SP<servicename>ServiceApplicationProxy Some Service Applications must be created via PowerShell only

State Service Session State Service Subscription Settings Service Workflow Service Application Proxy Azure Access Control Service Application Proxy Search Service Topology

and finally

Site Collections NEW host header-based site collections

To use multiple hostnames instead of limited AAM Get-SPSiteUrl | Set-SPSiteUrl | Remove-SPSiteUrl AAM still available and valid for alternate

authentication provides and app policies No self-Service site creation feature available here Limits on managed paths All site collections must be hosted on same Web

Application

20% de descuentoen todos nuestros cursos y libros hasta el 13 de Marzo

Introduce el cupón PECRSA8C al realizar tu compraen nuestra tienda online.

Patr

oci

nadore

sPlatino

Oro

Plata

Muchas gracias