Exchange 2007 - oullook 2010/07- autodiscover internal users


Would really appreciate any help on this.

This happened to one of our clients:
After installing outlook 2010 on internal workstations (running exchange 2007) I started getting the typical non matching certificate problem error. Been there, fixed after changing autodiscover internal URLs.

Now, on this particular case that didn't work. It was only after changing the external URLs that the certificate error stopped. Now how is that possible if these were internal domain users and not outlook anywhere clients.

Also, I found that outlook anywhere kept getting checked and the proxy settings were also being populated. Again, why would that happen with internal users.

It looks llike these users, for some reason were being treated as external users ??


The proxy settings problem happened also on another site, also running exchange 2007 but outlook 2007 in this case.  No certificate error (no clue why because I havent changed the URIs, maybe that error only shows up with outlook 2010??) but again the proxy settings were being filled.

Thanks so much for any help.
D.
reliantcorpAsked:
Who is Participating?
 
FeebleminderConnect With a Mentor Commented:
This issue is one of annoyance and something that one of my clients wasn't utilizing, so was able to disable it. Here is a link to the topic with fix suggestions:

http://ilantz.wordpress.com/2009/06/18/prevent-outlook-anywhere-aka-rpc-over-http-from-being-automaticly-configured-in-exchange-2007-with-autodiscover/

Hope this works for you!
0
 
praveenkumare_spCommented:
AFAIK autodiscover brings up the urls.. if ur network connection is slow or some thing like that, instead of boing a rpc over tcp/ip , it does RPC over HTTPS. and it will start using external urls and it describes ur issue.

Make sure there is good connectivity and no network issues in ur org.

even  if u want u can try and remove EXPR using the following command

Get-outlookprovider –identity EXPR | remove-outlookprovider
after this recycle the application pool of AutoDiscover in IIS

but be informed that no Otlook anywhere clients will be able to automatically configure the profile, they can only do manually
0
 
endital1097Commented:
0
 
praveenkumare_spCommented:
so u resolved ur issue by doing the following right  ??
remove EXPR using the following command

Get-outlookprovider –identity EXPR | remove-outlookprovider
after this recycle the application pool of AutoDiscover in IIS

reply is that was not what fixed the issue?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.