Prepare for migration to Project Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

Topic Last Modified: 2016-11-14

In this article:

• Upgrade to Project Server 2003 Service Pack 2a

• Install Windows SharePoint Services 3.0

• Install Project Server 2007

• Set up forms authentication, if necessary

• Back up and restore the Project Server 2003 and Project Server 2007 databases

• Install the migration tool

• Give appropriate permissions to the Migration Administrator account

• Verify that the Migration Administrator account has appropriate access

Before running the migration from Microsoft Office Project Server 2003 to Microsoft Office Project Server 2007, several tasks are required in preparation. This article describes the steps that are required.

Upgrade to Project Server 2003 Service Pack 2a

Microsoft Office Project Server 2003 SP2a is composed of three parts, each of which can be downloaded and installed separately, as needed:

1. An upgrade for the Office Project Server 2007 database

2. An update for the Project Server application binaries

3. An update for the Project Server template files on Windows SharePoint Services

Depending on your migration deployment strategy, you may need one or more of the parts listed above.

• To upgrade your existing installation to the latest service pack, you must use all three parts and upgrade your existing Project Server 2003 and Windows SharePoint Services 2.0 installation to SP2a. This is the simplest way to upgrade.

• To keep your existing Project Server 2003 installation (without applying SP2a), you must do the following:

  • Create a backup of your Project Server 2003 database. Restore it, optionally using a different name. Apply SP2a part 1 to the restored database.

  • Apply SP2a part 3 to the Windows SharePoint Services 2.0 installation.

  You might choose this option because you are going to deploy Office Project Server 2007 anyway and you do not want to complicate your process with an SP2a rollout.

  Note

  More information about the service pack can be found in the Knowledge Base article named Description of Project Server 2003 Service Pack 2a (https://support.microsoft.com/kb/887621). All the SQL files required for applying the Project Server 2003 SP2a database upgrade are also available in the Utilities\Migration\Database\PS03SP2a folder.

Install Windows SharePoint Services 3.0

You must install Windows SharePoint Services 3.0 if you want to upgrade your Windows SharePoint Services 2.0 data. If you are installing on a new computer, you need not install Windows SharePoint Services 3.0 separately — when you install Office Project Server 2007, it installs Windows SharePoint Services 3.0 automatically. So this step is only needed for the following migration deployment options:

• Full migration: Project Server 2003 with Windows SharePoint Services 2.0 (on the same computer)

• Full migration: Project Server 2003 with Windows SharePoint Services 2.0 (to a different computer)

• Gradual migration: Project Server 2003 with Windows SharePoint Services 2.0 (on the same computer)

• Gradual migration: Project Server 2003 with Windows SharePoint Services 2.0 (to a different computer)

In any of the above deployment options, when you install Windows SharePoint Services 3.0, it detects the existing Windows SharePoint Services 2.0 installation and gives the following options:

1. Yes, perform a Gradual upgrade. This will allow the existing installation to function and enable you to upgrade web sites in batches. This is best for large installations or where web sites have been extensively customized.: This is a gradual migration that allows Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0 farms to function side-by-side. You can selectively upgrade the Windows SharePoint Services 2.0 workspaces for the projects that will be migrated gradually. (Do not upgrade them yet; that process is covered in a different article). You can do this by using the SharePoint Central Administration Web site. (For more information, see Upgrading to Windows SharePoint Services 3.0). As projects are published, the links between Project items and Windows SharePoint Services items are fixed.

   Note

   In order to continue creating Project Server 2003 workspaces on Windows SharePoint Services 2.0, administrators need to make a change to the "Default Provisioning Settings" of Project Server 2003. As part of the gradual upgrade process, Windows SharePoint Services 3.0 takes over all the virtual servers used by Windows SharePoint Services 2.0, relocates the Windows SharePoint Services 2.0 sites to other temporarily created virtual servers and redirects the links (with the assumption that eventually all the Windows SharePoint Services 2.0 content will be migrated to Windows SharePoint Services 3.0). These temporary virtual servers need to be used for the Windows SharePoint Services 2.0 site creation. (For more information, see Upgrading to Windows SharePoint Services 3.0.)

2. Yes, perform an automated in-place upgrade. All web sites and databases will be upgraded; the process will continue until complete. This is best for installations with few databases and less than 30GB of content.: If you choose this full migration option, all your project workspaces in Windows SharePoint Services 2.0 are upgraded to Windows SharePoint Services 3.0. Note that even after you complete this step, the migrated workspaces will not function. (The corresponding Office Project Server 2007 Windows SharePoint Services templates are not yet installed — they will be installed with Office Project Server 2007.) As projects are published, the links between Project items and Windows SharePoint Services items are fixed.

3. No, do not upgrade at this time. The new version can be installed alongside the existing product and can run without impacting the older installation.: Do not choose this option.

Read the "IT Deployment options for migration" article closely. More information on how to upgrade to Windows SharePoint Services 3.0 can be found in the Upgrading to Windows SharePoint Services 3.0.

Install Project Server 2007

Which computer you install Project Server 2007 on is important — read the IT deployment options for migration to Project Server 2007 article closely and choose an option that is right for you. For more information on how to install, see Deploy Project Server 2007 to a server farm environment. Follow the instructions, install Office Project Server 2007, and provision a Microsoft Office Project Web Access site to migrate to. For the purposes of this article, we will call it the "target Project Web Access site."

When this step is completed, you should have an empty, working Project Web Access site into which you can migrate (the "target Project Web Access site" alluded to earlier).

Set up forms authentication, if necessary

If you are using Project Server authenticated users (non-Windows users) in Project Server 2003, you will not be readily able to log onto Office Project Server 2007 with those accounts after migration. Office Project Server 2007 relies on Windows SharePoint Services and ASP.NET forms authentication infrastructure. Therefore, you need to set up forms authentication on the Project Server installation — and this is a separate step. For more information, see Plan Project Server 2007 authentication method.

When this step is completed, you should have forms authentication enabled and working on the target Project Web Access site.

Back up and restore the Project Server 2003 and Project Server 2007 databases

We recommend that you back up all Project Server 2003 and Office Project Server 2007 databases that are involved in the data migration.

The following databases should be backed up:

• Project Server 2003 database

• Office Project Server 2007 databases:

  • Published

  • Reporting

  • Draft

  • Versions

• Microsoft Windows SharePoint Services 3.0 configuration and content databases

Once you have created backup copies of the databases that are involved with data migration, you can quickly restart the migration if any non-recoverable problems occur during the migration process. For example, if an error occurs during migration due to a data problem in Project Server 2003, it might corrupt the Office Project Server 2007 database. If the problem is corrected in Project Server 2003, you will need to create a new Office Project Server 2007 Project Web Access site before retrying migration. However, if an Office Project Server 2007 backup is already available, it will not be necessary to recreate a new Project Web Access site; you can simply restore the Office Project Server 2007 Project Web Access database and retry the migration.

The Windows SharePoint Services 3.0 configuration and content databases can be backed up in the event that a non-recoverable problem occurs when migrating Windows SharePoint Services workspace data to Windows SharePoint Services 3.0. A pre-migration database backup will assist in quickly starting over again.

Next, you must decide where to restore the Project Server 2003 database(s).

• Keep the Project Server 2003 database(s) on a separate computer from the Office Project Server 2007 databases: This is advisable if the database is large enough that backing up or restoring will be very time-consuming. In this case, you need to manually setup a "linked server" on the Office Project Server 2007 computer that points to the Project Server 2003 computer. For more information, look at the Project2003LinkedSQLServer parameter in the migration configuration file. For more information, see Configuring the migration tool for Project Server.

• Restore Project Server 2003 database(s) to the same computer that is hosting the Office Project Server 2007 databases: This is advisable for optimizing performance — the migration process is faster if the Project Server 2003 database and the Office Project Server 2007 databases are on the same computer.

When this step is completed, you should have all the relevant databases backed up so that you can restore them and quickly restart migration.

Install the migration tool

The migration tool is available on the Microsoft Office Project Professional 2007 installation media. (It is not installed by default.) The migration tool does not need to be installed on the Project Server computers that are involved in the migration; it only needs to be able to connect to them over the network. Use the following procedures to install the migration tool.

Install the migration tool (if Office Project Professional 2007 is not installed)

1. Run Setup on the Office Project Professional 2007 installation CD.

2. Select the Customize option. (Do not select Install Now).

3. On the Installation Options tab, expand the feature tree for Microsoft Office Project 2007.

4. Right-click Migration tool and change its state from Not Available to Run from My Computer.

5. Click Install Now. The migration tool executable file (P12migrationtool.exe) file is installed to the location you choose. The default location is: C:\Program Files\Microsoft Office\OFFICE12.

Install the migration tool (if Office Project Professional 2007 is already installed)

1. In Windows XP, click the Start button, and then click Control Panel.

2. In Control Panel, double-click Add/Remove Programs.

3. From the Currently installed programs list, select Microsoft Office Project Professional 2007, and then click Change.

4. In the Change your installation of Microsoft Office window that appears, select Add or Remove Features, and then click Continue.

5. In the Installation Options tab, expand Microsoft Office Project and right-click Microsoft Office Project Upgrader tool. Change the status from Not Available to Run from My Computer.

6. Click Continue. This action starts the installation of the migration tool, which adds the migration tool executable file (P12migrationtool.exe) to the same location as the Office Project Professional 2007 executable file (WinProj.exe). The default location is: C:\Program Files\Microsoft Office\OFFICE12.

7. When installation successfully finishes, click Close on the next window that appears.

How to run the migration tool

To run the migration tool, open a command prompt, go to the directory that contains the migration tool executable file (the default location is C:\Program Files\Microsoft Office\OFFICE12), and then run P12migrationtool.exe with the command-line parameters that you need. For example:

D:\Program Files\Microsoft Office\OFFICE12>P12MigrationTool.exe -c d:\migration\ProjectServer2007Migrate.ini

The following table lists and describes the options available for the P12migrationtool.exe.

If both the SQL Server authentication and forms authentication user name and password are not specified, the migration tool will be run under Windows authentication by using the identity of the currently logged on user.

If a user name is specified, but not a password, the migration tool prompts for the password.

When this step is completed, you should have a working Office Project Server 2007 migration tool.

Give appropriate permissions to the Migration Administrator account

The Migration Administrator account is the account with which the migration is run. In other words, the P12migrationtool.exe command-line tool is run under this account. The account needs the following permissions:

• Database reader permissions on the Project Server 2003 database(s)

• Administrator permissions on the target Project Web Access site

  Adding the Migration Administrator account to the default (unaltered) "Administrators" security group should give all relevant permissions. If an enterprise resource with the same name or Windows account exists in Project Server 2003, the Migration Administrator account has to be made an enterprise resource as well.

• System administrator privileges on the Office Project Server 2007 databases

  Adding the Migration Administrator account to the "SysAdmin" SQL group gives this permission. If the Migration Administrator account is the farm administrator on the Office Project Server 2007 farm, then this permission will already be available.

Verify that the Migration Administrator account has appropriate access

After installing Office Project Server 2007, you need to verify that your installation is functional before proceeding to migrate data to it. You can do this by performing the following tasks.

1. Using the Migration Administrator account, log on to the computer on which you have installed the migration tool.

2. Navigate to the 2007 version of Office Project Web Access. Log on by using the Migration Administrator account and make sure that you can access any page in Office Project Web Access Server Settings. This ensures that when the migration tool tries to add data to Office Project Server 2007 by using the Migration Administrator account, it will succeed.

3. Start Office Project Professional 2007, create a profile with the Migration Administrator account, and then connect to Office Project Server 2007 with that profile.

4. Create, save, and publish a project. Verify that you do not encounter any errors during this process. Delete the project when you are done.

5. Open SQL Query Analyzer, connect to the computer running SQL Server that is hosting the Project Server 2003 database(s), and login using the Migration Administrator account. Verify that you can access data in each Project Server 2003 database(s).

6. Open SQL Query Analyzer, connect to the SQL Server hosting the Project Server 2007 database(s), and log in using the Migration Administrator account. Verify that you have system administrator privileges.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

• Migration for Office Project Server 2007

See the full list of available books at Downloadable content for Project Server 2007.

See Also

Concepts

Pre-migration verification and cleanup