Your SlideShare is downloading. ×
The mechanics of moving share point to the cloud denver alt
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

The mechanics of moving share point to the cloud denver alt


Published on

The Mechanics of Moving SharePoint to the Cloud Denver

The Mechanics of Moving SharePoint to the Cloud Denver

Published in: Technology

  • Be the first to comment

  • Be the first to like this

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
  • What does the cloud promise to us?Where does it fail?
  • How much control do I need? what are my business requirements? Do I have SLA requirements?Do I have federal/state requirements (e.g. HIPPA)?Do I need to customize by environments? WSPs? Branding? Will I need to have SSO capabilities?Is VPN a requirement?How much data?Is search customization needed?current future storageRealistic migrations expectations and planmigration downtime?Auth requirementsBDC (external data)URLsInternal/external DNS
  • House Vs. Apartment metaphor You own the house you can change cable providers color outside of house change the rooms add rooms a standalone structureYou rent the Apartment inside of room don’t have to worry about trash don’t have to cut the grass a site within a structure
  • The cloud any structure outside of the company’s own infrastructureThe cloud can be SaaS or IaaS
  • Outline business requirementsAudit your current environment Space WSPs BrandingDetermine cut-over date and work backwards along time line (this is an project exercise as much as technical function)Copy Database and any customizations (if needed) to new environment (stale data)Copt Service Application databases (some can not be copied or migrated)Test new environment with people who know your data. More than functional test (testing can use AAM or HOST files)Update farm as needed to working condition. Test again and continue cycle as neededSet DNS TTLs (2 days)Set change management freeze (1 day)Set current environment to read-only (day of)Copy data to database (and service application DBs) or online as needed for refresh data (alternate methods will be needed if large of complex situations)Set DNS IP to new locationWait for DNS (not all DNS servers on Internet honor lower TTLs)Last round of testingCompleted migration
  • Transcript

    • 1. SharePoint Fest DenverThe Mechanics of MovingSharePoint to the | @jtbarrera |
    • 2. Why are we here? What are we talking about? Who is this guy? Questions? 2
    • 3. Promised Path?
    • 4. Knowledge and Planning
    • 5. The Right Choice
    • 6. What should I be asking?
    • 7. Agenda Defining the Cloud Software as Service Infrastructure as Service The Migration 8
    • 8. What is the Cloud?
    • 9. Elephant in the Room 10
    • 10. PositivesCostsLow KnowledgeFlexibly (growth)Easy Entry 11
    • 11. NegativesRegulationsLimited OptionsMigration PainsNo Deep Control 12
    • 12. Public Cloud 13
    • 13. Private Cloud 14
    • 14. Hybrid Cloud 15
    • 15. PositivesMigrationSingle Sign-OnFeaturesCustomization 16
    • 16. NegativesLicensingCostExpertise LevelComplexity 17
    • 17. Data Migration OptionsManualSharePoint Designer3rd Party Tools 18
    • 18. Migration
    • 19. Questions?@jtbarrera