Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, September 30, 2015 6:14 AM
I asked this question to the Microsoft community and they told me I needed to ask it here.
Firstly, I see that I can connect to the Exchange server at work using the Windows Mail app. That is nice.
Unfortunately, the app tends to freeze when I am composing a message. For some reason hitting the Windows key will defrost the app long enough for me to type in a few more words...it would be nice if I could use Outlook 2016, but for some, unknown to me, reason the settings I used to configure the Windows 10 mail app do not also allow me to connect to Exchange using Outlook 2016.
The best workaround I have found, to the lack of connectivity with Outlook 2016 and the freezing of the Windows 10 mail app, is to use Thunderbird to connect to our Exchange server via a third party plug-in called ExQuilla which actually uses the Outlook Web App settings.
Is this how the Windows 10 Mail app is connecting to Exhchange? That is, does the Windows 10 mail app basically use the Outlook Web App settings and run those through the email client?
All replies (10)
Wednesday, September 30, 2015 7:52 PM ✅Answered | 1 vote
I just read on a Microsoft Community thread that if your Exchange server isn't setup for autodiscover, then Outlook 2016 won't connect to the mailbox. Not sure if this is true or not; I'll have to try and validate this. You didn't mention what version of Exchange you're trying to connect to. Not sure why the Mail App is locking up on you.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.
Wednesday, September 30, 2015 7:54 PM ✅Answered | 1 vote
The following table identifies the mailbox clients that are supported for use together with each version of Exchange. Supported clients are identified by an X character.
Client | Exchange 2016 | Exchange 2013 SP1 and later | Exchange 2010 SP3 | Exchange 2007 SP3 |
---|---|---|---|---|
Outlook 2003 |
X |
X |
||
Outlook 2007 |
X2 |
X |
X |
|
Outlook 2010 |
X5 |
X3 |
X |
X |
Outlook 2013 |
X5 |
X |
X |
X |
Outlook 2016 |
X5 |
X |
X |
|
Outlook for Mac for Office 365 |
X5 |
X |
X |
|
Windows Phone 7 |
X |
X |
X |
|
Windows Phone 7.5 |
X |
X |
X |
|
Windows Phone 8 |
X |
X |
X |
X |
Windows Phone 8.1 |
X |
X |
X |
X |
Entourage X |
X1 |
|||
Entourage 2004 (DAV) |
X2 |
|||
Entourage 2008 (DAV) |
X2 |
|||
Entourage 2008 (EWS) |
X4 |
X4 |
X4 |
X |
1WebDav: Contacts, Events, IMAP: Mail
2Requires Outlook 2007 Service Pack 3 and the latest public update.
3Requires Outlook 2010 Service Pack 1 and the latest public update.
4EWS only. There is no DAV support for Exchange 2010.
5Supported with the latest Office service pack and public updates.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.
Wednesday, September 30, 2015 8:00 PM ✅Answered | 2 votes
Here's why: https://technet.microsoft.com/en-us/library/cc179110%28v=office.16%29.aspx? and also this: http://www.slipstick.com/outlook/exchange-account-set-up-missing-in-outlook-2016/
Additions/Changes in Outlook 2016
Addition/change | Description |
---|---|
AutoDiscover profiles |
Exchange connectivity settings are now retrieved directly from AutoDiscover instead of the registry, making profiles more reliable. As a result, Outlook 2016 administrators must configure AutoDiscover. |
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.
Wednesday, September 30, 2015 7:42 PM
Connecting to Exchange the mail app would default to Exchange Active Sync, basically same protocol that a smart phone would use.
Shawn Keene
Wednesday, September 30, 2015 7:53 PM
That is interesting. When I launch Outlook 2016 I see the choice for Outlook.com or Exchange Active Sync compatible service. I wonder why, then, I cannot connect to our Exchange server with Outlook 2016 the same way I can with the Windows 10 Mail App.
Wednesday, September 30, 2015 7:55 PM
Ahh I'll have to ask the never-very-friendly IT guys if the server is set for autodiscover. I am not sure, but I think they are running 2013. (I'll ask that too.)
Wednesday, September 30, 2015 7:57 PM
In my experience it connects easier if you choose the "manually select server type" and then pick the Exchange option, rather than letting it auto-detect.
Shawn Keene
Wednesday, September 30, 2015 8:01 PM
Yeah, but they guard that information like gold. The IT guy's REALLY do not want people connecting to the server on a machine they did not setup and can monitor. Their solution is Outlook Web Access (or Outlook Web App I guess it is now called.) I just do not like the web mail interface and since I do a lot of work at home anyway...
Wednesday, September 30, 2015 8:24 PM
You have to authenticate into Exchange (w/out going into details); just anyone can't open Outlook and it automatically connects into the Exchange server. If you're using a company owned PC/laptop, there's no reason they can't do it. If you're using a personally owned computer, then that's where is usually becomes an issue for compliance and security reasons. Good luck either way.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.
Thursday, April 20, 2017 8:19 PM
It's True you need to Configure Autodiscover, (It's Already configured by default in the Server). What make it not working is the fact that you need to add a CNAME in the DNS Configuration where the domain name is hosted.
Add cname : autodiscover.domain.com
Add cname : autodiscoverredirect.domain.com
Add SRV Record : _autodiscover._tcp and target it to your domain name
Test with the Remote connectivity Analyzer or try with outlook directly.
Everything should work.
Mathieu Lachance IT Consultant Services Informatiques Martin Roy Inc. Tél. : (418) 843-6603 Fax : (418) 843-0118 Courriel : [email protected]