Upgrading SharePoint 2007 to SharePoint 2010: Second Steps

Written By: Scott Murray -- 10/4/2011 -- join -- contribute -- (2493) comments -- printer friendly version

Rating: Rate --

Categories: Configurations, Infrastructure, MOSS 2007, SharePoint 2010, SharePoint Foundation 2010, System Administration, WSS2, WSS3

< Prev - 1 | 2 | - Next > | Become a paid author


In our last tip, we started with the following scenario:  

Your Boss tells you that the budget has been freed up and new capital for upgrades will be available next year.  Thus we will be purchasing SQL 2008R2 and MOSS 2010.  He wants you to determine an upgrade plan and any initial tips on performing the upgrade.   He wants you to confirm what versions need to be purchased and see if we can run through a test upgrade over the next few weeks on test box that is currently not being used.

At this point, you are ready for the actual test upgrade.   Your Boss is excited that you have gotten this far and is happy with the progress made..  Thus what are your next steps to get your test upgrade complete and a site available for some quick testing and user previews?


Step 2:

Once the PowerShell test-spcontentdatabase command no longer returns data, you are ready to run the actual upgrade.  

However before we begin the upgrade, one issue that many upgrades have encountered is with the Fabulous 40 Application Templates.  Microsoft decided to not produce a new set of templates for SharePoint 2010 as noted by Samantha Robertson's Blog To the SharePoint.

Although many of these applications will upgrade without issue, Mrs. Robertson's blog does offer a work around for getting these templates into SharePoint 2010.  Furthermore, TechSol, has created 2010 versions of some of the templates.

The actual upgrade may take some time depending on the size of  your content database.  At this point you should have deleted any unused sites, webparts, and other customizations.  Also, you should have added any customizations, webparts, and solutions to the new site.  It is important at this point to recheck your position and specifically document the process you have followed so far.  My methodology is very low tech in that I document each command in a text document or spreadsheet ( not always the best option as Excel, OpenOffice, or other spreadsheet applications are not normally installed on a server).  I also customarily number my steps in tens or hundreds to allow for easy insert.

During our most recent upgrade we actually used one of the SharePoint Project solutions to keep track of the steps to be performed;  this method was definitely easier to keep organized, but I also kept all my commands in a text file matching the step in SharePoint.

SharePoint List

 Documenting the upgrade process is extremely important and necessary.  Furthermore, Microsoft provides a wealth of Planning Spreadsheets to help you deploy SharePoint  2010.

< Prev - 1 | 2 | - Next >

Learn more about SharePoint

Sponsor Information

Copyright (c) 2010-2017 Edgewood Solutions, LLC All rights reserved
privacy | disclaimer | copyright | advertise | contribute | feedback | about
Some names and products listed are the registered trademarks of their respective owners. |