Mircosoft planner serial key or number

Q. What is Microsoft End of Support (EOS)?

Microsoft Lifecycle Policy offers 10 years of support (5 years for Mainstream Support and 5 years for Extended Support) for Business and Developer products (such as SQL Server and Windows Server). As per the policy, after the end of the Extended Support period there will be no patches or security updates.

Q. How does EOS affect my existing instances on Amazon Web Services (AWS)?

There is no direct impact to existing instances. Customers can continue to start, run, and stop instances.

Microsoft will not provide patches for EOS products, unless customers purchase Extended Security Updates.

Q. Can I launch new instances that include EOS software from my Custom Amazon Machine Images (AMIs)?

Yes.

Q. Can I import images that contain EOS software into AWS using AWS tools?

Yes, customers can continue to import images to AWS using VM Import/Export (VMIE), Server Migration Service (SMS), or CloudEndure.

Q. How does EOS affect Managed AWS Windows AMIs?

There is no direct impact to existing AMIs registered in customer accounts.

AWS will not publish or distribute Managed AWS Windows AMIs that contain EOS software to AWS Management Console, Quick Start, or AWS Marketplace.

Customers with dependencies on Managed AWS Windows AMIs impacted by EOS should consider their options, including creating Custom AMI(s) within their AWS account(s) to enable new instance launches. Learn more about custom AMI creation here.

Q. Can I create additional Custom AMIs from existing Custom AMIs in my account that contain EOS software?

Yes.

Q. What are my options for running Microsoft software that is approaching EOS?

AWS customers running EOS software on EC2 instances have several options:

Remain on EOS software: Customers may decide to remain on EOS software. There will be no impact to existing instances, or to custom AMIs.

Automated upgrade: For customers with SQL Server 2008 R2 and Windows Server 2008 R2, AWS Systems Manager automates the performance of non-destructive in-place upgrades. SQL Server 2008 R2 customers can upgrade to SQL Server 2012 R2 and again to SQL Server 2016 (BYOL only). Windows Server 2008 R2 customers can upgrade to Windows Server 2012 R2. For customers with a License Included (LI) version of Windows Server or SQL Server, there is no additional licensing cost to upgrade. For more information, please click here.

Manual in-place upgrade for Microsoft Windows Server:

License Included: Customers using Amazon License Included for Windows Server can perform in-place upgrades for their Windows instances. For more information, click here.

BYOL: Customers using the BYOL model can perform a manual in-place upgrade for Windows Server following the steps referenced in the License Included option above, using their own Media.

Manual in-place upgrade for Microsoft SQL Server:

License Included: AWS customers using License Included SQL Server can perform in-place upgrades on running instances. Please contact AWS support for additional assistance and detail on upgrade paths.

BYOL: Customers using the BYOL model can perform a manual in-place upgrade for SQL Server using their Media. For more information, click here.

Explore other platform options. AWS is committed to offering its customers the most flexibility in the cloud. AWS customers interested in the benefits of migrating certain SQL Server or Windows workloads to a different platform can contact their AWS account teams for more information.

For more information on all of Amazon’s products and Services, click here.

Q. Can I purchase Extended Security Updates to cover instances that run on AWS, utilizing Microsoft EOS software?

Yes, Extended Security Updates are available directly from Microsoft or a Microsoft licensing partner. Read more about Microsoft's Extended Security Updates here.

Customers should consider all their options for EOS, see “What are my options for running Microsoft software that is approaching EOS?” for more information.

Windows Server 2003

Extended Security Updates available for Amazon License Included? No.

Extended Security Updates available for Bring Your Own License (BYOL)? No.

Windows Server 2008/2008 R2

Extended Security Updates available for Amazon License Included? Yes.

Extended Security Updates available for Bring Your Own License (BYOL)? Yes; active Software Assurance (SA) required.

SQL Server 2005

Extended Security Updates available for Amazon License Included? No.

Extended Security Updates available for Bring Your Own License (BYOL)? No.

SQL Server 2008/2008 R2

Extended Security Updates available for Amazon License Included? No.

Extended Security Updates available for Bring Your Own License (BYOL)? Yes; active Software Assurance (SA) required.

Q. Which Microsoft products sold by Amazon are approaching EOS, and when will Microsoft cease support?

Note: Information reflects publicly available Microsoft EOS dates as of April 4th, 2019.

Microsoft Windows Server:

• Windows Server 2003 - July 14th, 2015 (EOS already reached)
• Windows Server 2008 - January 14th, 2020
• Windows Server 2008 R2 – January 14th, 2020

Microsoft SQL Server:

• SQL Server 2005 – April 12th, 2016 (EOS already reached)
• SQL Server 2008 – July 9th, 2019
• SQL Server 2008 R2 – July 9th, 2019

More information on Microsoft's Application Lifecycle can be found here.

Q. What Amazon products and services are affected by EOS and when will changes be made?

Starting July 1st, 2019 Microsoft requires AWS to no longer publish and distribute License Included Managed AWS Windows AMIs (available in AWS Management Console and Quick Start), media, and services that use or contain Microsoft EOS products. Products that have reached end of support in prior years are also subject to these restrictions. The following products and services are affected:

Managed AWS Windows AMIs:

AWS will no longer publish and distribute Managed AWS Windows AMIs that contain EOS software to AWS Management Console, Quick Start or AWS Marketplace.

Microsoft Windows Server:

• Windows Server 2003 - July 1st, 2019
• Windows Server 2008 - January 14th, 2020
• Windows Server 2008 R2 - January 14th, 2020

Microsoft SQL Server:

• SQL Server 2005 – July 1st, 2019
• SQL Server 2008 - July 9th, 2019
• SQL Server 2008 R2 - July 9th, 2019

Amazon Relational Database Service (RDS):

RDS will automatically upgrade customer databases that remain on SQL Server 2008 to SQL Server 2012 starting on June 1, 2019. We recommend customers test this upgrade prior to this date to ensure compatibility.

RDS customers can upgrade their Database version at any time. Learn more about upgrading your SQL Server 2008 R2 database in RDS here.

Amazon WorkSpaces:

WorkSpaces will stop offering License Included public bundles of Windows 7 Experience powered by Windows Server 2008 R2 after January 14th 2020.

WorkSpaces launched from License Included public bundles with Windows 7 Desktop Experience will no longer be able to be launched or rebuilt after January 14th 2020.

There is no impact for WorkSpaces created from BYOL bundles. Customers can continue to launch/rebuild those instances.

Customers who have created custom License Included bundles powered by Windows Server 2008 R2 will be able to use their custom bundles to launch or rebuild WorkSpaces after EOS.

Microsoft will not provide patches for EOS products unless customers purchase Extended Security Updates.

Q. Does the change to Microsoft’s EOS software distribution policy only apply to AWS?

Microsoft has advised that this change will apply to all hyperscale cloud providers.

Q. What are my options for running Microsoft software that is approaching EOS?

AWS customers running EOS software on EC2 instances have several options:

Remain on EOS software: Customers may decide to remain on EOS software. There will be no impact to existing instances, or to custom AMIs. Customers who are interested in purchasing Extended Security Updates from Microsoft should review the answer to the question, “Can I purchase Extended Security Updates from Microsoft to cover EOS instances that run on AWS?”.

Automated upgrade: For customers with SQL Server 2008 R2 and Windows Server 2008 R2, AWS Systems Manager automates the performance of non-destructive in-place upgrades. SQL Server 2008 R2 customers can upgrade to SQL Server 2012 R2 and again to SQL Server 2016 (BYOL only). Windows Server 2008 R2 customers can upgrade to Windows Server 2012 R2. For customers with a License Included (LI) version of Windows Server or SQL Server, there is no additional licensing cost to upgrade. For more information, please click here.

Manual in-place upgrade for Microsoft Windows Server:

License Included: Customers using Amazon License Included for Windows Server can perform in-place upgrades for their Windows instances. For more information, click here.

BYOL: Customers using the BYOL model can perform a manual in-place upgrade for Windows Server following the steps referenced in the License Included option above, using their own Media.

Manual in-place upgrade for Microsoft SQL Server:

License Included: AWS customers using License Included SQL Server can perform in-place upgrades on running instances. Please contact AWS support for additional assistance and detail on upgrade paths.

BYOL: Customers using the BYOL model can perform a manual in-place upgrade for SQL Server using their Media. For more information, click here.

Explore other platform options. AWS is committed to offering its customers the most flexibility in the cloud. AWS customers interested in the benefits of migrating certain SQL Server or Windows workloads to a different platform can contact their AWS account teams for more information.

For more information on all of Amazon’s products and Services, click here.

Q. What are other AWS Customers doing?

AWS customers such as Sysco, Hess, Ancestry, and Expedia have successfully migrated and modernized their Windows workloads on AWS. Read more about what AWS customers are doing here.

Q. What are the cost implications of moving to a supported Microsoft Operating System or SQL Server version?

License Included: There is no additional licensing costs to move to a newer version of the software when using Amazon's License Included options, for example:

• Microsoft Windows Server 2019 is the same price as Microsoft Windows Server 2003/2008/2008 R2.
• Microsoft SQL Server 2017 (by edition) is the same price as Microsoft SQL Server 2005/2008/2008 R2 (by edition).

BYOL: Customers with active Software Assurance (SA) can upgrade to a newer version at no cost. Customers without SA can purchase a new license from Microsoft.

Q. If I experience a technical issue running a product that has reached Microsoft EOS, will AWS Support assist me?

Yes, customers with AWS Support plans will be able to engage AWS Support for technical issues.

NOTE: As per Microsoft's policy, after the end of the Extended Support, Microsoft will no longer provide patches or security updates unless Extended Security updates has been purchased.

Find more information on AWS Support plans here.

Q. If I have further questions around the use of Microsoft EOS on AWS, whom should I contact?

Please email aws.EOS.Microsoft@amazon.com.

Q. Specifically, which License Included Managed AWS Windows AMIs are affected and when does this take effect?

July 1st, 2019

• Windows_Server-2003-R2_SP2-English-32Bit-Base-*
• Windows_Server-2003-R2_SP2-English-64Bit-Base-*
• Windows_Server-2003-R2_SP2-English-64Bit-SQL_2005_SP4_Express-*
• Windows_Server-2003-R2_SP2-English-64Bit-SQL_2005_SP4_Standard-*
• Windows_Server-2003-R2_SP2-Language_Packs-32Bit-Base-*
• Windows_Server-2003-R2_SP2-Language_Packs-64Bit-Base-*
• Windows_Server-2003-R2_SP2-Language_Packs-64Bit-SQL_2005_SP4_Express-*
• Windows_Server-2003-R2_SP2-Language_Packs-64Bit-SQL_2005_SP4_Standard-*
  
  

July 9th, 2019

• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2008_R2_SP3_Express-*
• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2008_R2_SP3_Standard-*
• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2008_R2_SP3_Web-*
• Windows_Server-2008-R2_SP1-Japanese-64Bit-SQL_2008_R2_SP3_Express-*
• Windows_Server-2008-R2_SP1-Japanese-64Bit-SQL_2008_R2_SP3_Standard-*
• Windows_Server-2008-R2_SP1-Japanese-64Bit-SQL_2008_R2_SP3_Web-*
• Windows_Server-2008-R2_SP1-Language_Packs-64Bit-SQL_2008_R2_SP3_Express-*
• Windows_Server-2008-R2_SP1-Language_Packs-64Bit-SQL_2008_R2_SP3_Standard-*
• Windows_Server-2008-SP2-English-64Bit-SQL_2008_SP4_Express-*
• Windows_Server-2008-SP2-English-64Bit-SQL_2008_SP4_Standard-*
• Windows_Server-2012-RTM-English-64Bit-SQL_2008_R2_SP3_Express-*
• Windows_Server-2012-RTM-English-64Bit-SQL_2008_R2_SP3_Standard-*
• Windows_Server-2012-RTM-English-64Bit-SQL_2008_R2_SP3_Web-*
• Windows_Server-2012-RTM-Japanese-64Bit-SQL_2008_R2_SP3_Express-*
• Windows_Server-2012-RTM-Japanese-64Bit-SQL_2008_R2_SP3_Standard-*

January 14th, 2020

• Windows_Server-2008-R2_SP1-Chinese_Hong_Kong_SAR-64Bit-Base-*
• Windows_Server-2008-R2_SP1-Chinese_PRC-64Bit-Base-*
• Windows_Server-2008-R2_SP1-English-64Bit-Base-*
• Windows_Server-2008-R2_SP1-English-64Bit-Core-*
• Windows_Server-2008-R2_SP1-English-64Bit
• Core_SQL_2012_SP4_Standard-*
• Windows_Server-2008-R2_SP1-English-64Bit-SharePoint_2010_SP2_Foundation-*
• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2012_RTM_SP2_Enterprise-*
• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2012_SP4_Enterprise-*
• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2012_SP4_Express-*
• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2012_SP4_Standard-*
• Windows_Server-2008-R2_SP1-English-64Bit-SQL_2012_SP4_Web-*
• Windows_Server-2008-R2_SP1-Japanese-64Bit-Base-*
• Windows_Server-2008-R2_SP1-Japanese-64Bit-SQL_2012_SP4_Express-*
• Windows_Server-2008-R2_SP1-Japanese-64Bit-SQL_2012_SP4_Standard-*
  
• Windows_Server-2008-R2_SP1-Korean-64Bit-Base-*
• Windows_Server-2008-R2_SP1-Language_Packs-64Bit-Base-*
• Windows_Server-2008-R2_SP1-Portuguese_Brazil-64Bit-Base-*
• Windows_Server-2008-R2_SP1-Portuguese_Brazil-64Bit-Core-*
• Windows_Server-2008-SP2-English-32Bit-Base-*
• Windows_Server-2008-SP2-English-64Bit-Base-*
• Windows_Server-2008-SP2-Portuguese_Brazil-32Bit-Base-*
• Windows_Server-2008-SP2-Portuguese_Brazil-64Bit-Base-*

Before you begin    Make sure your PC meets the system requirements.

The steps below are for the subscription versions of Project Online, and the non-subscription versions of Project 2019, 2016, or 2013. (For Project 2010 or 2007, follow the steps in Office 2010 or Office 2007.) Project is sold as a stand-alone application so if you don't have it yet, Buy or try Project.

Step 1: Sign in to download Project

1. Go to www.office.com and if you're not already signed in, select Sign in.

2. Sign in with the account you associated with this version of Project. This account can be a Microsoft account (used with non-subscription versions), or work or school account (used with subscription versions).

   Forgot your account details? See I forgot the account I use with Office.

3. After signing in, follow the steps below for your subscription or non-subscription version of Project.

   Project (Standard or Professional)
    Non-subscription version
   

   1. From the Office home page select Install Office.

      

   2. If you have multiple Office products you may have to scroll through the list of your owned products, or if you have an Microsoft 365 subscription, in the header, select Services and subscriptions which lists all the Microsoft products you own.

      Locate the version of Project you want to install and select Install.

   Tip: To install Project in a different language, or to install the 64-bit version, select the link Other options. Choose the language and bit version you want, and then select Install.

   Project Online (Professional or Premium)
    Subscription version
   

   1. From the Office home page select Install Office apps > Other install options. (If you set a different start page, go to admin.microsoft.com/OLS/MySoftware.aspx.)

      

   2. Under Software, select Project. Choose the language and the bit version you want, then select Install. (To install 64-bit, under Version, select Advanced, choose 64-bit, and then select Install.)

   3. Tip: If Project isn't listed under the Software navigation heading on the left-side of your page, it probably means you don't have a license. Check if you have a license and if you don't, contact your admin and ask to have one assigned to you.

   Project should now begin downloading. Follow the prompts in Step 2 to complete the installation.

Step 2: Install Project

1. Depending on your browser, select Run (in Edge or Internet Explorer), Setup (in Chrome), or Save File (in Firefox).

   If you see the User Account Control prompt that says, Do you want to allow this app to make changes to your device? select Yes.

   The install begins.

   

2. Your install is finished when you see the phrase, "You're all set! Project is installed now" and an animation plays to show you where to find the Project app on your computer.

   Follow the instructions in the window to find Project, for example depending on your version of Windows, select Start and then scroll to find Project from your list of apps.

   

Need more help?

If you're still not finding the answers you need, try searching for content on support.office.com, or browsing through the list of topics on the Project Help Center.

You may also find it helpful to post your questions and issues on a discussion forum. The Project discussion forums tend to be very active, which make them a great resource for finding others who may have worked through similar issues, or encountered the same situation.