Presentation Transcript

1. Managing and Using Microsoft SharePoint 2010 by Gerard Beckerleg
2. Course Website http://www.ssw.com.au/SSW/Events/ Course Materials
3. Part A: SQL Server 2008 for Developers Sessions Part A SharePoint Concepts and Use
4. Part A: SQL Server 2008 for Developers Sessions Part B SharePoint Configuration and Admin
5. Session 10: SharePoint 2010 Deployment and Configuration
6. Session Objectives and Agenda Planning Hardware and Software prerequisites Installing Installation types (single server, farm) Planning services applications Customizing Deploying solution features
7. Planning
8. Planning the Farm SharePoint means different things to different people SharePoint is not a turn-key server product like Exchange Every organisation will use it to solve a different problem The biggest problem is a lack of planning
9. What you need to look at Hardware & Topology Software & Installation Operating System Virtualisation Skill set for Administration
10. Deploying SharePoint is just like deploying a software system Must understand the Software Development lifecycle Planning Development Review User Acceptance Testing Rollout Support Decommission A good project has a large proportion of the total time in the support phase
11. Create a Plan that includes Stakeholders Business needs being solved Project description Site structure Security Search External access Software requirements / Hardware requirements Schedule Some aspect of SharePoint are difficult to change once set
12. Development Phase Set out the business needs clearly Prepare the server Install the software Configure SharePoint features Create the site structure and branding Set the site security
13. Review Phase Meet with stakeholders Compare solution against business needs Gather feedback and change requests Make the changes Schedule a follow-up meeting with stakeholders
14. Rollout Deploy Train users and set user expectations Handle initial support requests Monitor servers
15. Support Create Site Templates Mail-enable lists Manage users MySites Create and manage quotas Use STSADM to maintain the server
16. Database Server Support Microsoft SQL Server databases only The 64-bit edition of Microsoft SQL Server 2012 The 64-bit edition of Microsoft SQL Server 2008 R2 The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2 The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3) SQL 2008 Express Edition – Only for tiny installations < 4GB All content is stored in DB, so quickly becomes full!
17. Client Support Ideally consistent client OS Target screen resolution Version of Office is very important Recommend 2010 Professional Can use Office 2003 or 2007 IE 9 – recommended Also works on most browsers
18. Based on ball-parks Extra small: < 200 users Single 64-bit Four Cores with 4GB Small: 200 – 1k users WFE 64-bit Four Cores with 2GB SQL 64-bit Four Cores with 4GB Medium: 1k – 10k users 2 x WFE 64-bit Four Cores with 4GB 1 x Index Server 2 x SQL 64-bit Four Cores with 8GB Large: 10k++ users Multiple 64-bit Four Cores 4GB Multiple SQL clusters 64-bit Four Cores 16GB
19. Calculate User Base 1 employee = 1 user 1 external user <= 1 user 1000 users = 1 request per second
20. Calculate Storage Base Existing file shares Exchange public folders Calculate storage growth rate Understand some files will be redundant Estimate per department site per year (10-30GB) Estimate per record center per year(10-30GB)
21. Availability Server OS updates / service packs SharePoint updates / service packs / cumulative updates Hardware maintenance Unforseen problems Accidental deletions / backup restore Avoid downtime via a minimum 5 server farm (2 x WFE, 2 x SQL, 1 x Index Server)
22. Planning Network Configuation Naming http://subdomain.company.com Bandwidth LAN normally no issue WAN need to monitor Alternate access mapping (URL)
23. Extranet Access VPN Direct port access Reverse Proxy (ISA or TMG) Active Directory vs Form Based Authentication (FBA) Always provide SSL for FBA e.ghttp://employees.mycompany.com – Active Directory e.ghttps://partners.mycompany.com - FBA SSL should be used for any site with sensitive data/documents
24. Installing
25. SharePoint installation in 3 stages Run the setup exe Installs prerequisites and puts the DLLs and files in the right places SharePoint Configuration Wizard Installs the databases, sets up the Central Administration site Central Administration configuration wizard Installs the Service Applications in the farm
26. Installing SharePoint Default settings are not generally suitable for production You may have to install / reinstall several times to get production settings right as you learn Consider using virtualisation of the OS
27. Gathering Prerequisites DNS name that SharePoint will use (internal and external) Logon information for accounts that SharePoint will use (Admin, SQL) SQL Server instance name SMTP server for outgoing email
28. Server Requirements Windows 2008 R2 64 bit Four Cores only > 4GB Memory > 2GHz processor NTFS file system without compression Application Server role (IIS, ASP.NET) .NET 3.5 (sp1) feature SMTP feature
29. Use an Install Check List Enter values for each prerequisite Enter hardware and OS values Compare Hardware and OS against base thresholds Think about using a Sysprep image (up to stage 1)
30. Install Download appropriate SharePoint SharePoint.exe for SharePoint Foundation OfficeServer.exe for SharePoint Server Extract files CMD> SharePoint.exe /extract:path CMD> OfficeServer.exe /extract:path OfficeServer includes all file from foundation All change after SharePoint 2010 SP1
31. All-in-One Farm All SharePoint roles and SQL Server on the same server SQL and SharePoint content for resources OK for extra small installation without a lot of load OK for staging or development OK for physically isolated secure server (e.g self-contained in DMZ, or development)
32. SharePoint Stand-alone Can’t add additional WFE SQL and SharePoint compete for resources All data is stored on C: and extra configuration is required to use a separate data disk
33. Dedicated SQL Database Server Physical SQL Server All SharePoint roles on single server High disk IO contention lessened Greater performance can be gained by configuring hardware on separate servers based on role
34. Smallest Highly-Available Farm 2 Web/Query/Application Servers 1 Dedicated Index Server (With Web role to allow it to crawl content) 2 SQL Standard Edition Cluster Nodes (Active/Passive) This is the smallest fully redundant farm
35. Disk, Memory, and Processor SQL Database role requires a great deal of space, especially if versioning is turned on in Document Libraries. Don’t underestimate this! Index and Query servers also need hard drive space The more memory and processor cores that can be given to SharePoint the better, in the following priority: Database Role Index Role Web/Query Role
36. Virtualization Windows Server 2008 Hyper-V is a good option, and can save money. Microsoft supports third party if they are a member of the SVVP (KB 897615), this includes VMware and Citrix XenServer. There are some limitations, consult the KB article. Not all roles should be virtualized, depending on the level of disk I/O that is expected. The best candidate for virtualization is the Web/Frontend, followed by Query, then Index, and finally SQL.
37. Operating System Highly recommended: Windows Server 2008 R2 for security, performance (client/server traffic improvements), and ease of setup Enterprise Edition of Windows only required for very large SQL instances (More than two cluster nodes, high transaction volume, etc.) Standard edition of Windows is adequate in all other cases.
38. SQL Server SQL Server 2008 R2 Recommended, particularly if you have high security requirements, as it allows for transparent encryption of databases Enterprise edition of SQL only required for more than two nodes in a cluster, Asynchronous database mirror replication, and/or greater than 32GB RAM Use a SQL Alias to make it easier to move SharePoint configuration database to a new server in the future Separate Reporting Services server may be required for intensive reporting
39. Installation Best Practice Only install SharePoint Server Enterprise Edition if using advanced functionality such as Insights, Excel Services or Enterprise Search SharePoint Standard Edition is suitable for most companies, can upgrade the farm later Once upgraded to Enterprise edition, farm cannot be downgraded
40. Service Accounts Never use a single account for all services unless it’s a test farm. At a minimum, create the following accounts: SQL Admin Account Installation Account (Local admin rights on SP servers) SharePoint Farm Admin (Requires local admin rights on SP servers, SQL DBCreator and SQL Security Admin on SQL box) Search Admin (Requires local admin rights on any Query or Index servers Default Content Access Account (Read-only access to all indexed locations) Application Pool Identity Account (at least one, can use multiple for each App pool.) It is critical for security that this isn’t the farm admin account.
41. Setup.exe Run the setup exe SharePoint Configuration Wizard Central Administration configuration wizard
42. Scripted Installation Good to understand how to install SharePoint from the command-line, especially if setting up multiple servers. Allows for options not available in the GUI, such as the option to rename the Central Admin Database to something easier to understand. Use SETUP, PSCONFIG and STSADM to script the install process, check online blogs for details.
43. SharePoint Configuration Wizard Run the setup exe SharePoint Configuration Wizard Central Administration configuration wizard
44. Running the Config Wizard to Install Consider using an easy to remember port for the Central Admin service (i.e. 8888) Change the Config Database name to match a common naming convention Your database access account is the SP Service account, which only needs dbcreator and Security Admin rights (db_securityadmin) on SQL. Don’t give it more!
45. Use a DNS SQL Alias Prepare yourself and don’t forget to use a SQL Alias when creating the SQL Config Database. For example, if your SQL server name is ‘SQLSERVER1’, use something like ‘SPSQL’ to connect, and have DNS point to the proper server location. Later your will praise this flexibility.
46. Adding Additional Farm Members Run the Config Wizard on all remaining servers to add them all to the farm. Consider running SharePoint Central Admin on your web front-ends for redundancy (Advanced button). After adding to farm, configure the roles on the servers.
47. Service Applications Run the setup exe SharePoint Configuration Wizard Central Administration configuration wizard
48. Web Application Best Practices Highly, highly recommended to create multiple Web Applications, even for smaller farms, i.e.: SP Central Admin Web App ssp1.mycompany.com mysite.mycompany.com home.mycompany.com
49. Web Applications Best Practices Consider using unique hosts headers when creating the web applications, even if you will separate by IP later. This helps when provisioning new web front-ends. For Central Admin Web Apps you can use NTLM for convenience, but highly consider Kerberos for enterprise (multi server environments).
50. Configuration : Best Practices For Email enabled content, create a dedicated Organisational Unit (OU) for Email enabled contacts and distribution lists and give the SP Admin account rights to create and modify contacts and groups in that OU. Use the Index server (if a separate role) as a dedicated server for crawling content, to do this you have to turn on the web role, however. You can use multiple web applications that are ‘extended’ if you need to provide multiple access mechanisms to the same content.
51. Configuration : Best Practices Don’t forget Alternate Access Mappings if connecting to the content in more than one way (i.e. https://home.mycompany.com vs. just http://home) If using SSL on a web app, it must have a dedicated IP address, not just a host header Don’t forget to install Antivirus (MS Forefront Security for SharePoint recommended) Don’t forget a comprehensive backup solution (MS System Center Data Protection Manager (DPM) recommended)
52. Installing Customization Packages
53. SharePoint customizations are called Features You have already seen them everywhere – in Site Collection Features, in Site Features etc There are also Web Application Features and Farm features
54. Remember the beginning Farm Web Application Site Collection Site Sub Site
55. Features everywhere! Site feature – customizations relating to a list, or content type Site collection feature – customizations to be used by the entire site collection – such as publishing pages Web Application feature – customizations to be used by any site collection in the site, such as configuring your own web services Farm feature – service applications
56. Features are grouped into a Solution Package Windows SharePoint Services Solution Package (WSP) A WSP includes one or more features
57. Deploying features Using Central Administration NOT recommended Using command line tool STSADM
58. The lifecycle of a package (and features) stsadm -o addsolution –filename “C:\MyPackage.wsp” Stsadm –o deploysolution –name “MyPackage.wsp” Stsadm –o installfeature –name “MyPackage.MyFeature” Stsadm –o activateFeature –name “MyPackage.MyFeature” -urlhttp://server/mysite/
59. Tearing it down Stsadm –o deactivatefeature –name “MyPackage.MyFeature” –urlhttp://server/mysite/ Stsadm –o uninstallfeature –name “MyPackage.MyFeature” Stsadm –o retractsolution –name “MyPackage” Stsadm –o removesolution –name “MyPackage”
60. Fixing deployment problems Addsolution -> WSP file now in database DeploySolution -> WSP file now copied to all the server’s SharePoint Hive directory If file in WSP but not in SharePoint Hive – check deployment step ActivateFeature -> Customizations applied into SharePoint If File in SharePoint Hive but not in SharePoint site – check activation step
61. Session Summary There is no ONE way to configure SharePoint, but there are many best practices Plan your SharePoint Use multiple service accounts Separate the DB role from the SP server A five server farm is the smallest that is fully redundant
62. Where Else Can I Get Help? Where else can I get help? Free chats and webcasts List of newsgroups Microsoft community sites Community events and columns Community Portal sharepoint.microsoft.com CodePlexwww.codeplex.com
63. Session 10 Quiz SharePoint 2007 Deployment and Configuration Download from Course Materials Site: http://sharepoint.ssw.com.au/Training/UTSSP2010/
64. One thing gerardbeckerleg@ssw.com.au
65. Thank You! Gateway Court Suite 10 81 - 91 Military Road Neutral Bay, Sydney NSW 2089 AUSTRALIA ABN: 21 069 371 900 Phone: + 61 2 9953 3000 Fax: + 61 2 9953 3105 info@ssw.com.auwww.ssw.com.au