Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Solved
Exchange 2010 issues
Posted on 2012-12-24
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.
[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
-
4
2
- +3
10 Comments
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.
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??
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.
Active today
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.
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?)
Active 1 day ago
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.
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.
Featured Post
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.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012.
Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Course of the Month11 days, 8 hours left to enroll
718 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.