<Client> Microsoft Project Server 2010 Deployment

1. <Client>Microsoft Project Server 2010 Deployment Microsoft Project Server 2010 System Administrator Training Composed by FirstName LastName Month yyyy

2. Course Outline Module 1 System Admin Training Introduction Module 2 Project Server 2010 Architecture Module 3 Connect via Project Professional 2010 Module 4 Intro to Project Web App (PWA) Module 5 PWA Server Settings Area Module 6 SharePoint Server 2010 Admin Module 7 Troubleshooting

3. Module 1 Module 1 System Admin Training Introduction • Topic 1.1 – Logistics - Class Goals & Guidelines • Topic 1.2 – System Admin Training Prerequisites Module 2 Project Server 2010 Architecture Module 3 Connect via Project Professional 2010 Module 4 Introduction to Project Web App Module 5 PWA Server Settings Area Module 6 SharePoint Server 2010 Admin Module 7 Troubleshooting

4. Administrator Training Introduction Topic 1.1 – Logistics - Class Goals & Guidelines Topic 1.2 – Administrator Training Prerequisites

5. Class Logistics • Class Goals • Minimize time impact upon employees • Cover all material within the allotted time • Provide sound Project Management related training that will aid with the integration of Project Server within the organization’s infrastructure • Have fun! • Class Guidelines • Facilitator will provide hands-on training • Rules of the road • Please be on time for training • A break each hour for 10 minutes (timely return requested) • Turn off (or make silent), cell phones and pagers during class time • For the sake of time, we will add all detailed questions to the “Parking Lot” to be addressed at a later time • Please do not use the system outside of the training plan NOTE: The screen images used in this course have been captured from a Windows XP environment. Be sure to allow for differences in Menu / Dialog Box selections when using other Operation System versions (e.g. Windows 2000, Vista, etc…)!

6. Class Scope • Understand Project Server 2010 Technical Architecture • Support the Project Server 2010 Technical Environment • Maintain the Project Server 2010 implementation • Support the roles (where configured) of: • Project Server Administrator (Primary Support) • Executive • Portfolio Managers • Project Managers • Resource Managers • Team Leads • Team Members

7. Administrator Training Introduction Topic 1.1 - Logistics - Class Goals & Guidelines Topic 1.2 - Administrator Training Prerequisites

8. Admin Role Prerequisites • Knowledge of Technical System Support Processes • Knowledge of Network Support Procedures • Knowledge of Microsoft based Technical Architectures • Experience with Internet Information Services (IIS 6/7) • Experience with SharePoint Server 2010 • Experience with Application Software Troubleshooting • Exposure to Server Hardware Troubleshooting • Exposure to Client Hardware Troubleshooting • General knowledge of Project Server Business Concepts • Executive-level resolution support (Helpful)

9. Module 2 Module 1 Administrator Training Introduction Module 2 Project Server 2010 Architecture • Topic 2.1 – Architectural Outline • Topic 2.2 – Software Components • Topic 2.3 – Hardware Components • Topic 2.4 – Desktop Requirements • Topic 2.5 – High-level Business Process Module 3 Connect via Project Professional 2010 Module 4 Introduction to Project Web App Module 5 PWA Server Settings Area Module 6 SharePoint Server 2010 Admin Module 7 Troubleshooting

10. Project Server 2010 Architecture Topic 2.1 – Architectural Outline Topic 2.2 – Software Components Topic 2.3 – Hardware Components Topic 2.4 – Desktop Requirements Topic 2.5 – High-level Business Process

11. Architectural Outline A description of the various Project Server 2010 technical architecture components

12. Architectural Outline Overview • Describes Underlying Architecture • System Overview Diagram • Architecture Supports… • Technical Architecture Tiers • Project Server 2010 Tiers • SharePoint Server 2010 • Technology & Scalability Options

13. System Overview

14. Project Server 2010 Supports… • High Availability • Extensive Scalability • Management of Large Scale Projects • Management of High Levels of Complexity • Management of a large Centralized Resource Pool • Management of Complex Resource Scenarios • New Client/Server, Queue based Data Transfer: • Transfers data from the Client (Project Professional 2010) to Server • Downloads deltas, not the whole Project • Provides more data on demand • Allows for faster booting • Works across WANs and firewalls • Offers data integrity when saving Projects • A seamless Online/Offline experience

15. Technical Architecture Tiers

16. Project Server 2010 Tiers • Client Tier: • MS Office-based Applications • Web Browser-based client • Custom applications • Active Cache • Web (UI) Tier: • Project Web App • SharePoint Server 2010 • SharePoint Integration with Internet Information Services (IIS) • Availability of a Workflow Engine • Fully .NET Framework Compliant • Application Tier: • Project Server 2010 • Project Server Interface (PSI) • Project Server 2010 Eventing Service • Project Server 2010 Queuing service. • Database Tier: • ProjectServer_Draft • ProjectServer_Published • ProjectServer_Reporting • ProjectServer_Archive

17. Core Workspace Services API’s Fields/Forms OM and SOAP Events Deployment Storage Repository Metadata Versioning Backup Security Rights/Roles Pluggable Auth Per Item Rights Trimming Management Admin UX Delegation Provisioning Monitoring Topology Config Mgmt Farm Services Feature Policy Extranet Site Model Rendering Templates Navigation Visual Blueprint Operating System Services ASP.NET (Web Parts, Personalization, Master Pages, Provider Model for navigation, security, etc.) Database Search Workflow SharePoint Server 2010

18. Topology & Scalability Options Simple to Complex

19. Project Server 2010 Architecture Topic 2.1 – Architectural Outline Topic 2.2 – Software Components Topic 2.3 – Hardware Components Topic 2.4 – Desktop Requirements Topic 2.5 – High-level Business Process

20. Software Components A description of the various Project Server 2010 environment software components

21. End-User Components • Office Project Professional 2010 • Office Project Web App • Microsoft Outlook (or alternate Email) • Microsoft Office Applications • Microsoft Internet Explorer (7.x/8.x/9.x) • Recent versions of Firefox, Safari & Chrome supported

22. Server Components • Microsoft Windows Server 2008, R2 • Internet Information Services (IIS 6.0 / 7.0) • Microsoft Project Server 2010 • SharePoint Server 2010 • Microsoft Exchange Server (or other SMTP Server) • Project Server 2010 Components: • Project Data Services (PSI) • Queuing Service • Eventing Service • Scheduling Engine • Business Objects • Data Access Layer • Microsoft Active Directory • .Net 2.0 Framework • .Net 3.0 Framework • .Net 3.5 Framework • .Net 4.0 Framework

23. Database Components • Microsoft SQL Server • SQL Server 2008 • With SQL Server Service, Pack 2 applied OR • SQL Server 2008, R2 • With latest Service Pack applied • Analysis Services • Analysis Services 2008 • With Analysis Services, Service Pack 2 applied OR • Analysis Services 2008, R2 • With latest Service Pack applied

24. Project Server 2010 Architecture Topic 2.1 – Architectural Outline Topic 2.2 – Software Components Topic 2.3 – Hardware Components Topic 2.4 – Infrastructure Planning Topic 2.5 – High-level Business Process

25. Hardware Components A description of the various Project Server 2010 environment Hardware components

26. Desktop Hardware Specs

27. Server Hardware Specs

28. Project Server 2010 Architecture Topic 2.1 – Architectural Outline Topic 2.2 – Software Components Topic 2.3 – Hardware Components Topic 2.4 – Infrastructure Planning Topic 2.5 – High-level Business Process

29. Infrastructure Planning A description of the various Project Server 2010 infrastructure consideration during planning

30. Infrastructure Documentation • Physical Network Diagram • Physical Communication Links • Computer Hardware • Location of Devices • Logical Network Diagram • Domain Architecture • Server Roles • Trust Relationships • Network Configuration Documentation • Name Resolution • IP Addressing • Remote and Dial-up Networking • Bandwidth Issues

31. Analysis Guidelines • Create a Physical Network Diagram • Create a Logical Network Diagram • Gather Network Configuration Info • Identify Existing Hardware as Deployment Candidates • Analyze Network Performance • Identify Deployment Tools • Software / Service Packs / Hot Fixes • System Center Configuration Manager (SCCM) • Windows Group Policies

32. Availability Analysis • Reliable Components • Fault Tolerant Mechanisms • Clustering • Clustering Types • Active/Passive (Passive takes full control) • Active / Active (Load shared on failover) • Clustering Tools • Windows Clustering Server • Resource Monitor • Windows Cluster Service • SQL Server Failover Monitoring • Project Server 2010 Primary Benefit / SQL Server • Clustering can be used for Failover

33. Scalability Analysis • Scaling Up • Hardware Updates • Additional Processors • Additional RAM • Scaling Out • Distributing Workload • Network Load Balancing • Client Requests Distributed • IP Packets Received by Each Host • Accepted only by the Intended Recipient • Workload Distributed • Hosts can specify Workload Percentage • Distributed based on Server Workload • Distributed based on Number of Packets

34. Scalability Options • Distributed Server Targets • Project Server 2010 • Session Management Removed from Front-end Servers • Session Management Deployed outside the NLB Cluster • SharePoint Server 2010 • View Management Server • Must be outside of the PS2010 NLB Cluster • May be Clustered for Failover Purposes • SQL Server Options • Clustering (Applies also to Availability) • Database Partitioning • Two-Way Partitioning (Dual Server Mode) • Three-Way Partitioning (WinProj & Views Extracted)

35. Security Considerations • Project Server 2010 Related Service Accounts • *SPS2010 Setup Service Account (Member of Local or Domain Admin) • *SPS2010 Farm Service Account (Member of Local or Domain Admin) • *SPS2010 AppPool Service Account (NOT a Member of Local or Domain Admin) • *PS2010 Service Account (Member of Local or Domain Admin - Optional) • *SQL Server Service Account (Needs dbo to Create Permissions) * To be created before Project Server 2010 Installation • Organizational Requirements • Project Server 2010 Enterprise Resource Pool • Unique Resource Names • Based on Active Directory Accounts • Create Convention if None is in Place(FirstName LastName) • System Server Security • Verify that All Domain Accounts are Assigned • Verify that All Accounts have Proper Permissions • Use Proper Naming Conventions

36. Configuration Suggestions • Install the latest updates, but under the proviso that the targeted update (Service Pack or Cumulative Update), has been available sufficiently long enough to be validated by common use (peruse Blogs and News Groups for issues) • Install Views Processing and Session Management Service on Separate Hardware • Install a Single Project Server 2010 instance in a Load-balanced Cluster (For Future Expansion) • Increase Internet Information Services (IIS) Memory • Use Multiple Network Interface Cards (NIC) • Set all NIC Cards on Servers to Full-Duplex Mode

37. New with Project Server 2010 • Project Service Application 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 • Please Read “Deploy Project Server to a Server Farm Environment” on TechNet (Search Topic if Necessary)

38. Project Server 2010 Software Requirements 64-bit • Optional • Exchange 2007 SP1 or later • Team Foundation Server 2010 for Application Lifecycle Management

39. Installation Process PowerShell Support

40. 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

41. Post Setup Project Web AppCore Items • Time Reporting Periods • Required now for My Tasks/My Timesheets/SEM • 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 • Detailed setup procedures will be available

42. Deployment Scenarios • Together/Coexistence • Single farm with both Project Server and SharePoint Server • Apart/Standalone • Dedicated Project Server Farm running SharePoint Server • EPM and Office SharePoint Server 2007 Coexistence — Intranet Scenario(TechNet whitepaper applicable to 2010)

43. Together Pros & Cons - Single Project & 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

44. Apart Pros & Cons - Separate Project & 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

45. Single Farm Deployment Considerations • 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

46. Project Server 2010 Interface Object Link Provider Admin Events Calendar Cube Admin Custom Fields Project Lookup Table Notifications Queue Resource Security Resource Plan Statusing Timesheet WSS Interop Driver Archive Portfolio Analysis Workflow

47. Enterprise Project Management Project Workflow Overview • Enables custom project selection process • Custom Workflows created in Visual Studio 2010 • No Support for SharePoint Designer (SPD) Plan Select Manage Create Portfolio Selection Work Planning Collaboration & Reporting Demand Management

48. Project Workflow Architecture

49. Project Server Workflow Breakdown Project Server Interface Project Server Workflow Channel Custom Activity Custom Activity Custom Activity

50. Project Server 2010 Architecture Topic 2.1 – Architectural Outline Topic 2.2 – Software Components Topic 2.3 – Hardware Components Topic 2.4 – Infrastructure Planning Topic 2.5 – High-level Business Process