Upgrade form Project Server 2003 to 2007

J

Jayalakshmi

Hi,

My organisation wants to upgrade from 2003 to 2007 Server.

I am having some doubts:

1) Advantages of upgrading to 2007?

2) Differences in how timesheets are handled? What would the workflow
be, are there any controls so data is not changed once it is submitted?

3) Re-training requirement, which areas are different?

4) Process for upgrading, e.g. are there any issues with the current
data?

5) How is custom field information transferred during the upgrade?

6) Does 2007 allow for direct access from multiple locations (without
the use of Citrix)?

7) Does 2007 allow multiple servers to share the same database?

Please help me with this.

Thanks in advance...
 
P

Paul Conroy

See inline

Jayalakshmi said:
Hi,

My organisation wants to upgrade from 2003 to 2007 Server.

I am having some doubts:

1) Advantages of upgrading to 2007?
http://office.microsoft.com/en-au/epmsolution/HA101655111033.aspx

2) Differences in how timesheets are handled? What would the workflow
be, are there any controls so data is not changed once it is submitted?

This area is arguably causing the most issues. Task Updates and Timesheets
are now two separate functions. Basically Task Updates updates project
related time, whereas timesheets can be used to report on all time.

http://office.microsoft.com/en-au/projectserver/CH101477261033.aspx
http://office.microsoft.com/en-au/projectserver/CH101477381033.aspx

The workflow would change depending on whether you use timesheets or not.

Timesheets are approved by the timesheet manager, whilst task updates are
approved by the status manager (which maybe different people)
3) Re-training requirement, which areas are different?

Systems admins, application admins would need a fair amount of re-training
(www.msepmu.com). End users however would probably only need a single day
overview of the new features (depending on their existing knowledge of 2003)
4) Process for upgrading, e.g. are there any issues with the current
data?

I've not done a migration for a while and there was issues by the dozen.
Things may have changed with later releases of hotfixes etc.

I would strongly recommend multiple migration tests before moving the
production system. See the guides below

http://technet.microsoft.com/en-nz/library/cc303388(en-us,TechNet.10).aspx
5) How is custom field information transferred during the upgrade?

All enterprise fields get migrated, but the structure is different between
the versions. See the guide above.
6) Does 2007 allow for direct access from multiple locations (without
the use of Citrix)?

It's significantly better than 2003 due to the introduction of client side
cache and web services. With very high latency WAN connections, you may
still need to look at a thin client solution.
7) Does 2007 allow multiple servers to share the same database?

You can have multiple servers and instances of project server in the same
farm. Each project server instance requires it's own set of databases. all
servers should be on the same subnet.
 
H

hanni

Listen to me:

DONT DO THIS!!!

not now - not yet.

MSP 2007 has so many problems that I really do not understand why
Microsoft released this version.

I have projects that I cannot have access to (they stay in Check in
pending for days. it doesnt help that I try to force checkin)
I have projects I can open as "read only"
I have 1 project that the project start date chenged to 2049!!! and it
changed the all project to somthing not readble. it even changed the
task that were already 100% completed.

Stay with 2003

I'll be happy to let you know when ths 2007 will usable.
 
D

Dean C

Item5: Do before Item 4. Open an existing file and a new file created using
2007. Use Organizer to copy all customization to the new file. Verify that
Outline Code Fields and fields using values lists have transferred correctly.
Save the new file as a template for updating all files.
Item 4: Move your files to files created using the template described above
using any of the techniques for fixing corrupted files. If you do not, you
will eventually have corrupted files.
 
H

hanni

in the company we installed MSP 2007 & the server + SP1 (is it called
PS1?) + hot fix for problems that PS1 didnt solve.
it didnt help.
I still have projects that got stock in CHECK OUT status. I cannot
force check in on them from some reason.
another problem is that almost all the files I open (that are checked
in) open as "read only" files. what i usually do is I open the file.
it open as read only. I close the file without saving and reopn.
usually is solve the problem. sometimes when I close a read only file
I get a message that says I had a rpoblem with saving (I closed the
file without saving since it is a read only file) and then I enter the
"check in" problem loop again (as I described above)
I ahd a rpoblem with saving notes (all my old notes were deleted) this
proeblem solved with a hot fix.
I had a problem with copy tasks - this problem solved with hot fix.
When I buy a new system like MSP I expect it not to have such problem
that are part of the main path of working with MSP.

PS in the close Sunday I have to report to our CEO the project status.
I cannot do it since the work plan cannot be updated. they are read
only files. it is very frustrating :-(
 
H

hanni

Thanks.
i've already tryed it.
It doesnt help sometimes.
I have projects that where checked out 3 days and more.:-(
 

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