locked
Removing exchange from orphaned site RRS feed

  • Question

  • Hi All, 

    I appreciate this subject has been covered a number of times but I can't find answers for my particular situation, which is... 

    We've had to separate a site from an area wide service. This needed to be done quickly and we had to basically cut the link to the centralised services and seize FSMO roles etc to the "orphaned" site. 

    Up to the separation the site relied on centralised exchange services (no exchange installed at the site), and as part of the separation they have moved on to the MS Cloud email service. 

    We are now in the situation where AD at the site contains all the old exchange references and it seems to be causing autodiscover to fail. Basically autodiscover picks up outlook.com correctly but then picks up something (we presume from AD) and ponts autodiscover to the local DC and the autodiscover process fails. 

    My questions are therefore: 
    1. how can we get autodiscover to stop picking up the local DC 
    2. How can we (do we need to) remove exchange from AD 
    - if we remove exchange from AD would we have to use the unsupported ADSIEdit method or can we run the exchange set up on a DC (bearing i mind it doesn't have exchange installed) and somehow remove the entries from AD that way? 

    Look forward to your help!
    Tuesday, February 28, 2012 9:09 PM

All replies

  • Hi

    If you have a look in ADSIEdit at the following location it will probably have the URL for the old server: CN=Services, CN=Microsoft Exchange,CN=First Organization (YourOrg),CN=Administrative Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Servers,CN=YourServer,CN=Protocols,CN=Autodiscover.

    Cheers, Steve

    Tuesday, February 28, 2012 10:07 PM
  • Hi Steve,

    Thanks for the reply. I've checked and there are the 4 now uncontactable CAS servers each of which has an autodiscover URL pointing to the specific CAS server under the serviceBindingInformation - do you suggest this is changed / removed?

    That said; I've done some further testing (outlook 2007 client using autodiscover to outlook.com) and it appears that autodiscover works, in that the "Establish network connection" and "search for server settings" part of the process is successful, however when it gets to the "log on to server" part it is prompting to log on to the local domain controller rather than outlook.com account.

    If I use the outlook.com username and password it fails and if I use the local domain credentials I get "The name cannot be matched to a name in the address list"

    Everything works when users are at home and not connected to the domain which is why I'd been looking down the AD / previous exchange set up to resolve this. 

    KW

    Wednesday, February 29, 2012 12:03 AM
  • Ok - I bit the bullet and removed the Exchange org from AD using ADSIEdit and it made no difference at all!

    Autodiscover is still prompting to log on to the local domain controller when it gets to the "log on to server".

    I'm flummoxed now!

    I've checked through the registry on a workstation and been through DNS but all reference to autodiscover say nothing about the local DC. NSLookups resolve and barring the "log on to server" everything appears to be working. 

    Any assistance or guidance would be really appreciated.

    KW

    Wednesday, February 29, 2012 5:33 PM