Migrating EPM and Project Server

[Doug]

To All,

Does anyone know or where we can get documentation on migrating the Project
Server 2007 and EPM environment to a new domain? We had set up a test
environment and wish to go live. Unfortunately we tested in a seperate domain
and need to migrate into our current live domain (Project Server, SQL2005,
and EPM).

Any help (suggestions, whitepapers, tools, etc) would be greatly appreciated.

Thanks
Doug

 

[Marc Soester [MVP]]

Hi Doug,

I see what your problem is. In Project Server 2007 at present you are not
able to transfer your configuration from one server to another server. (
using backup restore for example).

Essentially you will need to re-isntall Prjoject Server on your live
environment and manually set the configuration again.

We have been trying to migrate server settings from one to another server
but have discovered that there are issues ( notification doesnt work etc).
Microsoft is aware of the issue, which has been logged as a bug. Hopefully
they will fix this soon, since we have the same issue when we roll out EPM to
our clients.

 

[mike.mahoney]

To All,

Does anyone know or where we can get documentation on migrating the Project
Server 2007 and EPM environment to a new domain? We had set up a test
environment and wish to go live. Unfortunately we tested in a seperate domain
and need to migrate into our current live domain (Project Server, SQL2005,
and EPM).

Any help (suggestions, whitepapers, tools, etc) would be greatly appreciated.

Thanks
Doug

Hi Doug

I regularly pull the production projectserver databases on to a
development environment. What I have yet to discover is an effective
way to move related sharepoint data.

Simply take the backups of the existing project server environment and
restore them over the empty production databases. To do this you need
to stop the various project server and sharepoint services which are
running processes against the db's. Restart the services.
Note my dev environment mirrors the production environment in terms of
service/pool accounts.
You need to review cube, alert, workspace setting to reflect the new
environment.
If any plans are associated with workspaces, you need to remove these
values from MS_Projects table in the Published database (set
WPROJ_STS_SUNSEB_NAME to <Null>)
I have experienced some initial problems logging on for some users and
have resolved it by re-saving the resource pool

regards

Mike

 

[Doug]

Mike,

Thanks for the info but what will happen if the dev database was on a
different domain than our production one? Do we have to modify within the
tables (domain\username)? Seems a bit messy but we need to try something.

Thanks
Doug

 

[Marc Soester [MVP]]

Hi Doug,

Mike's suggestion is a valid one, but will bring some issues if you are also
after workspaces ( which I believe you are) plus it will not resolve the
issue of having to restore Project server to a new domain. Further to this, I
personally dont like working directly in the database tables ( and believe
Microsoft does not support this approach. By saying this, I understand that
it has to happen at times to fix issues)

the problem you have at present, if you back up and restore project server
2007 from one to another server, the timer jobs in WSS will not work anymore.
(e.g. automatically empty receicle bin) - ( check out the all the timer jobs
under timer job definitions in the central administration of WSS. All of
them will not work anymore)

Another issue is the domain move. Generally I would assume that, as long as
the domains are trusted domains, that you should be fine. If they are not
trusted, you will have to manually recreate Project Server on the new domain.

I hope this helps

 

[Doug]

Marc,

Thanks for the excellent feedback. I concur with your statement and will go
with the trust relationship method.

Thanks
Doug