none
Office Communicator 2007 R2 integration error with Outlook 2016 on Windows 10 Pro

    Question

  • Recently purchased two Lenovo T series laptops for our company. Both with Windows 10 Pro. We utilize Office Communicator 2007 R2 in our company. As new MSFT office versions come out we roll them out to keep up with the times. These two new laptops have Office 2016 Home & Business installed and for some reason we cannot get the MOC conversation history to work properly. We can an integration error that states: There was a problem connecting to microsoft office outlook. Your outlook profile is not configured correctly. Contact your system administrator with this information. We are also running Exchange 2010 R2. I've tried the domain admin profile as well as a few end users and none seem to work. Any ideas would be welcomed.
    Tuesday, April 5, 2016 9:08 PM

All replies

  • I've tried the domain admin profile as well as a few end users and none seem to work.

    I don't quite understand this statement, you mean you have tested this with a few other users ( different Outlook profiles)?

    Please make sure that the Outlook profile file name doen't contain any non-English characters. Also, run Windows Update to install any available updates, especially this one - https://support.microsoft.com/en-us/kb/948159, then verify result again.

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Thursday, April 7, 2016 5:49 AM
    Moderator
  • Thank you for the reply. You are correct, we have signed onto the computer with different domain accounts and have the same result of it not working. We have ran all windows updates and the one you noted was installed. I was able to resolve one user by downgrading their office from 2016 to 1013. However would still like to get this resolved if possible.

    -Travis

    Thursday, April 7, 2016 8:29 PM
  • Office Communicator 2007 R2 is pretty old, which might be incompatible with Office 2016.

    Please check the OC 2007 R2 add-in is installed correctly on the outlook client.

    You might want upgrade to Skype for Business.


    • Edited by Bhanu Tej Monday, April 18, 2016 9:14 AM
    • Proposed as answer by Bhanu Tej Monday, April 18, 2016 9:15 AM
    Monday, April 18, 2016 9:13 AM
  • Thanks for the reply. However we thought it may be unsupported as well so we dug a little deeper. We are using Office 2016 Home and Business, and looking at the below site it states that our version of OC is supported still. We have R2, while regular OC isn't supported.

    "Certain advanced functionality may require connectivity to:

    Microsoft Exchange Server 2016, Exchange Server 2013, Exchange Server 2010, or Exchange Online. Outlook 2016 does not support connections to Exchange Server 2007.
    Microsoft SharePoint Server 2013, SharePoint Server 2010, or SharePoint Online; and/or Microsoft SharePoint Foundation 2013 or SharePoint Foundation 2010.
    For integration with Skype for Business/Microsoft Lync (optional): Skype for Business Online, Lync 2013, Lync 2010, and Office Communicator 2007 R2. Office Communicator 2005 and Office Communicator 2007 are not supported"


    Source:

    https://products.office.com/en-us/office-system-requirements#Office2016-suites-section



    • Edited by Tvesecky Monday, April 18, 2016 7:22 PM
    Monday, April 18, 2016 7:21 PM
  • Did you ever get this figured out??
    Thursday, August 31, 2017 8:24 PM
  • you need to migrate off OCS2007R2.

    I think it's very unlikely that Win10 + Office2016 would have been tested with such an ancient version of OCS.

    OCS2007R2 is end-of-life January 2018, it's time to get off it really.

    https://support.office.com/en-us/article/Office-Communications-Server-End-of-Life-Roadmap-54f3d5ba-bdf9-4b37-a9e8-f1ab452d4f78

    We've a rather ugly interop/co-existence scenario ourselves at the moment with a mixture of OCS2007R2 + Lync2013(SfB2015) and it is very ugly to support, with a lot of interop problems. We are almost finished with our migration but it has been horrible for everybody for 2years :(

    Whilst it is officially 'supported', it is a terrible combination to inflict on your business, and you should avoid it if possible, and if you can't avoid the combination you should aim to stay on it as briefly as possible.


    Don [doesn't work for MSFT, and they're probably glad about that ;]



    • Edited by DonPick Thursday, August 31, 2017 9:40 PM
    Thursday, August 31, 2017 9:34 PM