Lessons From The Field: Enterprise Migration

Lessons From The Field: Enterprise Migration PowerPoint PPT Presentation


  • 231 Views
  • Uploaded on
  • Presentation posted in: General

Lessons From The Field: Enterprise Migration. Danny HellinckxSenior Consultant, PMPMicrosoft Belux ServicesEnterprise Project Management. Objective. Project Server 2007 has 200,000 new features. You are just beginning to heal from the Project Server 2003 rollout completed 1-2 years back, and the organization is well underway to accepting the process changes introduced. Now you are hearing about this wonderful new features and scalability that Project Server 2007 offers. So is it worth to migr25

Download Presentation

Lessons From The Field: Enterprise Migration

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


2. Lessons From The Field: Enterprise Migration Danny Hellinckx Senior Consultant, PMP Microsoft Belux Services Enterprise Project Management

3. Objective

4. Agenda Technical Considerations - migration highlights from US session - Emmanuel Fadullon Boundaries 2003 – current engagements Q/A + => Hands On Lab 14h-15h15

5. Considerations Compatibility Is Side by Side Compatible Project Pro, Project Server & WSS 2003/2007 Is NOT Side by Side Compatible Office 2003/2007 Important: Project Professional 2003 is not compatible with Office Project Server 2007. Similarly, Microsoft Office Project Professional 2007 is not compatible with Project Server 2003. The main reason for the incompatibility between these versions is a fundamental update of the client-to-server communication protocol. Project Server 2003 uses ODBC to open or save enterprise projects from Project Professional 2003. Office Project Server 2007 uses Web services. This change enables Office Project Professional 2007 to connect to the server over a WAN by using low bandwidth HTTP/HTTPS connections, and it also provides a smooth experience for users whether they are online or offline. File-format compatibility between Project client versions Project 2007 clients (Including both Professional and Standard versions): • Can open .mpp files for: • Project 98 • Project 2000 • Project 2002 • Project 2003 (Professional and Standard versions) • Can save .mpp files to the following file formats: • Project 2000 • Project 2002 • Project 2003 • Can open from an existing ODBC data source. • Cannot save to an ODBC data source. Project 2003 (Professional and Standard versions): • Cannot open a Project 2007 .mpp file. SP4 can read Project 2007 file ? Important: Project Professional 2003 is not compatible with Office Project Server 2007. Similarly, Microsoft Office Project Professional 2007 is not compatible with Project Server 2003. The main reason for the incompatibility between these versions is a fundamental update of the client-to-server communication protocol. Project Server 2003 uses ODBC to open or save enterprise projects from Project Professional 2003. Office Project Server 2007 uses Web services. This change enables Office Project Professional 2007 to connect to the server over a WAN by using low bandwidth HTTP/HTTPS connections, and it also provides a smooth experience for users whether they are online or offline. File-format compatibility between Project client versions Project 2007 clients (Including both Professional and Standard versions): • Can open .mpp files for: • Project 98 • Project 2000 • Project 2002 • Project 2003 (Professional and Standard versions) • Can save .mpp files to the following file formats: • Project 2000 • Project 2002 • Project 2003 • Can open from an existing ODBC data source. • Cannot save to an ODBC data source. Project 2003 (Professional and Standard versions): • Cannot open a Project 2007 .mpp file. SP4 can read Project 2007 file ?

6. Considerations Environments

7. Considerations Hardware/software Platform: W2K SP4 should be ok .Net 3.0 obligated 32 bit to 64 bit: SQL (joining tables, virtual address spaces going 1 terra bit!) and also Project Server Application Application: SQL 2k5 SP1 no obligation but better performance/advantages WSS V2-> V3 requirement Before migrating should have P2003 DB SP2a X64 bit architecture Client: Desktops must have Windows XP SP2 or vista Still need: ActiveX (not for My Task and My timesheet, but still required for Project Center Views, Resource Center views, …), O2003 SP2 Addin (calendar), Office Web components (Analysis Services, drag and drop) Also: Visual Reports Excel 2003 and Visio 2007 are requested Server: P2003 => translated into several databases, draft, published, archived, and reporting (more space) WSS => translated into several databases, config and content, content available within OLAP cubes, Reporting Services Reporting=> You can not add tables to the draft, published and archived database, only reporting database is documented (pre-configured user views to facilitate reporting development) Client=> Local Cache: minimum 50Mb but 3,8 Gb would be great! Major improvement for your project managers!!! Customization: WSS (Webpart) migrate them P2003 (ASP) migrate to the proper webpart DB Custom=> no tables to add, no triggers in database allowed. Make use of PSI and Event Handler (Webservices tie to ligocal business objects). No converter available. Within SDK gives comparison, 2 to 3 PDS calls are mostly handled by 1 PSI call. Recoding!! VBA, macros, in the Enterprise Global Template: could work, test it!! Platform: W2K SP4 should be ok .Net 3.0 obligated 32 bit to 64 bit: SQL (joining tables, virtual address spaces going 1 terra bit!) and also Project Server Application Application: SQL 2k5 SP1 no obligation but better performance/advantages WSS V2-> V3 requirement Before migrating should have P2003 DB SP2a X64 bit architecture Client: Desktops must have Windows XP SP2 or vista Still need: ActiveX (not for My Task and My timesheet, but still required for Project Center Views, Resource Center views, …), O2003 SP2 Addin (calendar), Office Web components (Analysis Services, drag and drop) Also: Visual Reports Excel 2003 and Visio 2007 are requested Server: P2003 => translated into several databases, draft, published, archived, and reporting (more space) WSS => translated into several databases, config and content, content available within OLAP cubes, Reporting Services Reporting=> You can not add tables to the draft, published and archived database, only reporting database is documented (pre-configured user views to facilitate reporting development) Client=> Local Cache: minimum 50Mb but 3,8 Gb would be great! Major improvement for your project managers!!! Customization: WSS (Webpart) migrate them P2003 (ASP) migrate to the proper webpart DB Custom=> no tables to add, no triggers in database allowed. Make use of PSI and Event Handler (Webservices tie to ligocal business objects). No converter available. Within SDK gives comparison, 2 to 3 PDS calls are mostly handled by 1 PSI call. Recoding!! VBA, macros, in the Enterprise Global Template: could work, test it!!

8. Data Migration Types of Data Migrated Global Data – Migrated only once Enterprise Global Template Enterprise Resources Project Web Access Data Views, Server Settings, Admin Settings, Security Settings Project Data – Migrated once or gradually Enterprise, Administrative and Templates Local Resources, Cross Project Links SharePoint Data – Migrated once or gradually Pre-Scan utility Migrate Workspaces before associated projects Link association between projects

9. Data Migration Types of Data Not Migrated Outstanding Status Updates: Accept/Reject all Historical Timesheet Data: adjusted, transactions Status Reports To-Do list => Project proposals View Filters Project Versions => extension Status Update Rules Extra tables or fields added to db Project Web Access links and Saved Links Project Server 2003 data that is not migrated Outstanding status updates: Outstanding status updates are not migrated if the StopProjectUpdatesIfUpdatesPending setting in the migration configuration file is set to Yes (which is the default option). It is a best practice to make project managers accept or reject project status updates before running the migration tool. Timesheet history : Timesheet history data is not migrated. Timesheet data in the following tables is not migrated: • MSP_WEB_WORK • MSP_WEB_ADJUSTED • MSP_WEB_TRANSACTIONS However, timesheet periods are migrated. Also, all status data entered by team members (for example, Tom worked eight hours on assignment X), does get migrated. If you have a reporting system based on timesheet history, then your reports will be affected and will need to be redone. Status reports : Status report definitions and responses are not migrated. To-do lists: The related feature in Office Project Server 2007 is called "project proposals." Project proposal assignments affect resource availability, whereas to-do list assignments in Project Server 2003 do not. If you are manually shifting from to-do lists to project proposals, you need to take this situation into account. View filters: Each filter in each view that is not upgraded is noted in a log file. These log entries can help the administrator to recreate the filters manually in Office Project Server 2007. Project versions: Project Server 2007 does not have the concept of project versions. The version name from Project Server 2003 is appended to the project name as part of migration. For example, Project1, version 'target', becomes Project1_target after migration. Project2, version 'published', becomes Project2_published after migration. Status update rules: Not migrated. Extra tables or fields added to the database: Any extra tables or fields added to the database file by customers or partners are not migrated. They must be manually migrated to Office Project Server 2007. Project Web Access links and Saved Links: You must manually create your links to Project Web Access after migration. This includes the Saved Links feature in Project Server 2003.Project Server 2003 data that is not migrated Outstanding status updates: Outstanding status updates are not migrated if the StopProjectUpdatesIfUpdatesPending setting in the migration configuration file is set to Yes (which is the default option). It is a best practice to make project managers accept or reject project status updates before running the migration tool. Timesheet history : Timesheet history data is not migrated. Timesheet data in the following tables is not migrated: • MSP_WEB_WORK • MSP_WEB_ADJUSTED • MSP_WEB_TRANSACTIONS However, timesheet periods are migrated. Also, all status data entered by team members (for example, Tom worked eight hours on assignment X), does get migrated. If you have a reporting system based on timesheet history, then your reports will be affected and will need to be redone. Status reports : Status report definitions and responses are not migrated. To-do lists: The related feature in Office Project Server 2007 is called "project proposals." Project proposal assignments affect resource availability, whereas to-do list assignments in Project Server 2003 do not. If you are manually shifting from to-do lists to project proposals, you need to take this situation into account. View filters: Each filter in each view that is not upgraded is noted in a log file. These log entries can help the administrator to recreate the filters manually in Office Project Server 2007. Project versions: Project Server 2007 does not have the concept of project versions. The version name from Project Server 2003 is appended to the project name as part of migration. For example, Project1, version 'target', becomes Project1_target after migration. Project2, version 'published', becomes Project2_published after migration. Status update rules: Not migrated. Extra tables or fields added to the database: Any extra tables or fields added to the database file by customers or partners are not migrated. They must be manually migrated to Office Project Server 2007. Project Web Access links and Saved Links: You must manually create your links to Project Web Access after migration. This includes the Saved Links feature in Project Server 2003.

10. Data Migration Special Considerations P2003 Admin projects => regular P2007 projects (not = non project time in 2k7) Security categories before projects in categories Value Lists migrated as Lookup Tables Local Resource => Enterprise resource Project Server Auth users require Forms Auth Default Groups, Categories and Views

11. Data Exceptions Required Fields – must have value or turn off for migration Bad date – negative duration. Migration fails All projects checked in All pending updates processed All Ext Edited Flags = False Turn off SMTP to prevent spam

12. Migration Guide Specifically Performing Migration section Prepare for migration to Project Server 2007 Pre-migration verification and cleanup P12MigrationTool.exe –verify Checked-out Projects Externally edited project Pending status update StopProjectMigrationStatusUpdatePending=FALSE Configuring the migration tool for Project Server P12MigrationTool .INI Upgrading project workspaces from Project Server 2003 Running the migration tool to migrate global data and projects

14. Scenarios On Existing Hardware Full Migration Project Only Includes WSS Gradual Migration + Compartmental Project Only Includes WSS To New Hardware Full Migration Project Only Includes WSS Gradual Migration + Compartmental Project Only Includes WSS Multiple P2003 Instance to Single P2007 Instance Multiple P2007 Instance to Single P2007 Instance

15. Scenarios Existing hardware (in place upgrade) Using the Microsoft Windows SharePoint Services 3.0 installation media, install Windows SharePoint Services 3.0 with the In-place upgrade option. (For more information, see Upgrading to Windows SharePoint Services 3.0 .) After the installation process, the Windows SharePoint Services 2.0 installation will no longer exist — it will have been upgraded to Windows SharePoint Services 3.0. This process migrates all the Windows SharePoint Services data associated with Project Server 2003 and creates a Windows SharePoint Services 3.0 farm. Note that after you complete this step, the migrated workspaces will still not function. (The corresponding Office Project Server 2007 Windows SharePoint Services templates are not yet installed; the templates will be installed with Office Project Server 2007). 2. Install Office Project Server 2007 into the farm created in step 1 and create an instance of Project Web Access. For more information on installing Office Project Server 2007 and creating an instance of Project Web Access, see Deploy Project Server 2007 to a server farm environment . After this step, the migrated project workspaces work, but the links between tasks, projects, and assignments and Windows SharePoint Services issues, risks, and documents are not yet upgraded. 3. Migrate and publish Project Server 2003 projects to Office Project Server 2007 by using the migration tool. The fixing of links occurs as part of the project publishing process, so the migrated projects have to be published for the fixes to happen. 4. Uninstall Project Server 2003. Using the Microsoft Windows SharePoint Services 3.0 installation media, install Windows SharePoint Services 3.0 with the In-place upgrade option. (For more information, see Upgrading to Windows SharePoint Services 3.0 .) After the installation process, the Windows SharePoint Services 2.0 installation will no longer exist — it will have been upgraded to Windows SharePoint Services 3.0. This process migrates all the Windows SharePoint Services data associated with Project Server 2003 and creates a Windows SharePoint Services 3.0 farm. Note that after you complete this step, the migrated workspaces will still not function. (The corresponding Office Project Server 2007 Windows SharePoint Services templates are not yet installed; the templates will be installed with Office Project Server 2007). 2. Install Office Project Server 2007 into the farm created in step 1 and create an instance of Project Web Access. For more information on installing Office Project Server 2007 and creating an instance of Project Web Access, see Deploy Project Server 2007 to a server farm environment . After this step, the migrated project workspaces work, but the links between tasks, projects, and assignments and Windows SharePoint Services issues, risks, and documents are not yet upgraded. 3. Migrate and publish Project Server 2003 projects to Office Project Server 2007 by using the migration tool. The fixing of links occurs as part of the project publishing process, so the migrated projects have to be published for the fixes to happen. 4. Uninstall Project Server 2003.

16. Scenarios New hardware/farm gradual upgrade 1. Using the Windows SharePoint Services 3.0 installation media, install Windows SharePoint Services 3.0 with the Gradual upgrade option. (For more information, see Upgrading to Windows SharePoint Services 3.0 .) After the installation, Windows SharePoint Services 2.0 exists side-by-side with Windows SharePoint Services 3.0. 2. Install Office Project Server 2007 and join the existing Windows SharePoint Services 3.0 farm and provision an instance of Project Web Access. (For more information, see the Deploy Project Server 2007 to a server farm environment .) 3. Upgrade the Windows SharePoint Services 2.0 workspaces for the projects that will be gradually migrated. You can do this by using the SharePoint Central Administration Web site. For more information, see Upgrading to Windows SharePoint Services 3.0 . 4. Migrate and publish the projects corresponding to the workspaces that were upgraded in the previous step. This step fixes the links between project items and the Windows SharePoint Services items. Repeat steps 3 and 4 for every batch of projects or workspaces to migrated. When all of them have been migrated, you can uninstall Project Server 2003 and Windows SharePoint Services 2.0. 1. Using the Windows SharePoint Services 3.0 installation media, install Windows SharePoint Services 3.0 with the Gradual upgrade option. (For more information, see Upgrading to Windows SharePoint Services 3.0 .) After the installation, Windows SharePoint Services 2.0 exists side-by-side with Windows SharePoint Services 3.0. 2. Install Office Project Server 2007 and join the existing Windows SharePoint Services 3.0 farm and provision an instance of Project Web Access. (For more information, see the Deploy Project Server 2007 to a server farm environment .) 3. Upgrade the Windows SharePoint Services 2.0 workspaces for the projects that will be gradually migrated. You can do this by using the SharePoint Central Administration Web site. For more information, see Upgrading to Windows SharePoint Services 3.0 . 4. Migrate and publish the projects corresponding to the workspaces that were upgraded in the previous step. This step fixes the links between project items and the Windows SharePoint Services items. Repeat steps 3 and 4 for every batch of projects or workspaces to migrated. When all of them have been migrated, you can uninstall Project Server 2003 and Windows SharePoint Services 2.0.

17. Related Sessions SA302 Implementing and EPM Solution – Franck Mercier DEV100 EPM Solution Architecture fr Dev – Patrick Conlan SA201 Admin of an EPM Solution - Adrian Jenkins SA205 Monitoring & Troubleshooting - Adrian Jenkins DEV402 Extending Proj. Server Int - Christophe Fiessinger DEV304 Project Server 2007 Programmability - Phil Smail PO300 EPM Solution Architecture - Doug Welsby SA400 Project Server Integration w/ WSS - Eric Zenz DEV400 Custmzg Proj Web Access interface -Boris Scholl SA402 Deployment for High Avail & Scale - Jean-Noel Lienhart

18. 2k3 Concerns and Difficulties => 2k7 Opportunities

19. 2k3 Concerns and Difficulties => 2k7 Opportunities PM: Takes to long to administer the Time Registration approval in ALLLLLLLLLLLLLLLLL my files!

20. 2k3 Concerns and Difficulties => 2k7 Opportunities PM: Takes to long to manage my project files with ALLLLLLLLLLLLLLL these tasks and assignments

21. 2k3 Concerns and Difficulties => 2k7 Opportunities Prog/Prod Mgr: No ability to MANAGE Product/Program/Project structures. Outline Codes (reporting, filter, group) and Version is not enough

22. 2k3 Concerns and Difficulties => 2k7 Opportunities Prog/Prod Mgr: Difficult to COMMUNICATE and COLLABORATE on different reporting levels (team, project, program, executive)

23. From 2k3 boundary to 2k7 -ility Let ‘s have a look! demo

24. Related Sessions PO203 Collaboration in EPM Solution – EricZenz SA204 SharePoint Farm Essentials - Steve Haden SA201 Admin of an EPM Solution - Adrian Jenkins PO207 Reporting in the EPM Solution - Patrick Conlan BP208 Best Practise Governance w EPM - Mike Gruia PO300 EPM Solution Architecture - Doug Welsby SA400 Project Server Integration w/ WSS - Eric Zenz PO202 Timesheets & Task Mgmt Overview - David Duolon

25. We need your feedback! We really value your feedback to help us develop future Microsoft events.   Please fill in your session feedback form now and hand in your completed form before you leave the event. Please remember to note which sessions you have attended.

  • Login