asked on
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.
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.
Windows Server 2008Exchange
Last Comment
clesin
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.
ASKER
What do you mean by DNS replicates??
And also, how/where would I change the auto-configure settings to NOT configure outlook with HTTP??
And also, how/where would I change the auto-configure settings to NOT configure outlook with HTTP??
No Check and change (if necessary) the dns each Pc uses in TCP/IP properties of the nics.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ASKER
All the PC's are pointing to the local DNS server, and they all have the correct entry for the Exchange server.
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.
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.
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.
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.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
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.
And yes, it does revert back to the http settings automatically.
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?)
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?)
ASKER CERTIFIED SOLUTION
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
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 questionASKER
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.
All seems to work now.
Your help has saved me hundreds of hours of internet surfing.
fblack61