1 / 50

Getting Ready for 2010

chaeli
Download Presentation

Getting Ready for 2010

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    2. Getting Ready for 2010 Greg Bailey Vice President QuantumPM

    3. Agenda Overview Deployment Overview of 2010 Changes Scenarios with SharePoint Farm Upgrade Upgrade methods Project 2007 Compatibility Mode Extensibility sneak-peak

    4. Project 2010 Investment Areas Work management solutions for individuals, teams, and the enterprise

    5. Project and Portfolio Management For SharePoint

    6. Deployment

    7. Logical Architecture Project Server is a SharePoint application

    8. What’s Changed in Deployment? Project Service replaces Shared Service Provider Configuration of Non-Project Services for core functionality New required configuration steps No more ActiveX! Improvements Overall Setup experience Pre-requisite installer Farm configuration wizard Improvements to Central Administration Manage Project Service with all other services

    9. Project Server 2010 Software Requirements

    10. Installation Process

    11. Enable Required Services Minimal Services Required to operate a Project Server 2010 server farm Project Service Application Reporting Excel Services PerformancePoint Service Secure Store Service Charting State Service By default, all available services are enabled by the configuration wizard Performance Consideration: only enable necessary services to fulfill requirements

    12. Post Setup Project Web Access Core Items Time Reporting Periods Required now for My Tasks/My Timesheets Base Security Cube Building Service (Analysis Services OLAP cubes) Exchange Integration Project Server users can view Project Server tasks as Outlook tasks without ActiveX Requires configuration in both Project Server and Exchange Server

    13. Deployment Scenarios Together/Coexistence Single farm with both Project Server and SharePoint Server Apart/Standalone Dedicated Project Server Farm running WSS or SharePoint Server

    14. Together Pros and Cons Single Project and SharePoint Server farm Advantages Server consolidation Administration and maintenance Single software update plan Leverage high availability Disadvantages Software updates Additional training required for SharePoint Administrator(s) Additional licenses required

    15. Apart Pros and Cons Separate Project and SharePoint Server farm Advantages Farm hardware and software updates No dependency on the intranet farm’s availability Change management Security isolation Leverage the same SQL Server infrastructure as the other farm Disadvantages Additional administrative tasks Applying and testing patches on two farms versus one Content management and governance Project Server’s SharePoint content cannot be stored on another farm Greater cost Additional hardware Additional software licenses

    16. Deployment Considerations in a Single Farm Server and Client licenses Must install Project Server and SharePoint Server on each of your servers Isolate PS for performance/manageability/governance purposes Isolate Project Server content databases and Application Pool Separate Root Site Collection Separate Site Collection for Project Workspaces Isolate Reporting and Online Analytical Processing (OLAP) databases Patched together (Cumulative Updates/Service Packs) and plan accordingly Customization Line of Business integration Outsourcing and farm consolidation

    17. Upgrade

    18. Plan First! Assess the environment Evaluate configuration and customization Determine Service Pack and patch levels Enumerate configuration changes that must be replicated Evaluate licensing requirements and compliance Evaluate for supportability

    19. Upgrade & Migration to Project Server 2010 Project Server 2003 needs to be migrated via 2007 2007 does not need to be in production Consider using a “Virtual Migration Environment” Project Portfolio Server migration Project Portfolio Server (PPS) 2006 to 2007 Project Portfolio Server 2007 – three approaches Migrate to Project Server 2010 feature set Map, customize and develop desired functionality on Project Server 2010 Use the gateway to transfer data Finish existing projects in PPS 2007 and start new in Project Server 2010 Use side-by-side with Project Server 2010 Project Server 2007 to Project Server 2010 Out-of-the-Box experience

    20. Upgrade from Project Server 2007 Streamlined upgrade Out-of-the-Box experience Two ways to get environment ‘upgraded’ In-place upgrade Could be constrained by the 64-bit requirements or by the dependency on SharePoint Server 4 or 5 Database Attach 4 DB = Project Server data only 5 DB = SharePoint data (Project Workspaces) and Project Server data Upgrade of the databases happen automatically during PWA Provisioning. Possible warnings or errors in the ULS folder Backwards Compatibility Mode is automatically enabled after upgrade Enables of 2007 and 2010 clients to connect to 2010 server

    21. In-Place Upgrade – Key Steps

    22. Database Attach

    23. Backwards Compatibility Mode Accelerate deployment of Project 2010 Seamless co-existence and data exchange among various Project desktop versions Both Project 2010 desktop and Project Server 2010 scenario

    24. Backwards Compatibility Mode

    25. Backwards Compatibility Mode

    26. Backwards Compatibility Mode

    27. Backwards Compatibility Mode

    28. Backwards Compatibility Mode

    29. Backwards Compatibility Mode Implication to the feature set Manually scheduled tasks are not available on the server or client Tasks cannot be set to Inactive Font strikethrough not available All Departmental custom fields enforced on Project Professional 2007 All other server features fully functional New features of Project 2010 Professional including views and formatting – like Timeline, Team Planner, 32-bit colors could be used but are not available to Project Professional 2007 users

    30. Backwards Compatibility Mode Turning off BCM to Native is one way only setting BCM to native only should happen when All client are migrated to Project Professional 2010 All custom application are properly tested in the development/test/staging environments Project Web Access -> Server Settings -> Additional Settings

    31. Project Server and Professional Version compatibility matrix

    32. Project Standard and Professional New version of binary file format The Project 2010 MPP file format (MSProject.MPP.14) is changed to reflect all new enhancements, especially manual scheduling The file format extension is still “mpp” Project 2003/2007 users open/save/convert via Project 2010 Trial download

    33. Extensibility

    34. Extensibility Sneak-peak More on http://msdn.microsoft.com/project/ Project Professional/Standard 2010 Object Model, VBA, VSTO Fluent UI, Backstage, Project Guide infrastructure Project Server 2010 Web Services – Project Server Interface (PSI) & Evening Project Demand Management Workflow Rich Reporting/Business Intelligence Project Web Access site modifications Theming, Fluent UI, Extensible Grid Project and SharePoint “better together” Project Workspaces (SharePoint Sites) Any other customizations/add-ons leveraging any of the SharePoint Enterprise Suite

    35. QuantumPM

    37. 37 QPM Confidential 2008

    38. 38

    39. 39 QPM Confidential 2008

    40. 40

    41. 41

    42. 42

    43. 43

    44. 44

    45. 45

    46. 46

    47. 47

    48. 48

    49. Questions? QuantumPM: Greg Bailey, Vice President gbailey@quantumpm.com

More Related