Solved

Office 365 Hybrid Autodiscover DNS

Posted on 2014-12-22
8
1,133 Views
Last Modified: 2015-01-10
Hi

Recently we got Office 365, Exchange online hybrid solution.
We will both have on premise users with Exchange and office 365 users.
We have split brain DNS.

Struggling a bit with autodiscover.
How can we both have autodiscover for Exchange and autodiscover for Office 365 ?

Tried creating a cname to test:
autodisover.contoso.com -> outlook.autodiscover.com
*Cannot be created because it collides with AA Record autodiscover.contoso.com


Regards.
0
Comment
Question by:Lenblock
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
8 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40512495
Hi Lenblock,

In a hybrid situation you would just point your autodiscover record to your on premise Exchange servers. Through the hybrid configuration your on premise servers know what mailboxes are local and what are in the cloud.
0
 

Author Comment

by:Lenblock
ID: 40512505
Hi

Tried that and we get a timeout when trying to configure Outlook.
Any idea where to start looking ?

Regards.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40512507
When you say a timeout, is it working for the on premise users but not the cloud users? Or is it not working for anyone?

Can you try the Autodiscover test at www.exrca.com. Try the test for an on premise mailbox and a cloud mailbox and post the results here.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:Lenblock
ID: 40512614
Testing internally now with Outlook, also did a test exrca and it failed.
Two of our services on the ADFS-Proxy is failing to start.

Active Directory Federation Services
The federation server proxy could not be started.
Reason: Error retrieving proxy configuration from the Federation Service.

Additional Data
Exception details:
An error occurred when attempting to load the proxy configuration.


Web Application Proxy Service
The Web request failed because the web.config file is malformed.

User Action:
Fix the malformed data in the web.config file.

Exception details:
Root element is missing. (C:\Windows\ADFS\Config\microsoft.identityServer.proxyservice.exe.config)
Root element is missing.


Checked the file "microsoft.identityServer.proxyservice.exe.config", size 2kb but it's empty.
0
 

Author Comment

by:Lenblock
ID: 40512769
Result from EXRCA (translated from norwegian)

Received a HTTP 401 Unauthorized response from remote ISA Server . This is usually due to an incorrect username or password. If you try to log on to an Office 365 service , ensure that you use your full user principal ( UPN ) .
HTTP response headers :
Connection: Keep- Alive
Pragma : no-cache
Content-Length : 2073
Cache -Control : no-cache
Content-Type : text / html
WWW Authenticate : Basic realm = " "
Elapsed time : 1014 ms .


Checks for a CNAME record for Autodiscover in DNS for the domain contoso.com Office 365 .
Unable to validate CNAME record for Autodiscover in DNS. If the mailbox is not in Office 365 , you can ignore this warning.
There is no Autodiscover CNAME record for your domain contoso.com .
Elapsed time : 182 ms .
0
 
LVL 41

Expert Comment

by:Vasil Michev (MVP)
ID: 40513487
Definitely look at the AD FS issue first, manually editing those files can easily mess up the XML formatting. EO will always hit the AD FS proxy server, so that explains your autodiscover troubles.
0
 

Accepted Solution

by:
Lenblock earned 0 total points
ID: 40531428
Hi

Autodiscover issue was caused by the ADFS-proxy.
Reinstalled the web application remote proxy role, reconfigured it and it seems to be working as it should.

Outlook now works internally/externally with Office 365.
Tested autodiscover with exrca, and it's all green.

Regards.
0
 

Author Closing Comment

by:Lenblock
ID: 40541792
Reinstalling the role on the ADFS-Proxy solved the issue.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

It’s the first day of March, the weather is starting to warm up and the excitement of the upcoming St. Patrick’s Day holiday can be felt throughout the world.
This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
In a previous video Micro Tutorial here at Experts Exchange (http://www.experts-exchange.com/videos/1358/How-to-get-a-free-trial-of-Office-365-with-the-Office-2016-desktop-applications.html), I explained how to get a free, one-month trial of Office …
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

717 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