locked
CRM AutoUpdate behind Authenticating Proxy RRS feed

  • Question

  • Heya

    Is there a way of getting AutoUpdate to work if the client needs to go through an Authenticating Proxy?

    I have tried creating a Microsoft.Crm.Client.Autoupdate.exe.config file - one of the config setups I've tried is as follows :-

     <?xml version="1.0" encoding="utf-8"?>
    <configuration>
     <system.net>
    <defaultProxy enabled="true" useDefaultCredentials="true" >
    <proxy autoDetect="True" scriptLocation=http://myproxyscript.pac />
    </defaultProxy>
    </system.net>
    </configuration>

    I've tried others such as trying to use the default proxy setup in IE. Nothing seems to work, I keep getting a 407 - Proxy Authentication Required.

    The problem is that AutoUpdate gives a "Download Failed" error when trying to download the update from the Microsoft website. I'd prefer not to have to download and install on the server, as that would require changing the registry keys on each client machine to pull updates back from the local server.

    Any help appreciated!!

    Thanks

    Josh

    Thursday, April 9, 2009 1:22 AM

Answers

  • That download failed error may not have anything to do with your proxy.  That's how it behaves in every situation.  By default, autoupdate looks to a Microsoft URL for updates.  The problem is, unless your config file includes the linkid of the update, it will fail with an "untrusted location" error.

    You have two options:

    1.  put the linkid of the update in the config file.  See the "Making update rollup 2 available to your clients" section of this post for more info on the linkid http://blogs.msdn.com/crm/archive/2009/02/11/update-rollup-2-for-microsoft-dynamics-crm-4-0-more-info.aspx.  Starting with RU 3, they are including the linkid in the kb article with the update.  With the linkid specified, your users will be able to download updates via autoupdate if they have an internet connection.

    2.  You can also make the clients look for the updates from a local server directory.  See the instructions here: http://blogs.msdn.com/crm/archive/2008/05/08/crm-client-autoupdate.aspx.  All you have to do is add a string called AutoUpdateDownloadURL to the HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRMClient key on their local machine with the folder with patches on your server.
    This is what we did.  Then if they don't have internet access, they can still download the patches.  You can easily make a .reg file to update their registries and push it out with group policy.
    • Marked as answer by Jim Glass Jr Thursday, April 9, 2009 9:39 PM
    • Unmarked as answer by Josh Ashwood Monday, April 13, 2009 10:08 PM
    • Unmarked as answer by Josh Ashwood Monday, April 13, 2009 10:08 PM
    • Marked as answer by Jim Glass Jr Tuesday, April 14, 2009 6:05 PM
    • Unmarked as answer by Jim Glass Jr Tuesday, April 14, 2009 6:05 PM
    • Marked as answer by Josh Ashwood Tuesday, April 21, 2009 7:25 AM
    Thursday, April 9, 2009 10:39 AM
    Moderator

All replies

  • That download failed error may not have anything to do with your proxy.  That's how it behaves in every situation.  By default, autoupdate looks to a Microsoft URL for updates.  The problem is, unless your config file includes the linkid of the update, it will fail with an "untrusted location" error.

    You have two options:

    1.  put the linkid of the update in the config file.  See the "Making update rollup 2 available to your clients" section of this post for more info on the linkid http://blogs.msdn.com/crm/archive/2009/02/11/update-rollup-2-for-microsoft-dynamics-crm-4-0-more-info.aspx.  Starting with RU 3, they are including the linkid in the kb article with the update.  With the linkid specified, your users will be able to download updates via autoupdate if they have an internet connection.

    2.  You can also make the clients look for the updates from a local server directory.  See the instructions here: http://blogs.msdn.com/crm/archive/2008/05/08/crm-client-autoupdate.aspx.  All you have to do is add a string called AutoUpdateDownloadURL to the HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRMClient key on their local machine with the folder with patches on your server.
    This is what we did.  Then if they don't have internet access, they can still download the patches.  You can easily make a .reg file to update their registries and push it out with group policy.
    • Marked as answer by Jim Glass Jr Thursday, April 9, 2009 9:39 PM
    • Unmarked as answer by Josh Ashwood Monday, April 13, 2009 10:08 PM
    • Unmarked as answer by Josh Ashwood Monday, April 13, 2009 10:08 PM
    • Marked as answer by Jim Glass Jr Tuesday, April 14, 2009 6:05 PM
    • Unmarked as answer by Jim Glass Jr Tuesday, April 14, 2009 6:05 PM
    • Marked as answer by Josh Ashwood Tuesday, April 21, 2009 7:25 AM
    Thursday, April 9, 2009 10:39 AM
    Moderator
  • Thanks for the tips mate, we've decided to go that way, as per the CRM Team Blog's article re updates via the local server. I was just hoping we would [1] be able to avoid sending out a registry key and [2] uploaded the updates to the server.

    But just for anyone else who reads this, we are sure that it was a proxy authentication problem, as I could see a http status code of 407 - Proxy Authentication Required being returned when i viewed the update process using a web debugger.

    So if you ARE behind an authenticating proxy, you will to pick up the updates from the local server and create the registry keys as per the Team Blog articles.


    Thanks!

    Monday, April 13, 2009 10:15 PM