Upgrading SharePoint 2007 to SharePoint 2010: Second Steps
Written By: Scott Murray -- 10/4/2011 --
(4) comments --
Categories: Configurations, Infrastructure, MOSS 2007, SharePoint 2010, SharePoint Foundation 2010, System Administration, WSS2, WSS3
< Prev -
- Next >
| Become a paid author
last tip, we started with the following scenario:
Boss tells you that the budget has been freed up and new capital for
upgrades will be available next year. Thus we will be
SQL 2008R2 and MOSS 2010. He wants you to determine an
plan and any initial tips on performing the
wants you to confirm what versions need to be purchased and see if we
run through a test upgrade over the next few weeks on test box that is
currently not being used.
this point, you are ready for the actual test upgrade. Your
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
complete and a site available for some quick testing and user previews?
Once the PowerShell
test-spcontentdatabase command no longer returns data, you
ready to run the actual upgrade.
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
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,
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,
and other customizations. Also, you should have added any
customizations, webparts, and solutions to the new site. It
important at this point to recheck your position and specifically
document the process you have followed so far. My methodology
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.
upgrade process is extremely important and necessary.
Furthermore, Microsoft provides a wealth of Planning Spreadsheets to help you
deploy SharePoint 2010.
< Prev -
- Next >