Autodiscover Configuration Exchange 2007

I am migrating from Exchange 2003 to Exchange 2007. I am having an issue with my autodiscover.xml. The file is there and can be accessed, but there is nothing populating the file (it is just a place holder file). I have looked around to find out if the file
should autofill with the correct info (and it appears it should), but my file has none of the settings in it. I ran the commands below and the information appears to be correct.
get-OwaVirtualDirectory | fl
get-webservicesVirtualDirectory | fl
get-OABVirtualDirectory | fl
get-ActiveSyncVirtualDirectory | fl
Should the autodiscover.xml file populate itself with the correct information? If not, is there a template to follow to fill out the information that should be there?
Thanks,
Kevin

Hi ,
If we have configured audiscover in organization, we will some parameters in Autdiscover.xml, we will give an example that show a request that came in from an outlook 2007 client:
 <?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
  <Request>
    <EMailAddress>[email protected]</EMailAddress>
    <AcceptableResponseSchema>
         http://schemas.microsoft.com/exchange/autodiscover/
         outlook/responseschema/2006</AcceptableResponseSchema>
  </Request>
</Autodiscover>
If the configuration cannot be found, the outlook client will be notified and Autodiscover retrieval fail.
If there are any questions regarding this issue, please be free to let me know. 
Best Regard,
Jim

Similar Messages

  • Outlook 2013 not automatically configuring Exchange (2007) account when running the Auto Account Setup

    In previous versions, once I launched Outlook, it would automatically detect/passthrough my username and email address into the fields so that I could just click next and be done. In Outllok 2013 on Windows 2008 R2 this doesn't appear to be working even
    thought I am able to successfully resolve my autodiscover domain.

    Hi,
    Is there any error when you can’t connect your Outlook 2013 to Exchange 2007?
    If the autodiscover service is configured correctly, please change a computer to have a try. In this local windows 2008 R2, please check the following settings in Internet Explorer:
    Click Settings > Internet Options > Connections > LAN settings, please make sure there is no proxy server set there. Only “Automatically detect settings” option is checked.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Problems configuring exchange 2007 to original iphone

    My work just upgraded to exchange 07 and now I cannot set up my exchange account on the iphone. It was working fine with exchange 03 but now I get the "connection to server failed" error. Any ideas?
    I already have the latest updates and already contacted IT to see if anything has changed and they said everything should be the same.

    Here is an article from the apple support website that might help out.
    http://support.apple.com/kb/HT2099?viewlocale=en_US
    http://support.apple.com/kb/TS1693
    http://www.apple.com/iphone/enterprise/
    Hope these help.

  • Troubleshooting and Introduction for Exchange 2007/2010 AutoDiscover - Details about "Test E-mail AutoConfiguration"

    AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
    clients or later.
    We can determine whether problems related to AutoDiscover via OWA.
    For example:
    OOF is not working in Outlook Client but it is working in OWA.
    When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
    abnormal on AutoDiscover.
    There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
    Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
    1. Differences between “Test E-mail AutoConfiguration” and other tools
    The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
    Autodisocver
    Exchange Web Services
    Availability Service
    Offline Address Book
    When we run “Test-OutlookWebServices”, it returns all the web services’ states.
    However, some information are useless for some scenarios.
    For example:
    We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
    However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
    In contrast, using “Test E-mail Autodiscover” is more intuitive.
    If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
    KBs.
    Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
    find the root of problem.
    2. How to use “Test E-mail AutoConfiguration” Tool
    a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
    AutoConfiguration” option. Please see Figure 01.
    Figure 01
    b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
    Figure 02.
    Figure 02
    c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
    Figure 03
    Figure 04
    3. How to understand “Test E-mail AutoConfiguration” result
    According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
    URLs.
    If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
    - Internal OWA URL:
    https://vamwan310.vamwan.com/owa/
    OWA internal access.
    - External OWA URL:
    https://mail.vamwan.com/owa/
    OWA external access.
    - Availability service URL:
    https://vamwan310.vamwan.com/EWS/Exchange.asmx
    Free/Busy, OOF and meeting suggestions.
    - OOF URL:
    https://vamwan310.vamwan.com/EWS/Exchange.asmx
    Out of Office access.
    - OAB URL:
    https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
    OAB access.
    - Exchange Control Panel URL:
    https://vamwan310.vamwan.com/ecp/
    ECP access.
    4. AutoDiscover Tips
    - AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
    clients.
    - The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
    - AutoDisocver virtual directory is created in IIS within the Default Web Site.
    - A Sercive-Connection-Point (SCP) object is created in AD.
    - The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
    - In AD this object is located at the following location:
    DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
    Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
    - Setup creates the AutoDiscover URL based on the following structure:
    <CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
    If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site. 
    To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
    If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
    The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
    EXCH, EXPR, WEB
    The
    EXCH and EXPR setting are vital for the proper configuration of Outlook.
    5. AutoDiscover Workflow
    General Process flow:
    There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
    itself, the provider, and AD.
    a.
    Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
    b.
    IIS Authenticates User.
    c.
    Is the Autodiscover service in the appropriate forest?
    + If YES.
        1)
    Parse/Validate Request
        2)
    Is there a provider that can service the Request?
    ++ If YES
          a)
    Config provider processes request and returns config settings.
          b)
    Return config setting to client
    ++ If NO
    Inform client we cannot process request
    + If NO.
    Redirect client to Autodiscover service in the appropriate forest.
    Methods to find Autodiscover services: SCP and DNS
    Domain-joined
    a. Find SCP first.
    The SCP contains the URL to the AutoDiscover service.
    URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
    If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
    are in the same site to obtain the AutoDisocover URL.
    b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
    Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
    For example: If my email address is
    [email protected]
    Outlook tries POST commands to the following order of URLs:
    https://contoso.com/autodiscover/autodiscover.xml
    https://autodiscover.contoso.com/autodiscover/autodiscover.xml
    NOTE: The URLs above is by design, hardcode
    and cannot be changed.
    c.
    If those fail, Outlook tries a simple redirect to another URLs in IIS:
    http://contoso.com/autodiscover/autodiscover.xml
    http://autodiscover.contoso.com/autodiscover/autodiscover.xml
    If none of these URLs work then DNS is most likely not set up correctly.
    We can test that by pinging one of the above URLs.
    If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
    If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
    NOTE: If contoso.com is a non-CAS server,
    we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
    d.
    If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
    with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
    Non-Domain-joined
    It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
    the Autodiscover service by using DNS.
    Then, same as step b, c, d in
    Domain-joined scenario.
    6. How to change the AutoDiscover
    service location order forcibly?
    By default, Outlook client locates AutoDiscover service in that order above.
    We can also change the order forcibly.
    a.
    If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
    Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
    that you want)
    b. If we want to locate AutoDiscover service via
    SRV record, please follows this KB to set up SRV:
    http://support.microsoft.com/kb/940881
    7. How to check AutoDiscover Healthy
    a. We should make sure the AutoDiscover
    is healthy before using AutoDiscover to perform troubleshooting.
    b.
    We can browse following URL in IE explorer:
    https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
    If it returns “code 600”, that means AutoDiscover is healthy.
    Screenshot as below:
    c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
    request.
    The following table explains the possible errors that could be returned.
    Error   Value
    Description  
    600
    Mailbox not found and a   referral could not be generated.
    601
    Address supplied is not   a mailbox. The provided email address is not something a client can connect to.   It could
    be a group or public folder.
    602
    Active Directory error.
    603
    Others.
    The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
    the service is running and accepting requests.
    d.
    If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
    Steps as below:
    1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
    Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
    Please refer:
    http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx 
    2)
    Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
    Get-AutodiscoverVirtualDirectory | FL
    Please refer:
    http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
    3)
    Running following command in EMS to re-creating a new AutoDiscover VD:
    New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
    Please refer:
    http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
    8. Common issues
    a. Outlook Disconnection
    Issue and Troubleshooting
    Issue:
    Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
    always connect to the old CAS server.
    Troubleshooting:
    To solve this issue, we should change the SCP via following command:
    Set-ClientAccessServer -Identity
    <var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
    https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
    b. Autodiscover
    Certificate issue
    Tips on Certificate:
    Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
    This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
    Issue and Troubleshooting
    Issue:
    We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
    Troubleshooting:
    1) Please determine the FQDN that the client
    uses to access the resource. Steps as below:
    OutlookàToolsàAccount
    SettingsàE-mailàclick
    the Exchange accountàChangeàMore
    SettingsàConnectionàExchange
    Proxy Settingsànote the FQND that list in the
    Only connect to proxy servers that have this principal name in their certificate box.
    2)
    Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
    This command returns the result for the EXPR name.
    3)
    Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
    Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
    9. Resource for reference:
    Autodiscover and Exchange 2007
    http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
    White Paper: Understanding the Exchange 2010 Autodiscover Service
    http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
    Certificate Principal Mismatch
    http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    HI,
     I get following?  when run the test?  user is login to Domain A but accessing exchange in Domain B?

  • Exchange 2007 migrate to Exchange 2013

    Dear MS Support,
    I did migrate Exchange 2007 to Exchange 2013
    The install complete, the exchange 2007 and 2013 can work together successful
    DAG has created and work fine
    Below is capture on exchange group after migrate
    The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
    The cerificate enroll with
    Alternative Names: mail.biendongpoc.vn
    The autodiscover on exchange 2007:
    [PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
    Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
    Identity      AutoDiscoverServiceInternalUri
    BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
    I have created new certificate for Two exchange 2013
    The certificate enroll with
    Alternative Names: cas.biendongpoc.vn
    I have create cname cas point to dag  on DNS server
    I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
    I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
    connected to Exchange 2013 and working perfectly
    Our problem, the account exchange 2007 work not stable ,
    sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
    If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
    It is not stable for current exchange 2007
    Anyone who can help me ?
    Thanks

    Hi
    huynhtrongnhatminh,
    I suggest you please go through this article.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Please check this for step by step guide.
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Please point your autodiscover and commonname to Exchange2013 CAS
    Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
    You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally. 
    Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
    Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
    No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
    Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
    http://exchange.sembee.mobi/network/split-dns.asp
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Exchange 2007 not accepting my password

    I am having problems setting up Mail.app to connect to Exchange 2007, everytime i logon it says that Exchange has rejected my password.
    I am fairly sure that autodiscover is turned on as when i type in my email address it finds the server and settings, so don't think thats the problem, also the server is on Rollup 9 which exceeds the rollup 4 required.
    Has anyone encountered similar problems, or got any suggestions as to what else i can check/try as this is soooooooo frustrating!!!
    Justin
    PS: i have tried changing my password and that doesn't work!

    There are a lot of Mac users at my company. I've done an informal poll of those who have upgraded to Snow Leopard and are trying Mail connected to Exchange 2007. This appears to be a common problem for those I've spoken to unless the user is connected to the VPN. Besides the continuous password prompts my co-workers also complained of slow or sporadic mail synchronization.
    I should also note that our mail admins have configured Exchange 2007 for RPC over HTTPS and that Outlook 2007 configured to use "Outlook Anywhere."
    Again, if connected to the corporate network via VPN the repeated password prompts do not appear.
    I called Apple back after reading the updated posts to this thread. The support technician said that they were going to search their internal KB to see if there is a "master ticket" covering this issue since it appears to affect many people from around the world. I also directed them to this thread for their reference. I'm expecting a call back later today with an update on their findings. Let's see what they come back to me with.

  • Onsite Scanner Unable To Send Documents Through Exchange 2007 Server (SBS 2008)

    I have an SBS 2008 server complete with Exchange 2007 in house and have configured Exchange 2007 to use the Exchange Online Protection (EOP) to process mail for malware, etc.  This setup has worked great for the last year or so with no issues.
    However, all of a sudden in the last couple of weeks our onsite copier can no longer send documents through email to anyone within the organization.  The copier is a Kyocera TaskAlfa 3050CI and exists with the same network.  The copier can scan
    to a network folder without issue.
    If I change the SMTP settings to use a gmail account instead of a local account I can send mail to outside email address.  Even with this changed though I still can't send to our domain addresses.
    I tried running a message trace from the Exchange Management Console but it doesn't find anything for hte given subject or date/time when I scanned the document.  
    I am not exactly sure what I should be checking or what piece of the puzzle is causing the problem here.  Any ideas on what might be happening or how to correct it?
    Thanks so much!

    Hi,
    Any update? Would you please let us confirm some questions as Howtodo mentioned. Please feel free to let us
    know.
    Based on your description, it seems that only the copier can’t send documents via emails. On your SBS 2008
    environment, please check if some user accounts encounter the similar issue. In other words, did users also can’t send emails attached with documents? If the email was attached with a small size document, will the same result?
    In addition, can find any relevant error or events?
    Hope this helps.
    Best regards,
    Justin Gu

  • Intergrating Unity 7.0 with Exchange 2007

    I have a customer that is currently on Unity 7.0 and Exchange 2003. They are building a new 2007 Server and want to intergrate it with Unity 7.0.  Does anyone have any documentation or videos on how to do the migration?

    Hello Dushaune,
    Basically integrating  means that you are going to change Message Store also known as the partner server (Exchange 2k3) to the new partner with Exchange 2k7. For this there are several steps:
    -OAB and Extending AD schema
    - PW (Permission Wizard)
    - MSCW (Message Store Configuration Wizard)
    You need to follow this mandatory steps on the guide:
    Configuring Exchange 2007 for Cisco Unity   &    Extending the Active Directory Schema for Cisco Unity
    http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/installation/guide/umexnofo/5xcuigumenofo060.html#wp1942680
    ***Even though on the title you see unity 5.x this is still applicable for Unity 7.x, on the documentation guide you will read:
    Note
    The following link goes to a Release 5.x version of the guide; all 5.x content applies to version 7.x as well.
    On the Exchange side make sure you meet the following system requirements:
    Minimum Service Packs Required—Message Store
    •Exchange 2007 Service Pack 1 Update Rollup 4:
    –On Exchange 2007 servers that are running Windows Server 2008. Without the update rollup, message waiting indicators will not function properly. See Microsoft KB article 952580.
    http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/7xcusysreq.html#wp472166
    As a side note but still related, i'm not sure what outlook version you have so make sure it is on the compatibility matrix:
    http://www.cisco.com/en/US/partner/docs/voice_ip_comm/unity/compatibility/matrix/cuclientmtx.html#wp364674
    As for the PW (Permission Wizard)  it grants permissions for the Unity Service Accounts (Unity Install, Unity Directory Services and Unity Message Store) and to run it you need to be a domain admin. This tool is found on Tools Depot> Administration Tools>  Permission Wizard. Make sure it is the latest and greatest version (3.0.0.7) For a more detailed understanding with screenshots go to:
    Granting Permissions with Cisco Unity 5.0(1)+ Permissions Wizard
    http://www.ciscounitytools.com/Applications/Unity/PermissionsWizard/Unity50/Help/PWHelp_ENU.htm
    After you run the PW (Permission Wizard) you will get a pop-up window advising what permissions to apply depending on the Exchange version you choose, in this case:
    Version of Exchange in Which Mailboxes Are Homed:  Exchange 2007 only
    Active Directory Account:  Cisco Unity installation and Cisco Unity directory services
    Permissions to Grant to previous AD (Active Directory) accounts:
    Delegate Exchange Organization Administrator administrative control
    Delegate Exchange Organization Administrator admininistrative control
    The MSCW (Message Store Configuration Wizard) will define the actual partner. Here is a link with a short description:
    https://supportforums.cisco.com/docs/DOC-23513
    This tool is found on Control Panel> Add Remove Programs> Cisco Unity Message Store Configuration Wizard> Click on Change/Remove to execute it, below are the screenshots guiding through the tool.  **The only screenshot missing is where you see a pencil writting a book, this means it's synchronizing, just let it finish.**
    In this case my installation account was unityinstall, however sometimes people name then just Unity, or company_unityinstall and so on so chooose the applicable. For the admin account you could use unityadmi, i decided to use unityinstall:
    In the screenshot i only have a 2010 Exchange, however this will reflect all Exchange versions in your deployment (2k3 and 2k7) chooose the applicable, also this will require to stop Unity, so no auto attendant and no voicemail during this time:
    On this last part pay attention where it says Directory Service account:
    Best Regards,
    +|>@|/1D+

  • Exchange 2007 Autodiscover certificate mismatch

    Hello, the company that I work for is trying to switch from Exchange 2007 SP1 to Office 365.  However, when we try the cutover migration, 365 doesn't recognize our Exchange server.  After a bit of research, I discovered that there is a certificate
    mismatch that is causing the problem.  
    I've been searching for a way to solve this problem for a couple of days now and have not yet found a solution.  We'd like to keep the autodiscover location, but change the certificate that is bound to it.  We
    have a matching certificate installed, but for some reason, Autodiscover keeps pointing toward the wrong certificate (that doesn't even exist).
    Any help would be greatly appreciated

    We purchased new certs from GoDaddy and inserted them into exchange (overwriting the old certs and CAs), and this seemed to correct the certificate mismatch.  However, when I run the Remote Connectivity Analyzer, I get this:
    Connectivity Test Failed
    Test Details
    <input class=" __ecpStyleButton" id="testSelectWizard___CustomNav3_buttonStartOver" name="testSelectWizard$__CustomNav3$buttonStartOver"
    style="padding:8px 8px 8px 29px;text-align:left;border-style:none;cursor:pointer;background-image:url(https;background-background-repeat:no-repeat;" type="submit" value="Start Over" /><input class=" __ecpStyleButton"
    id="testSelectWizard___CustomNav3_buttonRunAgain" name="testSelectWizard$__CustomNav3$buttonRunAgain" style="padding:8px 8px 8px 29px;text-align:left;border-style:none none none solid;cursor:pointer;border-left-color:#cccccc;border-left-width:1px;background-image:url(https;background-background-repeat:no-repeat;"
    type="submit" value="Run Test Again" />
    <input class=" __ecpStyleButton" id="testSelectWizard_ctl12_btnExpandAll" name="testSelectWizard$ctl12$btnExpandAll" style="padding:8px 8px 8px 29px;text-align:left;border-style:none
    solid none none;cursor:pointer;border-right-color:#cccccc;border-right-width:1px;background-image:url(https;background-background-repeat:no-repeat;" type="submit" value="Expand All" /><input class="ecpStyleButtonImageOnly
    __ecpStyleButton" id="testSelectWizard_ctl12_btnSaveXml" name="testSelectWizard$ctl12$btnSaveXml" style="padding-padding-bottom:6px;padding-text-align:left;border-style:none;cursor:pointer;background-image:url(https;background-background-repeat:no-repeat;"
    title="Save as XML" type="submit" value="" /><input class="ecpStyleButtonImageOnly __ecpStyleButton" id="testSelectWizard_ctl12_btnSaveHtml" name="testSelectWizard$ctl12$btnSaveHtml" style="padding-padding-bottom:6px;padding-text-align:left;border-style:none;cursor:pointer;background-image:url(https;background-background-repeat:no-repeat;"
    title="Save as HTML" type="submit" value="" />
    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
    Testing Autodiscover failed.
    Additional Details
    Elapsed Time: 7624 ms.
    Test Steps
    Attempting each method of contacting the Autodiscover service.
    The Autodiscover service couldn't be contacted successfully by any method.
    Additional Details
    Elapsed Time: 7624 ms.
    Test Steps
    Attempting to test potential Autodiscover URL https://paidwarranty.com:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.
    Additional Details
    Elapsed Time: 1237 ms.
    Test Steps
    Attempting to resolve the host name paidwarranty.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 12.192.135.43, 50.232.20.50
    Elapsed Time: 129 ms.
    Testing TCP port 443 on host paidwarranty.com to ensure it's listening and open.
    The port was opened successfully.
    Additional Details
    Elapsed Time: 152 ms.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
    Additional Details
    Elapsed Time: 342 ms.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server paidwarranty.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=www.paidwarranty.com, OU=Domain Control Validated, Issuer: CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
    Elapsed Time: 247 ms.
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name paidwarranty.com was found in the Certificate Subject Alternative Name entry.
    Elapsed Time: 1 ms.
    Certificate trust is being validated.
    The certificate is trusted and all certificates are present in the chain.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=www.paidwarranty.com, OU=Domain Control Validated.
    One or more certificate chains were constructed successfully.
    Additional Details
    A total of 1 chains were built. The highest quality chain ends in root certificate CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
    Elapsed Time: 39 ms.
    Analyzing the certificate chains for compatibility problems with versions of Windows.
    Potential compatibility problems were identified with some versions of Windows.
    Additional Details
    The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 5 ms.
    Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.
    Additional Details
    The certificate is valid. NotBefore = 2/24/2014 3:11:57 PM, NotAfter = 2/24/2016 3:11:57 PM
    Elapsed Time: 0 ms.
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.
    Additional Details
    Accept/Require Client Certificates isn't configured.
    Elapsed Time: 371 ms.
    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
    Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
    Additional Details
    Elapsed Time: 241 ms.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://paidwarranty.com:443/Autodiscover/Autodiscover.xml for user [email protected].
    The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
    Additional Details
    A Web exception occurred because an HTTP 404 - NotFound response was received from IIS7.
    HTTP Response Headers:
    Content-Length: 5401
    Cache-Control: private
    Content-Type: text/html; charset=utf-8
    Date: Mon, 02 Mar 2015 14:58:45 GMT
    Server: Microsoft-IIS/7.5
    X-Powered-By: ASP.NET
    Elapsed Time: 241 ms.
    Attempting to test potential Autodiscover URL https://autodiscover.paidwarranty.com:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.
    Additional Details
    Elapsed Time: 5175 ms.
    Test Steps
    Attempting to resolve the host name autodiscover.paidwarranty.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 157.56.234.137, 157.56.244.217, 157.56.236.89, 157.56.232.9
    Elapsed Time: 327 ms.
    Testing TCP port 443 on host autodiscover.paidwarranty.com to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
     <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl01_ctl01_tmmArrow">Tell
    me more about this issue and how to resolve it</label>
    Additional Details
    A network error occurred while communicating with the remote host.
    Elapsed Time: 4847 ms.
    Attempting to contact the Autodiscover service using the HTTP redirect method.
    The attempt to contact Autodiscover using the HTTP Redirect method failed.
    Additional Details
    Elapsed Time: 995 ms.
    Test Steps
    Attempting to resolve the host name autodiscover.paidwarranty.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 157.56.234.137, 157.56.244.217, 157.56.236.89, 157.56.232.9
    Elapsed Time: 16 ms.
    Testing TCP port 80 on host autodiscover.paidwarranty.com to ensure it's listening and open.
    The port was opened successfully.
    Additional Details
    Elapsed Time: 111 ms.
    The Microsoft Connectivity Analyzer is checking the host autodiscover.paidwarranty.com for an HTTP redirect to the Autodiscover service.
    The redirect (HTTP 301/302) response was received successfully.
    Additional Details
    Redirect URL: https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
    HTTP Response Headers:
    Connection: close
    Pragma: no-cache
    Cache-Control: no-cache
    Location: https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
    Elapsed Time: 137 ms.
    Attempting to test potential Autodiscover URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.
    Additional Details
    Elapsed Time: 729 ms.
    Test Steps
    Attempting to resolve the host name autodiscover-s.outlook.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 132.245.64.242, 132.245.3.130, 132.245.92.226, 132.245.82.50, 132.245.81.194, 132.245.81.130, 132.245.88.194
    Elapsed Time: 17 ms.
    Testing TCP port 443 on host autodiscover-s.outlook.com to ensure it's listening and open.
    The port was opened successfully.
    Additional Details
    Elapsed Time: 53 ms.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
    Additional Details
    Elapsed Time: 221 ms.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover-s.outlook.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
    Elapsed Time: 127 ms.
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name autodiscover-s.outlook.com was found in the Certificate Subject Alternative Name entry.
    Elapsed Time: 1 ms.
    Certificate trust is being validated.
    The certificate is trusted and all certificates are present in the chain.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
    One or more certificate chains were constructed successfully.
    Additional Details
    A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
    Elapsed Time: 38 ms.
    Analyzing the certificate chains for compatibility problems with versions of Windows.
    Potential compatibility problems were identified with some versions of Windows.
    Additional Details
    The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 5 ms.
    Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.
    Additional Details
    The certificate is valid. NotBefore = 1/21/2015 10:45:26 PM, NotAfter = 1/21/2016 10:45:26 PM
    Elapsed Time: 0 ms.
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.
    Additional Details
    Accept/Require Client Certificates isn't configured.
    Elapsed Time: 158 ms.
    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
    Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
    Additional Details
    Elapsed Time: 277 ms.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user [email protected].
    The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
    Additional Details
    An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name
    (UPN).
    HTTP Response Headers:
    request-id: d823479c-c259-4474-8b3f-df60b4898533
    X-CasErrorCode: UnauthenticatedRequest
    X-FEServer: BY2PR12CA0033
    Content-Length: 0
    Cache-Control: private
    Date: Mon, 02 Mar 2015 14:58:53 GMT
    Set-Cookie: ClientId=GILRU7BQ40ROHZE90FEIA; expires=Tue, 01-Mar-2016 14:58:54 GMT; path=/; secure; HttpOnly
    Server: Microsoft-IIS/8.0
    WWW-Authenticate: Basic Realm=""
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 276 ms.
    end
    I've enabled basic authentication on the RPC virtual directory on the Exchange CAS in IIS and then restarted IIS, as suggested in another forum (https://social.technet.microsoft.com/Forums/exchange/en-US/69d83444-0528-4e39-a5e9-eb9040501be1/remote-connectivity-analyzer-problem?forum=exchangesvr3rdpartyappslegacy)
    and am still getting the same results from the Remote Connectivity analyzer.
    On a side note, we have reviewed multiple Exchange Deployment Assistance, including the one that you referred to, and are attempting a cutover migration.

  • How to Configure MS Exchange 2007 CCR and SCC Cluster in a single system

    Hi i want to configure ms-exchange 2007 server for both SCC and CCR. i have two Windows Server 2008 on running on my hyper-v. by using cluster on both hyper v i want to install MS-Exchange 2007 for both SCC and CCR. ideally one windows server 2008 has
    Active Nodes and another one has passive nodes. please guide me as i am new in the field

    Duplicate of
    http://social.technet.microsoft.com/Forums/exchange/en-US/edea43a1-59b4-4d26-9b41-76d0f4677095/how-to-configure-ms-exchange-2007-ccr-and-scc-cluster-in-a-single-system?forum=exchangesvrgenerallegacy#c6e08365-c01a-40aa-a8bc-94219757ef13
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Need to send mail from Microsoft Exchange 2007 account(different from Gmail) on behalf of another Gmail ID. How to configure that ?

    I have a Gmail ID (e.g [email protected])
    I have a Exchange ID (e.g  [email protected])
    I need to configure exchange account (2007)  such that I can send a mail from my Exchange account but at the receiver end it looks like it was sent from  ([email protected]).
    Both the accounts are my accounts.
    I need this because I do not have access to my Gmail account from place where I access the internet and I need to send the mails from my Gmail account only.

    So you want to spoof your e-mail address.
    You can make your Exchange server send as any address you want.  Just create a different mailbox with that address as the primary (reply) address.  It has to be a different account.
    However, be aware that many systems to which you send such mail to will bounce it as suspected spam because they'll detect that your server is sending mail from Gmail but your server is not Gmail.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2007 - 2010 Outlook doesn't autodiscover after mailbox move

    We currently are in the process of migrating from Exchange 2007 to 2010.  When I move a mailbox to 2010, Outlook (2010 in this case), fails to connect to the new environment.  Restarting outlook does not help.  I am forced to change the
    servername in the mail applet.  How can we make this happen automagically?

    That URL points to the autodiscover.xml page on the 2010 CAS servers. Returns the typical
    <?xml version="1.0" encoding="utf-8"
    ?>
    - <Autodiscover
    xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    - <Response>
    - <Error Time="01:46:57.9070185"
    Id="814683946">
      <ErrorCode>600</ErrorCode>
      <Message>Invalid Request</Message>
      <DebugData
    />
      </Error>
      </Response>
      </Autodiscover>

  • Snow Leopard and Exchange 2007 Configuration Issues

    I know this topic may have been covered in here previously but I have yet to find a solution.
    Here is the background. Our CEO has a Mac Book and two weekends ago he updated to Snow Leopard and now wants to use the Mail client on his Mac rather than OWA to get his email. We have Exchange 2007 (I am the Admin) and have all the latest patches and Roll Ups installed. We run OWA without issue and have 10 iPhones working perfectly (i realized they use different technology to sync). I enabled EWS by following this link http://technet.microsoft.com/en-us/library/bb201695.aspx and this is the actual command i used:
    Set-WebServicesVirtualDirectory -identity exchaname\EWS* -externalurl https://webmail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$True
    Seems to have run properly and there are no errors reported.
    Now when I go to connect using the Mac it does not Auto Discover and I must enter manually. I enter what i think it needed and its not working. On the Account Information Tab I have the following:
    Description: generic name
    Email Address: [email protected]
    Full Name: The Person's Name
    Internal Server: webmail.domain.com *Not sure what should be here
    External Server: Webmail.domain.com *Again not sure if this is correct
    Username: AD user name Also tried domain\username
    Password: AD password
    Ougoing Mail Server: not sure what should be here
    Next is the Mailbox behavior Tab:
    Did not change anything
    Advanced Tab:
    Internal Server Path: EWS/Exchange.asmx
    Port:80 SSL unchecked
    External Server: EWS/Exchange.asmx
    Port: 80 SSL unchecked
    I get no connections and I am sure somehting is not correct in the above but I am lost and new to Exchange as it is. Also new to Mac's
    Help Please

    We are already using webmail.domain.com for our OWA URL, well actually it is webmail.domain.com\OWA. Would I need one for the EWS & Autodiscover to use webmail.domian.com\ews?
    We have rules in the firewall for Exchange and OWA. Would we need another for this?

  • Exchange 2007 configure didn't sync

    We have 2 hub server and when I update the receive connector IP from Server A, if i login server B, I cannot see the update.
    I am going to reboot it. but I would like to know is it possible to check? because in the exchange console, it didnt have any error
    After I enable the log in the exchange, I saw 2 exchange server reference 2 different DC and the topology version are not same
    Configuration Domain Controller: DC123
    Topology Version 3124, Topology provider: DSAccessTopologyProvider.
    Not sure is it related?
    Thanks

    Hi Yeung,
    I have an Exchange 2007 and 2010 coexistence environment. I notice that every Hub Server has its own receive connectors and doesn't see other connectors from other servers.
    Based on my knowledge, you have saw the changes in Server A, because the changes only happen on Receive Connector of Server A, not Receive Connector of Server B.
    If I have anything misunderstanding, please don't hesitate to let me know.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

    I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

    All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
    A. For local clients
    You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
    Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml" 
    Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
    B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
    If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
    If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
    Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

Maybe you are looking for

  • Web Site Search Engine

    Hi, I was wondering if someone could help me locate a code for a search engine of my web site. My dilemma is, most of the search engines I've located search the web. This's not what I want. I'm looking for a search engine where you can select from a

  • Function module to get due date by terms of payment

    Hi, Is there any function module which can give me the due date when I pass 1) Terms of payment 2) Baseline date Read the terms of payment and use the properties of the terms of payment ( Like Fixed date )  to get to the due date. Thanks in advance.,

  • Landscape contact sheet?

    Anyone else noticed that selecting the "Contact Sheet" style in the print dialog resets your page orientation to landscape? Does't seem to be a way to print landscape contact sheets in iPhoto 6.

  • Setting up FTPS

    Dear all, I have a requirement where in have to enable FTPS in SAP XI System as well as the remote FTP server. Can some one please list down the steps required to execute an end to end scenario involving FTP(S). Apart from this query, I had some ques

  • PuP price not changed in Material master

    Hello All experts I have one question about the material ledger related transaciton, I have a Material with 2+V (price deter. and price control) setting in Material master data in Accounting 1 TAB. And material ledger is active for this material, the