none
Lync client auto discover not working?

    Question

  • Ok I'm having a tough time with this. I've found a lot where people are having issues with it but none of their solutions worked for me.

    So when the Lync client connects it should use the AUTODISCOVER A record to lookup information for Exchange. The problem is it doesn't seem to work. I have tried with the SRV record and A host record along with having both in DNS at the same time. I keep getting "EWS not  deployed" and "EWS Internal URL" and "EWS External URL" are blank. Also there is no "Autodiscovery" registry key under HKCU\Software\Microsoft\Communicator\<SIP>

    So what could I be doing wrong here?

    If I go to exchange I my Test-OutlookWebServices is fine:

    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1019
    Type    : Information
    Message  : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1006
    Type    : Information
    Message  : Contacted the Autodiscover service at https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1016
    Type    : Information
    Message  : [EXCH] The AS is configured for this user in the AutoDiscover response received from https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1015
    Type    : Information
    Message  : [EXCH] The OAB is configured for this user in the AutoDiscover response received from https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1014
    Type    : Information
    Message  : [EXCH] The UM is configured for this user in the AutoDiscover response received from https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1016
    Type    : Information
    Message  : [EXPR] The AS is configured for this user in the AutoDiscover response received from https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1015
    Type    : Information
    Message  : [EXPR] The OAB is configured for this user in the AutoDiscover response received from https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1014
    Type    : Information
    Message  : [EXPR] The UM is configured for this user in the AutoDiscover response received from https://SERVER.domain.local/Autodiscover/Autodiscover.xml.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1022
    Type    : Success
    Message  : Autodiscover was tested successfully.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1024
    Type    : Success
    Message  : [EXCH] Successfully contacted the AS service at https://mail.domain.com/ews/exchange.asmx. The elap
           sed time was 38 milliseconds.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1026
    Type    : Success
    Message  : [EXCH] Successfully contacted the UM service at https://mail.domain.com/ews/exchange.asmx. The elap
           sed time was 18 milliseconds.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1028
    Type    : Success
    Message  : [EXPR] Successfully contacted the RPC/HTTP service at https://mail.domain.com/rpc. The elapsed time
           was 1 milliseconds.
    RunspaceId : 053c285f-9ac6-4a79-9ae8-ec4ae160d11a
    Id     : 1128
    Type    : Success
    Message  : [EXPR] Successfully contacted the RPC/HTTP service at https://SERVER.domain.local/rpc. The elapsed time wa
           s 8 milliseconds.
    


    Saturday, August 20, 2011 4:07 PM

All replies

  • Hi,

    The following post has the similar issue with you, hoping it can help you:

    http://social.technet.microsoft.com/Forums/en-US/ocsplanningdeployment/thread/d3dbbf2f-92f5-434c-864a-1598aa9e4e7e


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, August 22, 2011 6:44 AM
  • I did do that. I neglected to mention that the link server is on one subnet and Exchange is on another. They are both routable. I think this might be causing the problem but I am unsure.  There is also one single Exchange 2010 server and then the new environment is a DAG group. We will be migrating soon and this might fix the problem once they are on the same subnet.

    Do you think that is the problem?

    Monday, August 22, 2011 11:55 PM
  • I have exactly the same problem and till now, nothing helped what I read on the net :

    1. set-organizationConfig -EwsEnabled $true - EwsApplicationAccessPolicy EnforceBlockList

    2. Check on CAS Exchange internal and external EWS URLs, both on https

    3. I can paste both URLs in IE and are working

    4. Have all DNS entries : autodiscover A record, SRV record

    5. No problems with Outlook 2007 -> Autoconfiguration Test -> No problem

    6. test-outlokwebservices...no errors, everything fine

    7. Using internal CA and everybody is trusting that CA, certificates are valid, CA can be reached

    8. Rebooted all PCs

    9. My domain is on the local intranet site

    I have such a simple configuration : 1x Exchange 2010SP1, 1x Lync FE, Standard and 1x Win 7 client as Hyper Vs, no HLB, ect..., very easy

    Problem : In Lync Client :

    a) No EWS InternalURL

    b) No EWS External URL

    c) No Autodiscover entry in the registry on the client


    I use a Polycom CX 600 -> no outlook integration and YES, I attached it via USB to the PC...

    Any help would be cool...

    EDIT :

    When I type into IE my domain : https://autodiscover.fabrikam.com/autodiscover, I will get an 500 Error :

    "This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying."

    Mhhh



    • Edited by VisionPro Tuesday, March 13, 2012 7:35 PM
    Tuesday, March 13, 2012 7:01 PM