MICROSOFT SHAREPOINT 2007-2010 MIGRATION BEST PRACTICES

1. MICROSOFT SHAREPOINT 2007-2010 MIGRATION BEST PRACTICES RAFAEL DE LA CRUZ SharePoint Developer/Architect

2. REVIEW UPGRADE BEST PRACTICES Update your servers to service pack 2. Ensure that the environment is fully functioning. Migrate to 64 bit servers is necessary. 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 Cruz http://technet.microsoft.com/library/cc261992(office.14).aspx

3. USE THE TRIAL UPGRADE TO FIND ISSUES What customizations you have. Whether you should upgrade your hardware. How long the upgrade will take. 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. http://technet.microsoft.com/library/cc262155(office.14).aspx Rafael de la Cruz

4. BEST PRACTICES FOR TESTING UPGRADE Know what is in your environment. Make your test environment as similar as possible to your real environment. Run multiple tests. Use real data. Do not Ignore warnings. Verify sites in both Visual Upgrade modes. Test the upgrade environment Verify the sites in both visual upgrade modes. http://technet.microsoft.com/en-us/library/ff382640(v=office.14).aspx Rafael de la Cruz

5. THE PRE-UPGRADE CHECKER REPORT 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 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 Cruz http://technet.microsoft.com/en-us/library/cc262231(v=office.14).aspx

6. DETERMINE HOW TO HANDLE CUSTOMIZATIONS Rafael de la Cruz

7. 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

8. IN PLACE UPGRADE (Check List) Rafael de la Cruz http://technet.microsoft.com/en-US/library/ff608117(v=office.14).aspx

9. IN PLACE UPGRADE (PERFORM THE UPGRADE) http://technet.microsoft.com/en-us/library/cc303423(v=office.14).aspx Rafael de la Cruz

10. DATABASE ATTACH UPGRADE (Prepare) 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. Install and configure SharePoint Create and configure the new environment. Verify the new environment. Perform the upgrade. Rafael de la Cruz http://technet.microsoft.com/en-us/library/cc263026(v=office.14).aspx

11. DATABASE ATTACH UPGRADE (Perform) Run the pre-upgrade checker Set the previous version databases to read-only Backup all your content databases 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 application Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication http://SiteName Monitor upgrade progress http://technet.microsoft.com/en-US/library/ff607663(v=office.14).aspx#Prepare Rafael de la Cruz

12. DATABASE ATTACH UPGRADE (Post-upgrade steps) http://technet.microsoft.com/en-US/library/cc263286(v=office.14).aspx Rafael de la Cruz

13. PLAN TO UPGRADE FORM TEMPLATES Rafael de la Cruz

14. ADDITIONAL INFORMATION • 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 WinDiffto 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 2010http://technet.microsoft.com/en-us/library/ff628582(v=office.14).aspx Rafael de la Cruz

15. ADDITIONAL INFORMATION • SharePoint USL Logs • http://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