CRM Client AutoUpdate

re: CRM Client AutoUpdate

Christian Elberfeld — Fri, 23 May 2008 13:46:17 GMT

Hi Eric,

thanx for this post it is very helpful in big deployments with many Laptop-Clients.

Is it possible to add other installers (other Patches an AddOns) to the Update Feature ?

chris

re: CRM Client AutoUpdate

Jesus — Wed, 04 Jun 2008 23:50:44 GMT

It doesn't work for me. I have it installed in vista abnd it didn't create the MSCRM key in HKLM, but it is created in HKUSERS. I don't know where it is looking at

re: CRM Client AutoUpdate

Michiel — Thu, 05 Jun 2008 15:24:04 GMT

Nice, except for the fact that the user needs to have administrative rights for this to work. It seems that Microsoft still assumes this is always the case.

re: CRM Client AutoUpdate

Alex — Sat, 07 Jun 2008 01:22:01 GMT

Great article. So the AutoUpdateDownloadUrl needs to be configured in each client?? No method to auto configure this?

re: CRM Client AutoUpdate

Eric Newell — Tue, 24 Jun 2008 07:03:59 GMT

Chris -

At this point, I'm not aware of other add-ons that can be pushed out via AutoUpdate. It requires a CRM Patch ID, so it's unlikely that another add-on would work through this system. I can provide feedback to the product team about that for future versions.

Thanks,

Eric Newell [MSFT]

re: CRM Client AutoUpdate

Eric Newell — Tue, 24 Jun 2008 07:07:08 GMT

Alex & Jesus -

The registry key needs to be created in the HKEY_LOCAL_MACHINE hive for it to be picked up by the Update exe. It needs to be created manually, or you can do what we did internally which was to have people double-click on a registry file (.reg), so they didn't have to make updates to their registry.

Thanks,

Eric Newell [MSFT]

re: CRM Client AutoUpdate

Eric Newell — Tue, 24 Jun 2008 07:08:17 GMT

Michiel -

I understand your concerns and I know the product team is looking into options for patching the client without requiring adminstrative access. When I have more information on that front, I will pass it along.

Thanks,

Eric Newell [MSFT]

re: CRM Client AutoUpdate

Justin — Wed, 01 Oct 2008 19:11:25 GMT

This method worked great...for employees on the LAN. I tried to set this up for a remote employee. When he launches Outlook, it prompts to install the updates I listed in the XML file, but fails immediately with the error "Untrusted Update." I cannot find any documentation concerning this error. Any thoughts?

re: CRM Client AutoUpdate

Austin — Tue, 07 Oct 2008 02:06:06 GMT

I too have seen some users receive the "Untrusted Update" error and have not found a solution. I can say that I've had other users successfully install over IFD connection so it appears to be something with the user's configuration rather than AD vs IFD authentication.

re: CRM Client AutoUpdate

UK — Mon, 27 Oct 2008 18:45:01 GMT

Austin,

is the registry key for the update location set?

re: CRM Client AutoUpdate

Oscar Weijman — Fri, 31 Oct 2008 09:48:39 GMT

When you're running Vista 64-bit the registry key location needs to be:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSCRMClient

The key mentioned above won't work.

re: CRM Client AutoUpdate

Aaron — Wed, 05 Nov 2008 22:26:59 GMT

Any word yet on when the Administrative rights issue?

I am uysing SCCM and this seems to be an alternative solution, but I would like a way to just slipstream these updates in the package itself.

Oscar thanks for the 64 Bit key.

Update Rollup 1 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Tue, 23 Dec 2008 21:03:17 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

Update Rollup 1 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Tue, 23 Dec 2008 21:39:49 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

Update Rollup 1 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Tue, 23 Dec 2008 22:11:44 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

re: CRM Client AutoUpdate

Sergei — Mon, 05 Jan 2009 18:00:53 GMT

Thanks Eric for the post. Do you have any information on the following issue that was mentioned during the MS Webcast about AutoUpdate back in Spring of 2008?

As I understand it if you use Group Policy Objects to install the CRM Clients and then use AutoUpdates to apply patches the patches will not show up in the Add-remove programs. As a workaround at the time of the webcast the SMS install of the CRM Client was suggested (the issue is specific to GPO installs, not to SMS or manual installs).

Do we know if this issue has been addressed?

Update Rollup 2 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Tue, 20 Jan 2009 19:11:42 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

Update Rollup 2 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Tue, 20 Jan 2009 20:29:57 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

Update Rollup 2 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Tue, 20 Jan 2009 21:06:48 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

re: CRM Client AutoUpdate

Mark Gould — Fri, 23 Jan 2009 15:41:40 GMT

Assuming I have followed the above for Rollup 1 (or 2) what would the Link Id be given I have extracted it them to the Autoupdate folder? Would it be CRMv4.0-KB952858-i386-Client-INTL.exe ot a number?

re: CRM Client AutoUpdate

Mark — Fri, 23 Jan 2009 18:17:32 GMT

Has the local admin rights issue been addressed in rollup 2?

re: CRM Client AutoUpdate

Ken Briscoe — Thu, 05 Feb 2009 23:44:20 GMT

Assuming I want my clients to update directly from Microsoft, not from my own CRM web server, how do I find the necessary LinkID to include in my XML file?

Update Rollup 2 for Microsoft Dynamics CRM 4.0 - More Info

Microsoft Dynamics CRM Team Blog — Wed, 11 Feb 2009 20:54:04 GMT

On 2/8/2008, the CRM Sustained Engineering team released a new version of the Update Rollup 2 packages.

Update Rollup 2 for Microsoft Dynamics CRM 4.0 - More Info

Microsoft Dynamics CRM Team Blog — Thu, 12 Feb 2009 07:29:16 GMT

On 2/8/2008, the CRM Sustained Engineering team released a new version of the Update Rollup 2 packages

re: CRM Client AutoUpdate

Scott — Mon, 16 Feb 2009 16:47:01 GMT

Is the administrative rights issue going to be addressed in CRM 4.0 or is that going to be in CRM 5.0 whenever that is released? To me, it seems like a LOT of re-engineering to do this for the clients.

Update Rollup 2 and groundhog day conspiracy

Georged CRM Blog — Wed, 18 Feb 2009 18:04:35 GMT

Update Rollup 2 and groundhog day conspiracy

re: CRM Client AutoUpdate

Noone — Thu, 26 Feb 2009 19:05:17 GMT

I got an answer tell Microsoft to add CRM and other applications to WSUS.

re: CRM Client AutoUpdate

Peter Mohr — Mon, 02 Mar 2009 23:17:59 GMT

I agree. Add MS CRM (and all other MS products to Windows/Microsoft Update).

Until then I got this up and running with only one problem. "Untrusted Update". The problem only occured on the laptops that did not have the HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRMClient\AutoUpdateDownloadUrl set right.

The clients _would_ see the update because it's listed in the CRM database, but would not install before the reg key was set.

Great!

re: CRM Client AutoUpdate

Simon Gadsby — Tue, 03 Mar 2009 06:11:11 GMT

Is it possible to view the whole XML tree that is registered for updates? Then I can delete old ones without having to remember the PatchId etc?

And it will also help me troubleshoot why the XSL transform in the ConditionsXSL does not work. The one in the Operating doco didn't work for me, and I suspect it is not formatted correctly. If I could see the whole tree then I could troubleshoot it.

Thanks!

re: CRM Client AutoUpdate

Simon Gadsby — Wed, 04 Mar 2009 06:32:04 GMT

When deploying the update this way, it complains that files are in use!

I have to manually close Outlook and any other Office apps and Exit CRM via the system tray, and then the update continues successfully.

I would prefer for it to just install & then prompt to reboot at the end, which is what happens if you download the update manually and run it.

Why is this happening?

CRM4.0: AutoUpdate Outlook CRM Client Patches

Rexiology::Work — Wed, 04 Mar 2009 11:52:55 GMT

so we are finally at the stage of service-in our CRM Project to customer. since we did use CRM Outlook

CRM4.0: AutoUpdate Outlook CRM Client Patches

Rexiology@MSDN — Wed, 04 Mar 2009 12:10:39 GMT

so we are finally at the stage of service-in our CRM Project to customer. since we did use CRM Outlook

Update Rollup 3 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Fri, 13 Mar 2009 18:15:18 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

re: CRM Client AutoUpdate

Delf — Wed, 18 Mar 2009 00:38:23 GMT

I would really like Microsoft to consider an update mechanism such as WSUS to deploy updates to clients. We operate all of our users as regular users (non-local-administrators).

re: CRM Client AutoUpdate

Paul — Fri, 20 Mar 2009 06:14:51 GMT

Also need a non-admin method of installing updates. :(

re: CRM Client AutoUpdate

PxPx — Thu, 26 Mar 2009 23:57:59 GMT

When I try to use the Microsoft.CRM.tools.ClientPatchconfigurator it says the following:

Usage: Microsoft.Crm.Tools.ClientPatchConfigurator [XML Config file]

1. The first thing I noticed was I didnt have a CRMWeb folder so I created one.

2. I extracted CRM 4.0 Rollup 3 to the crmpatches Directory I made. I then took the patchID and copied and pasted it into your sample config.xml file which I saved in the C:\Program Files\Microsoft Dynamics CRM\Server\CRMWeb\crmpatches directory. I also moved the original installation file CRMv4.0-KB961768-i386-Client-ENU.exe to the crmpatches directory.

What am I doing wrong your directions were not very clear on where I should be saving the config.xml I just assumed to save it to the crmpatches directory.

re: CRM Client AutoUpdate

dbenton — Tue, 14 Apr 2009 21:18:31 GMT

Please add my vote for a better client update solution. At Convergence all the talk was of SMS. We don't have or want to purchase SMS. Why not WSUS or at least a way to script the updates that isn't so painful and requires admin privileges.

<rant>

Best practice is not give users local admin permission but new MS products require local admin privileges for install/updates. Between Vista and new products released with the same admin issues, more SaaS solutions are looking better and better. MS has a good unified solution product set, take it to the next level and make it a no brainer. The door isn't being left open a crack for other solutions, it's being kick wide open by MS and at some point (in the near future at this rate) MS customers will be forced to migrate. I see incredible potential in MS CRM ,MOSS, SQL, SRS, etc. Quit making it so painful to be a MS shop.

</rant>

<P.S. Rant>

And get a decent Wiki on MOSS. Ya gotta be kidding me with that thing.

</P.S. rant>

Update Rollup 4 for Microsoft Dynamics CRM 4.0

Microsoft Dynamics CRM Team Blog — Thu, 14 May 2009 17:29:36 GMT

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup

re: CRM Client AutoUpdate

floppylo — Sun, 31 May 2009 20:38:51 GMT

Hi All,

I am desperately needing help in removing the configfile.xml from [Program Files]\MSCRM\Tools\Microsoft.Crm.Tools.ClientPatchConfigurator.exe.

I was testing the AutoUpdate in our Production environment and need to remove it because we are not ready to proceed with the rollup yet.

Please let me know how I can remove it. I really appreciate it! Thanks.

Victoria

re: CRM Client AutoUpdate

floppylo — Sun, 31 May 2009 22:39:53 GMT

I figured out how to remove the patch. It's documented in the Operating and Maintaining Guide : )

re: CRM Client AutoUpdate

John — Thu, 25 Jun 2009 00:35:04 GMT

Can you install the CRM 4.0 update rollup 4 patch on all the machines before installing the CRM 4.0 update rollup 4 patch on the server (the server is currently unpatched)?

re: CRM Client AutoUpdate

Roland — Wed, 12 Aug 2009 14:08:47 GMT

Can you please provide some guidance on how to create an XML file to update multiple language clients. For example: how would a XML file for updating English, French and German clients to Rollup 5 look like?

And why is this a manual process?!?

re: CRM Client AutoUpdate

hasrett — Thu, 17 Sep 2009 16:03:41 GMT

How to remove it again?? please its critical....

re: CRM Client AutoUpdate

David Keeble — Thu, 08 Oct 2009 12:29:28 GMT

If the user must have admin rights, what are the benefits of using this method against simply downloading the update from the MSFT web site?

It seems to me that the latter is a better solution as you don't need to patch the registry. It may come as a surprise to MSFT that most users of the CRM are sales people who are not that technical. Asking these people to patch the registry cannot be recommended.

re: CRM Client AutoUpdate

Ryan Schauer — Thu, 10 Dec 2009 18:11:27 GMT

@David Keeble: So take advantage of your networked environment and build a script to do it for them. There are many ways to do this. We use Numera Deploy, but logon scripts would work too.

What I'm unclear with here is how robust is this solution. With future rollups, do we have to jump through hoops and update the xml file again each time? Seems like there should be an easier way...

re: CRM Client AutoUpdate

MBowen — Tue, 22 Dec 2009 16:03:39 GMT

Has there been any progress regarding the local admin rights issue? We have reduced our number of Outlook Clients down to just 5 users. The benefits of the hook into Outlook are overshadowed by the pain point of having to touch every machine in our company. If I had my way, I would un-install the remaining 5 clients as well.

In my opinion, this issue totally negates the MS marketing that CRM integrates with Outlook. If I can’t reasonably support the frequent updates, it’s a non-feature.