How to remove internal autodiscover record

Posted on 2012-08-15
Last Modified: 2012-08-21
Hi all,

I inherited a Windows 2008 SBS installation and am migrating their Exchange to a hosted environment. After transferring MX records and setting up my first Outlook profile, I discovered that it prompted me for a login and password every time I opened Outlook.

The hosted firm determined that an internal autodiscover record is causing the problem. When their automated Outlook configuration utility is run, it should be automatically establishing Exchange Proxy settings that point to their server. However, after many attempts to manually add this entry, it keeps reverting back to the internal setting.

The internal setting that keeps appearing is  When I look in DNS on the server, I see the standard domain.local forwarding zone, but I also see a forwarding zone called, however, I don't see any autodiscover record in that zone.

How can I remove the internal autodiscover that keeps overriding the hosted firms autodiscover?

Thanks in advance for the help.

Question by:tgreendyk
    LVL 18

    Expert Comment


    Please try to create a CNAME of autodiscover.domain.local and point to
    LVL 26

    Expert Comment

    by:Leon Fester
    Autodiscover records are SRV records.
    You won't find them from NSLOOKUP, unless you set the type of record to locate.

    set type=srv

    How to configure autodiscover: Should be the same for your hosted solution, just make sure you've got the correct DNS zones.
    LVL 1

    Author Comment

    Thanks for the posts!

    Yesterday I got Microsoft's tech support to "help" me and now they've completely broken RWW -- they turned off MSExchange autodiscover and people can't see any available servers to connect to when they use the SBS RWW address.

    So I have to dig out from that now!

    LVL 36

    Expert Comment

    You have probably been experiencing the AD connection point, not an autodiscover record.

    If Microsoft PSS "broke" RWW while supporting you, then they should also fix RWW as part of the support call.
    LVL 1

    Author Comment

    Yes, particularly since it was a paid incident. I have a scheduled call with them shortly.

    Since they provided them in the followup email, here's what they did:

    ¿We repro the issue & found the url for autodiscover was changing to
    ¿We Opened the Exchange Management Shell on server & changed the internal url for autodiscover to the external exchange , still same issue
    ¿Found an Autodiscover record in DNS , removed it but had same problem
    ¿For Test purpose we stopped SBS web app & checked , Outlook worked fine
    ¿Went to SCP in Active Directory - ADSI Edit - Configuration - CN=Configuration,DC=Server,DC=local - CN=Services-CN=Microsoft Exchange-CN=First Organization-CN=Administrative Groups-CN=Exchange Administrative Group  (FYDIBOHF23SPDLT)-CN=Servers-CN=Server Name-CN=Protocols-CN=Autodiscover & removed the from there
    ¿Checked the Outlook now , it worked fine
    ¿Also stopped the Autodiscover app pool
    ¿We checked on other Outlook Client , were still getting Password Prompt
    ¿Recreated profile & were able to get Outlook Working.
    LVL 36

    Expert Comment

    So at least they got to the Service Connection Point :-)

    Not sure if Exchange will recreate it though.

    If it does, I would change it to the new hosted service URL and then modify the security on it to prevent it being overwritten by Exchange.
    LVL 1

    Accepted Solution

    Well don't I feel like an idiot! Definitely one of the most boneheaded things I've done in a while! :-)

    Turns out there was no problem at all -- I was doing all my testing using Firefox! Everything worked fine in IE.

    As for the user who reported it not working, when I called this morning he said "oh, yeah, it's working fine now".

    Thanks for the comments, though, everyone.

    (I need to get some sleep I think)
    LVL 1

    Author Closing Comment

    Resolved with Microsoft support - needed to use IE to test.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Shouldn't all users have the same email signature?

    You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

    Email signatures have numerous marketing benefits. Here are 8 top reasons to turn your email signature into a marketing channel.
    Granting full access permission allows users to access mailboxes present in their database. By giving full access permission one can open and read the content of any mailbox but cannot send emails from that mailbox.
    To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
    In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now