Microsoft Dynamics CRM Team Blog: Update Rollup 3 for Microsoft Dynamics CRM 4.0

[Blog bot]

Источник: http://blogs.msdn.com/crm/archive/20...s-crm-4-0.aspx
==============

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup 3 on Thursday, March 12, 2009.

Below are the links to the release and related information about the Rollup. Please see the Knowledge Base (KB) article for more details about the Update Rollup 3 content and instructions.

• Microsoft Download Center: http://www.microsoft.com/downloads/d...playlang=en&tm
• Microsoft Knowledge Base Article: http://support.microsoft.com/kb/961768

Install Details about Update Rollup 3

• Update Rollup 1 and Update Rollup 2 are not prerequisites for installing Update Rollup 3
• The Update Rollup 3 client can be deployed before the server is upgraded to Update Rollup 3
• Update Rollup 3 can be uninstalled
• Incorporated installer feedback on Update Rollup 2, so now we don’t over write your modified web.config file. See http://support.microsoft.com/kb/968793 for details.

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 3 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/20...utoupdate.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 3.

Note: These are steps 5, 6 and 7 of Eric’s blog.

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.

  

     

       



          {8B092580-482E-4EE3-98B1-28FB589B3012}

          Update Rollup 3 for Microsoft Dynamics CRM 4.0 (KB 961768)

          Update Rollup 3 for Microsoft Dynamics CRM 4.0 (KB 961768)

         

          true

          true

          OutlookLaptop, OutlookDesktop





          145425&clcid=0x409

     

  

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 3 for Microsoft Dynamics CRM 4.0 (KB 961768)” is available. If the 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.

Link and Patch IDs for Update Rollup 3:

Arabic

LinkID: 145425&clcid=0x401

PatchID: {E7CEBD6B-0E64-4130-B85D-F3A6E140B70B}

Chinese (Simplified)

LinkID: 145425&clcid=0x804

PatchID: {F60413F2-ECE0-4CD0-8925-09FC20623FFD}

Chinese (Hong Kong)

LinkID: 145425&clcid=0xc04

PatchID: {DC9B0ECB-CEF9-48E4-846E-384BFB993166}

Chinese (Traditional)

LinkID: 145425&clcid=0x404

PatchID: {E80BD416-07D3-4EDD-B81B-63C5C82B5671}

Czech

LinkID: 145425&clcid=0x405

PatchID: {09F81FB4-4369-41E9-B62F-08A1D7A2A40D}

Danish

LinkID: 145425&clcid=0x406

PatchID: {EA701D64-67B6-4E81-943E-AA1B803FB961}

Dutch

LinkID: 145425&clcid=0x413

PatchID: {B60D0F28-6B7E-4B79-AF12-DAD12F5820AD}

English

LinkID: 145425&clcid=0x409

PatchID: {8B092580-482E-4EE3-98B1-28FB589B3012}

Finish

LinkID: 145425&clcid=0x40b

PatchID: {A4C13D7F-75F1-42CC-BA98-CD42A135554F}

French

LinkID: 145425&clcid=0x40c

PatchID: {ACDAF77D-0D53-4390-A547-174B66FC51EA}

German

LinkID: 145425&clcid=0x407

PatchID: {0A59EBEC-0870-409A-B751-713CEDF9B59F}

Greek

LinkID: 145425&clcid=0x408

PatchID: {70BD553C-0AC9-40F7-A72F-6EC96D95DD86}

Hebrew

LinkID: 145425&clcid=0x40d

PatchID: {05F2A180-E338-4FB3-B48A-4C06737E5365}

Hungarian

LinkID: 145425&clcid=0x40e

PatchID: {19CA36A3-3A60-484F-AFF1-3C56347A07A7}

Italian

LinkID: 145425&clcid=0x410

PatchID: {7C2556F1-285C-4470-A473-3C6334F36C5A}

Japanese

LinkID: 145425&clcid=0x411

PatchID: {633DE31B-158A-4923-8B27-B3825626E567}

Korean

LinkID: 145425&clcid=0x412

PatchID: {8A3A317B-0780-44AC-8023-37BCFDF3FDF2}

Norwegian

LinkID: 145425&clcid=0x414

PatchID: {824DC47E-7BF1-48BF-A29C-160702D5D02F}

Polish

LinkID: 145425&clcid=0x415

PatchID: {A6012D95-B878-41F3-A27E-40F753CCC0B9}

Portuguese (Brazil)

LinkID: 145425&clcid=0x416

PatchID: {6E78D992-34E4-4B97-94AF-FE60C923EB00}

Portuguese (Portugal)

LinkID: 145425&clcid=0x816

PatchID: {C0956419-3589-4E4C-BE3B-089E63CDD213}

Russian

LinkID: 145425&clcid=0x419

PatchID: {2AC4EAC6-B1E0-453B-A038-F01FBCCEB74E}

Spanish

LinkID: 145425&clcid=0xc0a

PatchID: {57C540B7-1D7C-4B7D-BB93-36F1991483B2}

Swedish

LinkID: 145425&clcid=0x41d

PatchID: {27563C10-CE6C-4028-B44E-9A5003BD95E2}

Turkish

LinkID: 145425&clcid=0x41f

PatchID: {755633BF-DE12-47A5-AD87-9265C6CA317F}

Cheers,



Matt Brown



Источник: http://blogs.msdn.com/crm/archive/20...s-crm-4-0.aspx