In the previous chapters, you have learned about all the different features of MOSS 2007. In this chapter, we show you how you can upgrade your current environment to MOSS 2007. As we all know, this seemingly simple process can be a real headache if we don’t follow the right steps. This chapter will be completely directed toward system administrators, as they are the ones responsible for the upgrade. In this chapter, we discuss the various scenarios that might occur during an upgrade in your environment.

Depending on the size of your company, you will be coming in from a single server or a large server farm environment and will want to either stay the same in size or expand/reduce. There are three possible scenarios that are available for us to upgrade from SharePoint Portal Server 2003 to Office SharePoint Server 2007, as follows:

An in-place upgrade is used to upgrade all SharePoint sites at one time, which is suitable for single-server or small deployments. A gradual upgrade allows finer control of the upgrade process by allowing one or more sites to be upgraded at a time. Both in-place and gradual upgrades take place on the same hardware on which your previous version is installed. A database migration allows you to move your content to a new farm or new hardware.

Before we start diving into the upgrade scenarios, we need to understand the road map that Microsoft has made available for us in terms of upgrades. Figure 24-1 shows the basic path for upgrade from a SharePoint Portal Server 2003 environment to an Office SharePoint Server 2007 environment.

Figure 24-1. Supported upgrade paths for Office SharePoint Server 2007

All the material on upgrading to Office SharePoint Server 2007 is available on Microsoft sites and documents; however, our goal here is to make it concise enough so that you don’t have to go through hundreds of pages of documentation to find what you need. By the time you are done with this chapter, you should:

Table 24-1 lists the supported and unsupported topologies when upgrading to Office SharePoint Server 2007.

There are certain prerequisites to installing the Office SharePoint Server 2007 application on your server. If you launch the application setup, it will display a dialog box, as shown in Figure 24-2, stating that you do not have the prerequisites in place and need to install them before exiting.

The following are the steps that you want to implement in order to get ready for the installation:

Before we start upgrading our environment, we need to make sure that we have a rollback plan and that everything that we will need during the upgrade will be in place.

One of the first things that you should do is make sure that you have a complete backup of your current environment. In order to ensure that you can recover your existing environment, you must back up the databases that are used by Microsoft SharePoint Portal Server 2003, as listed in Table 24-2.

Figure 24-3. Enabling ASP.NET v2.0.50727

Test your backups in a nonproduction environment and confirm that you can successfully restore the previous environment if necessary without any loss of data or customizations.

Next, you need to run the preupgrade scan utility provided by Microsoft as part of the Office SharePoint Server 2007 installation to determine any potential issues with the upgrade. If you have not successfully run this utility and you attempt to run the upgrade process, the wizard will exit and prompt you to run the tool.

On the command line, change to the folder that contains the two files, and then run the following command to scan all servers in your server farm:

	prescan.exe /c preupgradescanconfig.xml /all

You can use the preupgrade scan tool to scan all web sites in your environment (by using the /all parameter) or to scan a specific URL (by using the /v URL parameter). See Figure 24-4. If you do not supply a scoping parameter, all web sites will be scanned.

You might need to run the upgrade utility more than once. After you resolve any issues from your first scan, you will need to run the utility again; otherwise, when you try to run the configuration wizard, you might see an error message that the prescan has not been run.

Unfortunately, as of now, the preupgrade scan utility is only a part of the Office SharePoint Server 2007 install and is not available as a standalone download. Therefore, you need to install Office SharePoint Server 2007 on a test environment and retrieve the prescan.exe file along with the preupgradescanconfig.xml file and copy them to the server running the existing version. These files are located in the Drive:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12Bin folder.

If you have modified your existing SharePoint Portal Server 2003 environment using Microsoft Office FrontPage 2003, you need to determine how you want to handle customized sites when you upgrade. You can choose to:

Figure 24-4. Upgrade scan tool

Additionally, during the in-place upgrade, you can also choose not to reset the pages to the site definition. This will preserve the customizations. After the upgrade, open the site and copy the customizations, and then reattach the page layouts and reapply your customizations to the master pages and page layouts as appropriate.

At the beginning of the chapter, we mentioned that there are three possible options available for upgrading from SharePoint Portal Server 2003 to Office SharePoint Server 2007. Here we discuss these options in detail and define the steps that are involved in each of these processes.

In-Place Upgrade

As mentioned earlier, the in-place upgrade is most suitable for single-server or small deployments of SharePoint Portal Server 2003. In an in-place upgrade, you will be installing Office SharePoint Server 2007 on your existing environment. The previous version is overwritten with the new version, and the content databases are changed. Hence, this is not a reversible process—you cannot roll back to the previous version. When you run the in-place upgrade, the process upgrades your entire installation in a preset sequence. The following list shows the steps that need to be taken to implement an in-place upgrade. (For this in-place upgrade, I have an existing SharePoint Portal Server 2003 environment set up. It is a basic out-of-the-box setup with a couple of Windows SharePoint Services v2 sites and no customizations.)

1. Run Setup.exe.

2. This will bring up the Product Key dialog box (Figure 24-5). Enter the proper information to be able to move forward.

   

   Figure 24-5. Office SharePoint Server 2007 Product Key installation page

3. On the Read the Microsoft Software License Terms page (Figure 24-6), review the terms, select the “I accept the terms of this agreement” checkbox, and then click Continue.

4. On the “Upgrade earlier versions” page (Figure 24-7), click “Yes, perform an automated in-place upgrade.”

   

   Figure 24-6. Office SharePoint Server 2007 install’s License Terms page

5. On the Server Type tab (Figure 24-8), select your server type:

   • Choose “Complete–Install all components. Can add servers to form a SharePoint farm” if this is the first server that you are upgrading in a server farm.

   • Choose Web Front End if you are running an upgrade on an additional frontend web server in a server farm.

   • Choose Stand-alone if this is a standalone server (not part of a server farm) and you want to use SQL Express for your database.

     

     Figure 24-7. Office SharePoint Server 2007 install’s upgrade type selection

6. On the File Location tab (Figure 24-9), select the locations where you want to install the applications.

7. Click Install Now to get the screen shown in Figure 24-10.

8. The setup runs and installs Office SharePoint Server 2007.

9. On the completion page (Figure 24-11), select the “Run the SharePoint Productions and Technologies Configuration Wizard now” if you have run the preupgrade scan tool previously. If you did not run the scan, you should run that first, before the configuration wizard.

10. In the SharePoint Products and Technologies Configuration Wizard on the Welcome page (Figure 24-12), click Next.

    

    Figure 24-8. Complete install

11. A message appears, notifying you that Internet Information Services (IIS), the SharePoint Administration Service, and the SharePoint Times Service may need to be restarted or reset during the configuration. (See Figure 24-13.)

12. Click Yes to continue with the wizard. A message appears, notifying you that you should download and install new language template packs for the new version (Figure 24-14).

13. Click OK to confirm the message and continue with the wizard. Do not install the language template packs until you have completed running the configuration wizard.

    

    Figure 24-9. Location selection page

14. On the Configure SharePoint Central Administration Web Application page (Figure 24-15), if you want to use a specific port number for SharePoint Central Administration, select the “Specify port number” checkbox, and then type the port number you want to use. In the Configure Security Settings section, select either Negotiate (Kerberos) or NTLM, depending on your environment, and then click Next.

    Warning

    To enable Kerberos authentication, you must perform additional configuration steps. For more information about authentication methods, see Plan authentication methods (Office SharePoint Server).

15. In the “Completing SharePoint Products and Technologies Configuration Wizard” page (Figure 24-16), verify the settings and click Next.

    The configuration wizard runs and configures the configuration database and Central Administration Web application for Office SharePoint Server 2007 (Figure 24-17).

    

    Figure 24-10. Install in progress

16. A message appears (Figure 24-18), notifying you that if you have a server farm with multiple servers, you must run the setup on each server to install new binary files before running the configuration wizard and starting the upgrade process.

    Depending on your server farm configuration, and where you are in the process of installing and configuring Office SharePoint Server 2007, you have three choices:

    • If this is the only server in your farm, no other actions are necessary. Click OK to continue with the wizard.

    • If you have other servers in your farm, and you have not yet run setup and the configuration wizard on the other servers, leave this message open on this server, and then run setup on the other servers in the farm. When all of the other servers are at this same stage, you can return to the frontend web server and click OK to continue with the SharePoint Products and Technologies Configuration Wizard.

      

      Figure 24-11. Install completed

    • If you have already run setup on all the servers in your server farm and they are all at this stage, on a frontend web server, click OK to continue with the configuration wizard.

17. On the Configuration Successful page (Figure 24-19), review the settings that have been configured and then click Finish. The SharePoint Products and Technologies Configuration Wizard closes, and the Upgrade Running page opens. You may be prompted to enter your username and password before the Upgrade Running page will open. The upgrade process might take a while to complete. The Upgrade Running page refreshes every minute.

18. After the process has completed, click Continue. The Central Administration home page opens (Figure 24-20).

You will see at this point that some of the jobs that were started to configure SharePoint Products and Technologies might not have been completed. You can check the status of these jobs on the Timer Job Status page from the Central Administration page (Figure 24-21).

Figure 24-12. SharePoint Products and Technologies Configuration Wizard

Figure 24-13. Restarting necessary services

Figure 24-14. Language Template message

Figure 24-15. Central Administration Configuration

Figure 24-16. Completing configuration

It might be a few minutes before these jobs are completed. You can also go back to the Central Administration page and click Finalize Upgrade to complete the process. Once all the jobs have been successfully completed, you should be able to see the status (Figure 24-22).

Congratulations! At this point your upgrade has been successfully completed, and you can launch the home page of your portal (Figure 24-23).

If the upgrade fails or reports issues, you can refer to the logfiles for more information. The Upgrade.logfile is located at %Windir%Program FilesCommon Files Microsoft SharedWeb Server Extensions12LOGS.

Figure 24-17. Configuration in process

Figure 24-18. Message prompting to run install on every server in the farm

Figure 24-19. Configuration Successful page

Figure 24-20. SharePoint Central Administration page shows the status of the upgrade

Figure 24-21. SharePoint Central Administration shows the status of pending jobs in the upgrade process

Figure 24-22. The SharePoint Central Administration page shows that all upgrade jobs have been successfully completed

Figure 24-23. Site successfully upgraded to SharePoint Office Server 2007

Similar to an in-place upgrade, a gradual upgrade takes place on the same hardware that is used for your previous version. However, in a gradual upgrade, you can control which sites are upgraded at any point, and it allows you to run both versions of your portal at the same time. When you implement a gradual upgrade, the starting and ending topologies are exactly the same, except for the following differences:

One of the obvious things to note is what happens to site URLs during the upgrade process. Obviously, site URLs have to be unique; therefore, during the upgrade process we need to make sure that we have different domain URLs for each site: the old site and the new site (for example, http://Portal_Old/sites/siteA and http://Portal_New/sites/SiteA). Hence, before we start the upgrade process, we need to make sure that we have a temporary domain URL. The upgraded sites take over the existing URLs and user requests will be routed to their content, regardless of whether it has been upgraded. The redirection process happens as follows:

So, let’s begin the installation and configuration of Office SharePoint Server 2007 for a gradual upgrade. This will install the new version alongside the previous version. After the installation is completed and you have configured Office SharePoint Server 2007, you can then determine which site collections to upgrade and when to upgrade them.

When upgrading a server farm, be sure to upgrade all of the servers in the server farm in the following order:

At this point, we need to make sure that all the prerequisite software for installing Office SharePoint Server 2007 is in place.

Next, let’s start the installation of Office SharePoint Server 2007 in a gradual upgrade. Make sure that you have performed all the preupgrade steps mentioned earlier the in-place upgrade instructions. Once again, I am going to start with the following environment: two SharePoint Portal Server 2003 Portals, with each of these having a few sites based on the old Windows SharePoint Services templates.

Most of the screenshots are the same as the in-place upgrade, so only the different screenshots are shown here:

Figure 24-24. Office SharePoint Server 2007 install, Gradual type selection

Before you start the SharePoint Products and Technologies Wizard, make sure you have performed the following steps:

Figure 24-25. Office SharePoint Server 2007 install, Complete type selection

Next, run the SharePoint Products and Technologies Configuration Wizard:

Gradual Upgrade

Upgrade sites

After you have performed a gradual upgrade, you can determine which sites to upgrade and when. Site upgrade can be implemented using either the upgrade pages in the SharePoint Central Administration Web Site or the upgrade operation on the command line. The command-line utility is more useful for large batches of sites at different times or if you have installed a language template packs upgrading other sites in your environment.

Figure 24-30. Completing the SharePoint Products and Technologies Configuration Wizard

Upgrade sites with Central Administration Pages. There are two phases in the process for upgrading sites from the Central Administration pages. First, create a new web application to host the upgraded versions of sites. Then, upgrade one or more site collections.

Warning

You must upgrade the root site collection before you can upgrade any other site collections in the web application.

Create a new web application to host upgraded sites

1. In Central Administration, on the Operations tab, under “Upgrade and Migration,” click “Site content upgrade status,” as shown in Figure 24-33.

2. On the Site Content Upgrade Status page (Figure 24-34), next to the URL you want to upgrade, click “Begin upgrade.”

   

   Figure 24-31. Finalizing the SharePoint configuration settings

3. On the Set Target Web Application page (Figure 24-35 and Figure 24-36), in the “Web Application to Upgrade” section, verify that the web application you want to upgrade appears, as shown in Figure 24-35.

4. In the “New URL for Original Content” section, type a port number in the Port box, and then in the Host Header box, type the host header to use (if needed), as shown in Figure 24-35.

5. In the Application pool for New Web Application section, select “Create new application pool.” In the “Application pool name” box, type a name, and then select either Predefined or Configurable.

   • If you selected Predefined, select which account to use.

   • If you selected Configurable, type the account name to use, and then type the password for that account.

     Warning

     You cannot use the same application pool that you used for the previous version. You can use the same user account, but you must create a new application pool or use an application pool that you already crated for your upgraded sites.

     

     Figure 24-32. Configuration Successful page

     

     Figure 24-33. Upgrade and Migration Status in Central Administration

     

     Figure 24-34. Site Content Upgrade Status page

     

     Figure 24-35. Set Target Web Application page

     

     Figure 24-36. Set Target Web Application page (lower half)

6. In the Reset Internet Information Services section, select either Restart IIS Automatically or Restart IIS Manually. If you choose Restart IIS Manually, you will need to restart IIS after the web application is created in the final step in this procedure.

7. In the “Security configuration” section, under Authentication Provider, select either Negotiate (Kerberos) or NTLM depending on your environment. If you select Kerberos, you will have to perform additional steps as defined in the Office SharePoint Server 2007 Installation guide.

8. In the Content Databases section, select either “Automatic database name selection” or “Manually set database names.”

9. In the SSP Database Settings section, in the SSP Database Name box, type the name for the Shared Services Provider database.

10. In the Search Database Settings section, type the name for the Search database.

11. In the Index Server section, in the Index Server box, select the Index Server to use.

12. Click OK:

    • If you choose to manually set the database names, the Database Names page opens. Type the names to use for the temporary content databases and the new version content databases for this web application, and then click Save.

    • An Operation In Progress page appears while the new web application is created. Once the web application has been created successfully, you will see the Site Collection Upgrade page, as shown in Figure 24-37.

Warning

If you choose to restart IIS manually, you must now run iisreset/noforce on each frontend web server in your server farm.

Upgrade Site Collections.

1. On the “Site Collection Upgrade” page (Figure 24-37), select the checkboxes next to the sites you want to upgrade, and then click Upgrade Sites.

   Warning

   You must upgrade the root site collection before you can upgrade any other site collections in the web application. If you are upgrading multiple site collections at one time, the root site collection must be included in the first set of sites that you upgrade.

   

   Figure 24-37. Site Collection Upgrade page

2. On the Sites Selected for Upgrade page (Figure 24-38), verify the number of site collections, the storage used, the originating database, and the target database, and then click Continue.

3. The Upgrade Running page (Figure 24-39) opens, and the upgrade runs for the selected site collections. This may take few minutes or a few hours, depending on how many site collections you have selected and how large the site collections are. If the upgrade fails or reports issues, you can refer to the logfile generated at the following location: %windir%Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12Logs. The trace log is named in the following format: Machine-name-YYYYMMDD-HHMM.log.

   

   Figure 24-38. Sites Selected for Upgrade page

   

   Figure 24-39. Upgrade Running page

4. After the upgrade process is completed successfully (Figure 24-40), click Home to return to the Central Administration home page.

   

   Figure 24-40. Site Collection Upgrade completed successfully

   At this point, if you access your site URL, you will see that the site collection root (Figure 24-41) has been upgraded to an Office SharePoint Server 2007 site (as shown in Figure 24-42), and the corresponding subsites that you selected have also been upgraded. On the other hand, the sites that you did not select for upgrade (Figure 24-43)—for example, Demo site five—still have the previous version template associated to the site. You can upgrade this site at any point by going back to the Central Administration step and performing the same steps again.

   The target URL that you had set up—in our case, http://spsweb01:9000—still has the portal from the previous version and the related subsites (Figure 24-44). This shows how you can have both versions of the portal side by side (Figure 24-45).

Perform a gradual upgrade with shared services (upgrading the parent portal first). Upgrading SharePoint Portal Server 2003 in a Shared Services requires that you perform the upgrade actions in the following specific sequence:

1. Upgrade the parent portal.

2. Upgrade the personal site host.

3. Upgrade My Sites.

4. Upgrade Team Sites.

5. Upgrade Child Portals.

Figure 24-41. Upgrade Site Collection page

Figure 24-42. Upgraded Site page

Upgrades of My Sites, team sites, and child portals can be done in any sequence; however, it is advisable to upgrade all My Sites at the same time, for consistent user experience.

Figure 24-43. Unselected sites not upgraded still utilize the template from the previous version

Figure 24-44. Target URL where our portal from the previous version is still available

Upgrade the parent portal. During a gradual upgrade in shared services, create a SQL Server backup file for the profile (PROF) and Component Settings (SERV) databases. This backup is stored in the default data directory for SQL Server, usually %PROGRAM FILES%mssqldata. Make there is enough disk space available to generate these backup files:

Figure 24-45. Both versions of the portal

1. Install and configure Office SharePoint Server 2007 for a gradual upgrade. Be sure to run setup on all servers in the farm.

2. Install language templates if necessary.

3. Check the logfiles for any open issues.

4. Configure the web application through the Central Administration pages.

5. Copy any Web Parts from the bin to the Office SharePoint Server 2007 web application. Copy all Web Parts marked as “safe control” in the web.config file. Install any upgraded Web Parts using their corresponding installers.

6. Prepare to upgrade the site collections:

   • Run the preupgrade scan tool again, review the reports, and troubleshoot issues.

   • You can use the command-line tool instead of Central Administration if you want to schedule the upgrade process or want to upgrade large numbers of site collections (more than 100 or so).

7. Upgrade the site collections, making sure to upgrade the root site web site first.

8. Review the Shared Services Settings. You will have to:

   • Recreate any search scopes.

   • Review upgraded content source definitions, crawl rules, etc.

   • Configure profiles and audiences to be synchronized between and Office SharePoint Server 2007.

   • Review the Manager properties of user profiles in Office SharePoint Server 2007.

   • Run a full crawl on the new portal site.

Upgrade the personal site host. Generally, the personal site and team sites hosts are the same as the parent portal. Perform the following steps only if you configured the Personal Sites or Team Sites to be on their own server farm:

1. Install and configure Office SharePoint Server 2007 for a gradual upgrade. Be sure to run setup on all servers in the farm.

2. Install language templates if necessary.

3. Configure the web application through the Central Administration pages.

4. Upgrade site collections, making sure to upgrade the root site web site first.

5. Review the upgraded sites.

During the upgrade process, if you are planning to utilize new hardware or just redesign your portal layout, you can choose to use the database migration method rather than using in-place or gradual upgrade. During the database migration, you perform an in-place upgrade on the database, but you do not upgrade your server farm configuration data. Even though this option is probably more complicated and tedious, it might be your best option if you have numerous customized sites.

In order to perform a database migration, first implement the following steps:

	Stsadm.exe–o addcontentdb–url URL [-databaseserver servername]–databasename
	databasename [-DatabaseUser username–DatabasePassword password] [-SiteWarning
	number] [-SiteMaximum number] [-SearchServer servername]

In order to finalize upgrade process, we need to perform the following post-upgrade steps:

This section reviews some of the common issues that come up while upgrading.

	Prescan /fixlocalhost

	prescan /all