1. Module 2 Creating a SharePoint 2010 Intranet

2. Start the Virtual Machines 1. Start 10174A-CONTOSO-DC-B. 2. After CONTOSO-DC has completed startup, start 10174A-SP2010-WFE1-B. 3. Log on to SP2010-WFE1 as CONTOSO\SP_Admin with the password, Pa$$w0rd.

3. Module Overview Performing Initial Farm Configuration Configuring the SharePoint Logical Structure Exploring the SharePoint Web Application and Physical Architecture

4. Lesson 1: Performing Initial Farm Configuration Walkthrough: Farm Configuration Wizard Farm Configuration Wizard Service Applications: An Overview Managed Accounts: An Overview

5. Walkthrough: Farm Configuration Wizard In this walkthrough you will: Run the Farm Configuration Wizard Identify the configuration tasks performed by the Wizard

6. Farm Configuration Wizard Applies SharePoint defaults  Service applications  Application connections  Managed accounts Why?  Simple, out-of-box defaults  Testing, training, development Why Not?  Custom farm configuration

7. Service Applications: An Overview Service applications host specific SharePoint functionality  Search Service Application  Business Connectivity Service  Managed Metadata Service  User Profile Service  Web applications connect to the service application* A service app’s application connection (proxy) allows connections to the service app  Web applications connect to the service app proxy* Connections are grouped into application connection (proxy) groups * In fact, web applications are associated with an application proxy group, which provides connections (proxies) to one or more service apps

8. Service Applications: An Overview Architecture  MOSS 2007: Shared Service Provider (SSP)  SharePoint Foundation 2010 Service application architecture Windows Communication Framework Extensible Setup and administration  MOSS 2007: SSP administration  SharePoint 2010 Central Administration Remote management and monitoring Windows PowerShell

9. Service Applications: An Overview Flexible topology  MOSS 2007: Web app  SSP  All services in the SSP  SharePoint 2010 Web app  proxy group  service apps Cross-farm service consumption over HTTPS

10. Service Applications: An Overview (Whiteboard)

11. Managed Accounts: An Overview What is the security and management challenge with service accounts in an enterprise? SharePoint managed accounts  SharePoint can change the password of managed accounts in Active Directory and the password in the service configuration Managing managed accounts  Registration  Password change  Password expiration and automatic password change

12. Lesson 2: Configuring the SharePoint Logical Structure SharePoint Logical Structure Request a Page from a SharePoint Site Create a Web Application Create a Site Collection Site Collection Settings Subsites, Site Collections, and Content Databases Managed Paths Content Databases

13. Content Database(s) SharePoint Logical Structure Web Application Site Collection Top-Level Site SiteListLibrary [Folder] ItemDocument Site Managed Paths

14. Request a Page from a SharePoint Site intranet.contoso.com DNS http request to 10.0.0.11:80 host header “intranet.contoso.com” SharePoint Query intranet.contoso.com Resolved 10.0.0.11 IIS Content DB SQL http://intranet.contoso.com

15. Create a Web Application Application Management  Web Applications  Manage Web Applications  New Unique URL: IP address:Port + host header  Typical: User port 80 (or SSL) with host header Application name: based on your naming standards Authentication mode: Classic or Claims-Based Public URL: for load balancing Application pool  Shared app pool for reduced RAM overhead  Separate app pools for process isolation Shared identity for simplicity Separate identities for manageability and audit Database name: based on your naming standards DNS: A record (not CNAME)

16. Notes Page Over-flow Slide. Do Not Print Slide. See Notes pane.

18. Load Balancing intranet.contoso.com intranet Content DB intranet.contoso.com :80 intranet.contoso.com WFE SQL DNS http://intranet.contoso.com

19. Create a Site Collection Application Management  Site Collections  Create site collections Ensure you’re focused on the correct Web application Title URL  Top level: /  Additional site collections: / [managed path /] SiteName Recommend URLs with no spaces (%20) and MixedCase Site definition: Template selection  Sub-sites: List is filtered based on parent site settings intranet.contoso.com Content Database Site Collection Top-Level Site Site Collection Top-Level Site

20. Site Collection Settings Application Management  Site Collections Ownership, Administration, and Access Quotas Site collection locks Self-service site creation Site use confirmation and deletion

21. Ownership, Administration, and Access Assign site collection ownership  Application Management  Change site collection administrators  Only two. Assigned by farm administrators.  Site collection administrator’s rights + e-mail notifications Assign site collection administrators  Site Actions  Site Settings  Site Collection Administrators  Multiple. Assigned by other site collection administrators.  Full control of site collection + site collection administration tasks Assign permissions to the top-level site 1. Site Actions  Site Permissions 2. Click the SharePoint group to which you want to add members 3. Click New to add users or groups to the group

22. Quotas  Storage limit Warning level to notify site collection owners  Resource utilization (Sandboxed Solutions) Warning level to notify site collection owners Configuring and managing quotas 1. Create a quota template Create a quota template Defined for farm. Available to apply to any site collection. 2. Apply a quota template to a site collection Apply a quota template to a site collection Template associated with site collection Applied to each site on creation  Updating a quota template: does not update existing sites  Applying a new quota template: updates sites

23. Create a Quota Template

24. Apply a Quota Template to a Site Collection

25. Site Collection Locks Restrict site access – overrides all permissions and policies  Unlocked  No access  Read-only  Prevent adding content

26. Self-Service Site Creation Allow users to create new sites within a site collection  Enable or Disable (Default)  Option: Require secondary contact

27. Site Use Confirmation and Deletion Ensure that sites are in use and delete unused sites  Run check for unused site collections and send notices to owners  Automatically delete unused site collections

28. Subsites, Site Collections, and Content Databases intranet.contoso.com Site Collection Top-Level Site Site Collection Top-Level Site HR Engineering Content Database intranet.contoso.com Site Collection Top-Level Site Site Collection Top-Level Site Content Database Site Collection HR Site Collection HR Site Collection Engineering Site Collection Engineering Content Database /depts/

29. Subsites intranet.contoso.com Site Collection Top-Level Site Site Collection Top-Level Site HR Engineering Content Database Ownership, Quotas

30. Multiple Site Collections intranet.contoso.com Site Collection Top-Level Site Site Collection Top-Level Site Site Collection HR Site Collection HR Site Collection Engineering Site Collection Engineering /depts/ Content Database Storage Management

31. Content Database Multiple Content Databases intranet.contoso.com Site Collection Top-Level Site Site Collection Top-Level Site Content Database Site Collection HR Site Collection HR Site Collection Engineering Site Collection Engineering Content Database /depts/

32. Content Database Managed Paths intranet.contoso.com Site Collection Top-Level Site Site Collection Top-Level Site Content Database Site Collection HR Site Collection HR Site Collection Engineering Site Collection Engineering Content Database /depts/ Wildcard inclusion Managed path http://intranet.contoso.com/depts/HR/Pages/benefits.aspx Pages/benefits.aspx

33. Content Databases Site collections and content databases  A site collection cannot span content databases  Out-of-box tools recovery tools require restoration of a content database Scalability support  300 CDBs per Web application CDBs per SQL server dependent on RAM  200 GB per content database is supported  100 GB per site collection  250,000 Web sites per site collection 2,000 under any one Web site Create a Content Database Add a Site Collection to a Content Database

34. Create a Content Database Application Management  Databases  Manage content databases Ensure you’re focused on the correct Web application Add a content database Database name: based on your naming standards

35. Add a Site Collection to a Content Database Create a site in a content database  Central Administration Content database with most available sites - If a tie, the content database with the lowest GUID wins  Windows PowerShell: New-SPSite -ContentDatabase parameter Move site collections between content databases  Move-SPSite

36. Content Database Example Logical Architecture intranet.contoso.com Site Collection Top-Level Site Site Collection Top-Level Site Content Database Site Collection HR Site Collection HR Site Collection Engineering Site Collection Engineering Content Database /depts/

37. Lesson 3: Exploring the SharePoint Web Application and Physical Architecture SharePoint and Internet Information Services (IIS) 7.0 and 7.5 SharePoint Web Application Components web.config SharePoint Root SharePoint Databases Customized vs. Uncustomized Pages

38. SharePoint and Internet Information Services (IIS) 7.0 and 7.5 HttpModules and HttpHandlers participate in all requests to the server ASP.NET configuration integrated in user interface Request auditing and error debugging  Request Tracing for 500 errors.NET API for IIS configuration settings No Metabase  Configuration stored in applicationHost.config Delegated configuration and administration

39. SharePoint Web Applications Components New SharePoint web application  new IIS site  Port and host header binding specified when creating a SharePoint Web app Application pool & associated identity  Efficiency: shared app pool = shared process, overhead  Isolation: separate app pool = separate process, overhead Root directory is a subfolder of c:\inetpub\wwwroot\wss\virtualdirectories  web.config for the SharePoint application  Virtual directories point to other folders, each with its own.NET configuration (web.config) HttpModules are responsible for adding the SharePoint object model properties to the memory space

40. Notes Page Over-flow Slide. Do Not Print Slide. See Notes pane.

41. web.config XML-based file in the root folder of each Web application or virtual directory Sections (XML elements) group the configuration  SafeControls: defines what controls can be used on a SharePoint page.  SafeMode: determines whether pages are allowed to execute in-line.NET code.  MergedActions: allows changes to web.config without actually modifying the file, by merging actions specified in selected and other files.  BlobCache: enables caching various file types in a location on the Web front end, rather than pulling files from the database for each request.

42. SharePoint Root Majority of SharePoint files reside in a single directory on the Web server called the SharePoint Root C:\Program Files\Common Files\ Microsoft Shared\web server extensions\14 Top-level folders TEMPLATE folder Synchronization of the SharePoint root

43. Synchronization of the SharePoint Root You must ensure that the SharePoint Root is synchronized across all Web front-end servers Activities that change the SharePoint root include:  Adding user controls  Adding site definitions  Adding global images  Adding application pages  Adding themes SharePoint solutions  Packages that deploy functionality and files  Similar to a Windows Installer (.msi) file  The farm ensures the solution is deployed to all servers

44. SharePoint Databases Config database: servers and services in the farm Service applications: one or more databases Web applications: one or more content databases  Plus shared content from the SharePoint root Content database  List items, document versions  Workflow instances  Web Part properties  Audit logs  Sandboxed solutions  User names and rights

45. Content Database Tables Each content database contains numerous tables Important tables:  AllDocs: metadata for folders and files  AllDocStreams: files and unghosted pages  AllDocVersions: previous versions of files  AllUserData: data for list and document library items  RecycleBin: deleted items from all sites in the site collection  WebParts: available web parts  Webs: configuration of each site (Web) in the site collection

46. Notes Page Over-flow Slide. Do Not Print Slide. See Notes pane.

47. Customized vs. Uncustomized Pages New site: Site definition generates initial content  Some pages are shared across sites, e.g. DEFAULT.ASPX  Page is actually stored in the SharePoint root Uncustomized page  Resides in SharePoint root  Content of page (e.g., definition of which Web parts appear) is stored in the content database Customized page  Modify the page itself using a tool: SharePoint Designer 2010 .aspx page is stored in the content database HttpModule analyzes URI of request, then gets page from content database or (if page is not there) SharePoint root Service packs overwrite files in SharePoint root

48. Lab: Creating a SharePoint 2010 Intranet Exercise 1: Creating a Web Application Exercise 2: Creating a Site Collection Exercise 3: Creating a Site Collection in a New Content Database Logon information Estimated time: 30 minutes

49. Scenario You have been asked to build an intranet to support communication and collaboration requirements at Contoso, Ltd. You have recently completed the installation of SharePoint 2010. You must now configure the farm using the Farm Configuration Wizard, and create the logical topology to support the initial business requirements. You are tasked with establishing a SharePoint 2010 intranet site so that business users can review the new features of the publishing site definition. Additionally, you have been asked to configure sites to meet the collaboration requirements of several divisions within the organization, so you will begin by creating a site for the Information Technology (IT) department.

50. Module Review and Takeaways Review Questions