On 2/8/2008, the CRM Sustained Engineering team released a new version of the Update Rollup 2 packages. The new version of Update Rollup 2 addresses some of the issues that have been noted in the comments for this blog entry.
Strings in the localized product showing up as garbage or in English.
Customized web.config causing issues after Update Rollup 2 is installed.
Customers do not need to uninstall the original Update Rollup 2 packages. The new packages will install over the top. If a customer has not been affected by the issues in the original Update Rollup 2 package they do not need to update to the new version. Customers can install Client, Server, Router Update Rollup 2 in any order.
The steps for the AutoUpdate have caused some confusion. There is a different PatchId and LinkId for every language of the product. You will find a table at the bottom of this post that has the PatchId and LinkId for each Language. Note: The new packages changed the PatchId so it will need to be updated, as the previous PatchId is no longer valid.
The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup 2 on Thursday, January 15, 2009.
Below is the link to the release and related information about the Rollup. Please see the Knowledge Base (KB) article for more details about the Update Rollup 2 content and instructions..
- Microsoft Download Center: http://www.microsoft.com/downloads/details.aspx?familyid=aa671769-61e9-45c4-919f-c88199aa4241&displaylang=en&tm
- Microsoft Knowledge Base Article: http://support.microsoft.com/kb/959419
Install Details about Update Rollup 2
- Update Rollup 1 is not a prerequisite for installing Update Rollup 2
- The Update Rollup 2 client can be deployed before the server is upgraded to Update Rollup 2
- Update Rollup 2 can be uninstalled
- Unlike Update Rollup 1, Update Rollup 2 is packaged so that each language is packaged individually. As a result, the download size of the packages for Update Rollup 2 is significantly smaller. For example, the CRM Server package size is reduced from about 171 MB in Update Rollup 1 to about 9 MB in Update Rollup 2. The Outlook Client package size is reduced from about 78 MB in Update Rollup 1 to about 4 MB in Update Rollup 2
How to avoid a required reboot when installing a patch for the CRM Outlook Client
- Before starting the update process, go to Options from the CRM menu. On the “General” tab, uncheck the bottom checkbox that says “Always run the…Host process” and then click “Ok” button.
- When manually checking for updates, go ahead and close Outlook by choosing Exit from Outlook’s File menu. This will close Outlook along with the CRM add-in and the Hoster process.
- Now check for updates by selecting All Programs from the Start menu. Then select Microsoft Dynamics CRM 4.0 and choose Update.
- Restart Outlook after the patch is installed.
Note: If the user doesn’t want to make the permanent change of always having the Hoster process exit when Outlook exits, they can close the Hoster process manually after Outlook has been closed by right clicking on the Dynamics icon in the Notification Area of the Task Bar.
Making Update Rollup 2 available to your clients via AutoUpdate:
You can find more information about AutoUpdate in Eric Newell’s blog entry at http://blogs.msdn.com/crm/archive/2008/05/08/crm-client-autoupdate.aspx and the Microsoft Dynamics CRM 4.0 Operating and Maintaining Guide, part of the Microsoft Dynamics CRM 4.0 Implementation Guide.
If you have a direct internet connection from your client machines, you can avoid some of the configuration steps and use the LinkId directly. Below are the necessary steps to configure the AutoUpdate for Update Rollup 2.
Note: These are steps 5, 6 and 7 of Eric’s blog.
*** 2/9/2008 Update ***
The steps below are for the English version of the product. The PatchId and LinkId values will be different for every localized version of CRM 4.0. There is a table at the bottom of this post that lists the correct PatchId and LinkId for each language.
1. Create the configuration XML file and save it.
<!— *** UR2 PATCH –>
<!— *** The PatchId is different for every Language. Please see the table at the end for correct Link ID to use –>
<Title>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)</Title>
<Description>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)</Description>
<!— *** This will make it Mandatory –>
<!— *** The LinkId is different for every Language. Please see the table at the end for correct Link ID to use –>
2. From the command prompt, go to the directory where the ClientPatchConfigurator.exe is located ([ServerInstallDir]\Tools and type microsoft.crm.tools.clientpatchconfigurator.exe [configfile].xml
3. Once the patch has been uploaded, launch the Outlook client
The dialog should now appear saying that “Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)” is available. If the <IsMandatory> is set to false, the client will only see the update if the user selects “Check for Updates” via the CRM Menu in the Outlook client.
*** 2/9/2008 Update ***
Chinese (Hong Kong)
LinkID: 140023&clcid=0x409 (or just 140023)
Keep your comments, experiences, and observations coming. We’re listening.