Moving Project Server to New Domain

S

sqldude7777

Howdy


I get all t he fun jobs....;-)

I have a need to move our Prod box from one domain to another doamin
of a different domain as the old domain is de-commissioned.

I have discovered there are many links with AD in PS, so users and
ownership of projects etc may be an issue.

Has anyone moved PS to a different domain and if so how did you do it
please?

My approach to moving PS content has been to copy the 4 SQL DBs for
Project Server & 2 DBs for Shared Services & 1 DB for search, and
then restore these on the new box. Then I'd export all the old sites
and import these onto the new server ( Thanks Mrc for help on
this...).

However, I suspect the security side of things will cause problems and
it will be messy to say the least. One of my concerns is as users
created in the system on the old domain own objects, deleting these
users is difficult as they seem linked deeply within the app and its
near impossible to remove them. I notice there are STADM commands to
do with users and domains, but dont know if these are applicable or
not in this case.

Any thoughts please?

Thansk in advance,

SD.
 
J

James Fraser

I have a need to move our Prod box from one domain to another doamin
of a different domain as the old domain is de-commissioned.

I have discovered there are many links with AD in PS, so users and
ownership of projects etc may be an issue.

Has anyone moved PS to a different domain and if so how did you do it
please?

I've worked on some related activities. Moved a 2003 environment in
one domain to 2007 in another in one case, and for test/demos, I've
done pieces of what you are trying to do.

First, realize you are trying to do two separate things:
1) Move Project Server with its projects to a new domain.
2) Move a bunch of SharePoint sites to a new domain.

Migrating the Project Server shouldn't be bad. Build a clean new
server in the new domain, but when you provision the databases, use
the four restored databases. Make sure the versions of Project server
installed match, down to the sharepoint and PS hotfixes. This will
create one user with admin rights in the new domain. You can then open
the resource pool and replace the old domain credentials with the new
ones.

Find out how many of the Project SharePoint sites are being used. If
it's only a few, you can do some of this migration work "by hand" with
STSADM.

Once the sites are restored, they need to be linked in PWA -> Server
Settings -> SharePoint workspaces. Then the next publish of a project
will add new permissions. You will have problems with any lists in
sharePoint sites that were set with custom permissions. They don't
inherit the new permissions, so they will need to be editted by hand
unless you try the STSADM userreplace functions (I forget if that's
the exact name, but there is something like that in the STSADM tool.)


Hope this gives you some direction...
James Fraser
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top