SharePoint 2010 enterprise implementation
•
0 recomendaciones•688 vistas
This presentation details best practices for successfully planning your SharePoint 2010 Enterprise Deployment.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a SharePoint 2010 enterprise implementation
Similar a SharePoint 2010 enterprise implementation (20)
Último
Último (20)
SharePoint 2010 enterprise implementation
- 1. Planning Enterprise Implementation of SharePoint 2010 Date: 04/13/2010 Nilesh Mehta Sr. SharePoint Architect NGenious Solutions, Inc. E-mail: Nilesh.Mehta@ngenioussolutions.com | © (201) 230-7922 | http://www.ngenioussolutions.com
- 3. Agenda SharePoint 2010 Top Features Installation and Configuration Small, Medium, Large Farms Managed Accounts Database Management Authentication options Windows Classic Claims FBA Setup SharePoint Services Setup Service Applications Search Configuration and Management Kerberos setup My Sites User Profile Synchronization Setup
- 4. SharePoint 2010 Top Features UI Office Web Applications Document Management Search Metadata Management Business Intelligence Components (BCS, ECS, PerformancePoint, Visio Graphics) My Sites Sandbox Solutions Administration PowerShell Restore Options SMS integration SharePoint Designer Lockdown from Central administration
- 5. Installation and Configuration Pre-Requisites: Windows Server 2008 x64 (Recommended R2) SQL Server (2005 / 2008) x64 (Recommended R2) IIS 7.0 IE 7 and above, Firefox 3.6, Safari4.04 Small (Single Server) Medium (1 WFE, 1 APP, 1 Search, SQL) Large (1+ WFE, 1+ App, 1+ Search, SQL Cluster)
- 6. Large Farm Setup Generic Steps to setup Large farm (2+ WFE, 2+ App Servers, Search Index, Search Query, SQL Cluster) Prepare servers with base W2K8 R2 OS Run SharePoint pre-requisites on all servers in the farm (Also downloads SP for W2K8 if necessary and configures IIS) Run SharePoint configuration wizard on the first server in the farm. Host Central administration site (Note: Second screen, requirement for Passphrase. Save this information properly) Finish Configuration Wizard Running SharePoint Wizard – Always run but create only following service applications: Application Registry Service State Service Finish configuration on server one
- 7. Managed Accounts Register different service accounts that you would like to use with your farm Recommended accounts: Farm Admin Account Service Application account Application Pool Account Search Account Maybe allow SharePoint to manage passwords for managed accounts?
- 8. Contd. Large Farm Setup Run SharePoint Configuration wizards on other servers. Join server to farm. Identify services that will run on each server( WFE vs. App) Manually create remaining service applications. Give Proper Names to SA and also corresponding databases. NOTE: Do not create Search Service application. You will create this when your Search server is joined to the farm
- 9. Office Web Applications Install Office Web Applications binary on each server in the farm Run SharePoint Configuration Wizard on each server in the farm (One at a time) Run the Central administration wizard but do not create the Service Application for Word Viewing and PowerPoint. Manually create them so you can give proper database names Start Word Viewing and PowerPoint services on the servers where you want them.
- 10. Setup Services / Service Applications on the Servers Reference SPEnterprise.vsd
- 11. Database Management Number of Databases created in SharePoint 2007: 4-6 maximum Number of Databases created in SharePoint 2010 ~15 databases Follow governance similar to MOSS 2007 for Content Databases, for example, group by collaboration sites vs. Highly visible vs. large sites vs. custom applications in content databases Make sure to hire a dedicated SQL Server admin
- 12. Authentication Options Windows Classic NTLM Negotiate (Kerberos) Windows Claims NTLM Negotiate (Kerberos) FBA
- 13. Kerberos Setup Setspn -A HTTP/wfe1.company.com Setspn -A HTTP/wfe1 Setspn -A HTTP/wfe2.company.com Setspn -A HTTP/wfe2 Constrained Delegation for: WFE1: Add constrained delegation and point to APP1 & APP2WFE2: Add constrained delegation and point to APP1 & APP2 APP1 (Should have SPN - dummy) Then add constrained delegation to server account: APP2, add domainerviceaccount ->MSSqlSVC/sqlserver.company.com for all authentication providers. NOTE: Make sure you do not have duplicate SPN’s in the farm. Between missing SPN’s or duplicate SPN’s, these would probably cause 90% of Kerberos setup issues
- 14. Search Setup & Configuration Identify Search Index and Query Server Create Search Service Application and use appropriate servers Create separate application pools for Search Admin and Query service Search service account should have read only permissions Search Topology – How to manage and modify?
- 15. My Sites Home Page Newsfeeds My Content My Profile Status Updates Quick Launch in My Sites Profile Pictures
- 16. User Profile Synchronization The feature that most people are having issues configuring Allows import of user profiles from multiple sources like AD, SUN LDAP, etc. Can use normal connection or BCS for import User FIM client for additional help. Microsoft now supports modifications from FIM client. Manage My Site settings from here.
- 17. Feature List UI Office Web Applications Document Management Search Metadata Management Business Intelligence Components (BCS, ECS, PerformancePoint, Visio Graphics) My Sites
- 18. NYC SharePoint Developers User Group Nilesh Mehta will be speaking at the NYC SharePoint Developers User Group on 4/20/2011 – Topic: SharePoint 2010 Claims Authentication http://www.sharepointusergroup.com/newyork
Notas del editor
- As we all know, with any technology, if it is not configured or planned for use properly, it will be just another technology in the stack. SharePoint will fall in the same bucket unless you plan properly. What does that mean for us? What it means is to plan ahead for the features that bring benefit to your organization (even if you have been using MOSS 2007 and are just upgrading to 2010), understand how these features work, what does it take to configure our environment so that it can provide these features in a stable and scalable manner, how do we support the environment, what is our roadmap? The worst thing you can do with any platform is to use it only for a specific purpose and not understand the full benefits of the platform. In case of SharePoint, success can be defined as any of the following:Successfully implement infrastructureSuccessfully create hundreds of sites enabling better collaborationSuccessfully leverage SharePoint featuresSuccessfully create business process automation or portal solutionsSuccessfully socialize on SharePoint platform with your colleaguesSuccessfully support the platform and consolidate multiple repositories into a single repository. The goal of the session today is to help understand some of the best features, how / where to use them, successfully implement the infrastructure for SharePoint 2010 (In my view), how to setup your farm so you can support these features and if time permits discuss some governance and support around these.Questions:How many of you are new to SharePoint 2010? Should we start with basic level session or advanced level session?How many business users vs. Administrators vs. DevelopersHow many of you have installed SharePoint 2010?What kind of farms?
- Enterprise planning of SharePoint 2010 would include the following: planning for SharePoint UI, SharePoint Features that you can support (includes Document management features, search, BI, etc.), Server architecture, Database management, planning for scalability, Governance and support. SharePoint is a huge platform and very easy to adopt if implemented the right way. The more you invest in it, the more returns you can get from it.
- UI: Ribbon navigation, Wiki Anywhere, Context Sensitive Menus, missing breadcrumb, AJAX page refresh.Office Web Applications – Word, PowerPoint, Excel, OneNote. Co-Authoring online for everything except PowerPoint. PowerPoint co-authoring from client side only.Document Management consists of a few different types of feature that I like: Content Organizer, Document Sets, Document ID, etc. Search: SharePoint Search and FAST Search. Much more reliable, stable and scalable from the previous version. We will cover some of it later in the session.Metadata management- Term Store concept to implement enterprise wide metadata terms, Content Type HubBusiness Intelligence components – Collection of BCS, Excel Services, PerformancePoint, Visio graphics. BCS the one with the most potential.
- Scripted install using PowerShell – Sample Scripts at http://technet.microsoft.com/en-us/library/cc262839.aspxSmall and Medium farms the same way as in MOSS 2007, with the exception of Passphrase and managed accounts.
- Discuss details on how Services can be organized for the farm, just for load balancing and also from Kerberos perspective.
- Where should you run Central administration from?If you run in to issue with User Profile Synchronization Service, I will cover those issues at the end of the deck and also have some additional material in a presentation that I did in December found at http://www.SharePointUserGroup.com/NewYork
- When setting up SharePoint, take care not to allow SharePoint to create all your databases for you. SharePoint will create databases with the guid’s in there and will make it difficult for you to identify them in the future. I had a session on SharePoint data and database management about 3 years ago. The same still holds true for SharePoint 2010 in a lot of ways. You can find it at http://www.sharepointusergroup.com/newyork
- Reference Visio Diagram for SPEnterprise.vsd. Add screen shots for setspn, and how to setup constrained delegations.
- With Search topology, show different components of the topology, how to manage them, move them from one server to another, how / when to create additional components? For FAST Search, check out Carlos’s session later in the day.
- Talk about how to import pictures for profiles.