1. SharePoint 2010 in a Multi-tenant and Hosted environment John Burkholder Welcome to SharePoint Saturday – New York @N8ivWarrior

2. Welcome to SharePoint Saturday – New York Thank you for being a part of SharePoint Saturday! Please turn off all electronic devices or set them to vibrate. If you must take a phone call, please do so in the hall so as not to disturb others. Open wireless access will time out after 40 minutes Feel free to “tweet and blog” during the session

3. Agenda Multi-tenant vs. Hosting SharePoint 2007 vs. SharePoint 2010 Multi-tenant SharePoint 2010 Installation Upgrades Hosting Tools and Options for Hoster’s Looking forward

4. Multi-Tenant vs Hosting Multi-tenant: Isolation of data, functionality, administration, customizations, and operations. Multiple customers within the same shared set of resources. Corporate, on-premise deployments. Hosting: Same as multi-tenant, plus an integration into other multi-tenant services to include: Exchange, OCS, Project, CRM, UMS, firewalls, control panels, billing systems, and DNS to name a few.

5. SharePoint 2007 vs 2010 Multi-tenant MOSS 2007 was basically non-existent. Multi-tenant WSS 3.0 was available but templates, and web parts were cross-platform. URL Namespaces in multi-tenant was limited. Inbound & Outbound email addresses were limited. No data isolation.

6. Multi-tenant SP 2010 SharePoint Framework and SharePoint Server 2010…mostly. Better control of hardware and data storage. Individual Web Applications. Host Headers/URL Namespaces! SSL Load balancer termination. Service Application Partitioning. Feature Sets.

7. Multi-tenant SP 2010

8. Differences MSF & MSS In a Multi-tenant environment - * Not partitioned ** Partitioned at Web Application ~ Partitioned at Site Collection

9. Differences MSF & MSS In a Multi-tenant environment - * Not partitioned ** Partitioned at Web Application ~ Partitioned at Site Collection

11. Host Header Collections Multiple root-level Site Collections within a Web Application. Allows for “vanity” domain names. Allows for “mix” &‟ match” URL namespaces. Host Header Site Collections now support Managed Paths companyA.com, companyB.com. companyA.com/sites/hr, companyA.com/hr.

14. Use the same instance to server multiple tenants.

15. Both the Service Application and Service Application Proxy must be configured.

16. Configured via PowerShell.

18. Do NOT use the Farm Configuration Wizard.

19. Can’t go from un-partitioned to partitioned.

22. Enabled by Farm administrators only.

23. Configured in PowerShell.

25. Installation Run the PowerShell Script! Get-SPServiceInstance| where{$_.GetType().Name -eq "SPSubscriptionSettingsServiceInstance"} | Start-SPServiceInstance $acc = Get-SPManagedAccount “Specific Account Name” $appPool = New-SPIisWebServiceApplicationPool -Name SettingsServiceAppPool -Account $acc $app = New-SPSubscriptionSettingsServiceApplication –ApplicationPool $appPool –Name SettingsServiceApp –DatabaseNameSettingsServiceDB $proxy = New-SPSubscriptionSettingsServiceApplicationProxy –ServiceApplication $app

26. Installation Now you can create sites! $pool = Get-SPIisWebServiceApplicationPool -Identity 'SharePoint Web Services Default'$meta = New-SPMetadataServiceApplication -HubUri http://website -ApplicationPool $pool -Name 'Tenant Managed Metadata' -DatabaseName O14_TenantMetadataDB -DatabaseServer SP14B -PartitionMode-SyndicationErrorReportEnabled$proxy = New-SPMetadataServiceApplicationProxy-PartitionMode -ContentTypePushdownEnabled -DefaultKeywordTaxonomy -DefaultSiteCollectionTaxonomy -Name 'Tenant Managed Metadata Proxy' -DefaultProxyGroup -ServiceApplication $meta

27. Upgrades Finally! You can upgrade from WSS 3.0 to SharePoint Foundation & SharePoint Server. Able to upgrade MOSS 2007 to Multi-tenant with Database attached. Able to add the 2010 look and feel to the newly upgraded sites.

28. Hosting Not supported by HMC…nor will it ever be. Most control panels do not yet support or integrate with SharePoint 2010. PowerShell allows for easier control panel development. Active Directory integration now allows for custom incoming e-mail. Manual provisioning through Tenant Administration.

29. Tools and Options PowerShell! Tenant administrator console.

30. Tools and Options Tenant administrator console requires PowerShell to install: ​$tasite = new-spsite –url “http://server/sites/tasite1” –template “tenantadmin#0” –owneralias domainsername. –sitesubscription $sub -AdministrationSiteType tenantadministration.

31. Updates

32. Updates On July 22, Microsoft released the cumulative patch for SharePoint 2010. Unlike the WSS 3.0 and MOSS 2007 cumulative updates this first cumulative update is not available as server package but has been released as 6 individual packages. You can download the fixes using the following links: Microsoft SharePoint Foundation 2010: KB 2028568 Microsoft SharePoint Server 2010: KB 983319 KB 983497 KB 2182938 KB 2281364 KB 2124512 After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

34. Most control panels do not yet support or integrate with SharePoint 2010.

35. PowerShell allows for easier control panel development.

37. Thanks to our Sponsors

38. For a chance to win cool prizes 2 ASUS Netbooks 3 Apple IPAD 32 GB Wifi Also Some Books 1 Typemock Isolator License A 2-5 Day Course from SetFocus on SharePoint Telerik RAD Controls Set 1 DeliverPoint WFE 2010 license (Worth $1500) 1 BCS Meta Man license (Worth $1200) 1 Lightning Conductor 2010 WFE license (Worth $800) 1 Lightning Storm Forums license. (Worth $600)

39. Session Evaluation Remember to fill out your evaluations Presenter: John Burkholder Session Name: SharePoint 2010 in a multi-tenant & hosted environment