The Dynamics CRM product group has released a Critical Update for Microsoft Dynamics CRM 2011 Outlook Client and CRM Server. Both the server and client updates are targeted to users who are constrained to Update Rollup 11 for Microsoft Dynamics CRM so that they can take advantage of the changes that are provided by this critical update release.
This Critical Update provides in a single package all previously released Critical On Demand (COD) fixes that were delivered for Update Rollup 11.
All users who are currently running Update Rollup 11 on the CRM server should apply this server-side Critical Update. Users who are running CRM Server Update Rollup 12, 13, or 14 do not require this critical update. These users do not have to downgrade their CRM Server installation to Update Rollup 11 because all fixes are incorporated in Update Rollup 12, 13, and 14.
Important After you apply this Critical Update to the CRM server, you should not apply Update Rollup 12, 13, or 14 on top of this Critical Update. You will have to wait until Update Rollup 15.
To deploy the client-side Critical Update if the CRM for Outlook Client Update Rollup 12, 13, or 14 is currently deployed, you must completely uninstall the existing CRM for Outlook Client, reinstall the CRM Outlook Client, and then apply the Client side Critical Update.
If the currently installed CRM for Outlook Client is Update Rollup 11 or earlier, you can install the client-side Critical Update without uninstalling the existing client.
Additionally, we recommend that you disable automatic updates for Dynamics CRM on the client computer. This ensures that only the binaries that are deployed by the Client side Critical Update get installed and that nothing from Windows Update gets integrated into the client installation.
Note You do not have to change the CRM Server version to use this client-side Critical Update. This client-side Critical Update works together with CRM Server running Update Rollup 11, 12, 13, and 14. However, if CRM Server is running any Update Rollup version that is earlier than Update Rollup 11, you must apply Update Rollup 11 to the CRM server in order for the CRM for Outlook Client Critical Update installation to be compatible.
This Critical Update is available for all languages that are supported by Microsoft Dynamics CRM 2011.
Important After you apply this Critical Update to CRM for Outlook Client, you should not apply Update Rollup 12, 13, or 14 on top of this Critical Update. You will have to wait until Update Rollup 15.
Critical Update features
Microsoft Dynamics CRM Server
The Microsoft Dynamics CRM 2011 Update Rollup 11 Critical Update for CRM Server is intended specifically for customers who cannot upgrade their Dynamics CRM Server installation past Update Rollup 11 for compatibility reasons, such as unsupported Javascript customizations.This Critical Update provides in a single package all previously released Critical On Demand (COD) fixes that were delivered for Update Rollup 11.
All users who are currently running Update Rollup 11 on the CRM server should apply this server-side Critical Update. Users who are running CRM Server Update Rollup 12, 13, or 14 do not require this critical update. These users do not have to downgrade their CRM Server installation to Update Rollup 11 because all fixes are incorporated in Update Rollup 12, 13, and 14.
Important After you apply this Critical Update to the CRM server, you should not apply Update Rollup 12, 13, or 14 on top of this Critical Update. You will have to wait until Update Rollup 15.
Microsoft Dynamics CRM for Outlook Client
The Microsoft Dynamics CRM 2011 Update Rollup 11 Critical Update for CRM for Outlook Client includes all previously issued COD stability fixes and customer requests from Update Rollup 11, 12, 13, and 14.To deploy the client-side Critical Update if the CRM for Outlook Client Update Rollup 12, 13, or 14 is currently deployed, you must completely uninstall the existing CRM for Outlook Client, reinstall the CRM Outlook Client, and then apply the Client side Critical Update.
If the currently installed CRM for Outlook Client is Update Rollup 11 or earlier, you can install the client-side Critical Update without uninstalling the existing client.
Additionally, we recommend that you disable automatic updates for Dynamics CRM on the client computer. This ensures that only the binaries that are deployed by the Client side Critical Update get installed and that nothing from Windows Update gets integrated into the client installation.
Note You do not have to change the CRM Server version to use this client-side Critical Update. This client-side Critical Update works together with CRM Server running Update Rollup 11, 12, 13, and 14. However, if CRM Server is running any Update Rollup version that is earlier than Update Rollup 11, you must apply Update Rollup 11 to the CRM server in order for the CRM for Outlook Client Critical Update installation to be compatible.
This Critical Update is available for all languages that are supported by Microsoft Dynamics CRM 2011.
Important After you apply this Critical Update to CRM for Outlook Client, you should not apply Update Rollup 12, 13, or 14 on top of this Critical Update. You will have to wait until Update Rollup 15.
CRM for Outlook Client improvements
The following are some of the improvements that this Critical Update provides for CRM for Outlook Client:- It includes a new feature that is scheduled to be delivered with Microsoft Dynamics CRM 2013. This feature moves the CRM client-specific workload into its own process so that it no longer shares memory with the Microsoft Office Outlook process. This feature is also known as Process Isolation.
- It includes an upgrade to Microsoft SQL Server for Windows CE 4.0 for better memory management, better caching, and connection enhancements.
- It updates the CRM for Outlook configuration files to make the CRM for Outlook SDF files compatible with SQL Server for Windows CE 4.0.
- It materializes the Address Book Provider to reduce performance issues that are caused by large address books.
- It limits the amount of active open forms.
- It provides a MAPI Lock time-out.
- It hard codes a previous registry setting that prevented pinned views from pulling down information to local SQL CE cache. This new DisableMapiCaching setting defaults to a value of 1. For more information about the behavior of this setting, see Slow Performance When Pinning Views in Microsoft Dynamics CRM.
This value can be overridden by modifying the DisableMapiCaching setting in the OrgDbOrgSettings tool if the Critical Update has been applied to the Dynamics CRM Server. For more information, see OrgDBOrgSettings Tool for Microsoft Dynamics CRM 2011.