Avatar of Evil_RSA
Evil_RSA
Flag for United States of America asked on

Outlook 2007 & 2010 connecting to Exchange 2010 via HTTP on internal LAN

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?
ExchangeOutlook

Avatar of undefined
Last Comment
MegaNuk3

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Akhater

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Alan Hardisty

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.
MegaNuk3

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
MegaNuk3

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)
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
SOLUTION
MegaNuk3

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Evil_RSA

ASKER
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.
MegaNuk3

Thanks for the points, I take it that all your Outlook clients were connecting over TCP/IP and not HTTP?
Evil_RSA

ASKER
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!
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
MegaNuk3

No problem, don't forget that we "Experts" learn off this site too, which is the Primary reason I joined...