MICROSOFT SHAREPOINT 2007-2010 MIGRATION

BEST PRACTICES

RAFAEL DE LA CRUZSharePoint Developer /Arch i tect

Update your servers to service pack 2.

Ensure that the environment is fully functioning.

Migrate to 64 bit servers is necessary.

REVIEW UPGRADE BEST PRACTICES

Run the pre-upgrade checker to look for potential issues.

Perform a trial upgrade on a test farm first.

Plan for capacity.

Back up your environment.

Optimize your environment before upgrade. Rafael de la Cruzhttp://technet.microsoft.com/library/cc261992(office.14).aspx

What customizations you have.

Whether you should upgrade your hardware.

How long the upgrade will take.

USE THE TRIAL UPGRADE TO FIND ISSUES

What resources to have available.

Which upgrade approach will be the most efficient.

How do you know when you have finished one phase.

Where are the log files located and hoe to read them.

Rafael de la Cruzhttp://technet.microsoft.com/library/cc262155(office.14).aspx

BEST PRACTICES FOR TESTING UPGRADE

Use real data.Use real data.

Make your test environment as similar as possible to your real

environment.

Do not Ignore warnings.Do not Ignore warnings.

Run multiple tests.Run multiple tests.

Know what is in your environment.

Know what is in your environment.

Verify sites in both Visual Upgrade modes.

Verify sites in both Visual Upgrade modes.

Rafael de la Cruzhttp://technet.microsoft.com/en-us/library/ff382640(v=office.14).aspx

Test the upgrade environmentTest the upgrade environment Verify the sites in both visual upgrade modes.

Verify the sites in both visual upgrade modes.

Return a list of all server and components in the farm

Return a list of Alternate access mapping URLs

Return a list of all site definitions, site templates, features

THE PRE-UPGRADE CHECKER REPORT

List any database or site orphans.

Reports any server-side customizations that are not supported.

• Stsadm –o preupgradecheck• stsadm -o enumallwebs -databasename <database name> [-databaseserver <database server

name>]• Stsadm -o databaserepair -url <url name> -databasename <database name> [-

deletecorruption]• stsadm -o deletesite -force -siteid e2a114b8-80c9-41f6-87bf-3feddf2ad9b6 -databaseserver

<DBS> -databasename <DBN>

Rafael de la Cruzhttp://technet.microsoft.com/en-us/library/cc262231(v=office.14).aspx

DETERMINE HOW TO HANDLE CUSTOMIZATIONS

• As part of your upgrade testing process, you should create an inventory of the server-side customizations in your environment (solutions, features, Web Parts, event handlers, master pages, page layouts, CSS files, and so on).

IDENTIFY CUSTOMIZATIONS

• Is the customization still valuable?• Is the customization well designed?• Keep , Replace, Discard customizations?

EVALUATE CUSTOMIZATIONS

• Site templates, Site definition, Features, Workflows, Event handlers, Manage paths, Themes, Master pages and CSS Files, Java Script, Search, Web Parts, Services, Authentication providers.

CONDIDERATIONS FOR SPECIFIC CUSTOMIZATIONS

• Ensure that your environment performs well and follows best practices.

ENSURE THAT FUTURE CUSTOMIZATIONS FOLLOW BEST

PRACTICES

Rafael de la Cruz

PERFORM THE UPGRADE

In Place Upgrade

Database Attach

Parallel Upgrade

Database attach with read only databases

In Place with detach databases

Rafael de la Cruz

Run the Pre-upgrade Checker

Clean up you environment

Record settings for use synchronization

Backup up your environmentRecord blocked file types

IN PLACE UPGRADE (Check List)

http://technet.microsoft.com/en-US/library/ff608117(v=office.14).aspx Rafael de la Cruz

• Make sure that have run the pre-upgrade checker tool,

• Backup your environment• Meet all hardware and software requirements• Ensure that you are prepare to setup the required

accounts

BEFORE YOU BEGIN

• Before you can upgrade, you must run the prerequisite installer successfully on each web server that has SharePoint Server 2007 installed.

INSTALL PREREQUISITES

• If you are running an in-place upgrade on a server farm, disconnect all the users from the server farm by stopping the World Wide Web Publishing Service (W3SVC) on all front-end Web servers.

RUN SETUP ON ALL WEB SERVERS

• The SharePoint Products Configuration Wizard runs and configures the configuration database and SharePoint Central Administration for SharePoint Server 2010.

RUN THE CONFIGURATION WIZARD

• You can monitor the upgrade process for each site from the Upgrade Status page in SharePoint Central Administration or by using the localupgradestatus operation in Stsadm.exe.

CHECK UPGRADE STATUS FOR SITES

• If upgrade fails or reports issues, you can refer to the log and error files for more information.VERIFICATION

IN PLACE UPGRADE (PERFORM THE UPGRADE)

Rafael de la Cruzhttp://technet.microsoft.com/en-us/library/cc303423(v=office.14).aspx

Ensure that you have met all hardware and software requirements

Ensure that you are prepared to se up the required accounts.

Run the pre-upgrade checker.

DATABASE ATTACH UPGRADE (Prepare)

Install and configure SharePoint

http://technet.microsoft.com/en-us/library/cc263026(v=office.14).aspx

Create and configure the new environment.

Verify the new environment.

Perform the upgrade.

Rafael de la Cruz

Run the pre-upgrade checker

Set the previous version databases to read-only

Backup all your content databases

DATABASE ATTACH UPGRADE (Perform)

Detach the previous databases (Only if you are going to upgrade the original databases)

Restore a backup copy of the database

Set the restore databases to be read-write

Verify custom components, permissions

Attach a content database to a web applicationMount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication http://SiteName

Monitor upgrade progress

Rafael de la Cruzhttp://technet.microsoft.com/en-US/library/ff607663(v=office.14).aspx#Prepare

•Reapply administrator permissions for services.1

• Upgrade profile properties to taxonomy data.2• Create and configure the Secure Store service

application and migrate data.3• Upgrade solutions that depend on the Business

Catalog.4• Update links that are used in any upgraded

InfoPath form.5

DATABASE ATTACH UPGRADE (Post-upgrade steps)

Rafael de la Cruzhttp://technet.microsoft.com/en-US/library/cc263286(v=office.14).aspx

• Existing administrator-approved form templates and data connections must be migrated and upgraded.• A database attach upgrade is the only way to upgrade Microsoft Office Forms Server 2007 to SharePoint Server 2010• Administrator-approved form templates and data connection files in the Central Administration libraries are stored in the configuration database and must be migrated separately.

Database Attach Upgrade

• All forms and form templates are upgraded automatically during an in-place upgrade.In-Place upgrade

PLAN TO UPGRADE FORM TEMPLATES

Rafael de la Cruz

• Update your servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later.• Pre-upgrade checker

• http://technet.microsoft.com/en-US/library/cc262231(v=office.14).aspx• http://support.microsoft.com/kb/960577

• Use the stsadm -o enumallwebs -databasename <database name> -databaseserver <database server name> on all content databases in your Office SharePoint Server 2007 environment to identify specific customizations in subsites.

• SharePoint Manager 2007• http://spm.codeplex.com/releases/view/22762

• Use this worksheet to record information about your environment while you test your upgrade.• Download the worksheet from http://go.microsoft.com/fwlink/p/?LinkId=179928.

• Use a tool such as WinDiff to compare your production environment servers with your test farm servers.• Use the SharePoint Diagnostics Tool (SPDiag) to find deployed solutions. For more information, see

SharePoint Diagnostics Tool (SPDiag).• Best Practices: Using Disposable Windows SharePoint Services Objects http://go.microsoft.com/fwlink/p/?

LinkId=105945&clcid=0x409• Best Practices: Common Coding Issues When Using the SharePoint Object Model http

://go.microsoft.com/fwlink/p/?LinkId=105946&clcid=0x409• SharePoint Products and Technologies customization policy http://go.microsoft.com/fwlink/p/?

LinkId=105947&clcid=0x409• Attach or detach content databases in SharePoint 2010

http://technet.microsoft.com/en-us/library/ff628582(v=office.14).aspx

ADDITIONAL INFORMATION

Rafael de la Cruz

ADDITIONAL INFORMATION

• SharePoint USL Logshttp://ulsviewer.codeplex.com/

• Link to the video used during the presentation http://www.youtube.com/watch?v=nmoU-K4W-wU&feature=youtu.be

Rafael de la Cruz