2. Todd Klindt That guy Solanite Consulting Shane Young And that other guy SharePoint911 OFC404

3. Who Am I? Shane Young Owner of SharePoint911.com Microsoft Office SharePoint Server MVP Consultant, Trainer, Writer, Speaker, & Towel Engineer for Lakers shane@sharepoint911.comshane@sharepoint911.com @shanescows Blog - http://msmvps.com/shane SharePoint Consulting http://www.sharepoint911.com SharePoint Training http://www.tedpattison.net

4. WSS MVP since 2006 Speaker, writer, consultant, Towel Boy for Rockets Personal Blog www.toddklindt.com/blog Company web site www.solanite.com E-mail todd@solanite.com @toddklindt I consider it an honor and privilege that Shane is so mean to me. todd@solanite.com Who is this Todd Klindt guy?

5. Agenda Farm topologies Install roadblocks Accounts and permissions

6. Topologies SharePoint scales from a single server install all the way to very large farms of servers Uses assignment of roles to span multiple servers

7. Keep in Mind Servers have roles Web Query, Index, Calculation DB Server Farms have relationships Authoring Publishing Dev, Test, Production SSP

8. SharePoint Containment Items Files, calendar items, contacts, customers, images, custom Lists Doc Lib, Pages, Events, Discussions, Surveys, etc… Sites/Webs Internet, Intranet Portal, Wikis, Blogs, Team, Doc, Mtg Site Collections The Bag Databases Content, Config, SSP, Search Web Applications Central Admin, SSP Admin, Content Servers Web Front End, APP, SQL Farm

9. Web Front-End Role Called WFE Provides the web interfaces for the users One to many servers with this role per farm Very little disk storage used 1 to 4 ratio is sweet spot for collaboration

10. Index Role Crawls and indexes the content 1 Index per Server 1 Index per SSP Index Files = 5% - 12% of crawled content 1% - 5% typical if only crawling SharePoint Database Storage = 4 x Index Files 50 Million item tested limit

11. Query Role Server that responds to user Search request Physical storage = 2.8 x Index No hard limit on number of servers Scale stops at 7

12. Excel Calculation Role In MOSS Enterprise farm this server handles calculating Excel Workbooks Also called Application Server Rendering components live on WFEs Calculation engine moved to own server No limit to number of servers Sizing is very complex

13. Topologies Spread the roles out across as many servers as you need and have at it No restrictions

14. Single Server Farm

15. Small Farm

16. “Medium Farm” Considered Minimum High Availability Topology

17. A Possible Large Farm

18. Do not Choose Basic! Unless you want to use SQL Express and Local System Account

19. Server Type Complete – used 99.9% of the time. Installs all components and gives you complete configuration flexibility. Web Front End – only installs web components of MOSS. Doesn’t give you the option of later hosting other roles. No Flexibility = bad. Stand-alone – exact same as previous slide choosing basic. Refer to that slide if you are tempted to use.

20. Install Accounts First choice – 1 account for everything or account isolation Account isolation has lots of challenges Second Choice – NTLM or Kerberos

21. NTLM vs. Kerberos Kerberos is generally preferred No double hop problem More secure Less authentication traffic Downside Requires extra work to setup Domain needs to be in order (Server time off by > 5 minutes and auth fails)

22. Accounts you will need (MOSS) Setup User Account * – used for running install and to admin server Server Farm Account * – central Admin App Pool Account, Timer Service Account SSP App Pool Account SSP Service Account – all SSP services and jobs MOSS Search Account – used by search service. Also become default content access account for search. You can change from the SSP level * Account needed for WSS

23. More accounts (MOSS) WSS Search Service Account * – used by the help system crawler WSS Search Content Account * – used to access the data by the help system crawler Application Pool Identities * – the account used to access the content databases for the web app. Also account for w3wp.exe * Account needed for WSS

24. SetSPN.exe Used to define Service Principal Names (SPN) An SPN is a multi valued attribute stored in AD for users Services only know how to use them to request a ticket Example SPN = HTTP/server.domain.com Experience says this stuff is case sensitive

25. Account Setup Before Install Single account install – Make account local admin on all boxes Secure multi-account Install Setup Account – domain User, local admin on all servers you install MOSS on, SQL Server login with SecurityAdmin and dbcreator roles All other accounts – domain User. Setup/config will automatically grant necessary rights

26. Updates Non SP1 support ended 1/13/2009 SP1 For more information on how to deploy it http://msmvps.com/blogs/shane/archive/2007/12/ 14/how-to-install-wss-and-moss-sp1.aspx Infrastructure Update Lots of cool new Search functionality Post IU update for AAM fixes February Cumulative update and SP2 available

28. www.microsoft.com/teched Sessions On-Demand & Community http://microsoft.com/technet Resources for IT Professionals http://microsoft.com/msdn Resources for Developers www.microsoft.com/learning Microsoft Certification and Training Resources www.microsoft.com/learning Microsoft Certification & Training Resources Resources

29. Track Resources Spin the Wheel: Attend SharePoint breakout sessions Mon-Thurs and collect the picture of the day. Come by the booth for a chance to spin the SharePoint wheel. Collect all 4 pictures and enter to win a Microsoft Arc Mouse, drawing 11:30am on Friday, game cards at the booth. Product Info http://www.microsoft.com/SharePoint Product Info http://www.microsoft.com/SharePoint http://www.microsoft.com/SharePoint Dev Resources SharePoint MSDN Web Site:http://msdn.microsoft.com/sharepoint http://msdn.microsoft.com/sharepoint SharePoint Developer Resources:http://mssharepointdeveloper.com/ http://mssharepointdeveloper.com/ SharePoint Conference 2009 www.mssharepointconference.comwww.mssharepointconference.com ITPro Resources SharePoint Tech Center: SharePoint Tech Center: http://technet.microsoft.com/en-us/office/sharepointserver/ http://technet.microsoft.com/en-us/office/sharepointserver/ SharePoint Best Practices: SharePoint Best Practices: http://technet.microsoft.com/en- us/office/sharepointserver/bb736746.aspx http://technet.microsoft.com/en- us/office/sharepointserver/bb736746.aspx

30. Attend an Interactive Theater Session and enter to win a Microsoft ARC Mouse Wednesday’s Picture is : Box shot Attend any SharePoint Breakout Session day 1 – 4 and check the last slide for a daily picture. Come to the TLC yellow area, SharePoint booths OFC 4 & 5 to spin the wheel for a chance to win a prize. The wheel only spins when the SharePoint spotlight is flashing. One spin per person. Collect all four daily SharePoint pictures and enter to win a Microsoft ARC Mouse. Game cards can be picked up at the booth. Drawing for Mice on Friday at the wheel at 11:30AM. Collect the SharePoint Session Picture of the Day

32. Complete an evaluation on CommNet and enter to win! Required Slide

33. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Required Slide