NEW UPDATE as of 10/22: Please note!
UR11 Outlook Client packages: The Update Rollup 11 installer packages for the CRM 2011 Client for Microsoft Office Outlook (build 5.0.9690.2835) were removed from the Microsoft Download Center temporarily and replaced on Wednesday Oct. 17th with a new build: 5.0.9690.2838. The reason for the re-release was an issue being reported when the client was running on Windows XP, where a user may see Watson errors when clicking on entities.
If you have already installed the original 5.0.9690.2835 Client build and you are not running Windows XP, there is no need to update to the new packages.
Build 5.0.9690.2838 (Outlook Client) as well as all other packages except Server were released to the Microsoft Update site Tuesday 10/23 around 10:30 AM Pacific time.
UR11 Server packages:
The UR11 server packages were reposted on the Download Center on 10/23/2012 to resolve the duplicate key error when importing solutions. The duplicate key fix is the only addition to the Re-released (v2) server packages. You only need to install V2 if you are experiencing the issue, i.e. cannot import your customizations.
We're proud to announce that Microsoft Dynamics CRM 2011 Update Rollup 11 was released on Thursday, October 11th, 2012 to the Microsoft Download Center! The release of Update Rollup 11 to Microsoft Update is still planned for October 23rd, 2012.
Here's the "Master" Microsoft Dynamics Knowledge Base article: (KB 2739504). Going forward, the plan is for the Master Knowledge Base article to be published a bit in advance of release to help your release planning.
On Friday, October 12th at Greg Nichols and Ryan Anderson from the Microsoft Premier Field Engineering team provided information about:
at 9 AM Pacific time on BlogTalkRadio during their Microsoft Dynamics CRM 2011 Update Rollup 11 Podcast.
Big Update Rollup 11 news!
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.
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.
Update Rollup 11 Build number: 5.0.9690.2835
Notes: You will be able to uninstall Update Rollup 11, unlike Update Rollups 4-6 which could not be uninstalled. However, you should always back up your databases and application servers before you install an Update Rollup.
Update Rollup 6 established a new servicing baseline. This will enable uninstalls of some future CRM 2011 Update Rollups, but this also means that Update Rollup 6 is prerequisite for installation of all future Microsoft CRM 2011 Update Rollups starting with Update Rollup 7.
A database created with Microsoft Dynamics CRM 2011 Update Rollup 6 or a higher version cannot be imported to a deployment of Microsoft Dynamics CRM 2011 Update Rollup 5 or an earlier version. This scenario is not supported. Best practice is to import databases or customizations between environments that are at the same Update Rollup level.
As Update Rollup 11 is cumulative, containing all changes released in earlier Update Rollup releases, it also contains the Dynamics CRM Q4 Service Update features released via Update Rollup 5. Some of these features include:
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: As of Jan. 20th, 2012 these installation files have been updated to include CRM 2011 Update Rollup 6 (Build 05.00.9690.1992)
Microsoft Dynamics CRM 2011 Update Rollup 11 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 11 is the eleventh (or tenth, 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 11 contains all fixes shipped via Update Rollups 1-11, including fixes that were never publicly released via Update Rollup 9.
Hotfixes and updates that were released as individual fixes before Update Rollup 11 release:
The following issues were fixed and delivered to requesting customers prior to Update Rollup 11 release as Critical On Demand (COD) fixes and are included in Update Rollup 11:
Other fixes released via CRM 2011 Update Rollup 11:
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 10 contains all fixes previously released via Update Rollups 1-9 as well as fixes newly released via Update Rollup 10. So if you install Update Rollup 10 on a machine upon which you previously installed no Update Rollups, you will need to manually enable any desired fixes for Update Rollups 1-10:
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. 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, and Office 2013 Preview Compatibility
The Microsoft Dynamics CRM Sustained Engineering team consistently Microsoft Dynamics CRM 2011 against pre-release and release versions of these products. When necessary, Microsoft plans to release enhancements via future Microsoft Dynamics CRM 2011 Update Rollups to assure compatibility with future releases of these products.
Greg Nichols Premier Field Engineering Microsoft Corporation
Many thanks. This is all good news but Rollup 10 is still not available on WSUS despite the earlier plan. Can you tell us if it would be better now to wait until Rollup 11 is released on WSUS?
I'd echo @MarkUnderhill comments as we need to see the client updates pushed onto WSUS on a schedule that is a public as the dates listed above as enterprises need to push their updates through WSUS, and not have to seperately package the Outlook RU updates and seperately manage them, Thanks
@Mark - Yes, we recommend waiting for UR11 (tentatively planned to be available tomorrow) as that is the next release that will be pushed to Microsoft Updates if you plan to leverage WSUS. UR11 is tentatively scheduled to be released to Microsoft Updates on 10\23\12.
@Scott - We can only provide tentative dates for the next update rollup as dates change often based on customer bugs accepted, time to resolution, testing, etc. Greg Nichols keeps this updated on his master Update Rollup KB - http://aka.ms/jwfeje
A heads up that the updaters do not like SQL connection strings for a SQL availability group. I can get around this by manually updating the connection strings to point at the active SQL node for all the orgs for now inside the database.
Example connection string: Server=tcp:CRMSQL,1433;Database=ORGNAME_CONFIG;Integrated Security=SSPI;MultiSubnetFailover=true;
13:43:22| Info| Database update install failed for orgId = 17b492aa-d0eb-e111-a695-00155d010cc1. Continuing with other orgs. Exception: Microsoft.Crm.CrmException: Metabase Connection string formatted incorrectly
at Microsoft.Crm.Setup.Database.DatabaseUtility.GetConnection(InstallDatabase database, Boolean disablePool)
at Microsoft.Crm.Setup.Database.DatabaseUtility.ExecuteScalar(InstallDatabase database, String sql, IDictionary`2 parameters, Int32 timeout)
at Microsoft.Crm.Setup.Database.DatabaseInstaller.set_Database(DatabaseUtility value)
at Microsoft.Crm.Setup.Database.DatabaseInstaller.Install(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase, Boolean isInstall)
at Microsoft.Crm.Setup.Database.DatabaseInstaller.InstallUpdate(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase)
What happened to the UR for the Outlook client? As of writing it isn't on the download page.
I was looking for update Rollup 11 for Outlook client and it is not availbe for dowanlod www.microsoft.com/.../details.aspx. Do you have any solid dates?
It seems UR 11 for Outlook Client was withdrawn from Download Center, because it has problems with Outlook on Windows XP. I guess it will be re-realeased just as UR 10 was.
@ Feridun / Michael_P / Jevgenij: see my comment at the top of this blog re: the Outlook Client re-release.
just update to update 11 and got
Version : 5.0.9690.2839(CRM Full Server) and DB server (SR) 5.0.9690.2835.
DB got updated via win update,
CRM Full server via CRM2011-Server-KB2739504-v2-ENU-amd64.exe as Win update only showed update 8.
Is this correct or should the SRS DB server also be 2839??
Well, the CRM Deployment Manager show this version numbers.
The CRM site/page under File > Help > About... shows both CRM and DB on 2839.
after RU11 the 404 issue still there..