Project Server VME: Do post-migration tasks

Verify that the migration was successful

During each of the three instances that the migration tool was run in the Migration phase (verification, enterprise global data migration, project migration), verify from the migration tool command line display or from the migration logs that the migration was successful. If the migration tool failed at any point, view the contents of the migration log file for more information about the error. Make corrections, import the updated data to the VME, and then re-run the migration tool.

If there is an irrecoverable problem, restore the VME virtual machine image to the original configuration, import and restore your Project Server 2003 databases, and then retry migration. Hyper-V manager automatically takes a snapshot of the VME virtual machine when the image is first restored. You can reapply the snapshot (titled "As Shipped") to restore the VME to its original state.

If the migration process appears to have been successful, ensure that the data migrated correctly to Office Project Server 2007 by doing the following tests:

• Verify project data: Open the migrated projects in Project Professional 2007, change them, add enterprise resources, publish them, accept status updates, and so on. The VME includes Microsoft Office Project Professional 2007.

• Verify Project Web Access data: Open Office Project Web Access to connect to your data. Verify that you can fill timesheets, create proposals, and so on.

We highly recommend that you have a migration checklist specific to your needs and that you test those items after migration.

Update migrated server settings

Not all kinds of data can be migrated from Project Server 2003 to Office Project Server 2007. (See Data that cannot be migrated to Project Server 2007.) Therefore we recommend that you review all the Office Project Server 2007 server settings and make sure that they are as you want them to be. Some specific areas are listed here:

• Security settings: There are some security permissions (global and category) that are new in Office Project Server 2007. These permissions may not get migrated. You may want to review each one and decide on whether to give users that permission. For more information, see Security and protection for Office Project Server 2007.

• Project Web Access view definitions: The "Filter by" and "Group by" clauses are not migrated from Project Server 2003. You may have to re-create these clauses. Also, some Office Project Web Access view fields do not migrate. You may want to make sure that all the fields important to you are available in the migrated views.

• Merge and rename similar security groups, categories, and templates and Project Web Access view definitions: If there is a naming conflict during migration that involves security templates, view definitions, or security groups or categories, the migration tool attaches a prefix or suffix to the conflicting names. This action is taken to preserve both Office Project Server 2007 entities and Project Server 2003 entities in one system. Then you can select which one to keep or else decide to merge them, as appropriate. We recommend that you resolve them so that end users do not become confused.

Synchronize the migrated forms-authenticated users by using the Project Server 2007 forms-based authentication store

This is a required step to make sure that the migrated forms-authenticated users work in Office Project Server 2007. For more information, see Configure SQL Membership Provider forms authentication for Project Server 2007.

Verify the project workspace provisioning settings

In Office Project Server 2007, the migration tool resets the Automatically Provision option in the Project Workspace Provisioning Settings page of Server Settings to Manually Create a workspace for each project. This setting ensures that the migration process does not provision duplicate workspaces for projects that may already have workspaces that are yet to be migrated.

After running the migration tool, check the Project Workspace Provisioning settings located in the Operational Policies section of Office Project Web Access Server Settings. Verify that the Site URL and the Automatic Provisioning options are configured correctly per your needs. In Office Project Server 2007, after the migration tool is run, you may want to reset the Automatically Provision option to Automatically create a workspace for the project when a project is published.

Delete migrated inactive users (optional)

By default, the Manage Groups page in Project Server 2003 does not display inactive users. But in Office Project Server 2007, by default, inactive users are displayed. Therefore, after the migration process (which migrates the inactive users also), you may see additional users in the Manage Groups Project Web Access page in Office Project Server 2007.

You can permanently delete the inactive users, if you need to.

To permanently delete the inactive users

1. In Office Project Web Access, click Server Settings.

2. In the Database Administration section, click Delete Enterprise Objects.

3. On the Delete Enterprise Objects page, in the What do you want to delete from Project Server section, select Resources and Users.

4. In the list of users that appears, select the users that you want to permanently delete, and then click Delete.

Fix project currency settings

It is a known issue that project currencies are not migrated correctly. Run the following query on the Project Server 2003 Project Tables database to get a list of projects and their currencies. This information can be used to manually correct the currency settings after migration.

select PROJ_NAME, PROJ_OPT_CURRENCY_SYMBOL from dbo.MSP_PROJECTS where PROJ_TYPE in (0, 1, 2)

Change local Windows accounts that were migrated

Local Windows accounts (for example, ComputerName\Brad Joseph), for computer names that are no longer valid should be removed. Go to Office Project Web Access Server Settings and use the Manage Users options to edit those accounts so that they are valid.

Update multi-language lookup tables

Multilanguage lookup tables are not updated correctly after migration. Run the following SQL statements on the Office Project Server 2007 Published database to resolve this problem.

DELETE FROM dbo.MSP_LOOKUP_TABLE_LANGUAGES WHERE LT_UID NOT IN (SELECT LT_UID FROM dbo.MSP_LOOKUP_TABLES)
DELETE FROM dbo.MSP_LOOKUP_TABLE_MASK_VALUES WHERE LT_UID NOT IN (SELECT LT_UID FROM dbo.MSP_LOOKUP_TABLES)
DELETE FROM dbo.MSP_LOOKUP_TABLE_MASK_STRUCTURES WHERE LT_UID NOT IN (SELECT LT_UID FROM dbo.MSP_LOOKUP_TABLES)
DELETE FROM dbo.MSP_LOOKUP_TABLE_VALUES WHERE LT_UID NOT IN (SELECT LT_UID FROM dbo.MSP_LOOKUP_TABLES)
DELETE FROM dbo.MSP_LOOKUP_TABLE_STRUCTURES WHERE LT_UID NOT IN (SELECT LT_UID FROM dbo.MSP_LOOKUP_TABLES)

If you are using Microsoft Office Project Portfolio Server 2007 with Office Project Server 2007, it is especially important to run these SQL statements to update the tables. If the statements are not run, you may encounter a "GeneralUnhandledException" error when you perform an export from Office Project Portfolio Server 2007 to Office Project Server 2007. The error would resemble this and would appear in the ULS logs:

PSI: LookupTable.ReadLookupTablesMultiLang Undefined Attibutes: PSError: GeneralUnhandledException Underined attributes list: System.Data.ConstraintException: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints….

Address user and permission issues

After migration (especially in localized builds), the users may not have certain expected permissions in the migrated Office Project Server 2007 installation. For example, imagine that you were assigned your permissions through the administrator template, but you cannot view timesheets. There are several reasons that such a situation might occur:

1. In Project Server 2003, a permission is denied at the organization level. You can verify this by checking your Office Project Web Access permissions to see whether any are disabled and whether they are the cause of your problem. To check your Office Project Web Access permissions:

   1. In the Office Project Web Access home page, in the left pane, click Server Settings.

   2. In Server Settings, in the Security section, click Project Web Access Permissions.

2. There are some permissions that are new in Office Project Server 2007. These permissions may not be mapped correctly during migration. You can check the Security documentation for a list of these permissions to determine whether they are the cause of your problem. For more information about Office Project Server 2007 permissions, see Security and protection for Office Project Server 2007.

3. If a Project Server 2003 user or resource exists in Office Project Server 2007 (by name or Windows NT account), then that user or resource’s security permissions are not migrated. For example, if you had done an Active Directory synchronization before migration (and if most of those users exist in Project Server 2003), those user permissions would not have been migrated. This problem should not be encountered in the VME, because the Office Project Server 2007 environment you are migrating to should not have any users in it before the migration process.

Address authentication issues

Project Server authentication is used in Project Server 2003, but it is not supported in Office Project Server 2007. When you migrate Project Server authenticated users to Office Project Server 2007, the user accounts are reset, because the forms-based authentication mechanism in Office Project Server 2007 is architecturally different from the Project Server authentication that is used in Project Server 2003. You do not see these users listed in the Office Project Web Access Server Settings Manage Users page, or the User Authentication section for the user does not appear. However, you can still edit these migrated users in the Project Web Access Resource Center.

Address master-project issues

When you migrate master projects and their associated subprojects from Project Server 2003 to Office Project Server 2007, the following two scenarios cause the project migration to fail:

• A subproject that is migrated after its master project. (You can correct the order of migration in the migration configuration file.)

  Important

  For more information about the migration configuration file, see Configure the migration tool (Project Server).

• A project that is a subproject to two master projects. (Such an arrangement is allowed in Project Server 2003, but not in Office Project Server 2007). The migration for this project will fail when you attempt to publish the project.