Exchange 2010 issues

I have an Exchange server with some issues, which I think they are related.

The Exchange server used to be hosted by a trusted domain in a different site, we recently moved it over to the local LAN, and it is now part of the same domain and site as the rest of the network.

The issues we are having are as follows:

1. Autodiscover configures Outlook using 'HTTP Proxy'. Any attempt to change that so that Outlook should connect to the Exchange server using the local DNS name, reverts itself back when Outlook is restarted.

2. The GAL does not update on the client Outlook. Forcing an update does not help.

3. Occasionally, 'some' users keep on getting popups to enter an Exchange password..

Please advise how to fix auto-discover first.

Thank you.
clesinAsked:
Who is Participating?
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
If you have Outlook Anywhere enabled in Exchange, then all clients will get the configuration for Outlook Anywhere. However that does NOT mean they will use it.
To confirm what method is being used to connect, once Outlook has started, right click on the Outlook icon while holding down CTRL and choose Connection Status. If the protocol is HTTPS then Outlook Anywhere is being used, if it is TCP then it is not.

As for the autodiscover issues, if you had Exchange in another forest then your forest might have been setup to allow autodiscover to work. It would be something like the method outlined here: http://blogs.technet.com/b/exchange/archive/2011/03/04/3412075.aspx

Simon.
0
 
Tony GiangrecoCommented:
Initially I would check the dns entried and make those corrections. Then verify the dns replicates. After that cycle, I'd check your certificates and see if the domain changes the server went through require your certificates to be regeneratd or corrected.
0
 
clesinAuthor Commented:
What do you mean by DNS replicates??

And also, how/where would I change the auto-configure settings to NOT configure outlook with HTTP??
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Tony GiangrecoCommented:
No Check and change (if necessary) the dns each Pc uses in TCP/IP properties of the nics.
0
 
clesinAuthor Commented:
All the PC's are pointing to the local DNS server, and they all have the correct entry for the Exchange server.
0
 
SeaSenorCommented:
have you manually set up a profile putting in the exchange server name?

if not, try that, and see if it keeps the settings.

Also, was the Outlook/Office install set up using the OCT? (office customization tool)

I have seen where that has an old entry causing it to look for the old server.
0
 
davorinCommented:
Here is a couple of links about autodiscover hoping they will help you.
http://blogs.technet.com/b/ilvancri/archive/2010/02/03/some-autodiscover-fun.aspx
http://www.networksteve.com/exchange/topic.php/How_Do_I_change_settings_set_by_autodiscover/?TopicId=17388&Posts=2
http://www.networksteve.com/exchange/topic.php/Is_there_a_way_to_disable_Autodiscover_for_Outlook_or_Exchange_2/?TopicId=30703&Posts=4

I would firstly try to check and correct autodiscover configuration. Check used certificates also.
In one case the certificate was incorrectly issued and the decided that they will wait with wrong certificate until it expires, so I was "forced to" disable internal autodiscover setting ExcludeScpLookup registry entry to 0 on problematic end user PCs. Complete path is in first link.
Hope this will help you a little bit.
0
 
clesinAuthor Commented:
I did try and create a new outlook profile, configuring it manually. No, I did not use OCT.

And yes, it does revert back to the http settings automatically.
0
 
sirakovCommented:
it seems that outlook can't find SCP and falls back to use HTTP
in  exchange power shell run:
get-clientAccessServer | fl *uri*

Check the returned URL and see if you can access it with a client ... (any proxy? or dns issues?)
0
 
clesinAuthor Commented:
I ended up disabling Outlook Anywhere on this Exchange 2010 server since it was causing me more trouble than what it was worth..

All seems to work now.
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.