Exchange 2010 Outlook 2010 Autodiscovery not working
Have 2 nodes Cas array. Something wrong with autodiscovery. It's not working. If i click TEST my connection in outlook it says that it can't determine my parameters. Is there a method to comeplete re enable of autodiscovery system ?Be real
July 23rd, 2012 10:03am

Hi, 1. Test autodiscover configuration: Test-OutlookWebServices -ClientAccessServer "CASServer01" 2. Ping and browse https://mydomain/autodiscover/autodiscover.xml 3. If you are testing from outside, test https://autodiscover.mydomain/autodiscover/autodiscover.xml 4. Test autodiscover virtual diretories: Get-AutodiscoverVirtualDirectory |FL 5. Also want to check whether your certificate is configured with autodiscover urlsRegards from www.windowsadmin.info | www.blog.windowsadmin.info
Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2012 11:29am

tnx 4 u for answering to my problem. Let me answer 1. WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to find the mailbox. Mailbox = 'extest_ea9586a4d6674@mydomain.local'. 2. ping to my cas array is succesful. browsing https://mydomain/autodiscover/autodiscover.xml prompting me to insert my credentials and then answer me <Autodiscover><Response><Error Time="09:36:36.5657593" Id="3182617819"><ErrorCode>600</ErrorCode><Message>Invalid request</Message><DebugData/></Error></Response></Autodiscover> 3. Its only internal. I dont need it externally at now. 4. RunspaceId : b9852ce9-c2e1-4819-bca8-cfb8c088468a Name : Autodiscover (Default Web Site) InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity} ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity} LiveIdSpNegoAuthentication : False WSSecurityAuthentication : True LiveIdBasicAuthentication : False BasicAuthentication : True DigestAuthentication : False WindowsAuthentication : True MetabasePath : IIS://CAS01.mydomain.local/W3SVC/1/ROOT/Autodiscover Path : E:\Exchange Server\ClientAccess\Autodiscover ExtendedProtectionTokenChecking : None ExtendedProtectionFlags : {} ExtendedProtectionSPNList : {} Server : CAS01 InternalUrl : ExternalUrl : AdminDisplayName : ExchangeVersion : 0.10 (14.0.100.0) DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=CAS01,CN=Servers,CN=Exchang e Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organizati on,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=local Identity : CAS01\Autodiscover (Default Web Site) Guid : 0e6a40e3-7d8f-44ef-8a73-a27b8a8cf1a0 ObjectCategory : mydomain.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory} WhenChanged : 8/17/2011 11:32:11 AM WhenCreated : 8/17/2011 11:32:11 AM WhenChangedUTC : 8/17/2011 8:32:11 AM WhenCreatedUTC : 8/17/2011 8:32:11 AM OrganizationId : OriginatingServer : dc01.mydomain.local IsValid : True RunspaceId : b9852ce9-c2e1-4819-bca8-cfb8c088468a Name : Autodiscover (Default Web Site) InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity} ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity} LiveIdSpNegoAuthentication : False WSSecurityAuthentication : True LiveIdBasicAuthentication : False BasicAuthentication : True DigestAuthentication : False WindowsAuthentication : True MetabasePath : IIS://CAS02.mydomain.local/W3SVC/1/ROOT/Autodiscover Path : E:\Exchange Server\ClientAccess\Autodiscover ExtendedProtectionTokenChecking : None ExtendedProtectionFlags : {} ExtendedProtectionSPNList : {} Server : CAS02 InternalUrl : ExternalUrl : AdminDisplayName : ExchangeVersion : 0.10 (14.0.100.0) DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=CAS02,CN=Servers,CN=Exchang e Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organizati on,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=local Identity : CAS02\Autodiscover (Default Web Site) Guid : aa71f17c-4c5e-43e4-8ecd-2ae98a797b68 ObjectCategory : mydomain.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory} WhenChanged : 1/30/2012 8:24:48 PM WhenCreated : 1/30/2012 8:24:48 PM WhenChangedUTC : 1/30/2012 6:24:48 PM WhenCreatedUTC : 1/30/2012 6:24:48 PM OrganizationId : OriginatingServer : dc01.mydomain.local IsValid : True 5. its configured maybe. I think everything goes wrong when i make kerberos authentication. (kerberos works fine, but i think something i missed) .... Be real
July 24th, 2012 2:51am

tnx 4 u for answering to my problem. Let me answer 1. WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to find the mailbox. Mailbox = 'extest_ea9586a4d6674@mydomain.local'. Hi, You need to create the testaccount. See the instructions here: http://www.howexchangeworks.com/2011/07/new-testcasconnectivityuserps1-script.html Also, what can you tell us about your certificate? (very important part for Autodiscover to work)Martina Miskovic
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2012 3:02am

Hi, There is something wrong with the extest mailbox used for outlook connectivity testing Make sure that by running Get-Mailbox cmdlet against 'extest_ea9586a4d6674@mydomain.local' Else create a new extest mailbox: Open the EMSNavigate to c:\program files\microsoft\exchange server\v14\scriptsType .\New-TestCasConnectivityUser.ps1You will be prompted to choose a password. Regards from www.windowsadmin.info | www.blog.windowsadmin.info
July 24th, 2012 3:05am

Done exactly as you say and have the following: AND I THINK I FOUND SOMETHING HERE !!!! [PS] E:\Exchange Server\Scripts>Test-OutlookWebServices -ClientAccessServer CAS01 RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1006 Type : Information Message : Contacted the Autodiscover service at https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1016 Type : Information Message : [EXCH] The AS service is configured for this user in the Autodiscover response received from https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1015 Type : Information Message : [EXCH] The OAB service is configured for this user in the Autodiscover response received from https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1014 Type : Information Message : [EXCH] The UM service is configured for this user in the Autodiscover response received from https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1016 Type : Information Message : [EXPR] The AS service is configured for this user in the Autodiscover response received from https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1015 Type : Information Message : [EXPR] The OAB service is configured for this user in the Autodiscover response received from https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1014 Type : Information Message : [EXPR] The UM service is configured for this user in the Autodiscover response received from https://CAS01.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1022 Type : Success Message : Autodiscover was tested successfully. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1024 Type : Success Message : [EXCH] Successfully contacted the AS service at https://CAS01.mydomain.local/EWS/Exchange.asmx. The elapsed time was 875 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1026 Type : Success Message : [EXCH] Successfully contacted the UM service at https://CAS01.mydomain.local/EWS/Exchange.asmx. The elapsed time was 196 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1124 Type : Success Message : [Server] Successfully contacted the AS service at https://CAS01.mydomains.local/ews/exchange.asmx. The elapse d time was 42 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1126 Type : Success Message : [Server] Successfully contacted the UM service at https://CAS01.mydomain.local/ews/exchange.asmx. The elapse d time was 14 milliseconds. ---------------------------------------------------------------------------------------------------------------------- EVERYTHING SUCCEED, BUT IF I TEST THIS TO CAS02 - ---------------------------------------------------------------------------------------------------------------------- But i noticed, that have errors with test connectivity to CAS02 [PS] E:\Exchange Server\Scripts>Test-OutlookWebServices -ClientAccessServer CAS02 RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1006 Type : Information Message : Contacted the Autodiscover service at https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1016 Type : Information Message : [EXCH] The AS service is configured for this user in the Autodiscover response received from https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1015 Type : Information Message : [EXCH] The OAB service is configured for this user in the Autodiscover response received from https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1014 Type : Information Message : [EXCH] The UM service is configured for this user in the Autodiscover response received from https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1016 Type : Information Message : [EXPR] The AS service is configured for this user in the Autodiscover response received from https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1015 Type : Information Message : [EXPR] The OAB service is configured for this user in the Autodiscover response received from https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1014 Type : Information Message : [EXPR] The UM service is configured for this user in the Autodiscover response received from https://CAS02.mydomain.local/Autodiscover/Autodiscover.xml. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1022 Type : Success Message : Autodiscover was tested successfully. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1024 Type : Success Message : [EXCH] Successfully contacted the AS service at https://CAS02.mydomain.local/EWS/Exchange.asmx. The elapsed time was 238 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1026 Type : Success Message : [EXCH] Successfully contacted the UM service at https://CAS02.mydomain.local/EWS/Exchange.asmx. The elapsed time was 14 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1013 Type : Error Message : When contacting https://CASARRAY.EXTERNALADDRESS.com/ews/exchange.asmx received the error Unable to connect to the remote server RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1013 Type : Error Message : When contacting https://CASARRAY.EXTERNALADDRESS.com/ews/exchange.asmx received the error No connection could be made because the target machine actively refused it GatewayIP:443 RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1025 Type : Error Message : [EXPR] Error contacting the AS service at https://CASARRAY.EXTERNALADDRESS.com/ews/exchange.asmx. Elapsed time was 670 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1013 Type : Error Message : When contacting https://CASARRAY.EXTERNALADDRESS.com/ews/exchange.asmx received the error Unable to connect to the remote server RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1013 Type : Error Message : When contacting https://CASARRAY.EXTERNALADDRESS.com/ews/exchange.asmx received the error No connection could be made because the target machine actively refused it GatewayIP:443 RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1027 Type : Error Message : [EXPR] Error contacting the UM service at https://CASARRAY.EXTERNALADDRESS.com/ews/exchange.asmx. Elapsed time was 912 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1124 Type : Success Message : [Server] Successfully contacted the AS service at https://CAS02.mydomain.local/ews/exchange.asmx. The elapsed time was 42 milliseconds. RunspaceId : b141efca-f9f5-4fc0-8292-38e05dee811d Id : 1126 Type : Success Message : [Server] Successfully contacted the UM service at https://CAS02.mydomain.local/ews/exchange.asmx. The elapsed time was 168 milliseconds. Interesting that CAS01 is looking in test only to CAS01.mydomain.local But in the test of CAS02 - it tryes to look for CASARRAY address on some tests and get the error ... Where to dig ? Be real
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2012 5:14am

As addition - i have two mail servers on organization. CASARRAY.EXTERNALADDRESS.com - its not right address. How to change it for CASARRAY.mydomain.local ??????Be real
July 24th, 2012 5:19am

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

Other recent topics Other recent topics