A new feature in CRM 4.0 is the administrative ability to prompt clients to install patches on their CRM For Outlook client. This feature is called AutoUpdate and it applies to any client where the user has administrative rights on his/her machine.
When you install the CRM 4.0 client, one of the new components is a tool called Update. This is the client component of the AutoUpdate process. You can launch the Update tool directly, run it as a scheduled task quietly, launch it from Outlook under the CRM toolbar – Check for Updates or it will run each time you launch Outlook. Also, by default, the AutoUpdate check is performed on all CRM 4.0 clients* every 4 hours*.
* These options can be turned off or adjusted via registry keys.
In order to make updates available to clients, you need to post the updates to the server. The CRM Server installation comes with a new tool called the Client Patch Configurator. The tool is installed by default at [Program Files]\MSCRM\Tools\Microsoft.Crm.Tools.ClientPatchConfigurator.exe. You need to run a DOS command to call the XML file in which you define the patches that will be provided to the client. The patch configurator process will add the patches to the MSCRM_Config database. You can use the tool to create, update or delete patch information, so if you add a patch you didn’t intend to add, you can remove it from being pushed to clients.
With that background information, here are the steps I give to customers asking how to set up AutoUpdate in their environment:
1. The first time you run autoupdate, go to your [ServerInstallDir]\Server\CRMWeb and create a new folder named crmpatches. Create this same folder on each subsequent web server in your deployment.
2. On each client, go to the registry and add a value in the HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRMClient key called AutoUpdateDownloadUrl (String) for 32bit Machines and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSCRMClient for 64bit machines. Give it a value of http://[servername]/crmpatches/ (remember the closing /). If you don't set this value, the clients will look to http://go.microsoft.com/fwlink/?LinkId= then the value in the LinkId XML parameter.
OR you can deploy the registry keys needed via Group Policy by Adding my “Group Policy Administrative Template” which there is a separate article: Creating A Group Policy Administrative Template For Deploying The CRM Client AutoUpdate Registry Keys
Troubleshooting Note: if when prompted to update the client you click install and crm responds “UntrustedUpdate” then please check the registry keys.
3. Download the hotfix to your server (or each web server) and extract the contents to the [ServerInstallDir]\Server\CRMWeb\crmpatches folder as set out below.
Extracting the contents of the client patch on your server to determine the PatchId value which is required for the XML file configuration.:
b. Open a command prompt, and type [DownloadLocation]\CRMv4.0-KB[KB#here]-i386-Client-ENU.exe /x
c. You will be prompted for a location to which the files will be extracted
d. Once extracted, find the config.xml file at the root of the directory
e. Within the XML file, copy the value of the <patchid> element and paste it into your configuration file you will create in Step 5
5. Creating your configuration XML file
Here's a sample configuration XML for Update Rollup 5:
<ClientPatches>
<Create>
<ClientPatchInfo>
<PatchId>{592DDF5E-D0D7-46FE-81C3-A3BCAC5E8F22}</PatchId>
<Title>CRM v4 Update Rollup 5</Title>
<Description>CRM v4 Update Rollup 5</Description>
<IsMandatory>true</IsMandatory>
<IsEnabled>true</IsEnabled>
<ClientType>OutlookDesktop,OutlookLaptop</ClientType>
<LinkId>CRMv4.0-KB970141-i386-Client-ENU.exe</LinkId>
</ClientPatchInfo>
</Create>
</ClientPatches>
Note: You can add multiple <ClientPatchInfo> and container elements to post multiple hotfixes at one time. The title and description are up to the administrator to complete. The IsMandatory option dictates whether a user has to install this hotfix in order to continue using CRM functionality within CRM. The ClientType can be either OutlookDesktop or OutlookLaptop or OutlookDesktop,OutlookLaptop depending on which clients should receive the updates. There are several more options available, so please see the Implementation Guide for further details.
6. In a command prompt, go to the directory where the ClientPatchConfigurator.exe is located ([ServerInstallDir]\Tools and type microsoft.crm.tools.clientpatchconfigurator.exe [configfile].xml
7. Once the patch has been uploaded, launch the Outlook client
When Outlook launches, the following screen will pop up:
When complete, you'll see this screen:
8. 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 Vista Control Panel or in Add/Remove Programs on Windows XP.
This feature provides administrators with the assurance that their clients will be on the most updated hotfix. Therefore, CRM client troubleshooting doesn’t have to begin with the question “Did you apply these patches?”
Thanks to Eric Newell of the CRM Team for his original article :Here
Subscribe