Smiti Shah Published Tuesday, January 20, 2009 8:11 AM
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..
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 Update Rollup 2 for 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.
- Check for Updates and start the install. While that is running, choose Exit from Outlook’s File menu to close down Outlook. This will avoid any “File in use” errors. If you do get the error, you were probably a little slow in shutting down Outlook. You can click-on “Retry” once Outlook and the CRM hoster process have completed their shutdowns.
- Restart Outlook after the patch is installed.
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 1.
Note: These are steps 5, 6 and 7 of Eric’s blog.
1. Create the configuration XML file and save it.
<ClientPatches>
<Create>
<!--- *** UR2 PATCH -->
<ClientPatchInfo>
<PatchId>{9EA7FDEB-9D7E-4278-8CD1-94ACEFA40D3F }</PatchId>
<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 -->
<IsMandatory>true</IsMandatory>
<IsEnabled>true</IsEnabled>
<ClientType>OutlookLaptop, OutlookDesktop</ClientType>
<LinkId>140023</LinkId>
</ClientPatchInfo>
</Create>
</ClientPatches>
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.
Smiti Shah