Microsoft Dynamics CRM / Dynamics 365 Updates: Release Dates, Build Numbers, and Collateral

Note: The Updates documented in this blog for:

• Microsoft Dynamics 365 (v9.X)
• Microsoft Dynamics CRM 2016 / Microsoft Dynamics 365 (v8.X)
• Microsoft Dynamics CRM 2015
• Microsoft Dynamics CRM 2013
• Microsoft Dynamics CRM 2011

update the Dynamics CRM components described in this Microsoft Knowledge base article:

Microsoft Dynamics CRM Installations, Updates and Documentation

Notes:

New naming conventions for Microsoft Dynamics CRM updates explained HERE

Microsoft Dynamics CRM Stack Technology Compatibility: Do you want to know if certain Service Packs or versions of a Microsoft product or technology are supported with Dynamics CRM? If so, consult the Microsoft Dynamics CRM Compatibility List. For example, you can use this KB to determine the latest Microsoft SQL Server major version and Service Pack that is supported. Microsoft will list new products like Internet Explorer 11 and Windows 8.1 as "TBD" until testing is complete; generally near General Availability (GA) of that product.

Dynamics CRM Organization Settings Editor (OrgDbOrgSettings)!

You may be familiar with the OrgDbOrgSettings command line tool released by the CRM Product Group in the "Tools" package that is updated and released with each set of Update Rollup packages. With it, you configure .xml and call your .xml with the command line utility described in KB 2691237. However, you may be daunted by configuring this .xml, to the point that you may not use the tool, or use it minimally; not exploring the many options outlined in KB 2691237 that may be of use to you.

The Microsoft Dynamics PFE team has another option for you; the "Dynamics CRM Organization Settings Editor." CRM Senior PFE Sean McNellis developed this managed solution which provides an easy-to-use GUI with which you can configure all of the options outlined in the Knowledge Base on a per-tenant basis. The download page has screenshots and information that will help you make good use of the tool. Sean has also published a Premier Field Engineering blog to share more details on the tool, and he keeps the tool update as needed. Thanks, Sean!

>===============================================================

Microsoft Dynamics 365 (v9.X)

Dynamics 365 CE RTM ("Release to Manufacture") build is 9.0.2.3034

Microsoft Dynamics CRM 2016 / Microsoft Dynamics 365 (v8.X)

CRM 2016 RTM ("Release to Manufacture") build is 8.0.0.1088

Mainstream Support Lifecycle: Keep in mind that Mainstream Support for Microsoft Dynamics CRM 2016 ends January 12th, 2021 as per CRM 2016’s supported lifecycle.

Go to Top
===============================================================

Microsoft Dynamics CRM 2015

CRM 2015 RTM ("Release to Manufacture") build is 7.0.0.3543

Mainstream Support Lifecycle: Keep in mind that Mainstream Support for Microsoft Dynamics CRM 2015 ends January 14th, 2020 as per CRM 2015’s supported lifecycle.

Go to Top
===============================================================

Microsoft Dynamics CRM 2013

Mainstream Support Lifecycle: Keep in mind that Mainstream Support for Microsoft Dynamics CRM 2013 ends January 8th, 2019 as per CRM 2013’s supported lifecycle.

Go to Top

===============================================================

Microsoft Dynamics CRM 2011

Mainstream Support for Microsoft Dynamics CRM 2011 ended July 12th, 2016 as per CRM 2011’s supported lifecycle.

CRM 2011 Update Rollup 18.1 (Update for Microsoft Dynamics CRM 2011) will be the final Update for Microsoft Dynamics CRM 2011. There are no plans to release an Update Rollup 19 for CRM 2011.
Support for .NET 4.6 or SQL Server 2014, will not be included for CRM 2011. The Supportability Knowledge Base article has been updated accordingly (https://support.microsoft.com/en-us/kb/3005163)
Per the support lifecycle policy mentioned above, when extended support starts, the only fixes delivered will be security fixes.

Notes:

Mismatched Update Rollup versions within a Microsoft Dynamics CRM 2011 or 2013 deployment: In a scenario where you may be running many client workstations with Microsoft Dynamics CRM 2011 or 2013 for Microsoft Office Outlook, a common question is whether it is supported to run mismatched versions. For example, where Update Rollup 5 has been installed on the CRM 2011 Server but the Outlook clients are still on Update Rollup 1, or where Update Rollup 1 is on the CRM 2011 server but due to updates available to the Outlook client you have decided to install Update Rollup 6 on the clients without installing Update Rollup 4 on the server.

The general rule of thumb is to try to keep the versions in sync as much as possible. However, it is permissible (though not recommended as a long-term solution) to run mismatched Update Rollup versions on Outlook client and server, as Microsoft does do some testing of such combinations.

However, regarding the other Update Rollups (for example Rollups for the Microsoft Dynamics CRM 2011 or 2013 Email Router or Microsoft Dynamics CRM 2011 2013 Reporting Extensions), it is not supported nor recommended to run mismatched versions. A best practice is to update these components at the same time you update your CRM Server. Do the best you can to keep these Update Rollup versions in sync.

See: Mismatched Update Rollup versions within a Microsoft Dynamics CRM 2011 deployment and "User experience while accessing CRM 2011 application servers while Update Rollups are being applied"