E
Eleanor
If you had a choice, which would be easier?
Situation:
I have a server in production that is up and running with Project Server
2003 and WSS. A seperate server is running SQL. I have a brand new server
that I can rebuild and make into the new Project Server or I can use the
existing one in production and use the new one to off-load services to. The
system is not AD sync'd yet. Soloman's PSA link, when broken, is not easy to
re-connect to.
My other concern centers around outline codes, enterprise fields, RBS, etc.
It will not be a major overall (about 15 changes, mainly adjustment to the
existing configuration); however, I do need to:
* Rename the Custom Fields
* Delete some Custom Fields
* Delete some Enterprise Codes
* Delete some users
* Change cost codes
* Project Server accounts have been allowed and the system should probably
be only NT authentication.
The existing system has not be fully deployed (25 or so projects), so the
impact to the company thus far is nominal. I am wondering, before I run off
and test my theory in the lab, if rebuilting what is already in production
(Option A) is the best route to go or that I would be better off biting the
bullet and rebuilt everything on the new server and risk the Solomon
syncronization issue and the migration of data that would come with this
choice. I can, of course, do some testing to determine this; however, I am
consulting and they want a quick turn-around time (Okay, who does not have
this problem with their clients?
, and I thought I would, therefore, put
this question out before re-inventing the wheel.
Any input would be greatly appreciated
-Eleanor
Situation:
I have a server in production that is up and running with Project Server
2003 and WSS. A seperate server is running SQL. I have a brand new server
that I can rebuild and make into the new Project Server or I can use the
existing one in production and use the new one to off-load services to. The
system is not AD sync'd yet. Soloman's PSA link, when broken, is not easy to
re-connect to.
My other concern centers around outline codes, enterprise fields, RBS, etc.
It will not be a major overall (about 15 changes, mainly adjustment to the
existing configuration); however, I do need to:
* Rename the Custom Fields
* Delete some Custom Fields
* Delete some Enterprise Codes
* Delete some users
* Change cost codes
* Project Server accounts have been allowed and the system should probably
be only NT authentication.
The existing system has not be fully deployed (25 or so projects), so the
impact to the company thus far is nominal. I am wondering, before I run off
and test my theory in the lab, if rebuilting what is already in production
(Option A) is the best route to go or that I would be better off biting the
bullet and rebuilt everything on the new server and risk the Solomon
syncronization issue and the migration of data that would come with this
choice. I can, of course, do some testing to determine this; however, I am
consulting and they want a quick turn-around time (Okay, who does not have
this problem with their clients?
, and I thought I would, therefore, putthis question out before re-inventing the wheel.
Any input would be greatly appreciated
-Eleanor