Your SlideShare is downloading. ×
SharePoint Natural Disasters: "Notes from the field"
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SharePoint Natural Disasters: "Notes from the field"

865
views

Published on

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
865
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • THIS SHOULD BE YOUR FIRST SLIDE
  • THIS SHOULD BE YOUR SECOND TO LAST SLIDE – Encourage everyone to attend and remind them that BJs Brewhouse is just a few blocks up Bidwell from Three Stages
  • THIS SHOULD BE YOUR LAST SLIDE – Please ensure to leave this on as people are walking out and you’re wrapping things up. Thanks so much!
  • Transcript

    • 1. Welcome to the First Annual
      SharePoint Saturday
      Sacramento!!
    • 2. Notes from the Field
      SharePoint Natural Disasters
    • 3. Who Am I
      Principal Architect SharePoint
      SharePoint Migration
      Architecture
      Strategy
      Quest Software
      Convergent Computing
      Interlink Group
      Microsoft
      adam.woodruff@quest.com
      @adamhadm
    • 4. Agenda
      The SharePoint Disaster
      Definition
      Solution
      Methodology for Success
      Customer Scenario (Notes From The Field)
      Customer Designation
      Issues
      Points to Success
      Lessons Learned
      Summary
    • 5. Problem
    • 6. Defined
      Organizations, Institutions and Departments have implemented SharePoint as a secondary process
      Unrealized expectations
      Failed Goals
      Outages
      In Short “SharePoint is a Disaster”
    • 7. Solution
      SharePoint is Business Critical
      Design, Architecture, Analysis
      Measureable Goals
      Meet the Needs with stages for Features and Release
    • 8. Methodology to Success
    • 9. Project Life Cycle
    • 10. Financial Customer
    • 11. Issues
      SharePoint 2007 Standard
      SharePoint Content DB 1.6 TB (Single DB)
      Two Server Implementation
      21 Days to recover
      Graphic and Media Files
      File Sizes up to 1 GB
      200 Users
      Search Failure
      Metadata minimal
      Versions take up 80% of space
    • 12. Guideline for Success
      Architecture to Scale for Requirements
      Define Business Goals
      Locate Resources
      Resell Intellectual Property
      Validate license validity
      Alert on license expiration
      Control Distribution of Market
      Establish Architecture
      Reduce Version(s)
      Workflow and Alerting
      Metadata Management (Content Types, Tagging)
      RBS Remote BLOB Storage
      Archiving
      Search Importance
    • 13. Updated Strategy
    • 14. Lessons Learned
      Small Organizations, Large Needs
      Financial Impact
      Defined Requirements
      Build to Needs and Measure for Success
      Governance at every level
      Recovery and Disaster Recovery
    • 15. RBS Guidelines
    • 16. HealthCare Customer
    • 17. Issues
      SharePoint 2003 and SharePoint 2007
      Implemented SharePoint 2010 internally
      40 Site Collections
      40 Content Databases
      Fabulous 40 Templates
      71 Custom Templates
      178,000 Public Folders
      Migration Failing
      Compliance Guidelines
      12,000 Users
    • 18. Guidelines for Success
      Determine the Proper Web Applications
      Isolation
      Security Boundaries
      Multi-Tenancy
      Permissions Management
      Site Definitions vs Stapling Features
      Storage Management Solutions
      Compliance Guidelines
      Reporting
      Reduction of Folder Structure
      Migration Process
    • 19. Updated Strategy
    • 20. Lessons Learned
      Reduction of Custom Site Definitions
      Business Requirements
      Reduction of Management Overhead
      Separate Migration Projects
      You don’t know what you don’t know
      Understanding usage and growth
    • 21. Stapling Features
      Feature Stapling allows you to create a feature and then associate it with any site definition without ever touching the site definition files themselves
      Provision as WSP
      Multiple Articles on how this is done
    • 22. Gas/Oil Customer
    • 23. Issues
      SharePoint 2003
      Multiple Event Handlers (30+)
      Company Split
      Customized Lists, Libraries, Sites
      SharePoint 2007 Unstable
      Lack of Governance from Site Level
      Field and Field Types Reserved Names
      Limited Migration Window
      Failed Backups
      Project Server Implemented and Removed
    • 24. Guidelines for Success
      Define the Business Stake Holders
      Stabilize Target Environment
      Reduced Event Handlers
      Reduced Custom Templates
      Remove Project Server effect
      Define Success Criteria
      Validate Data vs Look and Feel
      Educate on Feature Deprecation
      Suspend Indexing during migration
      Validate Backup’s
      Performance Monitoring
    • 25. Updated Strategy
    • 26. Lessons Learned
      Migrations are complex
      Mistakes from the past
      Reserved Names
      Content Types
      Site Columns
      Feature Enhancements and Deprecation
      Communication Strategy
    • 27. Site Columns
      When comparing the "create site column" screen of SharePoint 2010 versus the one in SharePoint 2007, the features are mostly similar except for three enhancements in 2010. These include:1. Column types for Rich Media and Managed Metadata.2. "Enforce unique values."3. Column validation
    • 28. Summary
    • 29. Lessons Learned
      Not Enough Analysis
      Business Goals are not defined
      Features are mis-understood
      Migrations are Messy
      Implementations are a process not a part time project
      Find a battle tested resource
    • 30. Here to There
    • 31. Key Takeaways
      Lessons Learned
      Expect surprises
      Planning and pilot will affect migration
      Performance of tool set
      Notes from the Field
      Integration
      Monitoring
      Maintenance
    • 32. Questions
      adam.woodruff@quest.com
      @adamhadm
    • 33. Don’t Forget
      SharePint!!
      Sponsored By…..
      Join us at 6:00 pm at BJs Brewhousefor a free drink, kindly provided by Rackspace! A great opportunity to network with other SharePoint Professionals!
      Don’t forget to fill out your bingo cards and surveys to be eligible for GREAT end of day raffles!
    • 34. Thanks to Our Sponsors