CRM 4.0 Update Rollup 3 Considerations

On Friday we posted about Microsoft Dynamics CRM 4.0 Update Rollup 3.  I thought it would be helpful to post some further details about it, and some recommendations that really apply to any update rollup.

The best advice is to read the knowledge base article prior to downloading and installing the update.  The knowledge base article contains details about what fixes are included.  Also worth noting is that there is an ever growing list of fixes included in the hotfixes that need to be manually applied with a registry change after the update is installed.

The reason that some fixes are applied automatically while others are hidden in a registry change has to do with whether the fix is a bug fix or if it is a change in the application design.  Bug fixes are automatically applied, while design changes require a registry change so users who like the old design are not forced to change.

Here is the list of changes with rollup 3 that have to be enabled or configured manually:

955452 (http://support.microsoft.com/kb/955452/ ) Line feeds are not used when you send an e-mail message that uses an e-mail template to render data that has line feeds in Microsoft Dynamics CRM 4.0

955745 (http://support.microsoft.com/kb/955745/ ) Error message when you try to configure the Microsoft Dynamics CRM 4.0 client for Outlook: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms"

956527 (http://support.microsoft.com/kb/956527/ ) The Microsoft Dynamics CRM client for Outlook consumes three times as much memory in version 4.0 as in version 3.0

959248 (http://support.microsoft.com/kb/959248/ ) Microsoft Dynamics CRM 4.0 slows to unacceptable levels when you process e-mail messages by using the Microsoft Dynamics CRM E-mail Router

957871 (http://support.microsoft.com/kb/957871/ ) The Workflow Expansion Task records cause the AsyncOperationBase table in the MSCRM database to grow too large in Microsoft Dynamics CRM 4.0

950175 (http://support.microsoft.com/kb/950175/ ) You cannot use Outlook as expected until all Microsoft Dynamics CRM 4.0 add-ins are loaded

953340 (http://support.microsoft.com/kb/953340/ ) E-mail messages from a CRM user to a queue are not delivered in Microsoft Dynamics CRM 4.0

958562 (http://support.microsoft.com/kb/958562/ ) The default precision of a money field is set to two when you use the Korean language or the Japanese language in Microsoft Dynamics CRM 4.0

955138 (http://support.microsoft.com/kb/955138/ ) You experience slow performance or timeouts when you try to access some views in Microsoft Dynamics CRM 4.0

956330 (http://support.microsoft.com/kb/956330/ ) Slow performance and high CPU utilization occur when you import customizations in Microsoft Dynamics CRM 4.0

968515 (http://support.microsoft.com/kb/968515/ ) The existing custom security roles are not granted hidden privileges after you apply hotfix 950886 in Microsoft Dynamics CRM 4.0

958601 (http://support.microsoft.com/kb/958601/ ) In Microsoft Dynamics CRM 4.0, the notes are lost if a duplicate record is detected when you try to save a record

968672 (http://support.microsoft.com/kb/968672/ ) The recipient does not see the Microsoft Dynamics CRM tracked e-mail icon when a Microsoft Dynamics CRM user sends another Microsoft Dynamics CRM user a Microsoft Dynamics CRM tracked e-mail message

968755 (http://support.microsoft.com/kb/968755/ ) The AsyncOperationBase and WorkflowLogBase tables grow very large and performance issues occur when you use many workflows in Microsoft Dynamics CRM 4.0

Additional considerations:

• It's ok to skip a rollup if you are not experiencing any of the issues addressed by the update
• Rollups are cumulative--update rollup 3 inculdes the fixes from rollup 1 and rollup 2, so if you install new clients, you only need to install rollup 3.
• If you have previously published rollup 1 or rollup 2 via auto updates, and you now are publishing rollup 3, you can remove rollup 1 and rollup 2 from autoupdates by using the <Delete> element in your update xml file, so new client installs will not be forced to download rollup 1 and rollup 2.  For example:

<ClientPatches>

<Delete>

<PatchId>{FB10E341-BAB3-4687-A719-1AC1BF43EC92}</PatchId>

</Delete>

</ClientPatches>

• If you install an update rollup, you need to also update the clients, router, and the dmm to keep all of your components in parity.

Technorati Tags: Microsoft Dynamics CRM,Microsoft CRM,Update,Rollup 3

Comments

[Regan]

So far i have encountered some problems with rollup 3. On importing a database if you map users and then attempt to change the user account after import it fails

Creating a user in the crm from another linked domain does not work anymore. In prev versions you could simply add a user and type in OTHERDOMAIN\Username and it would allow you to add the user, and the user could log in. Now i just get "an error has occurred" when attemnpting to save the user record.

At least I can actually import organisations now though... i never managed to successfully import one using HFRU2!

[Joel Lindstrom]

Thanks for sharing your feedback, Regan,

On your issue with adding a user, is the user's credentials in the domain that CRM is installed in, or is it a different domain with a trust to the crm domain? I have seen this issue in some cases without rollup 3, especially when adding users from a trusted domain.

The issue where I saw it was that CRM could not add the users to the crm user group in active directory.

The solution was to go into AD users and computers and add the user to the User group, then I could successfully save the user.