Note: The Updates documented in this blog for:
update the Dynamics CRM components described in this Microsoft Knowledge base article:
Microsoft Dynamics CRM Installations, Updates and Documentation
Microsoft Dynamics CRM 2015
RTM Build of CRM RTM ("Release to Manufacture") is 07.00.0000.3543
CRM 2015 Update #
Release date and Download Center URL
Release date – Microsoft Update
Knowledge Base article
Microsoft Dynamics CRM 2013
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? Now we have all of this in one “living" Knowledge Base article: 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.
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.
NEW RELEASE REGARDING the OrgDbOrgSettings tool for CRM 2011 and CRM 2013!
You're probably familiar with the OrgDbOrgSettings command line tool (mentioned above) 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 some .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. Well, the Microsoft Dynamics PFE team now has another option for you! By popular demand, our esteemed CRM PFE colleague Sean McNellis has developed a tool - a CRM 2011 / CRM 2013 managed solution - that provides you with an easy-to- use GUI with which you can configure all of the options outlined in the Knowledge Base on a per-tenant basis. Feel free to download it, install it, and check it out... I sure use it!
CRM 2013 pre-release builds
CRM 2013 Update Rollup #
6.0.0002.0046, 6.0.0002.0051 (Server-only re-release)
CRM 2013 Service Pack
CRM 2013 Service Pack 1 Update Rollup #
Go to Top
Microsoft Dynamics CRM 2011
Keep in mind that Mainstream Support for Microsoft Dynamics CRM 2011 ends July 12th, 2016 as per CRM 2011’s supported lifecycle.
CRM 2011 pre-release builds
CRM 2011 UR #
5.0.9688.1155, 5.0.9688.1157 (server)
Was not released to Microsoft Update
5.0.9690.1992 (contains the Q4 2011 Service Release and provides limited SQL 2012 support)
Not released publically
10/15/2012 (client), 10/22/2012 (server)
5.0.9690.2838 (Client), 5.0.9690.2839 (Server)
11 Critical Update
5.0.9690.2903 (Client, Server, MUI),
1/6/2013 (except for Server)
5.0.9690.3233 (Client), 5.0.9690.3236 (Server)
5.0.9690.3731, 5.0.9690.3739 (V2 - Outlook Client only re-release)
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.
For more information, see the blog posting "User experience while accessing CRM 2011 application servers while Update Rollups are being applied"
Silent Update Rollup installs: Please review Jon Strand's blog posting "CRM 2011: Silently Installing Update Rollups" which provides details on installing CRM Outlook client update rollups "silently" in order to limit end-user interruption
See also: Customers' choices... The most popular "Dynamics CRM in the Field" technical blog posts from Premier Field Engineering!
Greg NicholsSenior Premier Field EngineerMicrosoft Corporation
Awesome, wonderful, great information!
Thank u,Greg.I'm always follow rollups here.
this is great :) thanks
Thanks for sharing this- and providing a central location to keep up with it - much appreciated!
Someone should get this info in the TechNet wiki
I have spotted on the Rollup 6 download page that the version number has been increased to build number 05.00.9690.1992 with a Date Published of 20th January 2012, so a newer version of Rollup 6 has now been released.
I am now on the hunt as to whether we have to restore our live system back to the point that we first installed Rollup 6 with build number of 5.0.9688.1985, or if we just reapply the newly released 05.00.9690.1992 build.
@Scott Jackson - see my comments above. You can simply install the new build 1992 packages "over the top" unless you have installed any of the "UR6 slipstreamed" full product installs that were made available on 1/12. If you did, see my comments + KB 2668504
Can you include the release names? for example R7 was in UR5 and Q2 will be in UR8.
Greg - You totally rock! I the know field folks appreciate this knowledge sharing which is extremely helpful to our customers.
We have CRM Server 2011 installed on our production environment for Marketing team. Currently we have installation like RU 5 with Build .1985
So if I need to update RU 6 on it I can do it straight away.
My question is like if I want to update RU 7 + on that installation do I need to uninstall CRM and reinstall new build .1992?
Is there any another way to tackle this? What if we dont want this reinstallation process?
Thanks in Advance!
@Pradeep - you absolutely do not need to uninstall CRM and reinstall new build .1992, which is Update Rollup 6. You can install UR7 "on top" of UR6 and, as UR6 is the new baseline, UR7 can be uninstalled. In fact, if you try to install UR7+ on a pre-UR6 deployment (for example, UR5), the installer will not let you, it will say that UR6 (KB 2600640) must be installed first.
Good idea. Done. Thanks for the suggestions, keep them coming! Actually, the Q2 2012 Service Release is scheduled to be released via UR9, not UR8. Just FYI.