Welcome to the First Annual SharePoint

Saturday Sacramento!!

Notes from the FieldSharePoint Natural Disasters

Who Am I • Principal Architect SharePoint

o SharePoint Migrationo Architectureo Strategy

• Quest Software• Convergent Computing• Interlink Group• Microsoft

• adam.woodruff@quest.com• @adamhadm

Agenda• The SharePoint Disaster

o Definitiono Solution

• Methodology for Success• Customer Scenario (Notes From The Field)

o Customer Designationo Issueso Points to Successo Lessons Learned

• Summary

Problem

Defined• Organizations, Institutions and Departments have

implemented SharePoint as a secondary process• Unrealized expectations• Failed Goals• Outages

• In Short “SharePoint is a Disaster”

Solution• SharePoint is Business Critical• Design, Architecture, Analysis • Measureable Goals• Meet the Needs with stages for Features and

Release

Methodology to Success

Project Life Cycle

Discovery Rationalization Analysis Planning

Pilot Implementation Management

Financial Customer

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

Guideline for Success• Architecture to Scale for Requirements• Define Business Goals

o Locate Resourceso Resell Intellectual Propertyo Validate license validity o Alert on license expirationo Control Distribution of Market

• Establish Architectureo Reduce Version(s)o Workflow and Alertingo Metadata Management (Content Types, Tagging)o RBS Remote BLOB Storageo Archivingo Search Importance

Updated Strategy

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

RBS GuidelinesScenario Local SQL SKU Remote SQL SKU

FILESTREAM Provider, BLOB stored on local SQL Server file system

Any SQL SKU N/A

FILESTREAM Provider, BLOB stored on Remote SQL Server file system

SQL Enterprise SQL Standard or above

3rd Party RBS Provider SQL Enterprise N/A

HealthCare Customer

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

Guidelines for Success• Determine the Proper Web Applications

o Isolationo Security Boundarieso Multi-Tenancy

• Permissions Management• Site Definitions vs Stapling Features• Storage Management Solutions• Compliance Guidelines• Reporting• Reduction of Folder Structure• Migration Process

Updated Strategy

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

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

Gas/Oil Customer

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

Guidelines for Success• Define the Business Stake Holders• Stabilize Target Environment

o Reduced Event Handlerso Reduced Custom Templateso 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

Updated Strategy

Lessons Learned• Migrations are complex• Mistakes from the past• Reserved Names• Content Types• Site Columns• Feature Enhancements and Deprecation• Communication Strategy

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

Summary

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

Here to There

Key Takeaways• Lessons Learned

o Expect surpriseso Planning and pilot will affect migrationo Performance of tool set

• Notes from the Fieldo Integrationo Monitoringo Maintenance

Questions

• adam.woodruff@quest.com• @adamhadm

Don’t ForgetSharePint!!

Join us at 6:00 pm at BJs Brewhouse for 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!

Sponsored By…..

Thanks to Our Sponsors