1 / 51

Deploying and Upgrading to Microsoft Project Server 2010 

SESSION CODE: OSP303. Deploying and Upgrading to Microsoft Project Server 2010 . Christophe Fiessinger Senior Technical Product Manager Microsoft Corporation chrisfie@microsoft.com http://blogs.msdn.com/chrisfie Rolly Perreaux , PMP, MVP, MCSE, MCT Sr. EPM Consultant/Instructor

khuong
Download Presentation

Deploying and Upgrading to Microsoft Project Server 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

  1. SESSION CODE: OSP303 Deploying and Upgrading to Microsoft Project Server 2010  Christophe Fiessinger Senior Technical Product Manager Microsoft Corporation chrisfie@microsoft.com http://blogs.msdn.com/chrisfie RollyPerreaux, PMP, MVP, MCSE, MCT Sr. EPM Consultant/Instructor PMO Logistics Inc rolly.perreaux@pmologistics.com http://rperreaux.spaces.live.com

  2. Agenda • Architecture • Capacity Planning • Installation • Upgrade and Migration • Resources

  3. Project 2010 Investment AreasWork Management Solutions for Individuals, Teams, and the Enterprise • Common experience across full PPM lifecycle • Flexible project capture and initiation • Enhance governance through workflow • Powerful portfolio selection analytics • Fluent UI (Ribbon, Backstage view) • Intuitive Excel-like behavior • Timeline & Team Planner views • Web-based project editing • Built on SharePoint Server 2010 • Easily create reports and dashboards • Connect teams with SharePoint Sync • Better time and status reporting • Extend interoperability • Simplified administration • Rich platform services • Developer Productivity

  4. Architecture

  5. Architectural Changes in 2010 • Dependency on the SharePoint Server 2010 Enterprise • 64 bit only Server Architecture • Internet Explorer 7.0 and higher for Project Web App • New Services Application replaces Shared Service Provider • Claims Authentication • Windows PowerShell support • ActiveX Free!

  6. Logical Architecture (per instance) Client Tier ProjectProfessional 3rd PartyApplications LOBApplications InternetExplorer ActiveCache PWA Server Project Server Clients Microsoft SharePoint Foundation 2010 Microsoft SharePoint Server 2010 ASPXPages PSIForwarder Web Tier PWA Server ASPX Pages Project Server 2010 Project Server Interface (PSI) Microsoft SharePointServer 2010 Application Tier Microsoft SharePoint Foundation 2010 Project Server Workflow System Scheduling Engine Eventing System Queuing System Business Objects Data Access Layer (DAL) SQL Server Reporting Published Draft Archive Config Database Tier Content

  7. Capacity Planning

  8. Capacity PlanningConsiderations Projects • Number of projects • Typical project sizes in terms of tasks • Number of project level custom fields • Level of linking (dependencies) between tasks Users • Concurrency of users • What security permissions do users have? • Geographic distribution of users Usage Patterns • Workload Conditions • Average time between page requests. • Average session time. • Payload of Pages Other Considerations • Issues, Risks and Deliverables • Calendars • High Availability • Virtualization • Storage

  9. Dataset Calculations

  10. Hardware RecommendationsSmall Dataset SQL Server Application Server Web Front End Single Server Farm Deployment

  11. Hardware RecommendationsSmall Dataset Application Server Web Front End SQL Server Two Tier Farm Deployment

  12. Hardware RecommendationsMedium Dataset Web Front End Application Server SQL Server Three Tier Farm Deployment

  13. Apply appropriate security model to trim data Adhere to a stringent maintenance and operational process Monitor system performance against workloads Monitor SQL Indexes Monitor scalar depth and data retention Reduce statistical skew Limit tasks to 8hr – 80hr duration Limit publish operations Capacity Top Recommendations • Invest in appropriate SQL Server • Ensure optimized disk subsystem • Size the farm against appropriate workloads • Implement best practices across all technologies • Avoid “black box syndrome” • Bring users to the server on latent networks • Keep Web Front End, Application Server and SQL Server separate • Limit custom field usage and formula driven fields • Limit number of fields in views

  14. Capacity PlanningSummary • Determine which of the datasets (small, medium, or large) will match to your expected dataset • Use the recommended hardware topology • Monitor your Farm’s performance • Optimize your deployment according to Best Practices on TechNet and based on performance counters learning's Capacity Planning in Project Server 2010 White Paperhttp://technet.microsoft.com/en-us/library/ff686784.aspx

  15. Installation

  16. Software Requirementsfor Project Server 2010 or higher or higher 64 Bit or higher or higher 32 Bit or higher OptionalExchange2007 SP2 or later

  17. Installation Process SharePoint Server 2010 Post Configuration Project Server 2010 SQL Server Install Windows Server Run Windows Update Install SQL Server and Components Install Software Updates Run Pre-Requisite Installer Install SharePoint Server 2010 Install Project Server Run SharePoint Configuration Wizard Central Admin Configuration Project Web Access Admin Configuration Base Installation PowerShell Support

  18. Required Service Applications for Project Server 2010 Minimal services required to operate a Project Server 2010 server farm: • Project Service Application (to host Project Web App instances) • Excel Services (Used for Reporting) • PerformancePoint Service (Used for Reporting) • Secure Store Service (Used for Reporting) • State Service (Used for Charting) NOTE: Using the Farm Configuration Wizard enables all available services Performance consideration: only enable necessary services in Production to fulfill requirements

  19. Post Setup Project Web App Core Items • Base security • Configure reporting • Excel Services • Secure Store Service • Cube Building Service (Analysis Services OLAP cubes) • Time Reporting Periods • Required now for My Tasks/My Timesheets • Exchange Integration • Project Server users can view Project Server tasks as Outlook tasks without ActiveX • Requires configuration in both Project Server and Exchange Server

  20. Project Server Installation DEMO

  21. Upgrade and Migration

  22. Upgrade and Migration to Project Server 2010 • Project Server 2007 to Project Server 2010 • Out-of-the-Box Experience • Any 2010 pre-release to 2010 release upgrade is NOTsupported • Project Server 2003 needs to be migrated via 2007 • 2007 does not need to be in production • Use the Virtual Migration Environment(VME)-http://go.microsoft.com/?linkid=9729345 • 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 2010 • Use side-by-side with Project Server 2010 Upgrade and Migration for Project Server 2010: http://technet.microsoft.com/en-us/projectserver/ee691958.aspx

  23. Project Version Compatibility matrix Project Desktop and Project Server Project Server and SharePoint Server

  24. Upgrade – Out of the Box Experience • Streamlined upgrade experience • Any 2010 pre-release to 2010 release upgrade is NOTsupported • Two ways to get environment Upgraded • Database Attach (recommended) • 5 DB (full upgrade) = SharePoint data (Project Workspaces) and Project Server data (recommended) • 4 DB (core upgrade) = Project Server data only • Upgrade of the databases happen automatically during PWA Provisioning. Possible warnings or errors in the ULS folder. • In-place upgrade • Could be constrained by the 64 bit requirements or by the dependency on SharePoint Server • Backwards Compatibility Mode is automatically enabled after upgrade • Enables 2007 clients (mixed with 2010 clients) to connect to 2010 server

  25. In-Place Upgrade – key steps

  26. Project Server Upgrade DEMO

  27. Resources

  28. Microsoft Project 2010 Resources • Product information and trial download • Main product site www.microsoft.com/project • Project Team Blog blogs.msdn.com/project • End-User Product Help • Project 2010 Help http://office2010.microsoft.com/project-help • Project Server 2010 Help http://office2010.microsoft.com/project-server-help • Interactive content – Videos/Sessions/Webcasts • www.microsoft.com/showcase/en/US/channels/microsoftproject • www.microsoft.com/events/series/epm.aspx • Project & Project Server 2010 Demo Image • Download http://go.microsoft.com/?linkid=9713956 • Hosted Virtual Lab http://go.microsoft.com/?linkid=9713654 • SharePoint 2010 • http://sharepoint.microsoft.com • IT Professional related – TechNet • TechCenterhttp://technet.microsoft.com/ProjectServer • Admin Blog http://blogs.technet.com/projectadministration • Brian Smith http://blogs.msdn.com/brismith • Developer related - MSDN • Developer center http://msdn.microsoft.com/Project • Programmability blog http://blogs.msdn.com/project_programmability • Got questions? Search or ask in the official Microsoft Forums • http://social.msdn.microsoft.com/Forums/en-US/category/projectserver2010,projectprofessional2010

  29. Microsoft Project 2010 Related Content • Breakout Sessions • OSP209 - Microsoft Project and Project Server 2010 Overview  • OSP303 - Deploying and Upgrading to Microsoft Project Server 2010 • Interactive Sessions • BIO10-INT - Light Up Your Project and Portfolio Management with Powerful Dashboards • OSP11-INT - Microsoft Project 2010 Frequently Asked Questions • OSP03-INT - Customizing Microsoft Project 2010 • Product Demo Stations • OSP-3 - Microsoft Project 2010

  30. FREE Microsoft Project Server 2010 Book 100 books given away per day • Technical Learning Center (TLC) – Yellow • Tuesday, 4:30 – 5:00 PM • Wednesday, 2:00 – 3:00 PM • Thursday, 12:00 – 1:00 PM Rolly will be available for book signing 

  31. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Track Resources • For More Information – http://sharepoint.microsoft.com • SharePoint Developer Center – http://msdn.microsoft.com/sharepoint • SharePoint Tech Center – http://technet.microsoft.com/sharepoint • Official SharePoint Team Blog – http://blogs.msdn.com/sharepoint

  32. Required Slide Speakers, please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session. Related Content • Breakout Sessions – See Conference Guide for full list of OSP Track Sessions • Interactive Sessions – OSP Track has 10 Interactive Sessions – OSP01-INT – OSP10-INT • Hands-on Labs – OSP01-HOL – OSP20-HOL • Product Demo Stations – Yellow Section, OSP • Office 2010, SharePoint 2010, Project Server 2010, Visio 2010 have kiosks and demos

  33. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

  34. Required Slide Complete an evaluation on CommNet and enter to win!

  35. Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registrationJoin us in Atlanta next year

  36. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

  37. APPENDIX

  38. Sizing Guidelines

  39. Logical ArchitectureProject Server is a SharePoint Application Database Server Application/PSI Server Client Microsoft SharePoint Server 2010 http://Svr:32843/ProjectServerApplication/*.asmx Microsoft SharePoint Foundation 2010 Windows Workflow Foundation http://Svr/InstanceName/_vti_bin/psi/*.asmx Project User Context Eventing Service Queuing Service Server Side Scheduling Business Objects Filter Data Access Layer Data Access Layer Internal Web Services External Web Services Business Logic Tier Web Service Tier Serializer Web Server ASMX Interface Microsoft SharePoint Server 2010 Microsoft SharePoint Foundation 2010 WCF Services ASMX over http/soap WCF Interface Project Professional Project Web Access 3rd Party Client Scheduling Engine Desktop Reporting Client Active_Cache Soap Client Serializer Custom Logic Impersonation IE Browser Level Security Zone AJAX Workflow Platform Authentication Project User Context Shared Services Service Database Shared Services Content Database Central Admin Content Database PSI Forwarder Server Active_Cache Farm Configuration Database Project Server Draft Database(n) Project Server Reporting Database(n) State Service Database Web Application Content Database(n) Project Server Published Database(n) Project Server Archive Database(n) Web Analytics Database ASPX Web Parts PSI Proxies Master Pages PWA and WSS content pages WCF Services

  40. Sizing GuidelinesSequencing and example hardware list Web Server Application Server SQL Server Determine workloads Determine user concurrency Determine resource ratios Determine workloads Determine resource ratios against application server Determine resource ratios against SQL server Determine file allocation Determine workloads Determine data profile Determine throughput Determine queue model Size application resources Bus Hardware Sizing: • NOT about how many users • NOT about how many servers • IS how many workloads/profile • IS how many system resources General considerations: • # Instances • # web applications • Throughput tolerance • Co-existence • 64 bit (scale up) Virtualization: • Size for physical first • Extrapolate to virtual • Dedicate high demand to physical • Allow host machine overhead Storage: • SAN configuration • RAID level & optimization • # spindles • Storage size • File group allocation Balance: • Physical footprint • Scalar depth vs. concurrency • System ratios vs. server role • Physical vs. virtual allocation FINAL STEPS: Size to physical server count Size to virtual guest count Bus Hardware Bus Hardware Processor Processor Processor Primary Team Primary Team Primary Team Network Network Network Heartbeat Heartbeat Heartbeat External Storage SAN Connections Backup Backup Un-Restricted Management Un-Restricted Management Restricted Management Restricted Management Un-Restricted Management Restricted Management Backup 1TB Internal Storage Internal Storage Internal Storage RAID 1 RAID 1 RAID 1 RAID 1 RAID 1 RAID 1 72GB 72GB 72GB 72GB 72GB 72GB 72GB 72GB 72GB 72GB 72GB 72GB RAID 1+0 Host Bus Adaptor Host Bus Adaptor Memory Memory Memory 16Gb 16Gb 32Gb Physical Virtual

  41. Sizing GuidelinesCalculation Factors – SQL Server • TCC (Total CPU Count): The TCC represents the number of CPUs required for the SQL Server. Apply a ratio of 1:2 against the Application Server TTC. • TRC (Total RAM Count): The TRC represents the amount of memory for the SQL Server. Apply a 1:4 ratio of CPU to RAM. This is imperative on a SQL Server using 64bit. • Total TempDB Count: The total number of TempDB files to allocate from the TCC.Apply a 1:1 ratio with the TCC. • Total TempDB Size: The total size of the TempDB to allocate from the Profile Database Size. The size is calculated as 25% of the Draft database size. As the Database Size column includes all 4 databases for that instance. TempDB Size = [Profile Database Size] X [.25] / [TCC] • TempDB Spindle Count: This represents the number of spindles to allocate across TempDB. The rule is one spindle per file group. RAID 10 is recommended, therefore doubling the count. † = Minimum startup value 8Gb RAM

  42. Sizing GuidelinesCalculation Factors – Application Server • Profile: Use the Profile column the Estimated Database Size table to determine the number of projects in the system for processing. • # Users: Resource column from the chosen Profile row. • # Jobs: Project column from the chosen Profile row. • JTM= 0.146 minutes. (Refer to whitepaper for details) • HT (High Throughput): Toreduce a race condition on the Queue Group, set the Queue thread count to 1.5 per CPU on the server (do not exceed more than 12 threads for the entire farm – the Queue thread count is per Application Server). For each Application Server role added to the farm, the Queue thread count must be reduced proportionately to ensure Maximum Thread Count (MTC) of 12 is not exceeded. • PW (Processing Window): The PW represents a processing window through the Queue during peak load of 30 minutes. • TPT (Total Processing Time): The TPT represents the total estimated time to process all jobs on a single Queue thread - JTM x # Jobs. • TTC (Total Thread Count): The TTC represents the number of Queue threads to process the # Jobs within the desired processing window. TPT / PW. • TCC (Total CPU Count): The TCC represents the number of CPUs required for the Application Server. HT / TTC. • TRC (Total RAM Count): The TRC represents the amount of memory for the Application Server. Apply a 1:2 ratio of CPU to RAM. † = Minimum startup value 8Gb RAM

  43. Sizing GuidelinesCalculation Factors – Web Server • TCC (Total CPU Count): The TCC represents the number of CPUs required for the Web Front End server. • 1 – 1000 users = 2 CPU • 1001 – 5000 users = 4 CPU • 5001 – 15,000 users = 8 CPU • TRC (Total RAM Count): The TRC represents the amount of memory for the Web Front End Server. Apply a 1:2 ratio of CPU to RAM. † = Minimum startup value 8Gb RAM Additional Resources • Capacity planning in Project Server 2010 (white paper) • Project Server 2007 Hyper-V guide: http://go.microsoft.com/fwlink/?LinkId=128376 • Running a Project Server 2010 performance test lab • Performance and capacity planning best practices white paper (2007) • Using SharePoint Products and Technologies in a Hyper-V virtual environment: http://technet.microsoft.com/en-us/library/cc816955.aspx • Hyper-V Virtual Hard Disk (VHD) Performance White Paper: http://download.microsoft.com/download/0/7/7/0778C0BB-5281-4390-92CD-EC138A18F2F9/WS08_R2_VHD_Performance_WhitePaper.docx

  44. SharePoint Co-Existance

  45. Deployment Scenarios • Together/Coexistence • Single farm with both Project Server and SharePoint Server 2010 • Apart/Standalone • Dedicated Project Server Farm running SharePoint Server 2010 • Mixed server versions in the same farm is NOT supported • Project Server 2007 with SharePoint Server 2010 • Project Server 2010 with SharePoint Server 2007 or Windows®SharePoint® Services (WSS) 3.0 • EPM and Office SharePoint Server 2007 Coexistence — Intranet Scenario (TechNet whitepaper applicable to 2010)

  46. Sample Architecture Diagram

  47. Together Pros and ConsSingleProjectand 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

  48. Apart Pros and ConsSeparate 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

  49. Functional Coexistence Options

More Related