mops 2007 migrations

of 20 /20
MOPS 2007 Migrations Lessons from the field Peter Elkin, MCITP EPM Senior Lead Consultant Catapult Systems

Author: tassos

Post on 24-Feb-2016




1 download

Embed Size (px)


MOPS 2007 Migrations. Lessons from the field. Peter Elkin , MCITP EPM Senior Lead Consultant Catapult Systems. Topics. Terms and Technology Preparation Test Migration(s) Production Migration After the rollout. Terms and Technology. Project Server 2003 - PowerPoint PPT Presentation


Page 1: MOPS 2007 Migrations

MOPS 2007 MigrationsLessons from the field

Peter Elkin, MCITP

EPM Senior Lead ConsultantCatapult Systems

Page 2: MOPS 2007 Migrations


• Terms and Technology• Preparation• Test Migration(s)• Production Migration• After the rollout

Page 3: MOPS 2007 Migrations

Terms and Technology

• Project Server 2003o WSS 2.0 (Windows SharePoint Services)o Project Professional 2003o Project Web Access (PWA)o SQL Server 2000 or SQL Server 2005

• Microsoft Office Project Server 2007 (MOPS)o WSS 3.0 (Windows SharePoint Services)o Project Professional 2007o Project Web Access (PWA)o SQL Server 2000 or SQL Server 2005

• What do I mean by migration?

Page 4: MOPS 2007 Migrations


• How big are we talking?o Projects (10 projects or 1500 projects)o Workspaces (Project workspaces and plain team sites)o People

• Project managers• Team members• Plan for training your people• Rolling out MS Project

o The more projects and workspaces, the longer a migration will take.

Page 5: MOPS 2007 Migrations


• What customizations have been made to the workspace?o New document librarieso New custom listso Customization made to a standard listo New column on a standard listo Web parts

• Custom development?o Macros, InfoPath, SRSo What about Excel or a custom application?o Evaluate all custom items. Jettison the ones not needed anymore.

Page 6: MOPS 2007 Migrations

Tip #1

• CodePlex ( is your friend. Many valuable EPM solutions can be found on CodePlex.

• Project Reportcard• The Project Reportcard was developed as a tool to help Project Managers assess their projects based on

organizational standards implemented by their PMO. Understanding what the organizational KPIs are going to look like before their project update is published, can help a project manager avoid non-compliance issues and prepare to address real project challenges.

The Project Reportcard also makes it easier for the PMO to verify compliance with organizational standards.

Page 7: MOPS 2007 Migrations

Tip #1 Continued

More CodePlex Solutions:• EPM 2007 Test Data Population Tool• EPM Bulk Edit• EPM Timesheet & Statusing Customization Samples• EPMSync Utility• Microsoft Project Fx (mpFx)• Persisting SSAS OLAP Roles In Project Server 2007• Project Server 2007 AD/Resource Sync Utility• Project Server 2007 Event Handler Admin Tool• Project Server 2007 Log File Report Tool• Project Server 2007 Queue Watch Tool• Project Server 2007 Timesheet data population tool• Project Server 2007 Timesheet Tied-Mode Service and Event Handler• Project Server and InfoPath 2007• Search Project Server data using SharePoint Server's BDC and Enterprise Search• Project Reportcard

Page 8: MOPS 2007 Migrations

Test Migration(s)

• Setting up a Test environmento Virtual Environment

• Hyper-V (Windows Server 2008)• Virtual Server 2005• VMware• VPC

o Physical machineso Using Server Settings Backup/Restore tool

• (or better known as Playbooks)

Page 9: MOPS 2007 Migrations

Test Migration(s)

• Practiceo Do at least two test migrations even if the first one went perfectly.

• Convert the identified custom itemso SRS reports for example

• Communicationso Short demo(s) (30 min – 1 hour)o Downtime

• Communicate what impact it will be on the users.• “Windows of opportunity” – Be aware of any key dates or times of the month when the

system cannot be down.

Page 10: MOPS 2007 Migrations

Tip #2

• Actively search for blogs you like and utilize an RSS feed.

• • • •

Page 11: MOPS 2007 Migrations

Production Migration

• Key steps and Roles and Responsibilitieso Start this during the Test migrationso No need to specify exactly how something is done, but do specify who

is doing a particular item.o Document your contingency plan if you have to roll back.

• Testing (and more testing)

• Trainingo Oops, too late here.

Page 12: MOPS 2007 Migrations

Tip #3

• Get some screen real estate back in PWA.

• With Project Server 2003, you had an easy way to show/hide the Quick Launch on the left hand side.

• With Project Server 2007, that “out of the box” functionality is no longer there.

• Easy solution – Utilize a WSS web part (Content Editor), add some simple HTML code add the web part to the PWA page and that’s about it.


Page 13: MOPS 2007 Migrations

After the Rollout

• Plan for problems to occur

• What about the projects that didn’t get migrated?

• Why doesn’t everything work even though we did thorough testing?

Page 14: MOPS 2007 Migrations


Migrating from Project Server 2003 to Project Server 2007 can be challenging. One of the first things Microsoft states in the “Migration guide for Office Project Server 2007” is the following:

A lot of planning and consideration should go into the process of migrating your data to Office Project Server 2007.

Wow. Ya think?

Page 15: MOPS 2007 Migrations

Tip #4

Turning project summary task on by default.

• Tools > Options > View Tab > Show Project Summary (bottom right corner)

• Start >Run >Regedit (this opens Windows registry editor)• Go to HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\MS Project\

Options\View• Right click on View• Select New->DWORD Value• Set the name to Show Project Summary• Click off Show Project Summary• Double-click on Show Project Summary• Set the value to 1

Page 16: MOPS 2007 Migrations


• Just like a lot of other projects.

• Consider the people.

• Consider the environment.

• Be a project manager.

Page 17: MOPS 2007 Migrations

Tip #5

• No battle plan survives contact with the enemyo Field Marshall Helmuth Carl Bernard von Moltke

• It is not the critic who counts: not the man who points out how the strong man stumbles or where the doer of deeds could have done better. The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood, who strives valiantly, who errs and comes up short again and again, because there is no effort without error or shortcoming, but who knows the great enthusiasms, the great devotions, who spends himself for a worthy cause; who, at the best, knows, in the end, the triumph of high achievement, and who, at the worst, if he fails, at least he fails while daring greatly, so that his place shall never be with those cold and timid souls who knew neither victory nor defeat.o Theodore Roosevelt

Page 18: MOPS 2007 Migrations


• Migration guide for Office Project Server 2007URL:

• Performing migrationURL:

• Pre-migration verification and cleanup URL:

• Post-migration tasks for Project Server 2007 URL:

• Troubleshoot migration for Project Server 2007 URL:

• Upgrading Project Server 2003 to Project Server 2007• URL:!A8677D5751E6B4DA!1097.entry • Sample Project Server 2003 to Project Server 2007 Migration Plan• URL:

• Project Server Data Migration - Cheat Sheet• URL: • MS Project Reporter Blog• URL:

Page 19: MOPS 2007 Migrations

Q & A


Page 20: MOPS 2007 Migrations

MOPS 2007 MigrationsLessons from the field

Peter Elkin, MCITP

EPM Senior Lead ConsultantCatapult Systems