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.
Course Of The Month
11 days, 11 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Outlook 2007 & 2010 connecting to Exchange 2010 via HTTP on internal LAN
Posted on 2011-03-04
Hey everyone. I got an odd situation here.
Quick Back story:
Finishing up our Exchange 2007 to Exchange 2010 SP1 migration
Now, all my Outlook clients internally (on the same LAN as my exchange server) have started to self check the Outlook Anywhere checkbox, and have populated the information in there them selves. Is this the new way for all outlook clients to connect or was it something that somehow happened while setting up the server and configuring Active Sync, OWA, and Outlook anywhere in Exchange 2010 / IIS7?
Quick Back story:
Finishing up our Exchange 2007 to Exchange 2010 SP1 migration
Now, all my Outlook clients internally (on the same LAN as my exchange server) have started to self check the Outlook Anywhere checkbox, and have populated the information in there them selves. Is this the new way for all outlook clients to connect or was it something that somehow happened while setting up the server and configuring Active Sync, OWA, and Outlook anywhere in Exchange 2010 / IIS7?
[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
- +1
9 Comments
Active today
This is autodiscover configuring outlook, it is not new it existed on 2007 but maybe it wasnt working in your case, it doesnt mean that the client is using https to connect to exchange it is just setting up outlook anywhere
Active today
Starting with Exchange 2007, Autodiscover was implemented to ease the pain of configuring an account. Outlook 2007 started the client side process off and unless you have upgraded the clients, or didn't configure Exchange 2007 properly, you should have been able to do this with Exchange 2007 too.
If you create a new account with a new e2k10 mailbox, send it some items.
Login to a PC with that username, open outlook, does it autoconfigure? Has connect over HTTP become configured?
Open outlook with /rpcdiag and verify the connections are in fact showing as HTTP
Login to a PC with that username, open outlook, does it autoconfigure? Has connect over HTTP become configured?
Open outlook with /rpcdiag and verify the connections are in fact showing as HTTP
As the others have said already, your Outlook is just autoconfiguring itself as it should do, but it doesn't mean it will be connecting over HTTP
It will by default only try HTTP if the link is slow or it can't connect to exchange over TCP (RPC)
It will by default only try HTTP if the link is slow or it can't connect to exchange over TCP (RPC)
Outlook /rpcdiag
Will show you how Outlook is connecting OR if outlook is already open you can hold down the CTRL key and right click on the Outlook icon in the bottom right hand of your screen and then select the "connection status" option
Will show you how Outlook is connecting OR if outlook is already open you can hold down the CTRL key and right click on the Outlook icon in the bottom right hand of your screen and then select the "connection status" option
The Ctrl+right click on outlook icon in taskbar is an awesome tip that I had no clue about.
Thanks for putting my mind at easy that this is all just outlook and exchange working correctly and by design outlook auto configuring itself to be /ready/ to use Outlook Anywhere if the need should arise, and not that all my clients had in fact /switched/ to using Outlook Anywhere as the default connection.
Thanks for putting my mind at easy that this is all just outlook and exchange working correctly and by design outlook auto configuring itself to be /ready/ to use Outlook Anywhere if the need should arise, and not that all my clients had in fact /switched/ to using Outlook Anywhere as the default connection.
Thanks for the points, I take it that all your Outlook clients were connecting over TCP/IP and not HTTP?
Yeah, I kind of wish Microsoft would have made that a little more obvious, but after opening one of the clients here at work, and then remoting to my client at home off site, I saw the difference in the Connection list with TCP/IP versus HTTPS as the connection type. Thanks for all you guys do!
Featured Post
We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
The video tutorial explains the basics of the Exchange server Database Availability groups.
The components of this video include:
1. Automatic Failover
2. Failover Clustering
3. Active Manager
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month11 days, 11 hours left to enroll
623 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.