Hi, Please can someone link me to the right direction. Autodiscover is not working for users in our childdomain. For user@domain.local it is fine - for user@sub.domain.local it is not. At the Test-Autokonfiguration I can see that he tries to connect to the right site but I get the error x800C8203. - The Exchange server is located in the root domain. - Access to https://ex.domain.local/autodiscover/auto.xml through the browser is fine. - There not cert conflicts - all server names are listed. - Ping is also fine... Do the user from the sub domain need special permissions? Any ideas? Viele Grüße Christian

Hold the "ctrl" key and hit press the outlook icon in your system tray. There should be a "test e-mail autoconfiguration" and select "use autodiscover." See the following link: http://msexchangeteam.com/archive/2007/04/30/438249.aspx.

Hi Jose, I still wrote the output from test-email-autoconfiguration: 0x800C8203 This normaly means: ERROR_INTERNET_NAME_NOT_RESOLVED but he can resolve this name... Viele Grüße Christian

Did you try this :) http://clintboessen.blogspot.com/2010/04/0x800c8203-autodiscover.htmlClint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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.

Hi again Clint, Client certificates will be still ignored and with root users I have no issues... THX Christian

Bang.... Here we GO.... Cause: ---------------- The reason is because the "Keywords" attribute is missing the AutoDiscoverServiceGuid "77378f46-2c66-4aa9-a6a6-3e7a48b19596" in Active Directory under CN=Configuration, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN= Exchange Administrative Group, CN= Servers, CN=<CAS_ServerName>, CN= HTTP,CN=Autodiscover,CN=<CAS_ServerName> Resolution: ------------------------- 1. Run Adsiedit.msc 2. Expand CN=Configuration, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN= Exchange Administrative Group, CN= Servers, CN=<CAS_ServerName>, CN= HTTP,CN=Autodiscover,CN=<CAS_ServerName> 3. Right-click over CN=<CAS_ServerName>, Select Properties 4. Edit the attribute Keywords 5. Add the following enttry 7378f46-2c66-4aa9-a6a6-3e7a48b19596 6. Run the cmdlet Get-ClientAccessServer <CAS_ServerName> | fl Post the result after running the command in step 6Gulab | Skype: gulab.mallah

Hi again Clint, Client certificates will be still ignored and with root users I have no issues... THX Christian This also might be a Cause- Due to Asp.net 3.5 SP1 autodiscover.xml was corrupted. To fix it you will have to Re-created Autodiscoer Virtual directory Gulab | Skype: gulab.mallah

I saw that post on Experts Exchange Gulab. I didnt think it would be an issue though - the AutoDiscoverServiceGuid is part of the configuration partition! All domain partitions use information from the configuration partition. He said one of his domains work! Test it anyway :)Clint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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.

Hey can you run the test-OutlookConnectivity with the verbose switch Christian :)Clint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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.

I saw that post on Experts Exchange Gulab. I didnt think it would be an issue though - the AutoDiscoverServiceGuid is part of the configuration partition! All domain partitions use information from the configuration partition. He said one of his domains work! Test it anyway :) Clint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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. hmmm...than it got to be what i am thinking....Gulab | Skype: gulab.mallah

First Get-ClientAccessServer|fl*auto* [PS] C:\Windows\System32>Get-ClientAccessServer|fl *auto* AutoDiscoverServiceCN : Ex07 AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service AutoDiscoverServiceInternalUri : https://ex07.tifi.net/Autodiscover/Autodiscover.xml AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596 AutoDiscoverSiteScope : {Hamburg} @Gulab: Keyword is set to 77378f46-2c66-4aa9-a6a6-3e7a48b19596 and site=Hamburg. Two entries... test-OutlookConnectivity is not available but Test-OutlookWebServices|fl (only AutoConnectivityService parts listed): Id : 1003 Type : Information Message : AutoConnectivity will be tested with E-Mail-Address Administrator@public.eu Id : 1007 Type : Information Message : Server Ex07.tifi.net with public name https://ex07.domain.net/EWS/Exchange.asmx will be testet Id : 1019 Type : Information Message : Found connection point for AutoConnectivityService. URL https://Ex07.tifi.net/Autodiscover/Autodiscover.xml. Id : 1006 Type : Information Message : Connection established for AutoConnectivityService at https://Ex07.tifi.net/Autodiscover/Autodiscover.xml Id : 1016 Type : Information Message : [EXPR]-'AS' not configured for the user. Id : 1015 Type : Success Message : [EXPR]-Success to Service 'OAB' bei . Die verstrichene Zeit betrug 0 Millisekunden. Id : 1006 Type : Success Message : Successfully tested AutoConnectivityService. I deleted some parts for UM/RPC... Do I have to add an AutoDiscoverScope for the other site? Thx and best regards Christian

But I believe it is not neccessary, only if I have multiple sites and I want to use a special site, or? http://blogs.msdn.com/b/brad_hughes/archive/2007/09/11/autodiscoversitescope-and-client-only-sites.aspx

Run Test-OutlookWebServices -ver |fl <3 Clint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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.

Agree, its not necessary...Gulab | Skype: gulab.mallah

Do I have to add an AutoDiscoverScope for the other site? Answer: No. When you ran Test-OutlookWebServices -ver |fl did you get any more information? I also think its time we bump up the logging! Get-EventLogLevel "MSExchange Autodiscover" | Set-EventLogLevel -Level Expert Clint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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.

I also think its time we bump up the logging. Get-EventLogLevel "MSExchange Autodiscover" | Set-EventLogLevel -level expert Perform this on both the working server and the server that does not work and compare the logs!Clint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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.

[PS] C:\Windows\System32>Test-OutlookWebServices -ver nicolas@sub.domain.net |fl AUSFÜHRLICH: Test-OutlookWebServices : Die Verarbeitung wird begonnen. AUSFÜHRLICH: Die Outlook-Webdienste werden getestet. Id : 1003 Type : Information Message : Die AutoErmittlung wird gleich mit E-Mail-Adresse nstylianides@public1.eu getestet. Id : 1006 Type : Information Message : Es wurde eine Verbindung mit dem AutoErmittlungsdienst bei https://Ex 07.domain.net/Autodiscover/Autodiscover.xml hergestellt. Id : 1016 Type : Success Message : [EXCH]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'AS' bei https://ex07.domain.net/EWS/Exchange.asmx. Die verstrichene Zeit betrug 670 Millisekunden. Id : 1015 Type : Success Message : [EXCH]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'OAB' bei https://ex07.domain.net/EWS/Exchange.asmx. Die verstrichene Zeit betru g 0 Millisekunden. Id : 1014 Type : Success Message : [EXCH]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'UM' bei https://ex07.domain.net/UnifiedMessaging/Service.asmx. Die verstrichene Zeit betrug 15 Millisekunden. Id : 1016 Type : Information Message : [EXPR]-'AS' ist nicht für diesen Benutzer konfiguriert. Id : 1015 Type : Success Message : [EXPR]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'OAB' bei . Die verstrichene Zeit betrug 0 Millisekunden. Id : 1014 Type : Information Message : [EXPR]-'UM' ist nicht für diesen Benutzer konfiguriert. Id : 1017 Type : Success Message : [EXPR]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'RPC/HTTP ' bei https://ex.public.com/Rpc. Die verstrichene Zeit betrug 0 Millisekunden. Id : 1006 Type : Success Message : Der AutoErmittlungsdienst wurde erfolgreich getestet. AUSFÜHRLICH: Test-OutlookWebServices : Die Verarbeitung wird beendet. --------------------------- [PS] C:\Windows\System32>Test-OutlookWebServices -ver we@domain.net |fl AUSFÜHRLICH: Test-OutlookWebServices : Die Verarbeitung wird begonnen. AUSFÜHRLICH: Die Outlook-Webdienste werden getestet. Id : 1003 Type : Information Message : Die AutoErmittlung wird gleich mit E-Mail-Adresse C.Weihs@public.eu gete stet. Id : 1006 Type : Information Message : Es wurde eine Verbindung mit dem AutoErmittlungsdienst bei https://Ex 07.domain.net/Autodiscover/Autodiscover.xml hergestellt. Id : 1016 Type : Success Message : [EXCH]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'AS' bei https://ex07.domain.net/EWS/Exchange.asmx. Die verstrichene Zeit betrug 280 Millisekunden. Id : 1015 Type : Success Message : [EXCH]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'OAB' bei https://ex07.domain.net/EWS/Exchange.asmx. Die verstrichene Zeit betru g 0 Millisekunden. Id : 1014 Type : Success Message : [EXCH]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'UM' bei https://ex07.domain.net/UnifiedMessaging/Service.asmx. Die verstrichene Zeit betrug 15 Millisekunden. Id : 1016 Type : Information Message : [EXPR]-'AS' ist nicht für diesen Benutzer konfiguriert. Id : 1015 Type : Success Message : [EXPR]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'OAB' bei . Die verstrichene Zeit betrug 0 Millisekunden. Id : 1014 Type : Information Message : [EXPR]-'UM' ist nicht für diesen Benutzer konfiguriert. Id : 1017 Type : Success Message : [EXPR]-Erfolg beim Herstellen der Verbindung mit dem Dienst 'RPC/HTTP ' bei https://ex.public.com/Rpc. Die verstrichene Zeit betrug 0 Millisekunden. Id : 1006 Type : Success Message : Der AutoErmittlungsdienst wurde erfolgreich getestet. AUSFÜHRLICH: Test-OutlookWebServices : Die Verarbeitung wird beendet.

No error when I enable the "Get-EventLogLevel 'MSExchange Autodiscover' | Set-EventLogLevel -level expert". I see an information that the Autodiscover request processed successful. Informationen 28.01.2011 12:11:32 MSExchange Autodiscover 2004 Die Anforderung zur AutoErmittlung wurde erfolgreich verarbeitet, Benutzer-SID: "S-1-5-21-1756966931-3309897669-1823416043-1113", HostAddress: "192.168.10.52", HostName: "192.168.10.52". Test E-mail AutoConfiguration shows: - Autodiscover get settings begin - LegacyDN= - SMTP=Nicolas@child.domain.net Attempting URL https://ex07.domain.net/autodiscover/aut..xml found throgh SCP Autodiscover to https://ex07.domain.net/autodiscover/aut..xml starting Autodiscover to https://ex07.domain.net/autodiscover/aut..xml failed (0x800c8203) .... So it finds the URL but why 0x800c8203 grrrr

Ok, now I checked the IIS Its crazy. I got a success response but the sc-win32-status says 64. net helpmsg 64 says me that "The specified network name is no longer available". Lets see what google tells me to this issues Here are some log examples #Date: 2011-01-28 00:00:02 #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken 2011-01-28 12:11:40 192.168.93.3 POST /Autodiscover/Autodiscover.xml - 443 Child\Nico 192.168.10.52 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6545;+Pro) 200 0 64 93 2011-01-28 10:55:04 192.168.93.3 POST /Autodiscover/Autodiscover.xml - 443 Child\Acct2 192.168.10.48 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6545;+Pro) 200 0 64 140 2011-01-28 13:02:29 192.168.93.3 POST /Autodiscover/Autodiscover.xml - 443 DOMAIN\CP 192.168.93.96 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.5128;+Pro) 200 0 0 0 2011-01-28 11:03:28 192.168.93.3 POST /Autodiscover/Autodiscover.xml - 443 DOMAIN\Hit 192.168.93.182 Microsoft+Office/14.0+(Windows+NT+5.1;+Microsoft+Outlook+14.0.4760;+Pro) 200 0 0 15 2011-01-28 10:55:01 192.168.93.3 POST /Autodiscover/Autodiscover.xml - 443 DOMAIN\We 192.168.94.44 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.4760;+Pro) 200 0 0 62 Any ideas? I will install a second CAS temporaly to see if it has the same issues... Viele Grüße Christian

you have to generate a new DNS record: _autodiscover._tcp.sub.domain.local pointing to the Cname of your Exchange Server regards Thomas Paetzold visit my blog on: http://susu42.wordpress.com

I changed the autodiscover url configuration to ssl is not required and logged the traffic with wireshark. Result: The email address from child users could not resolved!: <?xml version="1.0" encoding="utf-8"?><Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006"><Request><EMailAddress>nicolas@aegispharma.eu</EMailAddress><AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema></Request></Autodiscover>HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Length: 374 Content-Type: text/html; charset=utf-8 Expires: -1 Server: Microsoft-IIS/7.0 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Date: Mon, 31 Jan 2011 11:55:18 GMT <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response> <Error Time="12:55:18.5735927" Id="3942132706"> <ErrorCode>500</ErrorCode> <Message>Die E-Mail-Adresse kann nicht gefunden werden.</Message> <DebugData /> </Error> </Response> </Autodiscover>

Have yu got an autodiscover entry in your DNS Server? The Autodiscover entry should be an Service Record. and looks like autodiscover._tcp.sub.domain.local pointing to the Cname of your Exchange Server Port 443 regards Thomas Paetzold visit my blog on: http://susu42.wordpress.com

Delegation, Stub Zones or Conditional Forwarders (whichever of the 3 you are using) are configured correctly i assume! You tried everything I would have - very strange. Maybe open a support case on this one - I would love to know the answer!Clint Boessen MVP - Exchange Server, MCSE, MCITPx4, Dip Network Engineering Perth, Western Australia Blog: http://clintboessen.blogspot.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.

Do you have RSA enabled on CAS server?Gulab | Skype: gulab.mallah

I configured a Stub Zone and no RSA is used. It's a shame but I did not recognize that the email address realy did not exist! For new user we create a smtp address which equates the upn. This is done by an email policy which was not configured for the child domain! So user@sub.domain.local does not work and primarysmtp@maildomain.eu works... maybe the whole time. Why does Outlook use the UPN and not the primary email address? http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/7b7d27a9-ddd2-420c-8bd8-b3f7acc470f2/ Furtermore it is not clear why it the request was fine from time to time: 2011-02-02 14:17:01 SUB\Alek 200 64 2011-02-02 14:17:11 SUB\Alek 206 0 2011-02-02 14:17:12 SUB\Alek 206 0 2011-02-02 14:17:22 SUB\Alek 200 64 2011-02-02 14:17:33 SUB\Alek 200 64 2011-02-02 14:18:43 SUB\Alek 200 64 2011-02-02 14:18:45 SUB\Alek 200 64 2011-02-02 14:29:27 SUB\Alek 200 0 2011-02-02 14:29:45 SUB\Alek 200 0 To make sure that the request works in the future I created the UPN-SMTP-address manually. I will check the IIS tomorrow and give you a feedack! Best regards Christian

Hi Christian, Let us know what is the status of the issue?Gulab | Skype: gulab.mallah

Hi Gulab, Hi Clint, Thanks for your assitance! The issues is causing by different updates and it is a known issues. A fix should be available soon... Best regards Christian

Autodiscover tries to use your computer joined domain first then email. When autodiscover first launches it does a directory function lookups to determine what domain you're joined into and tries that first. This is observable when doing migrations and your computer is joined in a different forest and mailbox is in another forest. Outlook will attempt autodiscover of the domain your computer is joined to.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hi everyone! Sorry for my late response! The problem occured as a result of problem with Hotfix KB2405793. The issues should be fixed in the next update... Thank you very much for your assistance! Christian ............... I finally got feedback from the next level of support. The current status is that it will be fixed in Outlook 2010 SP1 but there might also be a fix in a cumulative update. The ‘release deadline’ is currently set to the 23^rd of this month (feb 2011), though this can change also. The current workaround is: Uninstall the KB2405793 Manually configure Profile

You can't be serious!!!!!!!!!!!! After so much of work, what is the resolution (work around) Manually configure the profile. I hope they get it fixed in RU3...Gulab | MCTS-MCITP: 2010 | MCTS-MCITP: 2007 | MCC | Skype: Gulab.Mallah