We're proud to announce that all packages for Microsoft Dynamics CRM 2011 Update Rollup 13 were released on Wednesday, March 27th, 2013 to the Microsoft Download Center! We plan on releasing the Update Rollup 13 packages to Microsoft Update in April, 2013.
Update Rollup 13 Build number:
Update Rollup 13 Microsoft Download Center page
Here's the "Master" Microsoft Dynamics Knowledge Base article for Update Rollup 13: (KB 2791312). Going forward, the plan is for the Master Knowledge Base article for CRM 2011 Update Rollups to be published a bit in advance of release to aid planning.
On Wednesday, Mar. 27th 2013 Greg Nichols and Ryan Anderson from the Microsoft Premier Field Engineering team provided information about:
at 11 AM Pacific time on BlogTalkRadio during their Microsoft Dynamics CRM 2011 Update Rollup 13 Podcast.
Note regarding Podcasts: You can make our CRM Premier Field Engineering podcasts available on Zune by using the RSS feed below. In the Zune software, go to Collection -> Podcasts and click on the Add a Podcast button on the lower left, then enter the url for the RSS feed: http://www.blogtalkradio.com/pfedynamics.rss. After that, you can adjust the series settings like any other podcast, so you can sync with your smartphone or Zune.
The "CRM Update Rollup Collateral Page"
For pointers to download locations, release dates, build information, and CRM Premier Field Engineering blogs and podcasts for all Microsoft Dynamics CRM Update Rollups, visit the "CRM Update Rollup Collateral Page"
Update Rollup 13 news!
Unlike some earlier Update Rollup releases like Update Rollup 6 and 12, Update Rollup 13 does not add major functionality changes. It is a collection of fixes for issues reported by customers or found by Microsoft's Engineering Team, plus changes to provide support for related technology components. So, we're pleased to announce that the Microsoft Dynamics CRM Compatibility List now indicates that Update Rollup 13 provides support for:
Note: to install Microsoft Dynamics CRM on a server running Windows Server 2012, you must install the Update Rollup 13 SHS (Self-Healing Setup) package hosted on the Microsoft Update site when you are prompted to "update install files" during CRM setup. That release to Microsoft Update is tentatively scheduled for April 9th, 2013. This SHS package is also needed for upgrading a Windows Server to Windows Server 2013 when CRM 2011 is already installed. For more details on the last scenario, see:
How to upgrade a Microsoft Dynamics CRM Server application to Windows Server 2012
Update Rollup 12 news that you need to know because Update Rollups are cumulative, so these significant changes are also in Update Rollup 13!
For Microsoft Dynamics CRM business solutions that include an entity with a large dataset, record retrieval and grid rendering performance can be negatively impacted for users that do not have global access to all records associated with that entity. Code changes to mitigate this behavior first appeared in Microsoft Dynamics CRM 4.0, and have been fine-tuned since then.
With Microsoft Dynamics CRM 2011 Update Rollup 10 and later, big advancements have been made to optimize the performance of queries against large datasets by adjusting specific “statistical” settings to address the issue. Should this fail to achieve desired levels of performance, adjust the value associated with EnableRetrieveMultipleOptimization (ERMO) setting. You may have heard these changes described at this year's Convergence.
A first step in efforts to optimize the performance of queries against large data sets is to make adjustments to the “statistical” settings that affect the behavior of RetrieveMultiple queries. Although you can configure these settings by modifying the Windows Registry (under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM) on the each of the Web servers that is used in a deployment, we recommend that these settings be configured by using the OrgDbOrgSettings, which will ensure that the configuration applies to a specific organization. For additional information about configuring these settings by using the OrgDbOrgSettings, and to download the tool that makes the OrgDbOrgSettings changes you desire, see the Microsoft Knowledge Base article titled "OrgDBOrgSettings Tool for Microsoft Dynamics CRM 2011" (KB 2691237)
If making adjustments to these settings does not yield satisfactory levels of performance, then consider adjusting the value of the EnableRetrieveMultipleOptimization (ERMO) setting. The ERMO setting is commonly used to limit the duration of certain long running queries; specifically, to overcome issues related to local or deep business unit access within Microsoft Dynamics CRM 2011 security roles.
Many more details describing appropriate scenarios for the available settings are already available via the Microsoft Download Center in a revised version of the whitepaper "Optimizing and Maintaining the Performance of a Microsoft Dynamics CRM 2011 Server Infrastructure", in the sections “Optimizing the Performance of Queries against Large Datasets” and “Optimizing the Performance of Quick Find Queries”. The details will appear in the MSDN version of this whitepaper as quickly as possible.
Outlook Client Updates:
Data Management Enhancements to:
For more information about the Dynamics CRM Q4 2011 Service Update features, consult:
Packages will be available for download via:
for these CRM components:
NOTE: On Jan. 20th, 2012 these installation files were updated to include CRM 2011 Update Rollup 6 (Build 05.00.9690.1992)
Microsoft Dynamics CRM 2011 Update Rollup 13 Prerequisites:
Note regarding Microsoft Dynamics CRM Stack Technology Compatibility:
Do you want to know if certain Service Packs or versions of a Microsoft product 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 article to determine the latest Microsoft SQL Server major version and Service Pack that is supported. Microsoft lists new products like Internet Explorer 10, Microsoft Windows 8, and Microsoft Office 2013 Preview as TBD until testing is complete; generally near General Availability (GA) of that product.
Issues resolved via Microsoft Dynamics CRM 2011 Update Rollups:
Microsoft Dynamics CRM 2011 Update Rollup 13 is the twelfth (considering that Update Rollup 9 was not released publicly) of a series of cumulative Update Rollups that include fixes for the issues that are or will be documented in the "Master Knowledge Base Articles" for CRM 2011 Update Rollups. As they are cumulative, Update Rollup 13 contains all fixes shipped via Update Rollups 1-13, including fixes that were never publicly released via Update Rollup 9.
Hotfixes and updates that were released as individual fixes before Update Rollup 13 release:
The following issues were fixed and delivered to requesting customers prior to Update Rollup 13 release as Critical On Demand (COD) fixes and are included in Update Rollup 13:
Other fixes released via CRM 2011 Update Rollup 13:
Hotfixes and updates that you have to enable or configure manually
Occasionally, updates released via Update Rollups require manual configuration to enable them. Microsoft Dynamics CRM Update Rollups are always cumulative; for example, Update Rollup 13 contains all fixes previously released via Update Rollups 1-12 as well as fixes newly released via Update Rollup 13. So if you install Update Rollup 13 on a machine upon which you previously installed no Update Rollups, you will need to manually enable any desired fixes for Update Rollups 1-13:
Mismatched Update Rollup versions within a Microsoft Dynamics CRM deployment
In a scenario where you may be running many client workstations with Microsoft Dynamics CRM 2011 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 Server but the Outlook clients are still on Update Rollup 1, or where Update Rollup 1 is on the CRM 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, and we recommend that you avoid deltas of more than one version between client and server. So ideally, you would be running Update Rollup 13 server with Update Rollup 12 or 13 on your Outlook client. 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 Email Router or Microsoft Dynamics CRM 2011 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"
Internet Explorer 10, Windows 8, Office 2013, and Windows Server 2012 Compatibility
The Microsoft Dynamics CRM Engineering team consistently Microsoft Dynamics CRM 2011 against pre-release and release versions of technology stack components that Microsoft Dynamics interoperates with. When appropriate, Microsoft releases enhancements via future Microsoft Dynamics CRM 2011 Update Rollups or new major version releases to assure compatibility with future releases of these products.
Greg Nichols Premier Field Engineering Microsoft Corporation
Can you please clarify the following statement (it needs to be rewritten if it doesn't say what it really means)
So, we're pleased to announce that the Microsoft Dynamics CRM Compatibility List now indicates that Update Rollup 13 provides support for:
•Windows Server 2012
◦Both new installs of CRM 2011 on a Windows Server 2012 and upgrading a Windows server to Windows Server 2012 require
•Active Directory Federation Services (AD FS) 2.1
◦Windows Server role used by CRM 2011 as a security provider for claims-based authentication
Does this mean ADFS 2.1 for IFD implementation of does it it mean all CRM 2011 installations on Server 2012 will requires ADFS to be set and hence IFD ??
Hi, Pete. Yes, it just means AD FS 2.1 is compatible with CRM 2011 + Update Rollup 13, so new IFDs being set up for claims-based authentication with AD FS and Windows Server 2012 will work, as well as existing IFDs on Server 2008 (with AD FS 2.0) when the CRM server is upgraded to Windows Server 2012, which upgrades you to AD FS 2.1.
@Pete - to answer your question directly, no - not all CRM 2011 installations will need AD FS; only those that you need to be internet facing. If you're on-premise intranet, we use AD as before for authentication.
Thanks - I was assuming that but just confirming
Is the above statement really saying that you install rollup 13 on server 2012 do we need to ADFS 2.1 if you want IFD
Pete - I'm saying that you can use AD FS 2.1 to set up a new IFD if you use AD FS to be the security provider for claims-based authentication. Most customers, IMO, use AD FS because there's very complete documentation on how to configure it when setting up an IFD and it is an in-the-box Server Role for Windows Server 2008 and now Windows Server 2012. However, from: technet.microsoft.com/.../gg188610.aspx:
"Claims-based authentication <in CRM 2011> is built on Windows Identity Foundation (WIF), a framework for building claims-aware applications and security token service (STS) that is standards-based and interoperable. Interoperability is provided through reliance on industry standard protocols such as WS-Federation, WS-Trust, and Security Assertion Markup Language 1.1 (SAML)"
So other security providers can be used besides AD FS - what is required for a CRM 2011 IFD is claims-based authentication, usually but not necessarily provided by a supported AD FS version. Other providers can be used but they need to support WS-Federation, WS-Trust, and SAML 1.1
i am new to Dynamics CRM, just want to know. If i click on Product Updates under Administration.
what will be the effect? will it remove the configuration and the content data or simply update the CRM features.
Appreciate if anybody worked on that could share their experiences.
Thanks in advance,