Project 2007 End of Life Details

Total Page:16

File Type:pdf, Size:1020Kb

Project 2007 End of Life Details Project 2007 End of Life Details Please write support is ending for Project Server 2007 and Project 2007 Product End of life date Project Server 2007 October 10, 2017 Project Server 2007 October 10, 2017 Project Portfolio Server 2007 October 10, 2017 Project 2007 Standard October 10, 2017 Project 2007 Professional October 10, 2017 For more information about Office 2007 servers reaching retirement, see Plan your upgrade for Office 2007 servers. What does End of Life mean? Project Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the date of the product’s initial release, and the end of this lifecycle is known as the product’s End of Life. When Project Server 2007 reaches its End of Life on October 10, 2017, Microsoft will no longer provide: • Technical support for problems that may occur. • Bug fixes for issues that are discovered and that may impact the stability and usability of the server. • Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches. • Time zone updates. Your installation of Project Server 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Project Server 2007 as soon as possible. What are my options? If you are using Project Server 2007, you need to explore your migration options, which are: • Migrate to Project Online • Migrate to a newer on-premises version of Project Server (preferably Project Server 2016). Note: For more information about options for moving from your Office 2007 servers, see Plan your upgrade for your Office 2007 servers. Note that Project Server does not support a hybrid configuration since Project Server and Project Online cannot share the same resource pool. Important considerations you need to make when planning to mi- grate from Project Server 2007 You need to consider the following when planning to migrate from Project Server 2007: • Get help from a Microsoft Partner – Upgrading from Project Server 2007 can be challenging, and requires a lot of preparation and planning. It can be especially challenging if you were not the one to setup and configure Project Server 2007 originally. Luckily, there are Microsoft Project Partners who can help; whether you plan on migrating to Project Server 2016 or to Project Online. You can write to [email protected] • Plan for your customizations – Be aware that many of the customizations you have working in your Project Server 2007 environment might not work when migrating to Project Server 2016 or to Project Online. There are big differences in Project Server architecture between versions, as well as the required operating systems, database servers, and client web browsers that are supported to work with the newer version. Have a plan in place on how to test or rebuild your customiza- tions as needed in your new environment. Planning for your upgrade will also be a good opportu- nity to verify if a specific customization is needed as you move forward. Create a plan for current customizations during upgrade to SharePoint 2013 has some great general information about evaluating and planning for your current customizations when upgrading. • Time and patience – Upgrade planning, execution, and testing will take a lot of time and effort, especially if you are upgrading to Project Server 2016. For example, if you are migrating from Project Server 2007 to Project Server 2016, you will first need to migrate from Project Server 2007 to Project Server 2010, and then check your data, and then do the same thing when you migrate to each successive version. You might want to check with a Microsoft Partner to compare your costs with their estimates of how long it will take for them to do it, and at what cost. Migrate to Project Online If you choose to migrate from Project Server 2007 to Project Online, you can do the following to manually migrate your project plan data: 1. Save your project plans from Project Server 2003 to .MPP format. 2. Using Project Professional 2013, Project Professional 2016, or the Project Online Desktop Client, open each .mpp file, and then save and publish it to Project Online. You can manually create your PWA configuration in Project Online (for example, recreate any needed custom fields or enterprise calendars). Microsoft Partners can also help you with this. Key resources: Migrate to a newer on-premises version of Project Server While we strongly believe that you can achieve the best value and user experience by migrating to Project Online, we also understand that some organizations need to keep project data in an on-premises environment. If you choose to keep your project data on-premises, you can migrate your Project Server 2007 environment to Project Server 2010, Project Server 2013, or Project Server 2016. We recommend that you migrate to Project Server 2016 if you can’t migrate to Project Online. Project Server 2016 includes all the features and advancements included with previous releases of Project Server, and it most closely matches the experience available with Project Online (although some features are available only in Project Online). After completing each migration, you should check your data to make sure that it has migrated successfully. NOTE: If you are considering only migrating to Project Server 2010 if you are limited to an on-premises solution, it is important to note that it only has a few more years of support left. Project Server 2010 with Service Pack 2 end of life date is 10/13/2020. For more information about end of life dates, see Microsoft Product Lifecycle Policy. How do I migrate to Project Server 2016? The architectural differences between Project Server 2007 and Project Server 2016 prevents a direct migration path. This means that you will need to migrate your Project Server 2007 data to the next successive version of Project Server until you upgrade to Project Server 2016. You will need to do the following to upgrade to Project Server 2016: Step 1: Migrate from Project Server 2007 to Project Server 2010. Step 2: Migrate from Project Serve 2010 to Project Server 2013. Step 3: Migrate from Project Server 2013 to Project Server 2016. After completing each migration, you should check your data to make sure that it has migrated Step 1: Migrate from Project Server 2007 to Project Server 2010 For a comprehensive understanding of what you need to do to upgrade from Project Server 2007 to Project Server 2010, see the Upgrade to Project Server 2010 content set on TechNet. Key resources: How do I upgrade? While details on how to upgrade can be found in the Upgrade to Project Server 2010 content set, it is important to understand that there are two distinct methods you can use to upgrade: • Database-attach upgrade: This method only upgrades the content for your environment, and not the configuration settings. It is required if you are upgrading from Office Project Server 2007 deployed on hardware that only supports a 32-bit server operating system. There are two types of database-attach upgrade methods: Database-attach Full upgrade - Migrates the project data stored in the Office Project Server 2007 databases, plus the Microsoft Project Web App (PWA) site data stored in a SharePoint content database. Database-attach Core upgrade - Migrates only the project data stored in the Project Server databases. • In-Place upgrade: The configuration data for the farm and all content on the farm is upgraded on the existing hardware, in a fixed order. When you start the in-place upgrade process, setup takes the entire farm offline and the Web sites and Microsoft Project Web App sites are unavaila- ble until the upgrade is finished, and then setup restarts the server. After you begin an in-place upgrade, you cannot pause the upgrade or roll back to the previous version. It is highly suggested to make a mirrored image of your production environment and to do the in-place upgrade to this environment, and not your production environment. Additional Resources: SuperFlow for Microsoft Project Server 2010 Upgrade Migration from Project Server 2007 to Project Server 2010 Upgrade considerations for Project Web App Web Parts Project Software Development Kit (SDK) Step 2: Migrate to Project Server 2013 After migrating to Project Server 2010 and verifying that your data has migrated successfully, the next step is to migrate your data to Project Server 2013. For a comprehensive understanding of what you need to do to upgrade from Project Server 2010 to Project Server 2013, see the Upgrade to Project Server 2013 content set on TechNet. Key resources: Things to know about upgrading to this version What's new in Project Server 2013 upgrade tells you some important changes for upgrade for this version, the most notable being: • There is no in-place upgrade to Project Server 2013. The database-attach method is the only supported method for upgrading from Project Server 2010 to Project Server 2013. • The upgrade process will not only convert your Project Server 2010 data to Project Server 2013 format, but will also consolidate the four Project Server 2010 databases to a single Project Web App database. • Both SharePoint Server 2013 and Project Server 2013 changed to claims-based authentication from the previous version. You will need to make considerations when upgrading if you are using classic authentication. For more information, see Migrate from classic-mode to claims-based authentication in SharePoint 2013. Additional Resources: Overview of the upgrade process to Project Server 2013 Upgrade your databases and Project Web App site collections (Project Server 2013) Microsoft Project Server upgrade process diagram The Great Database Consolidation, Project Server 2010 to 2013 Migration in 8 Easy Steps Step 3: Migrate to Project Server 2016 After migrating to Project Server 2013 and verifying that your data has migrated successfully, the next step is to migrate your data to Project Server 2016.
Recommended publications
  • Project-Server-2010-MPUG-CIC-12-14-2010.Pdf
    12/20/2010 Overview of Project Server 2010 For MPUG Central Indiana Chapter Bud Ratliff Sean Pales 14 December 2010 Sponsor • Rick Miller and Eric Galloway www.infopoint.com 1 12/20/2010 Introductions • Bud Ratliff, The Solarity Group Project Management Training www.solarity.com • Sean Pales, Prosymmetry Project Server Hosting and Implementation www.prosymmetry.com Common experience across full PPM lifecycle Flexible project capture and initiation Enhance governance through workflow Powerful portfolio selection analytics Simple and Intuitive User Experience Fluent UI (Ribbon, Backstage view) Intuitive Excel-like behavior Timeline & Team Planner views Web-based project editing Enhanced Collaboration & Reporting Connect teams with SharePoint Sync Built on SharePoint Server 2010 Better time and status reporting Easily create reports and dashboards Scalable and Connected Platform Extend interoperability Simplified administration Rich platform services Developer Productivity 2 12/20/2010 Common experience across full PPM lifecycle Flexible project capture and initiation Enhance governance through workflow Powerful portfolio selection analytics Simple and Intuitive User Experience Fluent UI (Ribbon, Backstage view) Intuitive Excel-like behavior Timeline & Team Planner views Web-based project editing Enhanced Collaboration & Reporting Connect teams with SharePoint Sync Built on SharePoint Server 2010 Better time and status reporting Easily create reports and dashboards Scalable and Connected Platform Extend interoperability Simplified administration Rich platform services Developer Productivity Choose the Right Tools that Can Evolve with You Project & Portfolio Management Web-Based Project Editing (Project Server) 3 12/20/2010 Connected Platform 4 12/20/2010 Changes From Project Server 2007 Project Portfolio Microsoft Project Server Server 2007 2010 Project Gateway Includes Project Server Project Portfolio 2007 functionality Built on….
    [Show full text]
  • Installing Microsoft Office Project Server 2007
    Installing Microsoft Office Project Server 2007 This work may be reproduced and redistributed, in whole or in part, without alteration and without prior written permission, provided all copies contain the following statement: Copyright ©2011 sheepsqueezers.com. This work is reproduced and distributed with the permission of the copyright holder. This presentation as well as other presentations and documents found on the sheepsqueezers.com website may contain quoted material from outside sources such as books, articles and websites. It is our intention to diligently reference all outside sources. Occasionally, though, a reference may be missed. No copyright infringement whatsoever is intended, and all outside source materials are copyright of their respective author(s). Copyright ©2011 sheepsqueezers.com Page 2 Table of Contents Introduction .................................................................................................................................................. 4 Installing Project Server 2007 (Server Farm Setup) without WSS 3.0 Previously Installed ........................... 6 Configuring the Server Farm ...................................................................................................................... 24 Installing Project 2007 Professional ........................................................................................................... 27 Setting Up Project 2007 Professional to Work with Project Server 2007 .................................................... 33 References ...............................................................................................................................................
    [Show full text]
  • Microsoft Project 2010
    Microsoft® Project 2010 Microsoft Project 2010 Enterprise Project Management Solution Demo May 2010 / version 2.01 Information in the document, including URLs and other Internet Web site references is subject to change without notice. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you a license to any patent, trademarks, copyrights, or other intellectual property that are the subject matter of this document. As a valued Microsoft customer you can always search for a Microsoft certified project partner that can help you walk through Project 2010 products and help you determine the best solution to suite your needs. Please go to http://www.microsoft.com/project and click “Solutions & Partners” and then “Find a partner by geography” to access the extensive and experienced list of “Microsoft Certified Project and Portfolio Management” partners local to you. For further information on products and partners you can also speak to your local Microsoft representative. Requirements and pre-requisites Requirement Item Virtual Machine Downloaded, imported and running 2010 Information Worker Demonstration and Evaluation Virtual Machine (http://go.microsoft.com/?linkid=9728417) Supported Operating System Microsoft Windows® Server 2008 R2 with the Hyper-V role enabled RAM 8 GB recommended for the host machine, 5GB or more allocated to the Virtual Image recommended Additional disk space required for 5 GB, Solid State Drive recommended for better install performance Demonstration
    [Show full text]
  • What's New in Microsoft Project Server 2010
    What’s New Microsoft® Project Server 2010 provides unifi ed project and portfolio management to help organizations prioritize investments, align resources and execute projects effi ciently and effectively. © Microsoft Corp. All rights reserved What’s New in Project Server 2010 Microsoft Project Server 2010 brings together the business collaboration platform services of Microsoft® SharePoint Server 2010 with structured execution capabilities to provide fl exible work management solutions. Project Server 2010 unifi es project and portfolio management to help organizations align resources and investments with business priorities, gain control across all types of work, and visualize performance through powerful dashboards. Unifi ed Project & Portfolio Management (PPM) In Project 2010, the best-of-breed portfolio management techniques of Microsoft Offi ce Project Portfolio Server 2007 are included in Project Server 2010, providing a single server with end-to-end project and portfolio management (PPM) capabilities. • Familiar SharePoint user interface throughout the solution. • Common data store eliminating the need for the Project Server Gateway. • Intuitive and simplifi ed administration. • Localized portfolio selection capabilities. • Comprehensive Application Programming Interface (API) including both project and portfolio capabilities. two © Microsoft Corp. All rights reserved Built on SharePoint Server 2010 Project Server 2010 is built on top of SharePoint Server 2010, bringing together the powerful business collaboration platform services and structured execution capabilities to provide fl exible work management solutions. Gain additional value from the Microsoft platform. • Take advantage of the Business Intelligence platform to easily create reports and powerful dashboards. • Control document review and approval through workfl ow. • Enterprise search makes it easy to fi nd people and effectively mine project data (resources, tasks, documents etc.).
    [Show full text]
  • Technical Reference for Microsoft Sharepoint Server 2010
    Technical reference for Microsoft SharePoint Server 2010 Microsoft Corporation Published: May 2011 Author: Microsoft Office System and Servers Team ([email protected]) Abstract This book contains technical information about the Microsoft SharePoint Server 2010 provider for Windows PowerShell and other helpful reference information about general settings, security, and tools. The audiences for this book include application specialists, line-of-business application specialists, and IT administrators who work with SharePoint Server 2010. The content in this book is a copy of selected content in the SharePoint Server 2010 technical library (http://go.microsoft.com/fwlink/?LinkId=181463) as of the publication date. For the most current content, see the technical library on the Web. This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.
    [Show full text]
  • Microsoft Project Server 2010 Administrator's Guide
    1 Microsoft Project Server 2010 Administrator's Guide Copyright This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Excel, Internet Explorer, Outlook, SharePoint, SQL Server, and Windows are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners. Table of Contents Table of Contents Introduction 1 What Will You Learn from this Book? ..................................... 1 Who Should Read this Book? ................................................. 1 How is this Book Structured? ................................................. 2 1 Security 5 Manage Permissions .............................................................. 6 Manage Users ......................................................................... 8 Add or Edit a User ...................................................................................................... 8 Deactivate a user account ...................................................................................... 19 Reactivate a user account ....................................................................................... 20 Manage Groups ....................................................................
    [Show full text]
  • Microsoft Enterprise Project Management 2010 Licensing Guide Microsoft Project 2010 Licensing
    Microsoft Enterprise Project Management 2010 Licensing Guide Microsoft Project 2010 Licensing Microsoft® Project 2010 is a family of products that provide a range of functionality depending on organizational needs. Project 2010 allows organizations to ease into the correct level of maturity for their work management needs. The Project 2010 family consists of desktop and server products. Microsoft Project Standard 2010 and Microsoft Project Professional 2010 are both desktop editions. The flagship of the Enterprise Project Management solution is Microsoft Project Server 2010. This guide will help you understand the relationship among the various Project editions, their interdependencies, and requirements. The goal of this guide is to help identify the correct technologies to put in place in order to have an effective project management system. Work Management Solutions for Individuals, Teams, and the Enterprise For Enterprise Project Management (EPM) solutions to be effective, they Organizations can achieve incremental gains in collaboration need to provide organizations of different sizes and varying EPM maturity capabilities by using products within the Microsoft Project and levels with the appropriate tools to help ensure that teams can collaborate Microsoft SharePoint® families. Large and small organizations alike can to deliver projects successfully. A small or mid-size organization may have deploy the EPM solution to successfully support project management. different EPM requirements as compared to a multinational organization. Individual Project Management Microsoft Project Standard and Project Professional (used as standalone applications) and SharePoint task lists can help full-time and part-time project managers to create and track schedules that enable project teams to complete their work on time and within budget.
    [Show full text]
  • Microsoft Project Server 2010 a Look at Portfolio Strategy
    Microsoft Project Server 2010 A look at Portfolio Strategy A whitepaper for stakeholders in a program ecosystem Authors: Tim Cermak, PM Tim Runcie, MVP PMPP Manmeet Chaudhari, MVP Date published June 2010 www.Advisicon.com Example screen shots and product functionality are based on the Project 2010 Beta. Actual requirements and product functionality may change with the final release of the commercially available product and also may vary based on your system configuration and operating system. Information in the document, including URL and other Internet Web site references is subject to change without notice. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you a license to any patent, trademarks, copyrights, or other intellectual property that are the subject matter of this document. Table of Contents Table of Figures ............................................................................................................................................. 5 Executive Summary ....................................................................................................................................... 7 Introduction to Project Portfolio Management ............................................................................................ 8 What is Project Portfolio Management? .................................................................................................. 8 Objectives of PPM ..................................................................................................................................
    [Show full text]
  • Licensing Microsoft Project Server 2016 Volume Licensing
    ` Licensing Microsoft Project Server 2016 Volume Licensing This document covers licensing for an on-premises deployment of Project Server 2016. Project Online is an alternative Microsoft hosted offering and is licensed via a subscription model. MICROSOFT® PROJECT SERVER 2016 SERVER LICENSE and CALS Microsoft Project Server 2016 is a flexible on-premises solution for Purchase a Server license for each server, and then purchase project portfolio management (PPM) and everyday work. Team Client Access Licenses (CALs) for either users or devices: members, project participants, and business decision makers can get A Device CAL started, prioritize project portfolio investments and deliver the is assigned to A User CAL is intended business value from virtually anywhere. the device and assigned to the allows user and allows that user to use multiple MICROSOFT PROJECT USER INTERFACES users to use multiple that device devices Project Standard 2016 is a standalone desktop application for project managers to create and manage projects Organizations with Project Professional 2016 licenses also receive one Project Server 2016 Device CAL for each license. Project Professional 2016 is a desktop application that enables project managers to create and manage projects, and publish them to Project Server 2016 to allow collaboration within the complete project team LICENSING EXTERNAL USERS The Project Web App is a browser-based interface that allows External Users are users who are not the licensee’s or its affiliates’ project managers, team members, and portfolio managers to employees or on-site agents or contractors work with and report on Project Server 2016 information External Users are licensed with either User or Device CALs TYPICAL PROJECT MANAGEMENT SCENARIOS VIRTUALIZATION The following table presents several roles in typical project management scenarios.
    [Show full text]
  • Installation Guide
    Installation guide [email protected] www.nintex.com © 2013 Nintex. All rights reserved. Errors and omissions excepted. Table of Contents System Requirements ............................................................................................................................. 3 1. Installing Nintex Workflow for Project Server 2013 ............................................................................. 4 Before running the Installer ................................................................................................................. 4 1.1 Run the Installer ............................................................................................................................ 4 1.2 Deploy the Solution Package ........................................................................................................ 4 1.3 Installing Nintex Workflow for Project Server 2013 Backwards Compatibility UI Features (optional) ............................................................................................................................................. 5 1.4 Importing the License .................................................................................................................... 5 2. Database Configuration ...................................................................................................................... 6 2.1 Deploy Database Components ..................................................................................................... 6 3. Configure Nintex Workflow for Project
    [Show full text]
  • Microsoft Project Server
    IMPLEMENTING AND ADMINISTERING MICROSOFT® PROJECT SERVER 2019 MICROSOFT PROJECT SERVER IMPLEMENTING AND ADMINISTERING MICROSOFT PROJECT SERVER 2019 Implementing and Administering Microsoft® Project Server 2019 course is 5 Day / 40 Hours Instructor led training course which covers step by step instructions on Planning and implementation of Microsoft PPM / EPM. You will learn detailed step-by-step instructions for planning, installing, configuring, deploying and managing the Microsoft SharePoint 2019 and Microsoft Project Server 2019. ABOUT COURSE DELIVERABLES Course Name Implementing & ✓ Slides Handout Administrating Microsoft ✓ Practice Labs Project Server 2019 ✓ Reference Links Course Duration 5 Days / 40 Hours ✓ Exam Blueprint Courseware Custom Courseware ✓ Trial Software Practise on Microsoft Project Server, ✓ 1 year 360Skills email Support Microsoft SharePoint, Microsoft Project Labs MODULES Training Mode Classroom, Online, Corporate 1. Introduction and Project Server 2. Understanding the Human Challenge PREREQUISITES 3. Applying a Deployment Process 4. Installing SharePoint / Project Server 1. Basic understanding of SharePoint. 5. Post-Installation Configuration 2. Basic Knowledge of Microsoft Project 6. Understanding the Project Web App 3. Basic Concepts of Project Interface Management 4. Basic of Microsoft Windows Server / 7. Creating System Metadata and SharePoint Server administration Calendars 8. Configuring Portfolio and Project AUDIENCE Governance • Anyone responsible for Implementing, 9. Building and Managing the Enterprise Managing, Maintaining Microsoft Resource Pool Project Server 2019 including 10. Initial Project Server Configuration • IT Administrators, Project Server Administrators, SharePoint 11. Configuring Time and Task Tracking Administrators, System Architect, 12. Configuring Project Server Security Consultants, Business Analysts, System 13. Building the Project Environment Analysts 14. Creating and Managing Views 1 www.360skills.com Microsoft ®, SharePoint ®, Project Server ® are the registered trademark of Microsoft Corporation 15.
    [Show full text]
  • Microsoft Project Server 2010 Integration with SAP
    Microsoft Project Server 2010 Integration with SAP Leverage the Power of Project Server to Provide Timely and Cost effective Resource Forecast Business Intelligence through integration with SAP and other ERP Systems! Tim Runcie, MCTS, MCP, MVP, PMP Doc Dochtermann, PMP, PMI-SP, MCTS Chetan Patel, MCP, PMP January 2012 This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. © 2012 Microsoft Corporation. All rights reserved. Microsoft Project Server 2010 Integration with SAP 2 Executive Summary This white paper outlines the benefits and scenarios for integrating Microsoft Project Server 2010 with SAP’s ERP; in particular integrating the actual time reporting from SAP with the time-phased planning and resource forecasting power of Project Server 2010. This integration is cost-effective and enables the source of record Actuals (both Cost and Time reporting) to bring actuals to the planning activities that Project/Program Offices or Scheduling groups use Project Server 2010 for. This connection and process enables a large national company to drastically reduce the time spent in planning and trying to map the actuals directly with the way that the organization schedules work. Further, it enables the feature rich reporting capabilities of Microsoft Project Professional, Project Server and SharePoint Server and puts that planning and reporting directly in the hands of the end users.
    [Show full text]