How do I move Project Server 2003/WSS to a new server?

[Russ]

I currently have a single server deployment of Project Server 2003 (Project
Server, WSS and SQL all on the same box). I would like to move to a 2 server
configuration in which Project Server and WSS are on one box, and the
database server is on another. Neither of the two new boxes would have the
same name as the box that the apps are currently running on.

I have attempted to deploy the 2 server configuration using the following
steps.

1. Restore Project Server database to the new database server.

2. Install WSS and Project Server on the new application server (using the
'connect to an existing Project Server database' option).

3. Create WSS project workspaces on the new deployment via the Project
Server admin interface.

4. Backup project workspace data from the original WSS deployment using the
WSSMigr.exe.

4. Overwrite project workspaces on the new deployment with the data backed
up in the previous step using the WSSMigr.exe.

The migration appeared at first to be successful; I was able to access
Project Server via the web, the WSS sites were restored successfully and
matched to the appropriate projects, and the data all seemed to be intact.
However when I tried to open an issue, the application (on some level) was
trying to access project server via the original server name; Specifically,
when I clicked on an issue, I recieved a message stating that Sharepoint
could not access Project Server, and that I should add
'http://originalservername' to my trusted sites.

I have searched the registry and files on the new application server, as
well as the Project Server and Sharepoint databases, but have not been able
to find any reference to the original server. Any ideas?

 

[Rick Roszko]

The entire process is mapped out in KB article 905386...

(a) Go to www.microsoft.com
(b) In the search box, just type in 905386

It's a step by step proces for both SharePoint Services and Project Server...

 

[Russ]

I currently have a single server deployment of Project Server 2003 (Project
Server, WSS and SQL all on the same box). I would like to move to a 2 server
configuration in which Project Server and WSS are on one box, and the
database server is on another. Neither of the two new boxes would have the
same name as the box that the apps are currently running on.

I have attempted to deploy the 2 server configuration using the following
steps.

1. Restore Project Server database to the new database server.

2. Install WSS and Project Server on the new application server (using the
'connect to an existing Project Server database' option).

3. Create WSS project workspaces on the new deployment via the Project
Server admin interface.

4. Backup project workspace data from the original WSS deployment using the
WSSMigr.exe.

4. Overwrite project workspaces on the new deployment with the data backed
up in the previous step using the WSSMigr.exe.

The migration appeared at first to be successful; I was able to access
Project Server via the web, the WSS sites were restored successfully and
matched to the appropriate projects, and the data all seemed to be intact.
However when I tried to open an issue, the application (on some level) was
trying to access project server via the original server name; Specifically,
when I clicked on an issue, I recieved a message stating that Sharepoint
could not access Project Server, and that I should add
'http://originalservername' to my trusted sites.

I have searched the registry and files on the new application server, as
well as the Project Server and Sharepoint databases, but have not been able
to find any reference to the original server. Any ideas?

I beleive that I've found the answer. You must follow the steps outlined
above, but with one additional step.

5. Select 'Manage Windows SharePoint Services --> Manage SharePoint sites'
from the left navigation pane on the 'Admin' page. For each project listed,
select the project (by clicking in the margin next to it) and press the
'synchronize' button, on the top menu.

I performed the steps shown above, and everything seems to work fine. I
will be putting it through rigerous user testing before implementing in
production, and will let you know if I discover any problems.

Russ

 

[Russ]

Thanks for your reply.

This KB shows how to move the databases to a new server; however, my problem
was more on the application server side. If you simply backup and restore
the databases as outlined in this kb article, you must either use the same
application server name, or search through the sharepoint content database
and replace any reference to the original application server with a reference
to the new one (and I'm not entirely sure that this will work, as I've been
unsuccessful with this approach). Anyways, I believe I've found the answer.
It is in my other post on this question.