Solved

Office 365 Hybrid Autodiscover DNS

Posted on 2014-12-22
8
936 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
  • 5
  • 2
8 Comments
 
LVL 30

Expert Comment

by:Gareth Gudger
Comment Utility
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
Comment Utility
Hi

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

Regards.
0
 
LVL 30

Expert Comment

by:Gareth Gudger
Comment Utility
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
 

Author Comment

by:Lenblock
Comment Utility
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
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

Author Comment

by:Lenblock
Comment Utility
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 38

Expert Comment

by:Vasil Michev (MVP)
Comment Utility
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
Comment Utility
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
Comment Utility
Reinstalling the role on the ADFS-Proxy solved the issue.
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
If you don't know how to downgrade, my instructions below should be helpful.
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…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

743 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

8 Experts available now in Live!

Get 1:1 Help Now