Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

SharePoint Administration

188 visualizaciones

Publicado el

  • Sé el primero en comentar

  • Sé el primero en recomendar esto

SharePoint Administration

  1. 1. SharePoint Administration Planning Architecture, Installation, Configurations, Security and Content V 1.0 Muhammad Zeeshan Tahir MCP, MCSE SharePoint 2013 This document contains some helping guide lines. By following these, it may save time and effort for a SharePoint Administrator. Continue…
  2. 2. Why SharePoint?
  3. 3. Architecture
  4. 4.  Architecture is actually the topology that defines the farm.  Selection of SharePoint architecture depends on the usage, target audience, performance and availability.  Server Roles in the farm  Web Front End  Application Server  Database Server  Mostly considered topologies are defined into three categories  Single Server  Two-Tier Farm  Three-Tier Farm Architecture Roles and Types
  5. 5. What defines the role of a server?  Services provided by a server defines what actually the server role is in the farm. i.e.  Handling user requests > Web Front End  Running SharePoint services > Application Server  Storing content and config databases > Database Server Server hardware and software requirements for SharePoint. Architecture WFE APP
  6. 6. Web Front End  Fast, light-weight server which responds to user requests for web pages. All web servers in a farm are mirrors of each other and are load balanced. Application Server  Provides the service features of SharePoint products and technologies. An application server often provides all or a subset of service features. Multiple redundant application servers can be load balanced. Database Server  Stores content and service data. All databases can be assigned to one database server. Or databases can be spread across multiple servers. All databases can be clustered or mirrored for failover protection. Architecture
  7. 7. Single Server  Good for evaluation, Development, Training and Demonstration.  Best For < 100 users. Note: A Standalone installation is completely different from Single Server Farm installation of SharePoint. A stand alone installation installs SQL instance itself on the same server and use it for SharePoint databases. Uses single account to configure everything and later on cannot add any new server to the farm. All roles in one server including SQL Server + + Architecture
  8. 8. SharePoint Farm vs Standalone  Couple of more differences between SharePoint Farm and SharePoint standalone are…  Using separate account to connect to SQL serverSharePoint server  Using other accounts to manage a lot of services such as: Excel service, Performance Point, setup reverse proxy, setup load balancing  Allow multiple SharePoint servers join into this farm to improve availability.  Multiple SharePoint servers can host Central Administration, Search Index, Search query, Web Application, etc for better performance. Server hardware and software requirements for SharePoint. Architecture
  9. 9. Two-Tier Farm  Can support up to 10,000 users per server.  Can add multiple servers on each level with same roles as below.  Databases are handled separately by dedicated database servers.  User requests handled by the same server running the other SharePoint services. Database Server All Web and Application server roles Architecture
  10. 10. Three-Tier Farm  Split the servers according to their roles.  One web server can support up to 10,000.  Can add multiple servers on each level in WFE’s, Application or Database servers.  Dedicated servers can be added for Search service crawling and indexing. Architecture
  11. 11. Three-Tier Large Farms Example Architecture
  12. 12. High Availability - Failover Server  Failover Server acts as the secondary database server in case of main DB server failure. A witness server is an optional server.  Setting a failover server while creating a web or service application doesn’t create everything for you. It just points to the server and SharePoint checks whether the mentioned server exists or not. Failover Database Server Architecture
  13. 13. Mirroring Log Shipping Replication Always On ArchitectureHigh Availability Database Cloning SQL Server 2012 Enterprise ManualManualAuto
  14. 14. Logical Architecture of SharePoint Architecture
  15. 15. Installation
  16. 16. Service Accounts  Use separate service accounts for each type of service/web application. Min 3  User Profile Service  Search Service  Farm Account  Setup Account  SQL Server Svc Account  Apply AD policy for service account  User cannot change password  Password never expires Installation Required Account Example SQL Server Service Account sqlSvcAcc SharePoint Setup Administrator spAdmin SharePoint Farm Account spFarmAcc
  17. 17. Farm Installation  Always choose Server Farm installation if its not a development machine Installation
  18. 18. Config DB Name  Always try to stick with the default DB name  Changing the name may cause confusion in case of more than one Databases  Note recommended  SharePoint_Main_DB  SharePoint_Config_Prod  SharePoint_Config_Prod_Main  SharePoint2013_Config_Main Installation
  19. 19. CA Port Number  Although the installation wizard suggests a random port during installation but we should stick with a same port number for all of SharePoint environments. My favorite is 9000.  Easy to remember http://CAServer:9000  Not recommended  http://DevCA:23685  http://QACA:41272  http://ProdCA:35714 Installation
  20. 20. Services Auto Configuration  SharePoint provides one click creation of Service Application. Very handy when you have less time to configure the single server farm. However these services should be configured manually with dedicated service accounts. Installation
  21. 21. Configuration
  22. 22. Set Paths to non OS drive  Set ULS logs, SharePoint Web Applications and Search Indexes into non OS drive of servers. This would be helpful when the ULS logs will increase their size, you’ll not have any warning message in CA health monitoring.  Default path for logs is below  Change it to D:SharePointAppsLOGS  Default path for web applications is below  Change it to D:SharePointAppsWebs Configurations
  23. 23. Diagnose Logging  Generally the Diagnose Logging is set to Verbose which consumes more resources on server to write everything in logs.  Change it to Critical and & Unexpected if farm is running fine for all categories.  In case you want to troubleshoot any issue and want to track in logs. Change it to Verbose temporarily. Configurations
  24. 24. Health Monitoring  Keep an eye on Health Monitoring ribbon.  Try to fix the critical errors that may cause any service, web application or farm down. Configurations
  25. 25. Content
  26. 26.  Consistency throughout entire farm  Use complete names, not abbreviations  Not Recommended: MyComp Pvt Ltd  Recommended: MyCompanyPrivateLimited  Avoid spaces to limit population of %20  Not Recommended: My Company Private Limited  Recommended: MyCompanyPrivateLimited Naming Convention Content
  27. 27.  Microsoft recommends not to increase the size of a content database to more than 200 GB. However SharePoint will still work If the size crosses the limit.  A content database can contain 60 million items including documents and list items.  A content database can support 10,000 maximum (2,500 non-Personal site collections and 7,500 Personal Sites, or 10,000 Personal Sites alone).  If a site collection seems to have a lot more data in future, create a separate content database for it to optimize the size.  If a site collection has increased its size which wasn’t expected, don’t worry, you can move the site collection by creating a new blank content DB using PowerShell. Content Databases Size Content
  28. 28. Create More Lists/Libraries  Sometimes the users face the issues related to list view threshold of a list or library.  Try to create List/Library separately categorized by their types and usage. You can create more lists and libraries for managing data and keeping the threshold value less than 5000 items. However if once the threshold value increased, the recommended solutions may give a bad user experience but will work.  Turning off list threshold for a list/library  Adding metadata navigation  List column indexing Content
  29. 29.  SharePoint creates a “Local SharePoint Sites” content source automatically for crawling which is fine for a small level farm where crawling does not take much to complete or have dedicated search servers.  Content Sources must split and configured for each web application so can be scheduled for different times for crawling. Content Sources Content
  30. 30. Security
  31. 31. Permissions Structure  Avoid granting direct permissions on any site collection, site or list/library.  Always use SharePoint groups for permissions.  If there is any site, list or library where new/existing users need to have access frequently, then better way to maintain the permissions structure is to have an AD security group, add all of the target users in that security group and grant permissions to that AD group by adding them in the desired SharePoint group according the permissions level.
  32. 32. References        