We're delighted to announce that Microsoft Dynamics CRM 4.0 Update Rollup 20 released Thursday November 10th,2011!
Note regarding Podcast: Microsoft Dynamics CRM 4.0 Update Rollup 20 was discussed during the CRM 2011 Update Rollup 5 Podcast delivered on October 26th, 2011.
Related links you should know about:
Packages are available for download via the Update Rollup 20 Microsoft Download Center page for these CRM components:
Microsoft Dynamics CRM 4.0 Update Rollup 20 Prerequisites:
Microsoft Dynamics CRM 4.0 Update Rollup 11 (and beyond) Prerequisites:
Issues resolved via Microsoft Dynamics CRM 4.0 Update Rollup 20:
Microsoft Dynamics CRM 4.0 Update Rollup 20 is a cumulative Update Rollup that includes all the fixes for the issues that are documented in the "Master Knowledge Base Articles" for Update Rollups 1 through 20.
Hotfixes and updates that were released as individual fixes:
Update Rollup 20 for Microsoft Dynamics CRM 4.0 contains no updates that were released as individual fixes.
Other fixes released via CRM 4.0 Update Rollup 20:
Hotfixes and updates that you have to enable or configure manually
Update Rollup 20 for Microsoft Dynamics CRM 4.0 contains one update that you must enable or configure manually:
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 4.0 for Microsoft Office Outlook, a common question is whether it is supported to run mismatched versions. For example, where Update Rollup 20 has been installed on the CRM Server but the Outlook clients are still on Update Rollup 15, or where Update Rollup 10 is on the CRM server but due to updates available to the Outlook client you have decided to install Update Rollup 20 on the clients without installing Update Rollup 20 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.
Internet Explorer 9 Compatibility
The Microsoft Dynamics CRM Sustained Engineering team extensively tested Microsoft Dynamics CRM 4.0 against pre-release versions of Internet Explorer 9 and continue to address compatibility issues, as they're reported, against the released (Released to Web) version of Internet Explorer 9.0. If necessary, they plan to release enhancements via future Microsoft Dynamics CRM 4.0 Update Rollup releases to assure compatibility with Internet Explorer 9.
Greg NicholsPremier Field EngineeringMicrosoft Corporation
I wanted to report that an Microsoft CRM 2011 Client for Microsoft Outlook issue has surfaced, and the Update Rollup 6 packages for Client and Server are being temporarily removed from the Microsoft Download Center this morning pending our investigation. Please hold off on downloading Update Rollup 6 until new packages are available.
If you have downloaded UR6 packages for any components, please discard them and wait for an update on our investigation and the release of new packages. If you have installed them, please note that the issue appears to be related to Outlook Client sync and prepare to install a newer build when it is available.
We applied Rollup 20 for a client with CRM 4 in order to fix the issue mentioned above: Email messages are sent with unexpected characters in the subject header when you use CRM 4.0 email router. Therefore, the email messages may be caught by the spam filters.
The rollup did not fix the issue - there was no change in the subject header at all.
The client doesn't use the Outlook cilent or language packs so we only installed the Server and SSRS portions of the rollup. Do you think we need to install the Outlook component? Has only else had success issue using this rollup to solve that issue? What suggestions do you have to fix the issue?