Your SlideShare is downloading. ×
  • Like
Sharepoint Best Practices
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Sharepoint Best Practices


Sharepoint Best Practices, evento sharepoint, , corso formazione, corsi, sharepoint training

Sharepoint Best Practices, evento sharepoint, , corso formazione, corsi, sharepoint training

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Best Practices
    Michele Adamo
  • 2. Sommario
    Estimate performance e capacityrequirements
    Information Architecture
    Manage Security
    Document Management
    SharePoint Branding
    Solution Development
  • 3. Estimate performance e capacityrequirements
    The primaryfactorsthat affect a SharePoint Server Farm ares:
    Server and Network hardware
    Software Configuration
    User Load
    Traffic Profiles
  • 4. Estimate performance e capacityrequirements
    • Plan for highavailability
    Insertingat least two WFE server issufficent to providehighavailability for thousandusers in an out-of-box configuration
    • Plan for operational excellence
    64-bit hardware (for all server roles)
    Allocate at least 2 gigabytes (GB) of RAM per processor for front-end Web servers and application servers.
    Allocate at least 4 GB of RAM per processor for database servers.
    Consider Guideline for Acceptable Performance
    50.000 Site Collection per content db
    250.000 subwebs for Site Collection
    5.000.000 Items per List
    2000 Items per List View
  • 5. Information ArchitectureSite Collection vs SubSite
  • 6. Information ArchitectureSite Collection vs SubSite
    • Scalability
    MS recommend to limit content database size to 100GB
    • Backup & Restore
    Full fidelity backups are only possible at the site collection level
    If a sub-site needs to be restored then the entire site collection must be restored
    3rd party solutions offer full fidelity recovery at more granular levels
    • Security
    Site Collections allow security groups and permissions to be isolated from other site collections
    • Search
    Search Scopes are defined at the site collection level
    Settings must be manually (or programmatically) synchronized across site collections
  • 7. Information ArchitectureSite Collection vs SubSite
    • Audting
    Policies can be created at the site collection scope
    No built-in mechanism for synchronizing policies across site collections
    • Recycle Bin
    Each site collection has a first and second stage recycle bin
    First stage counts towards the quotaSecond stage does not count towards the quota. Be aware of the defaults – 30 days in the first stage and 50% of the site quota for the second stage, if there’s no quota then the second stage will grow infinitely.
  • 8. Information ArchitectureSite Collection disadvantages
    • Each site collection, insists to have it's own Menuyou must implement a consistent navigation between multiple site collections through CustomSiteMapProvider or XML SiteMap.
    Content Type & Site Column are Site Collection levelUse must use Features to deploy Content to multiple Site Collections
    Management is more complex with site collections No OOTB way to synchronize settings across site collections!
  • 9. Cross-Site Configurator
    Solution Accelerator from MSFT
    The tool automates the process of deploying site settings in all or selected sites in a server farm:
    Applying Master Pages across a SharePoint server farm.
    Setting up Web Titles for all or selected site collections across the farm.
    Applying audit control settings to all or selected sites.
    Adding advanced settings such as “Allow content type management” to all types of lists.
    Adding a new Expiration Policy at the site collection level.
    Adding a new Expiration Policy to content types, lists, and documents.
  • 10. Control Site Collection growths
    • Limit Max Versions
    • 11. Use versioning only if required
    • 12. Use Quotas
    • 13. Monitor Second Stage Recycle Bin
  • Manage Security
    • Add users and domain groups to the permission level/cross site group (site collection groups)
    • 14. Allow site administrators to assign permission directly
    • 15. Break Permission inheritance must be an Exception!
    • 16. Third-party tools:AvePointBamboo User ManagerDeliverPointSushi
  • Manage Security
    • Add users and domain groups to the permission level/cross site group (site collection groups)
    • 17. Allow site administrators to assign permission directly
    • 18. Break Permission inheritance must be an Exception!
    • 19. Third-party tools:AvePointBamboo User ManagerDeliverPointSushi
  • Manage Security
    • Audiences are not security objects, they can be used for targetting content.
    • 20. Can I Deny user?There is no granular or deny at a site level but you can do a deny at a web application level with a webapplication policy.
  • Manage Security
    • SharePoint Authentication Methods:
    Windows Authentication
    Anonymous access
    Form Based Authentication
    • Extend Web Application to allow more entry Point
  • SharePoint Branding
    What tools should I use?
    • Native in-BrowserSimple Branding (Themes, Navigation, Logo)
    • 21. MS SharePoint DesignerEnd-Users adequately trained can obtain more page customization Define Content Types & Metadata
    • 22. Visual StudioMore complex customizations
    There is no single best way, you should consider an appropriate mix
  • 23. SharePoint Branding
    • Use Master Pages to define Look & Feel of Site
    • 24. Branding features in publishing infrastructure:
    • 25. Master pages inheritance throughout site collection
    • 26. Alternate CSS URL to override Default SharePoint Core.css
    • 27. Using Page Layouts, customization will be placed in a associated content Type in the pages document library
    • 28. Do not change Master Pages & Application pages stored in Templates/Layouts Folder (Upload.aspx, Application.master)
    • 29. Use Site Definitions to globally deploying customizations
    • 30. Site definition are stored in file system
  • Solution Development
    • Use SharePoint Solution Package
    • 31. Visual Studio 2005/2008 Extensions
    • 32. STSDEV
    • 33. WSPBuilder
    • 34. Take advantage of native SharePoint CapabilitiesSharePoint includes a suite of Web Parts
    • 35. Many problem solved with:
    • 36. Custom Custom Content Types and custom associated list form(Disp/edit/New)
    • 37. Custom Action
    • 38. Do not use custom field type No support for advanced list functionality(Datasheet)
  • Solution Development
    • Do not insert/enable code in Content Pages
    • 39. Not supported
    • 40. Create ASP.NET Virtual subdirectories in Layout folder
    • 41. Developer with ASP.NET Skills
    • 42. Be aware of use ASP.NET User Controls Wrapper(SmartPart)
    • 43. Not included in SharePoint Standard Deployment
  • Solution Development
    • Memory management for SharePoint Object
    • 44. Dispose SPSite and SPWeb
    • 45. Do not dispose Context object
    • 46. Use List Event Receiver for Data Validation
    • 47. Only server side
    • 48. Use caching mechanism
    • 49. ASP.NET Cache Object
    • 50. Implement Async Web Part for potentially slow data source(Web Service, Legacy Databases)
  • WorkFlowDevelopment
  • 51. Document Management
    • SharePoint do not replace File Server
    File servers are usually cheaper solution than SharePoint
    File server are prefered for large storage(Up to 2GB)
    Define Content Types & Metadata
    Understanding data elements in your Organization
    For use the same content type across site collections, you need to develop features content types.
    Approval Workflow
    Use AD security groups to specify approvers