autodiscover problems
hi we have recently deployed office 2010 with exchange 2007 Spk 3 when i setup the exchange we were only using office 2003 so autodiscover was not part of the equation we used owa for external clients with a third party cer for mail.mydomain.com. now that we have moved to office 2010 the OOF ,and autodiscover doesn't work you get a" server is unavailable message" for the OOF. OWA works fine after doing some research i linked this to the single server name cer. i have replaced the cer with a ucc cer with the following names (mydomain.com, mail.mydomain.com, autodiscover.mycompany.mydomain.com, and mobile.mycompany.mydomain.com) our default email addresses are user@mycompany.mydomain.com but we use the alias user@mydomain.com we are on a 2003 AD if i try to create a new outlook user i get a message "unknown error occurred error code 0x80070057" i have read that that will occur if you are on a 2003 mailbox which i am not we never ran exchange 2003 in this domain and you are using auto setup which i am because that is how you setup office 2010 so i am back to the autodiscover service . one more thing i have 1 server running the cas.hub, and mailbox roles ( fqdn: server.mycompany.mydomain.com) which sits behind a FW/SMTP gateway now the questions how do i 1. determine if i am using the right names on the cer for autodiscover ? 2 do i need to enable the service somewhere ? 3 where do i start to troubleshoot this if i try to reach https://autodiscover.mycompany.mydomain.com/autodiscover/autodiscover.xml or https://mycompany.mydomain.com/autodiscover/autodiscover.xml i get a error not found 4. do i need to setup a dns A record on local dns server ? in the forward lookup zone there is a autodiscover zone with the following records autodiscover cname ( mail.mycompany.mydomain.com) autodiscover name server ( domain controler.mycompany.mydomain.com) autodiscover SOA ( domain controler.mycompany.mydomain.com.,hostmaster.mycompany.mydomain.com) any help would be greatly apreicaited
April 6th, 2011 11:10pm

1. You didn't say whether the problems are occurring when you use autodiscover internally or externally. If you have internal domain-joined machines, they get their autodiscover URL from the AutodiscoverInternalUri property of Get-ClientAccessServer. This may have certificate implications if you use a different domain internally, like mydomain.local. External joined machines get it from autodiscover.domain.com where domain.com is the e-mail domain. If you have only autosiscover.mycompany.mydomain.com, then users will have to enter their e-mail address with that domain in Outlook when creating their profile. In your case you might be best off putting adding autodiscover.mydomain.com as another SAN and make sure that both autodiscover addresses resolve properly in Internet DNS. 2. Autodiscover enables automatically. See the setting in the answer to part 1 above. 3. Well, that would be a problem. 4. If you use a hostname, it must be in DNS. I don't know why you'd have an autodiscover zone. I've never done anything but create an A record for hostname autodiscover. In your example, autodiscover would have the name autodiscover.autodiscover.mail.mycompany.com. I think you'd want to delete the autodiscover zone and create an A record for autodiscover in the mycompany.mydomain.com zone, and I'd also put one in the mydomain.com zone.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 2:58am

Additional Info: “the Autodiscover service URL will be either https://<smtp-address-domain>/autodiscover/autodiscover.xml or https://autodiscover.<smtp-address-domain>/autodiscover/autodiscover.xml, where ://<smtp-address-domain> is the primary SMTP domain address. For example, if the user's e-mail address is tony@contoso.com, the primary SMTP domain address is contoso.com” --------Refer to <Understanding the Autodiscover Service> Resources: How to Configure Exchange Services for the Autodiscover Service James Luo TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 7th, 2011 5:54am

the problem is internal we don' t use outlook external(except VPN) only OWA
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 4:58pm

If this is only VPN and Internal then you need to have only one A record created for autodiscover as autodiscover.mydomain.com in local DNS
April 7th, 2011 5:07pm

Additional Info: “the Autodiscover service URL will be either https://<smtp-address-domain>/autodiscover/autodiscover.xml or https://autodiscover.<smtp-address-domain>/autodiscover/autodiscover.xml, where ://<smtp-address-domain> is the primary SMTP domain address. For example, if the user's e-mail address is tony@contoso.com, the primary SMTP domain address is contoso.com” so the then i am correct in the autodiscover service url should be at https://mycompany.mydomain.com/autodiscover.autodiscover.xml after reading some other post i tried on the exch/cas server https:\\localhost.autodiscover.autodiscover.xml and recived a not found error ?
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 7:18pm

i made a dns A record for forwardlookup name= autodiscover.mycompany.mydomain.com ip address = cas/mb/hub server's IP all are on one server if that is correct?.......it still not working. i can't reach the autodiscover virtual directory on the localhost example on the exchange server browser if i try https:\\localhost.autodiscover.autodiscover.xml i get a "Internet explorer can not display this page message" so i am either using the wrong address or it don't exist i tried to use the ip for the (localhost) and i get the same results that seems to me to rule out dns as the culprit i checked the IIS manager under the default site there is a autodiscover virtual directory with a autodiscover.xml file in it
April 7th, 2011 7:51pm

i tried some more on the server i was able to reach the https:\\localhost\autodiscover\autodiscover.xml the results were <?xml version="1.0" encoding="utf-8" ?> - <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> - <Response> - <Error Time="14:13:06.9153227" Id="659281217"> <ErrorCode>600</ErrorCode> <Message>Invalid Request</Message> <DebugData /> </Error> </Response> </Autodiscover> i also trried on a client system https:\\servername\autodiscover\autodiscover.xml and got the same results now i am really confused
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 9:16pm

Quote: “problem is internal we don' t use outlook external” Ok, then please ignore my last post Quote: “i made a dns A record” For internal AutoDiscover functionality, DNS record isn’t required Quote: “ip address = cas/mb/hub server's IP all are on one server” So, there’s a single exchange box environment with typical installation (CAS/MBX/HUB), right? Quote: “<ErrorCode>600</ErrorCode>” Error 600 is the expected behavior when contacts to AutoDiscover URL Please check the settings of the default virtual directories on the exchange server (Reference) Please post the output in the “log” tab of “Test E-mail AutoConfiguration” on the outlook client (Here’s a screenshot for the test) Please check if there’s any related event in the application log on the exchange server after reproduced the issue Please run the cmdlet below, and then check the output Test-OutlookWebServices -Identity AliasOfProblematicUser Please run ExBPA against the exchange server for health checkPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 8th, 2011 6:34am

Sorry for the delay for some reason i can't paste to this forum after checking the outlook test email configuration all failed Attempting URL https:/mail.domain.com/autodiscover/autodiscover.xml found through SCP Autodiscover to https://mail.domain/autodiscover/autodiscover.xml starting Autodiscover to https://mail.domain/autodiscover/autodiscover.xml failed (0x800c0203) Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml starting Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml failed (0x800c0203) Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml failed (0x800c0203) Local autodiscover for mydomain.com started Local autodiscover for mydomain.com failed (0x8004010f) Redirect check to http://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting Srv record lookup for http://autodiscover.mydomain.com/autodiscover/autodiscover.xml failed (0x80072ee7) Srv record lookup mydomain.com starting Srv record lookup mydomain.com failed (0x8004010f) so after seeing this i changed the certificate alternative name to autodiscover.mydomain.com and created a external DNS record for it also created a public side ip record for my exchange server in my f/w's 1 to 1 but i still am getting the same errors there was no event log entries 0 test-outlookwebservices ID: 1003 type:information message: about to test autodiscover with e-mail address myaddress@mydomain.com id 1013 error message: when contacting https://mail.domain.com/autodiscover/autodiscover.xml recived error can't conect to remote server. id 1013 type error message when contacting https ://mail.domain.com/autodiscover/autodiscover.xml received the error no connetion could be made because the target machine actively refused it 72.5.54.21:443 (not sure what this address is maybe AT&T dns ) id 1006 type error message the autodiscover service could not be contacted health check i am geting a certificate SAN mismatch for all (activesync) "the subject alternativename(san) of ssl certificate for https;//myserver.mycompany.mydomain.com/micrisoft-server-activesync does not appear to match the host address myserver.mycompany.mydomain.com. current SAN : DNS name= mydomain.com,DNS Name =autodiscover.mydomain.com,DNS name =mycompany.mydomain.com, dns name+mail.mydomain.com (OWA) "the subject alternativename(san) of ssl certificate for https;//mail.mycompany.mydomain.com/owa does not appear to match the host address mail.mycompany.mydomain.com. current SAN : DNS name= mydomain.com,DNS Name =autodiscover.mydomain.com,DNS name =mycompany.mydomain.com, dns name+mail.mydomain.com
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2011 8:26pm

After attempted to reach AutoDiscover through SCP, the client got the wrong URL Attempting URL https:/mail.domain.com/autodiscover/autodiscover.xml found through SCP Autodiscover to https://mail.domain/autodiscover/autodiscover.xml starting Autodiscover to https://mail.domain/autodiscover/autodiscover.xml failed (0x800c0203) It should look like below: Attempting URL https:/mail.domain.com/autodiscover/autodiscover.xml found through SCP Autodiscover to https://mail.domain.com/autodiscover/autodiscover.xml starting Autodiscover to https://mail.domain.com/autodiscover/autodiscover.xml Succeeded (0x00000000) Please recreate your /AutoDiscover virtual directory on the CAS server, and then check the issue again Remove-AutodiscoverVirtualDirectory "cas-servername\Autodiscover (default web site)" New-AutodiscoverVirtualDirectory -WebsiteName "Default Web Site" -WindowsAuthentication $true -BasicAuthentication $true Restart IISAdmin service Please also run ExBPA against the exchange server for health checkPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 13th, 2011 4:51am

1. tried to remove autodiscover virtual directory error "the operation could not be performed because object could not be found on domain controller "my domain controller" tried to create virtual directory (failed already exists) 2. manually removed the autodiscover virtual directory in the IIS manager GUI 3. tried to recreate the autodiscover virtual directory (per instructions ) failed directory already exists 4 restart IIS (IISreset) 5 tried again to recreate the virtual directory same error now what?
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 4:11pm

Please try my suggestions in this thread Notes: Please backup all the configuration files before perform any actionPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 14th, 2011 4:59am

Please try my suggestions in this thread Notes: Please backup all the configuration files before perform any action Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. i have tried your sugestions Quote {Remove-AutodiscoverVirtualDirectory "cas-servername\Autodiscover (default web site)"} 1. tried to remove autodiscover virtual directory error "the operation could not be performed because object could not be found on domain controller "my domain controller" Quote{Please recreate your /AutoDiscover virtual directory on the CAS server, and then check the issue again} tried to create virtual directory (failed already exists) Quote{Please also run ExBPA against the exchange server for health check} health check i am geting a certificate SAN mismatch for all (activesync) "the subject alternativename(san) of ssl certificate for https;//myserver.mycompany.mydomain.com/micrisoft-server-activesync does not appear to match the host address myserver.mycompany.mydomain.com. current SAN : DNS name= mydomain.com,DNS Name =autodiscover.mydomain.com,DNS name =mycompany.mydomain.com, dns name+mail.mydomain.com (OWA) "the subject alternativename(san) of ssl certificate for https;//mail.mycompany.mydomain.com/owa does not appear to match the host address mail.mycompany.mydomain.com. current SAN : DNS name= mydomain.com,DNS Name =autodiscover.mydomain.com,DNS name =mycompany.mydomain.com, dns name+mail.mydomain.com so other than manually removing the autodiscover virtual dierctory because i was not able to remove it thru the shell i am not sure what suggestions that i haven't tried... believe me i do appreicate all the help so far. we are working on a live system not a test enviroment so i have to be careful that i don't kill the mail system the problems that i see are 1 the activedirectory doesn't seem to know where the autodiscover virtual directoy is ? 2 there appears to be a problem with the name on the certificate ( this may go back to the time the domain was setup) mycompany \ mycompany.mydomain 3 how can i get my autodiscover virtual directory back 4 why in the dns do i have a forward lookup zone "autodiscover.domain" and what should be in it?
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2011 6:30pm

Since manually remove /AutoDiscover virtual directory from IIS isn’t the method to remove it, please check if the bad cache remains in the Metabase directory, as I mentioned in the link above For the certificate issue, there’re two methods for it: 1. To modify the URLs in the CAS server in order to have the same name of the URL that has been mentioned in the warning (KB 940726) 2. To reissue the certificate with the same name of the URL that has been mentioned in the warning There shouldn’t be any requirement for such DNS zone (autodiscover.domain) for exchange. You can see the screenshot below, which is my exchange 2007 SP3 lab (Single DC + Single exchange server) Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 15th, 2011 5:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics