SharePoint content deployment presentation
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

SharePoint content deployment presentation

  • 1,112 views
Uploaded on

 

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

Views

Total Views
1,112
On Slideshare
1,020
From Embeds
92
Number of Embeds
1

Actions

Shares
Downloads
15
Comments
0
Likes
0

Embeds 92

http://www.techgrowingpains.com 92

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

Transcript

  • 1. SharePoint 2010 Content Deployment
    The what is that, who should use it, and when it should be used
    Prepared for: SharePoint Saturday Los Angeles
    Date: September 18, 2010
  • 2. Microsoft says:
    Content deployment deploys content from a source SharePoint Server 2010 site collection to a destination site collection. The complete source site collection can be deployed, or a subset of sites can be deployed.
    What do I say?
    2
    What is it?
  • 6. Consider your particular scenario. Is it a good fit?
    Farm Topologies are Completely Different
    Servers have specific performance tuning requirements
    Security concerns for content on the destination
    3
    That’s great! I’m going to go use it right now!
    What do you gain?
  • Author on Production via an extended web application
    Custom solution?
    Backup and restore
    4
    Content Deployments are horrible! Isn’t there a better way?
  • 10. Authoring and Production Farm
    Use this for:
    Internet-facing sites
    Extranet sites with read-only access
    5
    So what do you need to pull this off?
  • 11. Authoring, Staging, and Production Farms
    Use this for:
    Multi-stage approval process business requirement
    Validating content that reflects production environment
    Testing content with custom web parts and code
    6
    Next step up…
  • 12. Single Publishing Farm
    Use this for:
    Intranet deployments
    External testing/validation is not needed
    When one farm is all you have
    7
    Now that is to big. What about the little guy?
  • 13. Who gets it and who doesn’t…
    8
    I’m still interested….
  • 14. So what does it take to set this up?
    A Path…
    …is the road to get from A to B
    A Job…
    …is the car that drives you from A to B
    9
    The Details Please….
  • 15. Spin up that VM!
    10
    Enough Talk! Let take a look at SharePoint…
  • 16. Not enough Planning...
    Plan for which server are the export import server
    Plan content deployment paths
    Plan job scheduling
    Plan for large jobs
    And the complexity continues….
    Keep content in scope
    I exported the child but not the parent
    Use empty site collection as a destination (Not blank!)
    Install required features on destination but don’t active
    What's your patching level?
    Don’t forget the language packs
    11
    Common Pitfalls
  • 17. Database Snapshots!
    Import Settings
    UnattachedContentDatabase
    ExportFrontEndFileStreams
    Removed Export part – ‘retry’ is gone
    Custom deployment aware event handlers and feature activation code
    12
    So What new in SharePoint 2010?
  • 18. 13
    Javier Barrera
    Blog: http://www.techgrowingpains.com
    Twitter: @BlueUser