Join me as I discuss the challenges of upgrading one of the largest airlines in the world to SharePoint 2016/SharePoint Online from SharePoint 2010. I will discuss the planning and the tools that were used to help us along the way. I will provide specific examples of the roadblocks we faced and how we overcome them. I will also talk about the opportunities that SharePoint 2016 brings to the airline industry.
I will also talk about our current plans for building out our SharePoint 2016/SharePoint Online hybrid environment and the challenges and opportunities this presents. Lastly, I will provide insight into how United plans to leverage the new functionality of SharePoint 2016 and SharePoint Online to better serve our front-line customers (and internal business customers).
4. WORLD’S MOST COMPREHENSIVE ROUTE NETWORK
419 Destinations
213 Domestic destinations
206 International destinations
60 Countries served
5,322 Daily departures
Offering
more flights
and
capacity
options
World-class
gateways to
APAC,
EMEIA &
Latin Am
Most fuel-
efficient,
modern
fleet
Optimum
hub
locations in
4 largest
U.S. cities
Featuring the world’s most comprehensive route network
10. Vision and Goals…
Why upgrade?
What does the end state look like?
What direction do you want to go?
What features do you need?
Office 365 or On-Prem solution?
11. Planning the Project…
Initiate the Funding Process
Project Planning
Resource Planning
Infrastructure Planning
Storage Capacity Planning
Security Planning and Risk Acceptance
Plan for Hybrid/Office 365 Integration
15. SP2016 Web Front Ends
SP2016 Application Servers
SQL Cluster
SP2016 Add-Ins
K2 Blackpearl
Office Online Server
SP2016
Workflow Manager
SP2016
Distributed Cache
SQL Services
(SSRS, SSAS, SSIS)
SP2016 Search
22. Do you have a training site?
Is there training materials for users?
Communication is key. Have a plan.
How will you deal with post migration
issues?
24. Are you using tools now?
Any plans to use a migration tool?
Any plans to use a governance tool?
Are you using any development tools?
Are you using a deployment partner?
Database Balancer - DBs are recommended to be at 100GB. This script took larger DBs and split them up into smaller more manageable DBs.
Version Destroyer - Issues with documents that had hundreds of versions. Users were not using versioning properly.
Content Type Crusher - Old COAIR content types created back in SP 2007 days are unsupported. Broke pages.
List Liquidator – Also created in SP 2007. Old custom list templates that broke pages.
KFM, AvePoint, Metalogix, ShareGate. Will you use Fast Track?
SharePoint is smart enough to build the manage paths, but in our case… it was breaking and creating the wrong managed path. Master Control Program script runs the upgrade scripts in order. It calls other scripts, email the status, and update the SharePoint list with status and time (Used Power BI dashboard for tracking progress visually). MCPS – Mount 2013, Run Alfred 2013, Dismount 2013, Mount 2016.
Unsupported Site Collections=Bad Site Definitions. We migrated these to supported site templates.
Unsupported Features=COAIR Content Types. Deprecated solutions. MSFT Deprecated features.
Unused Resources=Master Pages, Page Layouts, Images, CSS
Validate Claims-Because we were reusing the servers, there was a chance the server would say that it was already upgraded
SharePoint is smart enough to build the manage paths, but in our case… it was breaking and creating the wrong managed path. Master Control Program script runs the upgrade scripts in order. It calls other scripts, email the status, and update the SharePoint list with status and time (Used Power BI dashboard for tracking progress visually). MCPS – Mount 2013, Run Alfred 2013, Dismount 2013, Mount 2016.
Claims Authentication breaks a lot of things. So following the migration, we had to validate what claims authentication broke.
Hyper Care – Working with customers that have post migration issues. Why does SharePoint look different? It must be broken!
Who is responsible/accountable/consulted with/informed (RACI)
Make sure your environments are patched or all servers are patched at the same level.
We had to phase our migrations because of weather during the first attempt.