asked on Migration to Hosted Exchange
I'm going to be moving away from local Exchange this year in favor of hosted. I have a general question about something I don't understand.
My domain.com has an external DNS, but also an internal AD DNS for everything on the inside (same domain name). Externally I have an auto discover record and all that and the Outlook anywhere clients work just fine. I would change to autodiscover record and Outlook clients would begin using the new host.
Now internally on the AD domain I do not have any autodiscover record and all the Outlook clients still automatically connect to my internal exchange server and configure themselves just fine. However, I don't understand how that actually works without an autodiscover record. I'm asking this because I don't know what would be needed to internally make the Outlook clients start connecting to the new external host. I know I would need to add an autodiscover record internally, but would that work and how is it even working now?
My domain.com has an external DNS, but also an internal AD DNS for everything on the inside (same domain name). Externally I have an auto discover record and all that and the Outlook anywhere clients work just fine. I would change to autodiscover record and Outlook clients would begin using the new host.
Now internally on the AD domain I do not have any autodiscover record and all the Outlook clients still automatically connect to my internal exchange server and configure themselves just fine. However, I don't understand how that actually works without an autodiscover record. I'm asking this because I don't know what would be needed to internally make the Outlook clients start connecting to the new external host. I know I would need to add an autodiscover record internally, but would that work and how is it even working now?
ExchangeOutlookEmail Servers
Last Comment
davorin
Outlook at first step is looking for SCP records in AD, if that is not available, then is looking for outodiscover.xml at https:/domain.com/autodiscover/autodiscover.xml, again if there is no record it will move on looking at https:/autodiscover.domain.com/autodiscover/autodiscover.xml, and so on. I hope I will find a link nicely describing the whole procedure.
If you are talking about Ms Exchange online, the you will be able to sync your AD with the cloud.
MX records have nothing to do with autodiscover. It just points internet servers to the server which is responsible to receiving mails for your domain.
If you are talking about Ms Exchange online, the you will be able to sync your AD with the cloud.
MX records have nothing to do with autodiscover. It just points internet servers to the server which is responsible to receiving mails for your domain.
That link is not the one I was talking about, but it may help you:
http://blogs.technet.com/b/kristinw/archive/2013/04/19/controlling-outlook-autodiscover-behavior.aspx
http://blogs.technet.com/b/kristinw/archive/2013/04/19/controlling-outlook-autodiscover-behavior.aspx
ASKER
Okay, so then my Outlook clients must be reading the ad scp records then. That being said, I'm guessing that I'll have to disable scp and add an autodiscover record before the clients will be able to see and configure themselves to the hosted environment.
That sounds about right?
That sounds about right?
ASKER
Have you disabled or removed the autodiscover from the local Exchange server?
Sudeep
Sudeep
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
To answer your question, I am migrating from on premise Exchange 2010 to hosted. No hybrid type situation, all mailboxes will be moved to the cloud.
I will check out those links when I get back a little later.
I will check out those links when I get back a little later.
ASKER
Also, while I realize the process is similar, I'm not moving to Office 365, but a different hosted Exchange host.
I've got all the processes worked out to transfer the mailboxes, it's more to make my local machines ignore the local Exchange environment without completely disabling it, as I will remove the local Exchange environment later after I'm happy that everything was successful
The regkey solution seems like it will work, but a little bit of a pain. Is there a way to disable autodiscover in the local Exchange environment completley (SCP records, everything), but in an easily revertible manner in case everything goes horribly wrong?
I've got all the processes worked out to transfer the mailboxes, it's more to make my local machines ignore the local Exchange environment without completely disabling it, as I will remove the local Exchange environment later after I'm happy that everything was successful
The regkey solution seems like it will work, but a little bit of a pain. Is there a way to disable autodiscover in the local Exchange environment completley (SCP records, everything), but in an easily revertible manner in case everything goes horribly wrong?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I'm sorry folks, something came up and have been busy. So if disable it on the Exchange side via powershell, it should then just use the autodiscover cname record and all should be well?
Last question, if I need to restore the scp lookup for some reason, how do I put it back? I would assume that I would issue the same powershell command with null replaced with the proper entry, but what is the proper entry here?
Last question, if I need to restore the scp lookup for some reason, how do I put it back? I would assume that I would issue the same powershell command with null replaced with the proper entry, but what is the proper entry here?
It should be. The same entry you should have also at certificate used at new exchange server. You can use this tool to test the connectivity: https://testconnectivity.microsoft.com/
You should first check existing entry with Get-ClientAccessServer | fl and look for AutoDiscoverServiceInterna
http://www.shudnow.net/?s=autodiscoverserviceinternaluri
You should first check existing entry with Get-ClientAccessServer | fl and look for AutoDiscoverServiceInterna
http://www.shudnow.net/?s=autodiscoverserviceinternaluri
May be a way is to change the MX record in your local DNS to point to the new external host