?
Solved

Office 365 Hosted Exchange

Posted on 2014-01-31
4
Medium Priority
?
291 Views
Last Modified: 2014-05-03
We are in the process of moving to hosted. Exchange. The autodiscovery record has been setup on the external DNS and when we are outside of the domain we can setup/connect and connect with outlook no problem. Internally it always connects to the internal email system. The dns internally is domain.com. I've set a cname record autodiscover.domain.com->autodiscover.outlook.com but this does not seem to work. It authenticates me using the hosted exchange email address and password but then connects to the internal exchange and not the hosted exchange.

The internal domain should have been domain.local but this is inherited. How do I bypass the internal Exchange server and use hosted exchange?
0
Comment
Question by:mail2clk
  • 3
4 Comments
 
LVL 26

Expert Comment

by:ronnypot
ID: 39823785
Hi,

This is probably because outlook is resolving the connection from AD or from the client computers registry, These are always checked before using the DNS record.

Depending on if your server is Exchange 2003 (does not use autodiscover) or 2007 or higher check this article: http://www.allcloudallthetime.com/2012/10/exchange-2007-to-office-365-mailbox-migration-autodiscover.html

Also check: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Autodiscover\RedirectServers as mentioned over here: http://community.office365.com/en-us/forums/158/t/45179.aspx
0
 

Author Comment

by:mail2clk
ID: 39832478
We have Exchange 2003 Standard. I understand that exchange 2003 does not use autodiscover. I checked HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Autodiscover\RedirectServers and key entered is autodiscover-s.outlook.com. I changed it to autodiscover.outlook.com and we still have the same issue.

Does anyone have any other suggestions?
0
 

Accepted Solution

by:
mail2clk earned 0 total points
ID: 39865318
I created a CNAME record autodiscover for the internal domain and pointed it to autodiscover.outlook.com. The  ipconfig /flushdns [RETURN] then ipconfig /registerdns [RETURN]. This resolved the issue but you will lose connectivity to the onsite exchange.
0
 

Author Closing Comment

by:mail2clk
ID: 40039013
It resolved the issue
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
Exchange administrators are always vigilant about Exchange crashes and disasters that are possible any time. It is quite essential to identify the symptoms of a possible Exchange issue and be prepared with a proper recovery plan. There are multiple…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

850 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