270 likes | 416 Views
Platino. Patrocinadores. Séptimo Simposio Latinoamericano. Oro. Plata. Ultimate SharePoint Best Practices Session. Michael Noel - CCO. Michael Noel.
E N D
Platino Patrocinadores Séptimo Simposio Latinoamericano Oro Plata
Ultimate SharePoint BestPracticesSession Michael Noel - CCO
Michael Noel • Author of SAMS Publishing titles “SharePoint 2013 Unleashed,” “SharePoint 2010 Unleashed”, “Windows Server 2012 Unleashed,” “Exchange Server 2013 Unleashed”, “ISA Server 2006 Unleashed”, and a total of 19 titles that have sold over 250,000 copies. • Partner at Convergent Computing (www.cco.com / +1(510)444-5700) – San Francisco, U.S.A. based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security
What’s new in Infrastructure for SharePoint 2013 Software/Hardware Requirements • Windows Server 2008 R2 SP1 or Windows Server 2012 (Preferred) • SQL Server 2008 R2 w/SP1 or SQL Server 2012 (Preferred)
What’s new in Infrastructure for SharePoint 2013 Changes in Service Applications and New Service Applications • Office Web Apps is no longer a service application • Web Analytics is no longer service application, it’s part of search • New service applications available and improvements on existing ones • App Management Service – Used to manage the new SharePoint app store from the Office Marketplace or the Application Catalog • SharePoint Translation Services – provides for language translation of Word, XLIFF, and PPT files to HTML • Work Management Service – manages tasks across SharePoint, MS Exchange and Project. • Access Services App (2013) – Replaces 2010 version of Access Services
What’s new in Infrastructure for SharePoint 2013 Distributed Cache Service • A new Windows service – the Distributed Cache Service – is installed on each server in the farm when SharePoint is installed • It is managed via the Services on Server page in central admin as the Distributed Cache service • The config DB keeps track of which machines in the farm are running the cache service
What’s new in Infrastructure for SharePoint 2013 Request Management (RM) • The purpose of the Request Management feature is to give SharePoint knowledge of and more control over incoming requests • Having knowledge over the nature of incoming requests – for example, the user agent, requested URL, or source IP – allows SharePoint to customize the response to each request • RM is applied per web app, just like throttling is done in SharePoint 2010
What’s new in Infrastructure for SharePoint 2013 User Profile Sync – Three Options for Deployment • Option 1: Simple one-way Sync (a la SharePoint 2007) • Option 2: Two-way, possible write-back to AD options using small FIM service on UPA server (a la 2010) • Option 3: Full Forefront Identity Manager (FIM) Synchronization, allows for complex scenarios – Larger clients will appreciate this
What’s new in Infrastructure for SharePoint 2013 Claims-based Authentication - Default • SharePoint 2013 continues to offer support for both claims and classic authentication modes • However claims authentication is THE default authentication option now • Classic authentication mode is still there, but can only be managed in PowerShell – it’s gone from the UI • Support for classic mode is deprecated and will go away in a future release • There also a new process to migrate accounts from Windows classic to Windows claims – the Convert-SPWebApplicationcmdlet
What’s new in Infrastructure for SharePoint 2013 Shredded Storage • Stores new versions of documents as ‘shredded BLOBs that are deltas of the changes • Promises to reduce storage size significantly
What’s new in Infrastructure for SharePoint 2013 Search – FAST Search now included • New Search architecture (FAST based) with one unified search • Personalized search results based on search history • Rich contextual previews
Architecting the Farm Three Layers of SharePoint Infrastructure
Architecting the Farm Small Farm Models • ‘All-in-One’ (Avoid) • DB and SP Roles Separate
Architecting the Farm Smallest Highly Available Farm • 2 SharePoint Servers running Web and Service Apps • 2 Database Servers (AlwaysOn FCI or AlwaysOn Availability Groups) • 1 or 2 Index Partitions with equivalent query components • Smallest farm size that is fully highly available
Architecting the Farm Best Practice ‘Six Server Farm’ • 2 Dedicated Web Servers (NLB) • 2 Service Application Servers • 2 Database Servers (Clustered or Mirrored) • 1 or 2 Index Partitions with equivalent query components
Architecting the Farm Ideal – Separate Service App Farm + Content Farm(s) • Separate farm for Service Applications • One or more farms dedicated to content • Service Apps are consumed cross-farm • Isolates ‘cranky’ service apps like User Profile Sync and allows for patching in isolation
SP Server Virtualization Sample 1: Single Server Environment • Allows organizations that wouldn’t normally be able to have a test environment to run one • Allows for separation of the database role onto a dedicated server • Can be more easily scaled out in the future
SP Server Virtualization Sample 2: Two Server Highly Available Farm • High-Availability across Hosts • All components Virtualized • Uses only two Windows Ent Edition Licenses
SP Server Virtualization Sample 3: Mix of Physical and Virtual Servers • Highest transaction servers are physical • Multiple farm support, with DBs for all farms on the SQL cluster
SP Server Virtualization Scaling to Large Virtual Environments
Virtualization of SharePoint ServersVirtualization Performance Monitoring • Processor (Host Only) • <60% Utilization = Good • 60%-90% = Caution • >90% = Trouble • Available Memory • 50% and above = Good • 10%-50% = OK • <10% = Trouble • Disk – Avg. Disk sec/Read or Avg. Disk sec/Write • Up to 15ms = fine • 15ms-25ms = Caution • >25ms = Trouble • Network Bandwidth – Bytes Total/sec • <40% Utilization = Good • 41%-64% = Caution • >65% = Trouble • Network Latency - Output Queue Length • 0 = Good • 1-2= OK • >2 = Trouble
Data Management Sample Distributed Content Database Design
HA and DR AlwaysOn Availability Groups in SQL 2012
HA and DR Network Load Balancing • Hardware Based Load Balancing (F5, Cisco, Citrix NetScaler – Best performance and scalability • Software Windows Network Load Balancing fully supported by MS, but requires Layer 2 VLAN (all packets must reach all hosts.) Layer 3 Switches must be configured to allow Layer 2 to the specific VLAN. • If using Unicast, use two NICs on the server, one for communications between nodes. • If using Multicast, be sure to configure routers appropriately • Set Affinity to Single (Sticky Sessions) • If using VMware, note fix to NLB RARP issue (http://tinyurl.com/vmwarenlbfix)
Security Five Layers of SharePoint Security • Infrastructure Security and Best practices • Physical Security • Best Practice Service Account Setup • Kerberos Authentication • Data Security • Role Based Access Control (RBAC) • Transparent Data Encryption (TDE) of SQL Databases • Transport Security • Secure Sockets Layer (SSL) from Server to Client • IPSec from Server to Server • Edge Security • Inbound Internet Security (Forefront UAG/TMG) • Rights Management
Gracias porvenir! Michael Noel Twitter: @MichaelTNoel www.cco.com Slides: slideshare.net/michaeltnoel linkedin.com/in/michaeltnoel Travel blog: sharingtheglobe.com
Platino Patrocinadores Muchas gracias Oro Plata