Comment unsuccessful. Please correct the errors below.

Update Rollup 2 and groundhog day conspiracy

Not so long Microsoft has released Update Rollup 2. Some fixes were just too tempting to pass on so we duly deployed the rollup on the server. Some strange message about failure to update a report (which it did not actually try to update) aside, it all went well and, thanks to AutoUpdate feature, deploying update to the Outlook client was going to be a snap, according to the Implementation Guide and Eric Newell.

We followed this instructions and, indeed, Outlook prompted and successfully updated itself, as advertised. Just to make sure, we tried CRM->Check for Updates command and, to our surprise, Outlook decided to download and install the update again. In fact, it decided to prompt us every time it started. Which turned out to be not only extremely annoying but made it plain impossible to run Outlook client on Terminal Server as normal users do not have administrative privileges to run any update.

To cut the long story short, PatchID {9EA7FDEB-9D7E-4278-8CD1-94ACEFA40D3F} mentioned in the instructions turned out to be incorrect and the correct ID is {84EBD2D4-7530-47DA-B7C5-72E4F4FA5AE5}. However, simply changing patch ID after the fact would not work as we still need to remove erroneous ID first using <Delete> “instruction”. The correct configuration XML is as following:


<ClientPatches>
   <Create>
      <!-- *** UR2 PATCH -->
      <ClientPatchInfo>
         <PatchId>{84EBD2D4-7530-47DA-B7C5-72E4F4FA5AE5}</PatchId>
         <Title>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419) Jan-09</Title>
         <Description>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419) Jan-09</Description>
         <!-- *** This will teach users! -->
         <IsMandatory>true</IsMandatory>
         <IsEnabled>true</IsEnabled>
         <ClientType>OutlookLaptop, OutlookDesktop</ClientType>
         <LinkId>140023</LinkId>
      </ClientPatchInfo>
   </Create>
   <Delete>
      <PatchId>{9EA7FDEB-9D7E-4278-8CD1-94ACEFA40D3F}</PatchId>
   </Delete>
</ClientPatches>

Tried both default Url (to download update from Microsoft site using numeric LinkId) and custom AutoUpdateUrl (to download update from the custom location using file name as LinkId), both work fine.

Note: unlike Rollup 1, files in Update Rollup 2 are language-specific meaning that PatchId and LinkId would need to be changed for languages other than English. PatchId for Spanish version, for example, is  {A090EBC0-F3EC-414F-9E0A-02DABFB07618}. At this point in time I have no idea how to find correct LinkId, the workaround is to use custom download URL as documented here.

By the way, Groundhog Day and Update Rollup 2 release are both in February. Coincidence? I don’t think so.

 

Posted by: George Doubinski
Last revised: 05 Dec, 2012 05:25 PM

Comments

Your Comments

Comment unsuccessful. Please correct the errors below.
Used for your gravatar. Not required. Will not be public.
Posting code? Indent it by four spaces to make it look nice. Learn more about Markdown.

Preview