W
Wouter
MIGRATION:
a production environment of Project Server 2002 with MS Project Professional
2002 clients has been migrated to Project Server 2003 SP1 with Project
Professional 2003 clients.
MANAGED TIMESHEET PERIODS:
We changed to Managed Timesheet Periods. Therefore we followed the
guidelines mentioned in the Administrator Guide:
Moving to Managed Timesheet Periods from Microsoft Project Server 2002 (all
timesheet periods) This scenario requires that the Microsoft Project Server
2002 database be upgraded to the Project Server 2003 database format. After
successfully upgrading the Project Server database, open all of the upgraded
projects in Project Professional 2003. Publish each project to the Project
Server 2003 database using Project Professional 2003. Point to Collaborate,
then Publish and select Republish Assignments. Be sure to select the
Overwrite actual work entered by resources option. This process will move the
data that was defined as Actual Work (the MSP_ASSIGNMENTS.ASSN_ACT_WORK field
in the Microsoft Project Server 2002 database) and redefine it as Actual Work
Protected (the MSP_ASSIGNMENTS.ASSN_ACT_WORK_PROT field in the Project Server
2003 database). When the project plan is published to the Project Server
database, the corresponding fields in the MSP_WEB_WORK and
MSP_WEB_ASSIGNMENTS tables are updated.
PROBLEMS:
-In several projects the remaining work disappears (becomes zero) after
accepting actuals.
-A certain resource always seems to be updating actuals for a task that no
longer exists, although she doesn’t enter any actual on such a task
-Renaming projects using the ProjectRenamer utility often fails.
ProjRenamerDownload.exe from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=21541). After renaming, sometimes it
is impossible to open a project with Project Professional from the Project
Web Access Project Center. Renaming back to the old name makes everything
work again.
-'Enterprise Global already contains a filter named 'Enterprise Resources'
and other warning arise without a clear cause.
-Tasks page always opens with as timeframe the current Managed Timesheet
Period. Users are now used to see the current and next week as time period,
always starting on Monday. It is not clear to us how we can change the
default time range shown in the Tasks page when using Managed Timesheet
Periods (one period/month)
-Users get warnings that their Timesheets are not submitted for periods
where they did submit their timesheet.
Regards,
Wouter
a production environment of Project Server 2002 with MS Project Professional
2002 clients has been migrated to Project Server 2003 SP1 with Project
Professional 2003 clients.
MANAGED TIMESHEET PERIODS:
We changed to Managed Timesheet Periods. Therefore we followed the
guidelines mentioned in the Administrator Guide:
Moving to Managed Timesheet Periods from Microsoft Project Server 2002 (all
timesheet periods) This scenario requires that the Microsoft Project Server
2002 database be upgraded to the Project Server 2003 database format. After
successfully upgrading the Project Server database, open all of the upgraded
projects in Project Professional 2003. Publish each project to the Project
Server 2003 database using Project Professional 2003. Point to Collaborate,
then Publish and select Republish Assignments. Be sure to select the
Overwrite actual work entered by resources option. This process will move the
data that was defined as Actual Work (the MSP_ASSIGNMENTS.ASSN_ACT_WORK field
in the Microsoft Project Server 2002 database) and redefine it as Actual Work
Protected (the MSP_ASSIGNMENTS.ASSN_ACT_WORK_PROT field in the Project Server
2003 database). When the project plan is published to the Project Server
database, the corresponding fields in the MSP_WEB_WORK and
MSP_WEB_ASSIGNMENTS tables are updated.
PROBLEMS:
-In several projects the remaining work disappears (becomes zero) after
accepting actuals.
-A certain resource always seems to be updating actuals for a task that no
longer exists, although she doesn’t enter any actual on such a task
-Renaming projects using the ProjectRenamer utility often fails.
ProjRenamerDownload.exe from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=21541). After renaming, sometimes it
is impossible to open a project with Project Professional from the Project
Web Access Project Center. Renaming back to the old name makes everything
work again.
-'Enterprise Global already contains a filter named 'Enterprise Resources'
and other warning arise without a clear cause.
-Tasks page always opens with as timeframe the current Managed Timesheet
Period. Users are now used to see the current and next week as time period,
always starting on Monday. It is not clear to us how we can change the
default time range shown in the Tasks page when using Managed Timesheet
Periods (one period/month)
-Users get warnings that their Timesheets are not submitted for periods
where they did submit their timesheet.
Regards,
Wouter