Get documents about "Upgrading to Microsoft Office SharePoint Server 2007 from
Document Sample
Hands-on Lab Overview
1. Introduction
HOL414: Upgrading to Microsoft® Office SharePoint® Server 2007 from Microsoft Office SharePoint Portal
Server 2003
2. Technologies Highlighted
Microsoft® Office SharePoint® Server 2007
3. Audience
ITPro – 400 level
4. Scenario
Learn about the available methods and procedures for upgrading to Microsoft Office SharePoint Server 2007 from Microsoft Office
SharePoint Portal Server 2003.
5. Purpose of Hands-on Lab
The objective of this lab is to provide a walkthrough of upgrade capabilities with Windows SharePoint Services 3.0.
6. Prerequisites
In order to keep waiting times down in this lab, a number of the steps needed in an upgrade have been completed in advance. The first step
in any migration is to choose a migration type. For this lab, we will use a gradual upgrade migration. The following steps in the upgrade
process that have already been completed:
1. Install Microsoft .NET Framework v2.0
2. Install Microsoft .NET Framework v3.0
3. Install Windows SharePoint Services v2.0 SP2
4. Install SharePoint Portal Server 2003 SP2
5. Install Microsoft Office SharePoint Server 2007
6. Choose to perform a gradual upgrade
1
7. Run C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin\prescan.exe /all
8. Run the Start All Programs Microsoft Office Server SharePoint Products and Technologies Configuration wizard
9. Create a new server farm
10. Open the new Central Administration site
11. Click on the Operations tab
12. Click on Site upgrade status link
13. Begin upgrade on the web application
Planning and Preparing for the Upgrade
The upgrade process for Microsoft Office SharePoint Server 2007 is not as simple as installing the software. There are a number of things which
require an administrator’s careful and thoughtful consideration before attempting the upgrade. The first consideration is to determine which
upgrade process option makes the most sense for your environment. There are three different types of upgrade process available:
In-place upgrade: This method will upgrade all items as part of the installation and configuration of the Microsoft Office SharePoint
Server 2007 installation. It is the easiest upgrade method, but it does have a few drawbacks. The environment is offline while it the
upgrade completes (which can take quite some time) and there is no ability to revert to the original site. This method is ideal for single
server or small server farm deployments.
Gradual upgrade: This method installs Microsoft Office SharePoint Server 2007 side-by-side with Microsoft SharePoint Portal Server
2003. The server administrator can then determine on a site-collection-by-site-collection basis which content is upgraded. This enables a
more granular approach to the upgrade process. This process does allow an administrator to revert to the original site, however if the
reversion is done after changes or updates have been made to the new site those changes will be lost. This approach is more complex and
does require additional storage resources to be able to allow the upgrade reversion to take place. This is the process that will be described
in this lab. This method is ideal for medium to large server farm deployments or environments where there are many customizations.
Database migration: Requires the server administrator to install the new version on a separate farm or separate hardware, and then
manually migrate the databases into the new environment. This allows the administrator to move data to a new farm or new hardware.
This is the most complex method available and has several manual steps to complete successfully. This method is ideal if you are moving
to new hardware.
How URL Redirects are Handled
Two sites cannot share the same URL. During a gradual upgrade (when you have both the old version and the new version of each site) you need
two different domain URLs for each site (for example, http://company_name/sites/SiteA and http://company_name_old/sites/SiteA). During
upgrade, a temporary domain URL is needed to host the original previous version sites. The new version takes over the domain URL that points to
the content prior to upgrade, and user requests will be routed to their content whether or not it has been upgraded. The following process occurs
during upgrade to make this redirection possible:
2
1. Before you begin the upgrade, create a temporary URL domain for your previous version sites.
2. When you run the upgrade, the upgrade process will ask you for the domain you specified above. The process moves the previous version
site to the temporary URL domain, and the new version site takes over the original URL domain.
3. A redirect is created automatically for each site collection to send requests for the original URL to the previous version site until the site is
upgraded.
4. After each site has been upgraded, the redirect for that site is dropped.
5. After all sites have been upgraded, and after you have deleted all of the previous version sites and completed the upgrade process, you can
manually remove the temporary URL domain from the Domain Name System (DNS).
During this process, browse access to the original URL will continue to work. However, certain client applications (such as Microsoft Office client
applications) cannot use these types of redirects. Before a site is upgraded, the original URL points to the previous version; after a site has been
upgraded, the original URL points to the new version.
The following table illustrates how the URLs work during gradual upgrade.
Stage Original site URL Upgraded site URL Notes
Before upgrade http://company_name/sites/SiteA n/a The server administrator creates
http://company_name_old for use during gradual
upgrade.
During upgrade http://company_name_old/sites/SiteA http://company_name/sites/SiteA Requests for http://company_name/sites/SiteA are
redirected to http://company_name_old/sites/SiteA
until it is upgraded.
After upgrade http://company_name_old/sites/SiteA http://company_name/sites/SiteA The redirect is removed after upgrade is complete
(until deleted) and the results are validated.
Gradual upgrade
This lab will focus on the gradual upgrade process so we will look at some more specific information about this upgrade method.
Similar to an in-place upgrade, a gradual upgrade takes place on the same hardware that is used for your previous version installation. However, a
gradual upgrade allows you to control when upgrade takes place for each individual site collection, and it also allows you to continue running the
previous version and the new version side by side on that hardware. When you perform a gradual upgrade, the starting and ending topologies have
the same configuration, similar to an in-place upgrade except for the following differences:
3
• During and after upgrade, the front-end Web servers run both SharePoint Portal Server 2003 and Office SharePoint Server 2007. Any upgraded
site collections run under Office SharePoint Server 2007, whereas site collections that could not be upgraded or that were not selected for upgrade
continue to run under SharePoint Portal Server 2003.
Note:
Scenarios in which you may not want to upgrade sites include: you may need to keep some sites in the previous version until a needed language
pack is available for the current version, or you may need to wait for a new custom site definition to be created.
• During and after upgrade, the application servers run both SharePoint Portal Server 2003 and Office SharePoint Server 2007 services. Upgraded
portal sites consume Office SharePoint Server 2007 shared services; portals that have not yet been or cannot be upgraded consume SharePoint
Portal Server 2003 shared services. Additional services (such as Microsoft Excel® services) can be added after upgrade.
• During and after upgrade, both the SharePoint Portal Server 2003 and the Office SharePoint Server 2007 databases are available. Content for
upgraded sites is stored in the Office SharePoint Server 2007 databases; content for sites that could not be upgraded or that need to remain as they
were will continue to be stored in the SharePoint Portal Server 2003 databases. Configuration databases exist for both Office SharePoint Server
2007 and SharePoint Portal Server 2003.
Hands-on Lab
Discussion Points Actions taken
Exercise 1 – Upgrade a site collection using Central Administration
This exercise will focus on familiarizing you with the Central Administration Login using the following credentials:
interface to the side-by-side upgrade process. When opening Internet o Username: administrator
Explorer you will be taken to the homepage of http://server, however you will o Password: pass@word1
notice that you are immediately redirected to http://server:8000. This Open Internet Explorer, this will open to the Portal home page
redirection is a mechanism of the upgrade process. In order to manage all Examine how the site looks prior to upgrade, with the side-by-side migration
requests to the original URL Windows SharePoint Services 3.0 tracks the SharePoint Portal Server 2003 site will be used until you start the
upgraded vs. non-upgraded sites and manages a redirect to them. For more upgrade process
information on this read the “How URL Redirects are Handled” section above. Select Favorites Central Administration
Click on the Operations tab
Site content upgrade is in the Operations section of the Central Click on the Site content upgrade status link
Administration, and the “Continue upgrade” link designates that you have
Click the Continue upgrade link
started the upgrade for this web application. If your farm had multiple web
Select the checkbox next to /
applications you could start the upgrade process on any of them at any time.
Click the Upgrade Sites button
Once you start the process the URL redirects will begin until you “Finalize”
the upgrade. Note the summary information for the upgrade process, amount of data
contained in the site, originating and target databases
4
As you will note as you go through this exercise all of the site collections in Click the Upgrade Sites button
the web application are listed as options to upgrade. Once the upgrade has The Upgrade Running status page will appear showing the status of the
completed for that site collection it will no longer show in the list. Upgrade upgrade **this will take several minutes**
can only be done at the site collection level and no lower. You cannot When the Upgrade Running status page shows the upgrade job completed
upgrade a specific subweb or list independently. click the Operations tab in the top navigation area
Click on the Site content upgrade status link
Click the Continue upgrade link
Note that / is not listed anymore
Click on the Home button on Internet Explorer toolbar and examine the
differences in the site after it has been upgraded
o New left and top navigation has been added
o News Articles have been assigned to new page layouts
o General web parts have been upgraded to their Microsoft Office
SharePoint Server 2007 equivalents where applicable, and any
web part that could not be upgraded displays an error message
o URL is no longer redirecting to http://server:8000 it is going
directly to http://server
Also note that all sites in the site collection were updated with this process
A site-by-site method does not exist to migrate anything smaller than a site
collection
Exercise 2– Upgrade a site collection using stsadm
Along with the Central Administration upgrade user interface Windows Click on Favorites Marketing in Internet Explorer
SharePoint Services 3.0 can control the upgrade process using stsadm. Note the site layout, this is a standard and unmodified Team Site
Both the Central Administration and stsadm upgrade processes use the Click on Favorites Products in Internet Explorer
same SPTimer jobs so only one may be active at a time. If you try to start an Note the site layout, this is a standard Team Site that has been modified
upgrade from stsadm while there is one running in the Central Administration using Microsoft FrontPage 2003. A data view Tasks web part has been
interface you will receive an error. The opposite is true as well. added and the default.aspx was customized to show the site title in the
quick launch area and the search box was removed
A quick and easy way to get a number of sites upgraded is to use the Click Start Command Prompt
enumsites option in stsadm and pass in the –redirectedsites parameter. Type stsadm –o upgrade to view the command line options for upgrade
This tells stsadm to only enumerate the sites that SharePoint is managing Type stsadm –o enumsites –url http://server –redirectedsites >
redirects to. I.e. only enumerate non-upgraded sites. By redirecting the
sites.xml to create a list of all sites available for upgrade
output to a file we can use the upgrade options –sitelistpath parameter to
Type notepad sites.xml to open the list for editing
pass in multiple sites easily.
Remove all of the listed sites except for http://server/sites/marketing and
As shown in this exercise upgrading a non-customized site collection results http://server/sites/products
in a user experience that will flow very nicely without further steps required. Type Ctrl-S to save the file and close Notepad
When customizations are in place there are additional steps that a site Type stsasm –o upgrade –sidebyside –sitelistpath sites.xml
administrator must perform to bring the additional new features in to the user Note: When selecting sites to upgrade through the command line only
interface for that site. specify sites from the same content database.to run at the same time.
Wait for the SharePoint Setup dialog to exit
(Optional) Follow the next 3 steps prior to the SharePoint Setup dialog
5
completing and notice the error message. The upgrade process uses
SPTimer jobs and the command-line and Central Admin interfaces are
aware when the other is in progress. Only one upgrade may be active at a
time, though the upgrade job may contain a list of several site collections.
Return to Internet Explorer and select Favorites Central Administration
Click on the Operations tab
Click on the Site content upgrade status link
Click the Continue upgrade link
Note that /sites/products and /sites/marketing are not listed anymore
Click on Favorites Marketing in Internet Explorer
Note the site layout, the upgrade process has left the site layout mostly
unchanged and all of the new Microsoft Office SharePoint Server 2007
additional features are now accessible
Click on Favorites Products in Internet Explorer
Note the site layout, you will see that since the default.aspx file has been
modified the site looks no different. There are two option available to get
access to the Microsoft Office SharePoint Server 2007 additional navigation
and menu systems
o Resetting the default.aspx to the site definition
o Opening the default.aspx in SharePoint Designer and fixing or
recreating the customizations
Note: Microsoft Office SharePoint Server 2007 features are available on
this site after the upgrade. The only issue that is being displayed here is
that customizations must be dealt with separately from upgrade in order to
ensure that full functionality is available to the end user.
Click the Site Settings link in the top navigation
Under Look and Feel, click the Reset to site definition link
Note you can select specific pages or all, select the Reset all pages in this
site to site definition version radio button
Click the Reset button
Click Ok on the warning dialog
Click on the Home tab to view the changes
Exercise 3 – Revert an upgraded site collection
Part of the upgrade process is a back-out strategy. If you have run through Select Favorites Central Administration in Internet Explorer
an upgrade on a site collection and you find that there are customizations Click on the Operations tab
that you were not prepared to handle in place, you have the option to revert Click on the Site content upgrade status link
the upgraded site back to the original. Click the Continue upgrade link
In the left-hand navigation area in the Actions section click the Revert site
It is very, very important to note that any changes made to the upgraded site link
6
once it became functional will be lost. The site reversion feature should be In the Site Collection dropdown select Change Site Collection
exercised as soon as possible when dealing with site upgrades to avoid loss Select /sites/Productsand click the Ok button
of data when you revert the site to the original. Click the Continue button
Click the Ok button on the warning dialog
Note you are returned to the Site Collection Upgrade page and
/sites/Products is available for upgrade
Select Favorites Products in Internet Explorer
Note the site layout has reverted to the original and the URL redirection is
set back to the original site
Conclusion
I. Conclusion
In this lab, you learned about the Microsoft Office SharePoint Server 2007 upgrade system. You stepped through the upgrade process
using the Central Administration and command line interfaces. Finally, you looked at the upgrade reversion feature that allows you to
back out of an upgrade process if the site had issues after the upgrade completed.
7
