This Presentation cover step-by-step instructions on how upgrade to SharePoint 2013. Learn how to plan & prepare for Upgrade & Migration. What’s new in SharePoint 2013 for upgrade and what is the upgrade process and best practices. How to clean up an environment before an upgrade, Strategy on Claims Migration and how to prepare for known Issues, Customization Upgrade tips and tricks.
5. Hardware Requirements
Installation Scenario RAM Processor Hard disk space
Single server with a built-in
database or single server
that uses SQL Server
8 GB 64-bit, 4 cores 80 GB
Single server with a built-in
database or single server
that uses SQL Server
10 GB 64-bit, 4 cores 80 GB
Single server with a built-in
database or single server
that uses SQL Server
24 GB 64-bit, 4 cores 80 GB
Web server or application
server in a three-tier farm
12 GB 64-bit, 4 cores 80 GB
6. Cross Product Support
Starting edition Supported ending edition Unsupported ending edition
SharePoint Server 2010, Standard
edition
SharePoint Server 2013, Standard
edition
SharePoint Server 2013, Enterprise
edition
You can convert to Enterprise edition
after upgrade.
SharePoint Server 2010, Enterprise
Edition
SharePoint Server 2013, Enterprise
edition
SharePoint Server 2013, Standard
edition.
SharePoint Server 2010, Trial edition SharePoint Server 2013, Trial edition SharePoint Server 2013, full product
You can convert to the full product
after upgrade.
13. SPTest
• Create SharePoint ‘SPTest’ Sites
• Create a site for all out of box scenarios
• Create customizations scenarios
• Create Master Test Plan based on all the scenarios in SPTEST
• Move all SPTest Sites into one database ‘WSSContent-SPTEST’
14. Claims Migration
• Classic Mode Auth Web Apps in SharePoint 2010 need
to be migrated to Claims.
• Apply June CU 2012 in SP 2010 environment before
migration
• An update enables the Migrate User method to accept
content database names as parameters so that you can
perform migrations on the specified list of database.
17. Issues with Claims Migration
• In Progress Serial Workflow leaves Assigned to field
Blank
• Existing alert may not fire.
• People picker (in SP 2010) will display the user
information in a different way like
"i:0#.w|amspdevstore"
• InfoPath Forms might show duplicate User Accounts
• Search crawling
• There will be two duplicated owner entries for any
my site created after claims conversion.
18. Cleanup
• Delete unused or underused site collections and sub webs
• Check large lists (lists with lots of data)
• Consider moving site collections into separate databases
• Remove extraneous document versions
• Remove unused templates, features, and Web Parts
• Remove PowerPoint Broadcast sites
• Turn off web analytics
• Check databases for duplicate or orphaned site collections
• Enumallwebs
• Upgrade sites still in the old experience in the SharePoint
2010 Products
20. Install SharePoint 2013
.NET 4.5
Framework
SharePoint
2013
SQL Server
• Install SharePoint Server 2013
• Install March Public Update
• Install SQL Server (one of the following):
• The 64-bit edition of Microsoft SQL Server 2012.
• The 64-bit edition of SQL Server 2008 R2 Service Pack 1
• Microsoft .NET Framework version 4.5
21. Create SharePoint 2013 Farm
• Configure alternate access mappings
• Create Quota Templates
• Create Managed Paths
• Configure Incoming outgoing emails
• Install certificates
Farm
2010
Web App
Port:8080
Web App
Port:9090
Web App
Port:1010
Farm
2013
Web App
Port:8080
Web App
Port:9090
Web App
Port:1010
22. Customizations Upgrade
Site definition
Event Handler
Timer Jobs Services
Web Parts Master PagesThemes
Workflows
Third PartyCmdletsFAST SC Ps Scripts
• Identify customizations in your environment
• Evaluate the customizations
• Keep the customizations, don't upgrade the sites
• Replace or redo the customizations
• Discard the customizations
23. Database Backup & Restore
SQL Server
Old
Backup Service
Application
Databases
Backup
Content
Databases
SQL Server
New
Restore Service
Application
Databases
Restore
Content
Databases
24. Upgrade Service Applications
• Some service applications can be upgraded
• Business Data Connectivity
• Managed Metadata
• PerformancePoint
• Secure Store
• User Profile
• Search administration
• Web analytics is retired
• Other apps do not store any data that requires
migration
25. Process for Migration
(Service Applications)
• Process for Migration
• Restore service application database
• Start the Service Instance
• Create App Pool
• Create Service Application
• Create service application proxy
26. Process for Migration
(Content Databases)
• Test database before you attach the content
databases to the web applications.
• Attach Content Database to Web Application
• Verify the Database Upgrade
27. Upgrade site collections
• Run Site Collection Health Checks
• Repair Site for any errors
• Request Upgrade Evaluation Site Collection
• Verify Site Upgrade Throttle Settings
• Upgrade the Site
• Verify Upgrade
29. Upgrade Issues
• Missing server-side files or customizations, such as
features or Web Parts.
• Configuration issues in the server farm, web
application, or service applications, such as
managed paths or service applications that are not
started.
• Additional issues that you discover on a site-by-site
basis, starting with high-profile or very important
sites.
30. Post upgrade steps
• Verify that site collections are working as expecting
in 2010 mode
• Update links that are used in any upgraded InfoPath
form templates
• Configure your Search topology
• Start a full crawl
• Backup your Farm
• User Training