• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2179
  • Last Modified:

Exchange 2010 Autodiscover problems

Can anybody help with an Autodiscover problem i'm having between Outlook 2007 (all updates
applied) and Exchange 2010 (all updates applied). Whenever we try to use the OOF feature
from Outlook it always pops up telling us the server is unavailable, if we then run 'Test Email
Autoconfiguration' from Outlook the test fails. If trying to browse to autodiscover we get the following
- <Error Time="08:48:45.9957481" Id="45117063">
  <ErrorCode>600</ErrorCode>
  <Message>Invalid Request</Message>

I've also seen on some websites that i need to check the autodiscover settings in Sites and Services,
looking at that the autodiscover folder is visible but there are no other folders or settings below
that i.e. no SCP details or settings.

Is there any way of re-installing Autodiscover or repairing it or is it tied to a problem with CAS?

any help would be appreciated.
0
PEbuilder
Asked:
PEbuilder
  • 7
  • 7
  • 3
3 Solutions
 
Vipin VasudevanAssociate Infrastructure SpecialistCommented:
0
 
Vipin VasudevanAssociate Infrastructure SpecialistCommented:
This discribe how to recreate Auto discover if at all required

http://technet.microsoft.com/en-us/library/aa996418(EXCHG.80).aspx
0
 
Vipin VasudevanAssociate Infrastructure SpecialistCommented:
If Autodiscover and OAB is running on Http also make these sort of issues

get-autodiscovervirtualdirectory |set-autodiscovervirtualdirectory -autodiscoverserviceinternalurl "https:\\MyExchangeServer.Domain.com/autodiscover/autodiscover.xml

get OAB URL name by
Get-OABvirtualdirectory |fl internalurl,name
If it is http change to https using

get-oabvirtualdirectory |set-oabvirtualdirectory -internalurl httpS://exchange.domain.com/OAB 

run the commands

get-addresslist |update-addresslist

and then
update-globaladdresslist -id:"Default Global Address list"

0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
MegaNuk3Commented:
If your Outlook autoconfig can't find the SCP then you can bypass this with a internal DNS SRV record:
http://support.microsoft.com/kb/940881

You should normally see your SCP through ADSIedit or AD Sites and services under here:
Services\Microsoft Exchange\org\admin groups\e2k10 admin group\servers\CAS\protocols\AutoDiscover

There should be a SCP in the name of the CAS server in there, if you do properties on it and look at the 'ServiceBindingInformation' attribute it should have the AutoDiscover URL e.g. Https://CASnameOnCert/AutoDiscover/AutoDiscover.XML 
0
 
PEbuilderAuthor Commented:
To MegaNuk3;

I've just had a look at the AD Sites and Services, under Protocols the Autodiscover folder is there along with {CAS} folder but in each of them there is no other information.

I have found a link to Autodiscover but it appears under the HTTP folder under protocols.

To All - i am working my through all the solution until i find one that cures the fault may thanks to all.
0
 
MegaNuk3Commented:
The folder that is the name of the CAS server under AutoDiscover is the SCP, do properties on it and look at the attributes and you will see what I mean.

It's objectCategory will be "CN=Service Connection Point..."
0
 
PEbuilderAuthor Commented:
To MegaNuk3

I've follwoed a couple of your suggestions and i have also seen where the configuration is on SCP within AD sites and services.

I was also looking aroud the forum for some other testing and found one from yourself about testing the Outlook Web Services. When i tried this an error reult came back stating 'unauthorised' for the Autodiscover service. Checking on IIS further and found Windows Authentication was disabled on part of IIS.

Because of this i may cut my losses in attempting to fix what i already have and just re-install the Autodiscover service then re-test the system. Hopefully this will resolve the problem.
0
 
PEbuilderAuthor Commented:
o.k. to update i have now removed and re-created the Autodiscover system on the server and still no luck with OOF or autodiscover.

I spotted and error frrom the command shell where EWS was pointing to the wrong FQDN and corrected it.

I logged a laptop in as the administrator and the outlook client configured correctly and autodiscover works perfectly fine.

I logged ion the same laptop as a test user and OOF and autodiscover do not work http status 403

looking at my own machine when i try 'Test Email Autoconfiguration' i realised it is picking up the wrong email address and when corrected OOF and Autodiscover work!

Any thoughts? would i be better off removing office from the pc and reloading?
0
 
MegaNuk3Commented:
What version of outlook are you running? There are Feb 2011 hotfixes for the wrong email AutoDiscover issue:
Outlook 2007:
http://support.microsoft.com/kb/2475891
0
 
MegaNuk3Commented:
0
 
PEbuilderAuthor Commented:
we are currently runnig Office 2007 Enterprise edition.

the pc's being affected have been removed from one domain (previous owners) to my new domain, there could possibly be something sitting in the registry affecting office?
0
 
MegaNuk3Commented:
Install the Feb 2011 hotfix I mentioned earlier
0
 
PEbuilderAuthor Commented:
WOO HOO !!! getting closer to working !!!

Hotifx is curing the incorrect email problem, just got to cure HTTP status 403 in autoconfiguration
0
 
PEbuilderAuthor Commented:
and we are there, proxy settings are preventing certificate authentication. All i need to do is add the internal system to the exception lists.

Many thanks for all your help!
0
 
PEbuilderAuthor Commented:
where would we be without Experts Exchange !!
0
 
MegaNuk3Commented:
Thanks for the points, glad you got it working
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 7
  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now