16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 42: Upgrading <strong>and</strong> Migrating to SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> 1101<br />

the architecture affect your existing team <strong>and</strong> portal sites. You then need to plan<br />

your upgrade <strong>and</strong> migration process accordingly.<br />

Planning is important to any upgrade or migration scenario. As well as underst<strong>and</strong>ing<br />

the updated features, you will need to identify the sites <strong>and</strong> the workspaces<br />

that are actively used <strong>and</strong> need to be migrated, <strong>and</strong> then identify the sites <strong>and</strong> the<br />

workspaces that are no longer used or are no longer required. In large installations,<br />

this analysis can reduce the number of sites you must migrate by as much as 25 percent.<br />

You can back up <strong>and</strong> retire the sites <strong>and</strong> workspaces that you do not migrate.<br />

When you plan your migration, you might want to restructure your new site(s),<br />

instead of just duplicating the old structure.<br />

This chapter will introduce you to the tools you can use during the upgrade<br />

<strong>and</strong> migration process. You should refer to other chapters within this <strong>Resource</strong> <strong>Kit</strong><br />

concerning the planning <strong>and</strong> installation of SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>,<br />

<strong>and</strong> to the following related white papers:<br />

■ “Migrating from SharePoint Team Services <strong>and</strong> SharePoint Portal Server 2001 to<br />

<strong>Microsoft</strong> SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>,” by Michael Herman, Parallelspace<br />

Corporation, October 2003, which can be found at http://www.microsoft<br />

.com/technet/prodtechnol/office/sps2003/deploy/spst2003.mspx.<br />

■ “SharePoint Portal Server 2003 Advanced Migration Scenarios,” by Michael Herman,<br />

Parallelspace Corporation, March 2004, which can be found at http://www.microsoft<br />

.com/downloads/details.aspx?FamilyID=4925b907-0dd8-4be0-af9f-<br />

02c8543f47c9&displaylang=en.<br />

■ “Upgrading from an Evaluation Version to the Final Release of SharePoint Portal<br />

Server 2003,” by Erik Heino, September 2003, which can be found at http://www<br />

.microsoft.com/technet/prodtechnol/office/sps2003/deploy/upgreval.mspx.<br />

■ “Converting Dashboard Web Parts to the Web Part Infrastructure for <strong>Microsoft</strong><br />

SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>,” by Andrew Miller, Michael Herzfeld,<br />

<strong>and</strong> Scott Ruble, August 2003, which can be found at http://msdn.microsoft<br />

.com/library/default.asp?url=/library/en-us/odc_sp2003_ta/html/sharepoint<br />

_north-windwebparts.asp.<br />

Migration Strategies<br />

When you upgrade any software product, there are three possible strategies to consider.<br />

■ In-place upgrade. Install the new version on the same computer, on the<br />

same hard disk(s), <strong>and</strong> in the same directory as the previous version of the<br />

product, replacing the previous version of the product in a single step. This<br />

strategy is useful if you do not have another server available on which to install<br />

Windows Server 2003 <strong>and</strong> SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>. The drawbacks<br />

with this strategy are that the server is unavailable during the upgrade,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!