{"id":31,"date":"2012-12-27T09:05:07","date_gmt":"2012-12-27T15:05:07","guid":{"rendered":"https:\/\/sysadminnightmare.com\/?p=31"},"modified":"2012-12-27T09:05:07","modified_gmt":"2012-12-27T15:05:07","slug":"crm-rollup-and-patch-updates","status":"publish","type":"post","link":"https:\/\/sysadminnightmare.com\/index.php\/2012\/12\/27\/crm-rollup-and-patch-updates\/","title":{"rendered":"CRM Rollup and Patch Updates"},"content":{"rendered":"<p>After having to sit in the conference room for 4 days straight and participate in a &#8220;PC Pitstop&#8221; where users brought thier laptops in i began to think there has got to be an easier way to do some of this, which lead me on a google quest for:\u00a0AutoUpdate\u00a0CRM Server.<\/p>\n<p>Luckly I found some information that lead me to setup and configure the AutoUpdate feature to Microsoft CRM 4.0<\/p>\n<p>1. Download the hotfix or Rollup to your Computer and extract the contents<br \/>\n\u00a0\u00a0\u00a0\u00a0 a) Extracting the contents of the client patch on your System to determine the PatchId value which is required for the XML file configuration:<br \/>\n\u00a0\u00a0\u00a0\u00a0 b) Open a command prompt, and type [DownloadLocation]CRMv4.0-KB[KB#here]-i386-Client-ENU.exe \/x<br \/>\n\u00a0\u00a0\u00a0\u00a0 c) You will be prompted for a location to which the files will be extracted<br \/>\n\u00a0\u00a0\u00a0\u00a0 d) Once extracted, find the config.xml file at the root of the directory<br \/>\n\u00a0\u00a0\u00a0\u00a0 e) Within the XML file, copy the value of the element and paste it into your<\/p>\n<p>configuration file you will create in Step 3<br \/>\n2. Copy the exe file you downloaded (CRMv4.0-KB[KB#here]-i386-Client-ENU.exe )to the Server at location C:Program FilesMicrosoft Dynamics CRMCRMWebCRMPatches<br \/>\n3. Creating a configuration XML file name CRMRollup[#]Config.xml<\/p>\n<p>&lt;ClientPatches&gt;<br \/>\n&lt;Create&gt;<br \/>\n\u00a0\u00a0\u00a0 &lt;ClientPatchInfo&gt;<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &lt;PatchId&gt;(enter patch ID from above)&lt;\/PatchId&gt;<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &lt;Title&gt;CRM v4 Update Rollup #&lt;\/Title&gt;<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &lt;Description&gt;CRM v4 Update Rollup #&lt;\/Description&gt;<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &lt;IsMandatory&gt;false&lt;\/IsMandatory&gt;<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &lt;IsEnabled&gt;true&lt;\/IsEnabled&gt;<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &lt;ClientType&gt;OutlookDesktop,OutlookLaptop&lt;\/ClientType&gt;<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &lt;LinkId&gt;(file name of rollup that you put in patch directory)&lt;\/LinkId&gt;<br \/>\n\u00a0\u00a0\u00a0 &lt;\/ClientPatchInfo&gt;<br \/>\n&lt;\/Create&gt;<br \/>\n&lt;\/ClientPatches&gt;<\/p>\n<p>Note: The title and description are up to the administrator to complete.<br \/>\nNote: The IsMandatory option dictates whether a user has to install this hotfix in order to continue using CRM functionality within CRM.<br \/>\nNote: The ClientType can be either OutlookDesktop or OutlookLaptop or OutlookDesktop,OutlookLaptop depending on which clients should receive the updates.<br \/>\n4. Copy the xml config file to c:Program filesMicrosoft Dynamics CRMTools<br \/>\n5. On the Server in a command prompt, go to the directory where the ClientPatchConfigurator.exe is located at c:Program filesMicrosoft Dynamics CRMTools and type microsoft.crm.tools.clientpatchconfigurator.exe [configfile].xml<br \/>\n6. Once the patch has been uploaded, launch the Outlook client<br \/>\nWhen Outlook launches, the following screen will pop up:<\/p>\n<p><a href=\"https:\/\/sysadminnightmare.com\/?attachment_id=107\" rel=\"attachment wp-att-107\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-107\" alt=\"1\" src=\"https:\/\/i0.wp.com\/sysadminnightmare.com\/wp-content\/uploads\/2012\/05\/1.jpg?resize=300%2C228&#038;ssl=1\" width=\"300\" height=\"228\" \/><\/a><\/p>\n<p>When complete, you&#8217;ll see this screen:<\/p>\n<p><a href=\"https:\/\/sysadminnightmare.com\/?attachment_id=108\" rel=\"attachment wp-att-108\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-108\" alt=\"2\" src=\"https:\/\/i0.wp.com\/sysadminnightmare.com\/wp-content\/uploads\/2012\/05\/2.jpg?resize=300%2C228&#038;ssl=1\" width=\"300\" height=\"228\" \/><\/a><\/p>\n<p>7. You can then proceed to use CRM with the hotfixes applied. The hotfix installs will show in the Installed Updates area within Programs and Features in the Windows 7 Control Panel.<\/p>\n<p>To Remove a Rollup from being listed<br \/>\n1. Creating a configuration XML file name RemoveCRMMRollup[#]Config.xml, where is equal to the patch you want to remove<\/p>\n<p>&lt;ClientPatches&gt;<br \/>\n&lt;Delete&gt;<br \/>\n\u00a0\u00a0\u00a0 \u00a0\u00a0&lt;PatchId&gt;{A4CEC8ED-18B4-4682-9D4D-1BD0C4FC85AC}&lt;\/PatchId&gt;<br \/>\n&lt;\/Delete&gt;<br \/>\n&lt;\/ClientPatches&gt;<\/p>\n<p>2. Copy the config file to c:Program filesMicrosoft Dynamics CRMTools<br \/>\n3. On the Server in a command prompt, go to the directory where the ClientPatchConfigurator.exe is located at c:Program filesMicrosoft Dynamics CRMTools and type microsoft.crm.tools.clientpatchconfigurator.exe [configfile].xml<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After having to sit in the conference room for 4 days straight and participate in a &#8220;PC Pitstop&#8221; where users brought thier laptops in i began to think there has got to be an easier way to do some of this, which lead me on a google quest for:\u00a0AutoUpdate\u00a0CRM Server&#8230;. <a class=\"continue-reading-link\" href=\"https:\/\/sysadminnightmare.com\/index.php\/2012\/12\/27\/crm-rollup-and-patch-updates\/\"> Continue reading <span class=\"meta-nav\">&rarr; <\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[2,6],"tags":[13],"class_list":["post-31","post","type-post","status-publish","format-standard","hentry","category-admin","category-microsoft-crm-4-0","tag-automation"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p2bgeE-v","_links":{"self":[{"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/posts\/31","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/comments?post=31"}],"version-history":[{"count":0,"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/posts\/31\/revisions"}],"wp:attachment":[{"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/media?parent=31"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/categories?post=31"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysadminnightmare.com\/index.php\/wp-json\/wp\/v2\/tags?post=31"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}