locked
CRM 2011 Outlook Plugin with Outlook 2016 RRS feed

  • Question

  • Hi, 

    I noticed a couple of websites mention support for CRM 2011 with Outlook 2016:

    1. https://community.dynamics.com/crm/b/dynamicscrmsupportblog/archive/2015/07/10/dynamics-crm-support-with-windows-10-edge-browser-and-office-2016 - Says there is support

    2. https://technet.microsoft.com/en-us/library/dn832152.aspx - No support

    I've tried on a couple of PCs, and it did manage to install and connect to our CRM server, with items populated. However, things such as Accounts, Advanced Finds, etc, will not open. 

    What I would like to know is which link should I believe. Are there any plans to add support for CRM 2011 Outlook Plug-In with Office 2016? 



    Tuesday, October 13, 2015 12:58 PM

Answers

  • https://community.dynamics.com/crm/f/117/t/186929

    I recently found this thread, which shows how-to resolve the issue. Moreover, the CRM Outlook plug-in is far more responsive since adding this:

    1. Open regedit.

    2. Open HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient

    3. Add a new DWORD 32key called: 'UseWebFormProcessIsolation'

    4. Set the value to 0.

    5. Restart Outlook.

    • Marked as answer by Vernon Gomes Monday, April 4, 2016 3:24 PM
    Monday, April 4, 2016 3:24 PM

All replies

  • I don't know for sure but my feeling is that number 2 is the one to believe. I'd be surprised if CRM 2011 was updated to support Office 2016.

    As you've find it might well install and appear to work but that is quite a different thing from supported.

    Tuesday, October 13, 2015 7:33 PM
    Moderator
  • The latter is definitely correct.

    The postings on this site are solely my own and do not represent or constitute Hitachi Solutions' positions, views, strategies or opinions.

    Tuesday, October 13, 2015 7:59 PM
  • I've done some testing, and here is what I found:

    - If you use Office 2016, you'll need to downgrade the local CRM 2011 install to RU6, misguided as that may be. 
    - If you're on Windows 10, you'll need to add Windows Identity Foundation in Installed Features, in addition to above (Control Panel > Programs and Features > Installed Features > Check the box next to Windows Identify Foundation). 

    This is a more of a workaround than a fix, as this isn't recommended. "The general rule of thumb is to try to keep the versions in sync as much as possible. However, it is permissible (though not recommended as a long-term solution) to run mismatched Update Rollup versions on Outlook client and server, as Microsoft does do some testing of such combinations." Source: http://blogs.msdn.com/b/crminthefield/archive/2012/08/15/microsoft-dynamics-crm-4-0-and-2011-update-rollup-release-dates-build-numbers-and-collateral.aspx

    There is also mention of a RU 19, and that information all seems to be TBD, so that may be the fix, if it comes out. 

    • Proposed as answer by r3x4h Thursday, December 3, 2015 3:17 PM
    • Unproposed as answer by Vernon Gomes Monday, April 4, 2016 3:24 PM
    Thursday, November 19, 2015 2:45 PM
  • https://community.dynamics.com/crm/f/117/t/186929

    I recently found this thread, which shows how-to resolve the issue. Moreover, the CRM Outlook plug-in is far more responsive since adding this:

    1. Open regedit.

    2. Open HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient

    3. Add a new DWORD 32key called: 'UseWebFormProcessIsolation'

    4. Set the value to 0.

    5. Restart Outlook.

    • Marked as answer by Vernon Gomes Monday, April 4, 2016 3:24 PM
    Monday, April 4, 2016 3:24 PM