• Article

Prepare your Project Server 2007 environment

 

Applies to: Project Server 2010

Topic Last Modified: 2011-09-10

In order to migrate to Microsoft Project Server 2010, you must prepare your Microsoft Office Project Server 2007 environment when you migrate from Microsoft Office Project Server 2003 to Office Project Server 2007. Things that you need to do to prepare your environment include the following:

  • Install Office Project Server 2007

  • Apply updates to Office Project Server 2007 and Windows SharePoint Services 3.0

  • Set up forms-based authentication (optional)

  • Back up all Project Server 2003 and Office Project Server 2007 databases

  • Determine the number of workstations where the migration tool must be installed

  • Install the migration tool

  • Apply updates to Microsoft Office Project Professional 2007 for the migration tool

If you do not have the Office Project Server 2007 installation media available to you within your company, you can download the evaluation version of Office Project Server 2007 from the Microsoft TechNet Office Project Professional 2007 and Office Project Server 2007 Evaluation Download Page. If you do not have Office Project Professional 2007, you should also download the evaluation version of it from that page, because you have to run the Migration Tool that is included with it.

Note

Microsoft also provides a Office Project Server 2007 virtual migration environment (VME) that can be used for migrating your Microsoft Office Project Server 2003 data to Office Project Server 2007. Office Project Server 2007 VME is a stand-alone environment that can be used only for migration purposes. It can be downloaded from the Microsoft Download Center and can be run on a virtual machine on a Windows Server 2008 R2 Hyper-V Server. It also includes many helpful migration scripts that can make the migration process easier. For more information, see Migrate your Project Server 2003 data by using the VME.

Install Project Server 2007

Which computer you install Office Project Server 2007 on is important — read IT deployment options for migration to Project Server 2007 (https://go.microsoft.com/fwlink/p/?LinkId=188765) closely and select an option that is right for you. For more information about how to install, see Deploy Project Server 2007 to a server farm environment (https://go.microsoft.com/fwlink/p/?LinkId=188762). Follow the instructions, install Project Server 2010, and provision a Microsoft Project Web App site to migrate to. For the purposes of this article, we will call that site the "target Project Web Access site."

Important

This Project Web Access site should be empty —that is, it should not have any projects, users, resources, or other global data.

Note

Office Project Server 2007 can be installed on the same computer as Project Server 2003. If you want Windows SharePoint Services to take over the Internet Information Services (IIS) virtual server that was hosting Project Server 2003, you have to create several "managed paths" to exclude the Project Web Access virtual directories. For more information, see the Knowledge Base article named How to enable an ASP.NET application to run on a SharePoint virtual server (https://go.microsoft.com/fwlink/p/?LinkID=25292).

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).

Apply updates to Project Server 2007 and Windows SharePoint Services 3.0

When migrating your Project Server 2003 data to Office Project Server 2007, you must apply the following updates to your Office Project Server 2007 environment:

  • Office Project Server 2007 Service Pack 2

  • Windows SharePoint Services 3.0 Service Pack 2

For information about how to apply both service packs, see Deploy Service Pack 2 for Office Project Server 2007 (https://go.microsoft.com/fwlink/p/?LinkId=188768).

We also recommend that you also apply the latest cumulative updates to Office Project Server 2007. For more information about how to apply cumulative updates, see Deploy cumulative updates (Project Server 2007) (https://go.microsoft.com/fwlink/p/?LinkId=188772).

Set up forms-based authentication, if necessary

If you are using Project Server authenticated users (non-Windows users) in Project Server 2003, you will not be immediately able to log on to 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-based authentication on the Office Project Server 2007 installation — and this is a separate step. For more information, see Plan Project Server 2007 authentication method (https://go.microsoft.com/fwlink/p/?LinkId=188779).

When this step is completed, you should have forms-based 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

  • 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 have 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 databases and retry the migration.

The Office Project Server 2007 configuration and content databases can be backed up in case a non-recoverable problem occurs when you migrate Windows SharePoint Services workspace data to Office Project Server 2007. A pre-migration database backup will assist you 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 a good idea if the database is large enough that backing up or restoring will take a long time. In this case, you have to manually set up 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 Configure a linked server in SQL Server (Project Server 2010).

  • Restore Project Server 2003 database(s) to the same computer that is hosting the Office Project Server 2007 databases: This is a good idea 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 as needed.

Install the migration tool

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

To 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 that you specify. The default location is as follows: C:\Program Files\Microsoft Office\OFFICE12.

To 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 or Remove Programs.

  3. From the Currently installed programs list, select 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. On 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 as follows: C:\Program Files\Microsoft Office\OFFICE12.

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

Apply updates to Project Professional 2007 for the migration tool

You must apply updates to the Office Project Professional 2007 installation on which the migration tool is used. You should apply the following:

  • Office Project Professional 2007 Service Pack 2

  • The latest cumulative update for Office Project Professional 2007 (this should match the date of the cumulative update applied to Office Project Server 2007).