Forum Discussion
Setup up autoDiscover In On-Perm DNS to integrate with O365
- Jul 10, 2020
hntaurus Yes, you should do that as well to avoid your clients connecting to the old namespace after migration. In fact, you don't need this anymore and after your cutover, you can decommission Exchange as well.
Thanks a lot for your prompt reply
Do I need to create SRV and CNAME for that auto discover on my Internal DNS as well?
hntaurus please use Exchange Management Shell to change it, not ADSIEDIT 😉
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://autodiscover.outlook.com
Disable-OutlookAnywhere –Server <ServerName>
You only have to change/add the CNAME record in your external DNS after migration.
- aussupportJul 18, 2020Brass ContributorHi Dominik,
I have fully hybrid env with exch2010, and I just run AutoDiscoverServiceInternalUri $Null
So how do I retrieve old value?
TA- Jul 20, 2020
aussupport what do you want to achieve? The old value is often your Autodiscover URL e. g. https://autodiscover.domain.tld/Autodiscover/Autodiscover.xml
- aussupportAug 02, 2020Brass Contributor
It is not setup like that and just need to know the way of identifying the old value? We have different regions and load balancers so DNS got auotdiscover-Nz, autodisocover-aus,and autodiscover-us etc etc..
As
- hntaurusJul 10, 2020Copper Contributor
Thanks a lot for your time
I see you mentioned a command about Outlook Anyehre
DO I need to disable that one as well?
- Jul 10, 2020
hntaurus Yes, you should do that as well to avoid your clients connecting to the old namespace after migration. In fact, you don't need this anymore and after your cutover, you can decommission Exchange as well.
- PeterRisingJul 10, 2020MVP
Good call I agree, I would avoid using ADSIEdit unless you absolutely have no choice. The Exchange Shell method is absolutely the way to go.
- hntaurusJul 10, 2020Copper Contributor
Sure, I'll do it from exchange
and I guess by doing that I should not be worried about outloook clients finding the right path to connect to O365 ?
- PeterRisingJul 10, 2020MVP
Yes that should do the trick for you with internal autodiscover. Any of the mentioned methods to alter the service connection point will work, but it was correct to point out that ADSIEdit is the least desirable way to do it, as you can very easily mess things up in there if you don't know your way around.