ITPro's taking the SharePoint 2013 Red Pill


Published on

With every new version of SharePoint come changes that either rock our world or make us scratch our heads and say "WHAT THE WHAT?!?"
If you are bold enough to want to adventure past the surface and are ready for the good, the bad, the great & the somewhat scary, join us as we deep dive into the rabbit hole of ITPro changes that are coming with SharePoint 2013.
Come on this journey as we:
-explore changes to the service applications (including search)
-what is new for visual upgrade
-how SQL 2012 changes the storage scenario
-take a look at the maturity of the Office Web Apps
-examine how the new App Model will impact us
-discuss the new workflow model
-discuss what the "Claims First" model is going to do to our world.
By the end of this session you should be as excited for SharePoint 2013, but as keep in mind twisted take on what Morpheus said: "Unfortunately, no one can just be told what the SharePoint 2013 is. You have to see it for yourself.”

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

ITPro's taking the SharePoint 2013 Red Pill

  1. 1. ITPro’s taking the SharePoint 2013Red PillJason Journey down the rabbit hole
  2. 2. Thanks to our sponsors!
  3. 3. SharePint!!!
  4. 4. Jason’s• Microsoft vTSP• virtual Technology Solutions Professional• SharePoint Foundation Logger•• Blog:• Twitter: @sharepointlhorn• LinkedIn:• SlideShare:• Email:• Author of Developing Business Intelligence Apps for SharePoint•
  5. 5. Wheels?Where we are going, we don’t need wheels!
  6. 6. Dependencies and Prerequisites
  7. 7. Web tierApplication tierDatabase tierWeb servers withquery componentApplication server with:• Central Administration• Search administrationcomponent• Crawl componentDatabase server with:• Central Administrationconfiguration and contentdatabases• Farm content database• Search administration database• Crawl database• Property databaseLoad balanced or routed requests
  8. 8. SharePoint 2010 vs. SharePoint “2013” Comparison:Component SharePoint 2010 Minimum Requirement SharePoint “2013” Minimum RequirementProcessor 64-bit, four cores 64-bit, four coresRAM 4 GB for developer or evaluation use8 GB for production use in a single serveror multiple server farm4 GB for developer or evaluation use8 GB for production use in a single server orin a multiple server farmHard disk 80 GB for system driveMaintain twice as much free space as you have RAM forproduction environments.80 GB for system driveMaintain twice as much free space as you have RAM forproduction environments.
  9. 9. Web tierApplication tierDatabase tierWeb servers withquery componentApplication server with:• Central Administration• Search administrationcomponent• Crawl componentDatabase server with:• Central Administrationconfiguration and contentdatabases• Farm content database• Search administration database• Crawl database• Property databaseLoad balanced or routed requests
  10. 10. SharePoint 2010 vs. SharePoint “2013” Comparison:Component SharePoint 2010 Minimum Requirement SharePoint “2013” Minimum RequirementProcessor 64-bit, four cores for small deployments64-bit, eight cores for mediumDeployments64-bit, 4 cores for small deployments64-bit, 8 cores for medium deploymentsRAM 8 GB for small deployments16 GB for medium deployments8 GB for small deployments16 GB for medium deploymentsHard disk 80 GB for system driveHard disk space is dependent on the sizeof your SharePoint content80 GB for system driveHard disk space is dependent on the size of yourSharePoint content
  11. 11. Hardware RequirementsMemory Processor Disk8 GB x64 1x4 80 GB (OS)24 GB x64 1x4 80 GB (OS)12 GB x64 1x4 80 GB (OS)HardwareandsoftwarerequirementsforSharePointServer2013
  12. 12. Dependencies and Prerequisites
  13. 13. Minimum Software Requirements
  14. 14. SharePoint 2010 vs. SharePoint “2013” Comparison:Component SharePoint 2010 Minimum Requirements SharePoint “2013” MinimumRequirementsSQL Server The 64-bit edition of Microsoft SQL Server2005 with Service Pack 3 (SP3).The 64-bit edition of Microsoft SQL Server2008 with Service Pack 1 (SP1) andCumulative Update 2The 64-bit edition of Microsoft SQL Server2008 R2The 64-bit edition of Microsoft SQLServer 2008 R2 Service Pack 1.WindowsServerThe 64-bit edition of Windows Server 2008with SP2The 64-bit edition of Windows Server 2008R2The 64-bit edition of Windows Server2008 R2 Service Pack 1 (SP1)
  15. 15. Minimum Software RequirementsWeb Server (IIS) roleApplication Server role(s).NET 4 DGR Update KB2468871Information Protection &Control Client (MSIPC)Windows Identity Foundation(WIF 1.0 and 1.1)SQL Server 2008 R2 NativeClientSync Framework Runtime v1.0(x64).Net Framework version 4.0 Open Data Library (ODataLib) Windows PowerShell 3.0
  16. 16. Software RequirementsHardwareandsoftwarerequirementsforSharePointServer2013
  17. 17. Software RequirementsHardwareandsoftwarerequirementsforSharePointServer2013
  18. 18. Deployment ScenariosSharePoint 2013 SharePoint 2010Workgroup Unsupported SupportedDomain Controller Developer Installation Supported for SBSClient OS Unsupported Developer InstallationDynamic Memory in VMs Unsupported UnsupportedWindows Web Server Unsupported Supported
  19. 19. Versioning Changes• Shredded Storage• Versioning Scenario• 1st file = 10m storage requirement• 2nd.. 10th = 1m file increase per version storage requirementOld versioning modelShredded Storage versioning modelWhat does this mean for RBS?1st = 10m 2nd = 11m 3rd =12m 10th = 19m Total = 145m1st = 10m 2nd = 1m 3rd =1m 10th = 1m Total = 19m
  20. 20. Claims
  21. 21. Authentication Modes• SharePoint 15 continues to offer support for both claims and classicauthentication modes• However claims authentication is THE default authentication option now• Classic authentication mode is still there, but can only be managed in PowerShell – it’sgone from the UI• Support for classic mode is deprecated and will go away in a future release, so werecommend moving to Claims• There also a new process to migrate accounts from Windows classic toWindows claims
  22. 22. Authentication Migration• The MigrateUsers method in SharePoint 2010 is no longer thecorrect way to migrate accounts – it is now deprecated• A new cmdlet has been created called Convert-SPWebApplication• A simple example – you have a Windows classic web application• Run Convert-SPWebApplication -Identity "http://yourWebapp" -To Claims –RetainPermissions [-Force]
  23. 23. Other Claims Migration Scenarios• You have an existing Windows claims application and you want to bring overcontent from a SharePoint 2010 Windows classic web app• Option 1 (the safest):• Create a web application in o15 that uses Windows classic authentication• Attach the SharePoint 2010 content database to this o15 web app• Attaching it will upgrade it to the o15 database format, so verify that it is working correctlyafter attach• Run the Convert-SPWebApplication command on the o15 web app to convert the users fromWindows classic to Windows claims• Detach the content database from the o15 Windows classic web app• Attach the content database to it’s final o15 Windows claims web app• Option 2 (the quickest):• Attach the content DB to an existing Windows claims web application• Run the Convert-SPWebApplication cmdlet again on the web app
  24. 24. Authentication Infrastructure• One of the big improvements is that SharePoint tracksFedAuth cookies in the new Distributed Cache Service• In SharePoint 2010 each WFE had its own copy• That meant that if you got redirected to a different WFE, youwould need to re-authenticate• This means that sticky sessions are no longer required whenusing SAML claims!
  25. 25. New Claims Features• You can choose the characters for the claim type and there is noenforcement on the ordering of claim types• Pre-populate the custom claim types and characters across all farms• Install the claim providers that use those custom claim types in any order• You can add multiple token signing certificates to the SharePointSTS• Useful in S2S scenarios• Use the Set-SecurityTokenServiceConfig cmdlet
  26. 26. New Claims Features (continued)• The SharePoint STS now supports a federation metadataendpoint• SharePoint publishes an endpoint describing it’s configuration andcertificates, and can consume the same• HOWEVER…the format it uses and consumes is JSON, so the trustingpartner must support that (AD FS does not today)• There is a possibility we will publish guidance on how to develop this forADFS• That would also support multiple token signing certs
  27. 27. Authentication Logging• There is significantly more logging provided to help troubleshootauthentication issues. You can see things like:• Adding / removing FedAuth cookies from the cache• Where authentication requests get redirected• Which claims providers were used and which were not• Reason why a FedAuth cookie failed to be used (i.e. expiration, failure todecrypt, etc.)
  28. 28. Request ManagementSourced from:
  29. 29. Request Management (RM)• The purpose of the Request Management feature is to giveSharePoint knowledge of and more control over incomingrequests• Having knowledge over the nature of incoming requests – forexample, the user agent, requested URL, or source IP – allowsSharePoint to customize the response to each request• RM is applied per web app, just like throttling is done inSharePoint 2010
  30. 30. RM – Goals• RM can route to WFEs with better health, keeping low-healthWFEs alive• RM can identify harmful requests and deny them immediately• RM can prioritize requests by throttling lower-priority ones (bots)to serve higher-priority ones (end-users)• RM can send all requests of specific type, like search forexample, to specific machines• Isolated traffic can help troubleshoot errors on one machine• RM can send heavy requests to more powerful WFEs
  31. 31. RM ComponentsRequest Manager (RM)Request Throttling and RoutingThrottle if appropriate, or select whichWFE’s the request may be sent toRequest PrioritizationFilter WFEs to only ones healthyenough for the requestRequest Load BalancingSelect a single WFE to route to, basedon weighting schemes like health
  32. 32. RM Routing and Pools• Routing rules route requests and are associated with MachinePools• MachinePools contain servers• Servers use weights for routing – static weights and health weights• Static weights are constant for WFEs; health weights change dynamically based on healthscoresStatic Weight = 1Health Weight = 4Static Weight = 1Health Weight = 4Routing Rule #1Routing Rule #2…Routing Rule #n
  33. 33. RM Routing Rules• Routing to a server in a MachinePool is based onmatching a routing rule• Routing rules are placed in ExecutionGroups• These are numbered 0 to 2, with 0 the default• Rules are evaluated in each ExecutionGroup• As soon as a match is found no more ExecutionGroups are evaluated• All machines from pools that match any routing rules are union’edtogether to determine possible target servers• This means that you create your most important rules inExecutionGroup 0
  34. 34. Routing Rules and Execution GroupsExecution Group 0Routing Rule #1Routing Rule #2Routing Rule #3Execution Group 1Routing Rule #4Routing Rule #5Execution Group 2Routing Rule #6Routing Rule #7Match!XNo MatchNot Evaluated
  35. 35. RM Routing Rules (cont.)•There are some important caveats to rememberabout routing rules• If no rules are matched, then the request will be sentto any server that is NOT in any machine pool for anyrule• In a one server farm that means nothing will route ifno rules match, so the alternative is to create a “catchall” rule that matches everything• Just put it in ExecutionGroup 1 or 2 so it’s the last match
  36. 36. RM Routing Weights• RM uses static weights and health weights• Static weights are associated with WFEs so certain ones will always befavored when selecting.• This gives added weight to more powerful WFEs and less to weakermachines• Health weights are used to even out load and keep “sick” WFEs going• Health scores run from 0 to 10 where 0 is the healthiest and therefore willget the most requests; this score is used to derive the health weight• WFEs start with a healthy weight; the Policy Engine health rule updateshealth weights dynamically – you cannot change it manually
  37. 37. RM Scenario – Health Based Routing• A series of requests come in; one WFE is in poor health, while twoothers are in good health. RM evaluates the following:• Health information: { [WFE1, sick], [WFE2, healthy], [WFE3, healthy] }• Based on this RM routes most of the requests among WFE2 andWFE3• It is still random routing, but greater weight is given to healthier machines• Alternatively the admin could remove WFE1 from the routingpool, allow it to complete its requests then return it back to thepool
  38. 38. New & Retiring Service Applications
  39. 39. What happened to Office Web Apps?• OWA is now stand alone. It cannot run on a SharePoint Server.• Why?• Not all documents are in SharePoint• Provide unified platform for other applications as well• Benefits• Large customers had numerous farms to manage in 2010 time frame• Consolidation of services to single Office Web Apps farm which provides services for multipleapplications• Manage scale and performance of Office Web Apps independent of the SharePoint environment• Easier upgrade and maintenance for Office Web Apps functionality• Easier consuming of Office Web Apps functionalities without complex SharePointfederation• Easier to setup also without SharePoint – if only used for example with Exchange• Scalability with OWA “Farms”
  40. 40. New Replacement for Web Analytics Service• The Analytics Platform replaces the Web Analytics service application• Some of the reasons for that included:• There was no concept of item-to-item recommendations based on user behavior, i.e.people who viewed this also viewed foo• Couldn’t promote search results based on an item’s popularity (as determined by # oftimes an item was viewed)• It required a very powerful SQL box and significant storage and IO• Lists don’t have explicit view counts• The architecture could have problems scaling to large numbers
  41. 41. How the New Platform Improves on Analytics• The new Analytics Processing engine aims to solve these issues:• Find relevant information (improve search relevance) – based on views, clickthru, etc.• See what others are looking at (“hot” indicators and usage numbers – i.e.what’s popular based on # of views as well as # of unique users to view)• Understand how much content is being used (i.e. viewed) and how it comparesto other documents• See discussion thread usage and find the hot topics• Use this popularity info to populate views through the Content by Search (CBS)WebPart• The model is extensible for 3rd parties to build into the platform
  42. 42. Processing and Storing Analytics Data• Data goes through an analysis and reporting process that is containedwithin the search service application• Things like views and counts are combined with click-thru and othersearch metrics and pushed into the reporting database• Some data like view counts are also pushed into the index so it can beincluded in search results, sorted on (i.e. what’s most viewed), etc.• An analytics processing job examines data for clicks, links, tags, etc., aswell as the usage data to create the data points used for reporting
  43. 43. Analytics System Components• The Analytics system can be considered as five parts:• Event: Each item comes into the system as an event with certainparameters• Filtering & Normalization: Each event is looked at to see:• Special Handling: Certain types of events will be directly written to the.usage files• Filtered Out: Some events like those from robots, should not be countedand allowed to pass• Normalized: Rewritten so it can be counted along with other hit types. E.g.document reads through the WAC should be counted as reads against thedocument• Allowed to Pass: So that normal counting methods can be performed
  44. 44. Analytics System Components (cont.)• Custom Events: You can configure up to 12 customevents in addition to what comes OOB• Calculation: We run calculations to sum or averageacross events• Reports: A number of default reports are available,including:• Top queries• Most popular documents in a library or site• Historic usage of an item – view counts for last recenthistory as well as all time
  45. 45. Access Services• Good news: the old Access Services 2010 Service App is still here• Better news: the new Access Services 2013 Service App is here• The horrifying news: how Access Services 2013 management is done
  46. 46. SharePoint SQLManageability
  47. 47. Service applications in SharePoint 2013• New service applications available andimprovements on existing ones• Office Web Apps is no longer a serviceapplication• Web Analytics is no longer serviceapplication, it’s part of search
  48. 48. Enterprise Content Management
  49. 49. New Cache Service• A new Windows service – the AppFabric Caching Service – is installedon each server in the farm when SharePoint is installed• It is managed via the Services on Server page in central admin as theDistributed Cache service• The config DB keeps track ofwhich machines in the farmare running the cache service
  50. 50. Cache Setup• The farm account is used as service account for Cache Service• Like user profile service in SharePoint 2010, during setup theservice account should have elevated privileges (i.e. local admin)• After setup is complete you should lower the privileges for theaccount
  51. 51. Cache Architecture• For caching in farm, scale points have not been determined yet• How many servers are needed, what resources should be built out (CPU,memory, etc.)• More data will be available after Beta 2
  52. 52. Cache Server Performance• There are hundred(s) of perf counters; there are also countsexposed via developer’s dashboard• # of reads• # of writes• # of hits• # of misses• time for read• time for write• Total I/O (how much data has been transferred in a given period of time)
  53. 53. Cache Service Health• The following health rules have been created to help you track the CacheService (look in the Availability section for most):• One of the cache hosts in the cluster is down (Availability)• Firewall client settings on the cache host are incorrect (Configuration)• Cache host is in throttled state (Availability)• The high availability node for SharePoint distributed cache is not available(Availability) – happens when there are less than 2 servers running the cache service• There exists at least one cache host in the cluster, which SP doesnt know about(Configuration) – happens when the cache service is disabled in SharePoint butAppFabricCaching Service is running on the machine• Cached objects have been evicted (Configuration) – indicates eviction happenedacross the cache cluster. Not bad in and of itself but may be a clue if it happensfrequently and/or there are perf issues
  54. 54. ECM & e-Discovery
  55. 55. SharePoint 2013 ECM - Big BetsInternet Business• Major WCMInvestment• Search Driven Sites• Intranet and InternetapplicabilityeDiscovery• In place preservationin SP & Exchange• Integrated, enterprisewide casemanagementTeam Folders• Work on mail anddocuments together• SharePoint, Outlook,OWA• Retention/complianceacross stores
  56. 56. Central Place to view all Cases
  57. 57. Add, manage and export discovery sets
  58. 58. Site Based Compliance & preservation• Compliance officers create policies, whichdefine:• The retention policy for the entire site andthe team mailbox, if one is associated withthe site.• What causes a project to be closed.• When a project should expire• Can set also site collection as read only• Policy also available optionally from selfsite creation• Policies can be replicated from contenttype hub cross enterprises
  59. 59. The Team Folders – Exchange and SPtogether • Documents are stored inSharePoint• Emails are stored in Exchange• Team Folders can receiveemails and have their ownemail address• Easy access to both fromOutlook and SharePoint• Unified compliance policyapplies to both
  60. 60. Unified Discovery across Exchange, SharePointand Lync• Find it all in one place (unified console)• Find more (in-place discovery returns the richest data)• Find it without impacting the user (Give legal team discovery, leave IWs alone)Discovery Center in SharePoint Unified Preserve, Search and ExportExchange Web Services Connect to Exchange to get mailbox dataLync Archiving to Exchange Exchange is the compliance store for LyncSearch Infrastructure Exchange and SharePoint use the same search platform
  61. 61. Search
  62. 62. Search• New Search architecturewith one unified search• Personalized search resultsbased on search history• Rich contextual previews
  63. 63. Connectors
  64. 64. Crawling and Content Sources
  65. 65. Crawling “Continuously”
  66. 66. Search UI Configuration• Result Types• Display Templates• Search Navigation• Search Refinement• Query Suggestions• Thumbnail Previews• Site Level Search Admin Summary
  67. 67. Search Refinement
  68. 68. Faceted Navigation with Search Refiners
  69. 69. Query Suggestions
  70. 70. Thumbnail Previews
  71. 71. Business Intelligence
  72. 72. Business Intelligence• Excel BI• Instant analysis through In Memory BIEngine• Power View Add-in• Excel Services• Improved data exploration• Field List and Field Well Support• Calculated Measures and Members• Enhanced Timeline Controls
  73. 73. Business Intelligence• PerformancePoint Services• Filter enhancements and Filter search• Dashboard migration• Support for Analysis Services EffectiveUser• Visio Services• Refresh data from external sources –BCS and Azure SQL• Supports comments on Visio Drawings• Maximum Cache Size service parameter• Health Analyzer Rules to report onMaximum Cache Size
  74. 74. Jason’s favorite new feature…
  75. 75. Introduction• Business challenge• It is challenging for information workers to get a comprehensive view of their tasks or tohave a central point for managing their work.• Tasks are stored across applications and systems, and even in the case where all tasksare stored within a single system, information can still be scattered.• Work management Service applications provides functionality to aggregatetasks to central place• Users can go to view and track their work and to-dos• Tasks cached to person’s my site
  76. 76. Tasks - Architectureanimated
  77. 77. Technical background and configuration• Service application doesn’t have any configuration options in CentralAdministration• Accessed and used directly programmatically by out of the box functionalities• Out of the box task aggregation with Microsoft SharePointProducts, Microsoft Exchange Server, and Microsoft Project Server• Example, users can edit tasks from Exchange Server on a mobile phone, and theWork Management Service aggregates tasks to the My tasks SharePoint list.• Implementation is based on provider model, so that additional systemsmaybe integrated to same architecture in future
  78. 78. Thanks to our sponsors!
  79. 79. SharePint!!!
  80. 80. Jason’s• Microsoft vTSP• virtual Technology Solutions Professional• SharePoint Foundation Logger•• Blog:• Twitter: @sharepointlhorn• LinkedIn:• SlideShare:• Email:• Author of Developing Business Intelligence Apps for SharePoint•
  81. 81. Upcoming NHSPUG SpeakersJune 13 – Leanne BatemanJuly 11 –Maybe you???August 8 – Becky IssermanSeptember 12 – Richard HarbridgeSeptember 21 – SPSNHOctober 10 – Tim FarrellNovember 11 – Sadie van Buren
  82. 82. Handy information• Jason’s info••• @sharepointlhorn• This Deck is available now at• SharePoint 2013 Presentation: ITPro training•• Wictor Wilen• Claims Auth:• Spencer Harbar• Request Manager:• Dan Holme• Shredded Storage:• Andrew Connell• Setup Guide for Devs:• Todd Klindt•• SPC 2012 shtuff:• Weekly Netcast: