February 13 th , 2013

1. Donald Donais February 13th, 2013 SharePoint 2013 – IT Pro Brian Caauwe & Mark Gamm

2. Agenda • Architecture Changes • Features • Break • Upgrade

3. Presenters

4. Brian Caauwe SharePoint Consultant & Speaker • Email: bcaauwe@Avtex.com • Twitter: @bcaauwe • Blog: http://blog.avtex.com/author/bcaauwe • Certifications • MCM: SharePoint Server 2010

5. Mark Gamm SharePoint Consultant • Email:  mgamm@atomicdata.com • Twitter:  @markgamm • Certifications

6. Architecture Changes

7. Architecture Changes Things only get more complex

8. Architecture Changes • Before the changes… Is anything still the same? • YES!!! • Service Applications • Web Applications • Content DBs • PowerShell • etc...

9. Farm Topologies • SharePoint 2010 • Medium Farm • High Load Services • Search

10. Farm Topologies • SharePoint 2013 • Medium Farm • High Load Services • Distributed Cache • Search

11. Farm Topologies • SharePoint 2013 • Medium-er Farm • High Load Services • Distributed Cache • Search

12. System Requirements • http://technet.microsoft.com/en-us/library/cc262485.aspx • 64-bit Only • All servers in the farm must be physically in the same datacenter (no stretched farm support) • No more client install

13. System Requirements – Single Server • Single Server Dev or Eval of SharePoint Foundation • 8 GB RAM • 4 Cores CPU • 80 GB System Drive • Single Server Dev or Eval of SharePoint Server • 24 GB RAM • 4 Cores CPU • 80 GB System Drive • DO NOT DO THIS IN PRODUCTION

14. System Requirements – Hardware

15. System Requirements– SQL Server • Max Degree of Parallelism ( MDOP) = 1 • Dedicated SQL Instance for SharePoint • SQL Alias • Makes moving databases easier in the future • I/O makes a difference • Virtualize with caution

16. System Requirements - Software • Server 2008 R2 SP1 • KB 2554876 • KB 2708075 • KB 2759112 • SQL Server 2008 R2 SP1 • I Recommend Server 2012 and SQL 2012

17. Architecture Changes • What’s New • Shredded Storage • Distributed Cache • Request Management • License Mapping • App Model / SharePoint Store • What’s Changed • Office Web Apps • Workflow • Search • Security

18. Architecture Changes – NEWShredded Storage • What is it? • Stores changes instead of entire new version • Does it help me? • Yes (in a lot of scenarios) • Database growth should be slower than in 2010 • Improved I/O • What else should I know about it? • Works best with OpenXML Office docs • Documents are not shredded on upgrade

19. Architecture Changes – NEWDistributed Cache • What is it? • Stores various types of information in memory • Does it help me? • Claim token caching • Social Feature Caching • What else should I know about it? • Adjust your memory considerations • Do NOT use dynamic memory • During install assigns 10% of total physical memory • Update-SPDistributedCacheSize –CacheSizeInMB <CacheSize> • When “stopping” service use Graceful shutdown • Stop-SPDistributedCacheServiceInstance –Graceful • Remove-SPDistributedCacheServiceInstance

20. Architecture Changes – NEWRequest Management • What is it? • enables administrators to manage the routing and throttling of incoming requests • Does it help me? • It can in certain scenarios • Most admins will not use • What else should I know about it? • Does not replace your load balancer • Managed through PowerShell • http://www.harbar.net/archive/2012/07/27/sp2013rm1.aspx

21. Architecture Changes – NEWLicense Mapping • What is it? • Enables admins to map licenses to users associated with AD Groups • Does it help me? • Yes - buy CALs for what your users are using • Mixing CALs in a farm is fully supported • What else should I know about it? • Managed through PowerShell (have you figured out you need PowerShell yet?)

22. Architecture Changes – NEWLicense Mapping • PowerShell cmdlets • Add-SPUserLicenseMapping • Disable-SPUserLicensing • Enable-SPUserLicensing • Get-SPUserLicense • Get-SPUserLicenseMapping • Get-SPUserLicensing • New-SPUserLicenseMapping • Remove-SPUserLicenseMapping

23. Architecture Changes – NEWLicense Mapping • Feature Categories • Unlicensed • Standard • Enterprise • Project • WACEdit (Office Web Apps) Enable-SPUserLicensing $lm = New-SPUserLicenseMapping      -SecurityGroup "CORP\Enterprise Client Access License"      -License EnterpriseAdd-SPUserLicenseMapping -Mapping $lm

24. Architecture Changes – NEWApp Model / SharePoint Store • What is it? • New development model for “customizations” • Heavy use of the client side object model • Does it help me? • If you don’t want server side code – YES • If you want server side code – NO • What else should I know about it? • Need wildcard DNS A (HOST) record for app domain • companyapps.com • Wildcard SSL Certificate • Use SSL otherwise OAuth tokens unsecured • SharePoint Store • App Requests • Enabled or Not

25. Architecture Changes – NEWApp Model / SharePoint Store (Continued) • What else should I know about it? • App Catalog (Special site collection) used for managing approved apps • App Licensing • No explicit setting prevents site owners from purchasing apps, use App Request process • URL Structure • https://<prefix>-<appID>.<appdomain> • Example: https://hrapp-4a9cce52782633.companyapps.com • Related Service Applications • Subscription Settings • App Management • User Profile Service (High Trust Apps)

26. Architecture Changes – ChangedOffice Web Apps • What is it? • Allows for viewing and editing Office documents in browser • Does it help me? • Yes - eliminates need to open client application • Yes - allows for co-authoring • Yes - preview capabilities

27. Architecture Changes – ChangedOffice Web Apps • What else should I know about it ? • Separate product now • Needs its own server( No really, it does...) • Read-only is free • SSL Certificate (Wildcard Certificates NOT supported)

28. Architecture Changes – ChangedWorkflow • What is it? • Enables new workflow actions / conditions • Does it help me? • Actions • Calling HTTP web services • Start List / Site workflow • Translation • Project Support • Conditions • “Valid” SharePoint User • Skip Project Stage • Components • Non-sequential workflows using stages • App Steps • Looping

29. Architecture Changes – ChangedWorkflow (Continued) • What else should I know about it? • Requires SharePoint Server (Standard or Enterprise) • Requires User Profile Service Application • Separate installation • Azure Workflow Manager • Azure Workflow Client • Can be installed ON or OFF of SharePoint servers • Requires routable DNS entry • Should utilize SSL for OAuth connectivity

30. Architecture Changes – ChangedSearch • What is it? • Single service instance using FAST as the base service regardless of Foundation, Standard or Enterprise • Does it help me? • Site Admins can now managed components • Result Sources (Scope Replacement) • Result Types • Query Rules • Schema (Managed Properties) • Farm Settings • Search Dictionaries • Result Sources • Query Rules • Crawl Schedules (Continuous Crawl)

31. Architecture Changes – ChangedSearch (Continued) • What else should I know about it? • Search Components QueryProcessing (QPC) FAST Search Index WFE Crawl ContentProcessing (CPC) Index Analytics Processing (APC) Search Admin

32. Architecture Changes – ChangedSearch (Continued … again) • What else should I know about it? • Search Topology can only be managed through PowerShell • Don’t forget to remove inactive topologies $searchInstance = Get-SPEnterpriseSearchServiceInstance -Local $ssa = Get-SPEnterpriseSearchServiceApplication $clone = $ssa.ActiveTopology.Clone() New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance $searchInstance New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance $searchInstance New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance $searchInstance New-SPEnterpriseSearchCrawlComponent-SearchTopology $clone -SearchServiceInstance $searchInstance New-SPEnterpriseSearchIndexComponent -SearchTopology $clone -SearchServiceInstance $searchInstance New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $searchInstance $clone.Activate()

33. Architecture Changes – ChangedSecurity • Claims vs. Classic • And the winner is……Claims • Claims is needed for full functionality • Switch to claims post-upgrade or before upgrade? • Post-upgrade allows for easy fallback if needed • Pre-upgrade seems cleaner and makes upgrade easier • Time will tell... • Sharing • Facebook like • Very easy to break inheritance (Is this a good thing?)

34. Features

35. Features • Web Content Management (WCM) • Enterprise Content Management (ECM) • Search • Access Services 2013 • User Profile Service • Machine Translation • App Management / Subscription Service • Work Management

36. FeaturesWeb Content Management (WCM) • Metadata navigation • Use Term Sets to navigate your site • Clean URLs (e.g. /west/northwest/wild) • SEO Improvements • Meta Description • Keywords • SiteMap • Channels • HTML5 / CSS3 • Theming

37. WCM Demo

38. FeaturesEnterprise Content Management (ECM) [Mark] • Records Management • Site based retention policies • eDiscovery improved • search and in-place hold • Drag and Drop • Browser Support • Firefox - latest version • Chrome - latest version • IE 10 desktop • IE 8 or IE 9 only if Office 2013 is installed • Team Mailbox • Adding site mailbox allows users to share communication concerning project • Requires Exchange 2013

39. ECM Demo

40. FeaturesSearch • Terminology • Result Sources (Scope replacement) • Display Templates (JavaScript kills XSLT) • Search Schema (Managed / Crawled Properties) • Query Rules • Promoted Results (Best Bets, can be defined at service application) • Result Block (Group like results) • Continual Crawling • Results also include social content • All analytics controlled in Search • Search web parts have been re-written • New Content Search Web Part (Enterprise Only – NOT in Office365) • When using Office Web Applications, includes document previews • Admins can force a re-index of specific lists / libraries • Managed Properties have more power • Query, Search, Retrieve, Refine, Sort

41. FeaturesSearch (Continued) • New Search Center

42. Search Demo

43. FeaturesAccess Services 2013 [Mark] • Requires SQL 2012 and a dedicated server • Allows users to create web applications • Each App gets its own SQL Server database (not access) • databases are created with GUID in name • Access 2013 client is required to build your app • it then gets published to SharePoint • Replacement for Info Path?

44. FeaturesUser Profile Service [Mark] • Direct AD Import vs. FIM • Direct AD Import • Much faster • Single domain • Start here • Switch to FIM if you need the features • Social Feature Dependencies • News Feed • SkyDrive Pro • Has nothing to do with SkyDrive (thank you Microsoft Marketing) • Allows sync between SharePoint and your PC • New version of SharePoint WorkSpace • http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=388 • If you want social you need MySites

45. User Profile Service Demo

46. FeaturesMachine Translation • Enables translation for pages and documents • Documents: docx, doc, docm, dotx, dotm, dot, rtf • Pages: html, htm, aspx, xhtml, xhtm • Other: txt, xlf • Out of the box uses Microsoft Translator • Mostly utilized through development API’s • Requires Server to Server authentication and app authentication • Translation also works in Word Web Application • Service Application Dependencies • App Management • Subscription • User Profile

47. FeaturesMachine Translation • Word Web App Example

48. FeaturesApp Management / Subscription Service [Brian] • App Catalog site per web application • Publish “acceptable” apps • Manage App Request • Internet Facing Apps • Web Application feature • Requires routable internet DNS

49. FeaturesWork Management • Task Aggregation • View and track to-dos and tasks • Can be aggregated from Exchange, Project Server and SharePoint • Tasks can be cached on users MySite • Requirements • Search Application • User profile service application

50. Work Management Demo