Share Point Infrastructure And Setup


Published on

  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Share Point Infrastructure And Setup

  1. 1. SharePoint Infrastructure and Setup<br />Greg Kamer – The Mirazon Group<br />
  2. 2. MCSE:2003, MCTS: MOSS 2007, WSS 3.0<br />Working with SharePoint for nearly 3 years<br />Blog:<br />Twitter: @gregkamer<br />Email:<br />I desire to see a strong community built around SharePoint<br />About Me<br />
  3. 3. Windows Server Administration <br />IIS Experience<br />SQL Experience<br />You DON’T have to be a DBA<br />You need to get comfortable with SQL<br />99% of all content in SharePoint is stored in SQL<br />Fundamentals<br />
  4. 4. Windows SharePoint Services 3.0 (WSS 3.0)<br />Search Server & Search Server Express (MSS & MSSX)<br />Microsoft Office SharePoint Server 2007 (MOSS 2007) <br />Comes in both Standard and Enterprise flavors<br />Versions of SharePoint<br />
  5. 5. SharePoint Structure (aka the “World’s Greatest Slide”)<br />
  6. 6. Proper planning is the basis of a healthy, well structured farm.<br />Planning can save you from lengthy and costly re-architecting of your farm<br />Don’t skimp; take the time to do it right the first-ish time!<br />Free e-book<br />Planning<br />
  7. 7. Web Front End (WFE) – All versions of SharePoint<br />Query – Search Server & MOSS<br />Index – Search Server & MOSS<br />Excel Calculation Services – MOSS only<br />Every role has a design consideration!<br />Server Roles<br />
  8. 8. Applies to all versions of SharePoint<br />Serves up content to users<br />Can host other roles as well (careful planning required)<br />Can be made highly available and scaled out via load balancing – Microsoft NLB, Third Party vendors<br />Web Front End<br />
  9. 9. Exists in Search Server and MOSS farms<br />Answers search queries from users<br />Can be made redundant<br />In larger farms avoid placing the query and Index server roles together<br />Query Server(s)<br />
  10. 10. Available on Search Server and MOSS only<br />Responsible for crawling content (web sites, SharePoint sites, file shares, etc)<br />CANNOT be made highly available (MSFT only supports one index per Shared Service Provider)<br />Scale according to content to be crawled.<br />Search results can still be returned even if Index is offline. New content will NOT be added until brought back online.<br />Index Server<br />
  11. 11. Sometimes called “application servers”<br />Scale by themselves with little admin intervention<br />Can be on dedicated servers if need arises<br />Excel Services Server <br />
  12. 12. Install Types<br />Service Accounts<br />Configuration Wizard<br />Proper Setup<br />
  13. 13. Types of Installs<br />Basic – Don’t click it…really. Nor Advanced then Stand-Alone<br />Installs all components on one server using local account credentials (NT AuthoritySystem, etc)<br />Advanced – gives the flexibility to grow the farm<br />
  14. 14. Basic Installs are BAD<br />
  15. 15. Install as either Complete or Web Front End Only<br />Complete allows for more flexibility in the future<br />Even if a single server install, it is still advisable to use the complete option<br />Advanced Installs<br />
  16. 16. Proper planning is essential -<br />Consideration <br />Passwords are cached in a “black hole” <br />Service accounts passwords cannot just be changed in the services console.<br />App Pool accounts cannot be changed in just IIS manager<br />STSADM is your friend<br /><br />Service Accounts<br />
  17. 17. Create a custom account for administering SharePoint (SPAdmin)<br />All accounts can be plain-Jane domain user accounts<br />Add SPAdmin and farm accounts to local admins on each SharePoint server<br />In SQL give SPAdmindbcreator and securityadmin rights<br />SharePoint gives least privelages to each account (except DBA creation mode)<br />Service Accounts (cont’d)<br />
  18. 18. Allows for creation of new farm or adding (or removing) servers to a farm<br />Need SQL server name and Farm account name and credentials<br />Some antivirus programs can make this fail (Symantec Endpoint Protection is one I have run into)<br />Select Authentication for Central Admin site<br />Config Wizard<br />
  19. 19. NTLM<br />Works OOB<br />Kerberos<br />Requires extra steps to configure<br />SetSPN or ADSIEdit<br />FBA<br />Anonymous<br />Other<br />Live Federation<br />ASP.NET<br />Authentication<br />
  20. 20. Keep all Content DBs under 100 GB<br />Not for scalability reasons; more for backup and restores<br />Tables can be locked during backups<br />Site collections cannot span multiple DBs<br />Virtualization<br />Debate in the SharePoint community<br />WFEs are great candidates; Index servers and SQL are debatable<br />Best Practices<br />
  21. 21. Backups<br />Backup GUI in Central Admin<br />Not able to be scheduled<br />WILL get both Index DB and file simultaneously<br />STSADM Command Line<br />Can be made into a scheduled task.<br />May cause table locking issues in SQL DB with larger site collections (40+ GB)<br />Neither provide restore or single items or sites (without great pain!)<br />Third party<br />AvePoint, Idera, Microsoft Data Protection Manager<br />Best Practices (cont’d)<br />
  22. 22. Server OS – Server 2008<br />IIS 7 and SharePoint run together very well and have performance advantages over IIS 6/Server 2003<br />Go x64! SharePoint 2010 will be x64 ONLY.<br />SQL, 2005 or 2008, but go x64 as well.<br />2000 SP4 is supported, but it suffers from performance issues and BI is severely limited.<br />Best Practices (cont’d)<br />
  23. 23. Q&A<br />Don’t be afraid to play, it’s a resilient platform.<br />Thank you!<br />