Don't think that's going to be a problem, it's trying to find the SSL cert via http://islesofscilly-travel.co.uk:443 but it's not there (the name directs to our web host) I have added in a separate sub-domain autodiscover and pointed that to the network - it's seen that and validated the SSL certificate on the next line. Host name autodiscover.islesofscilly-travel.co.uk was found in the Certificate Subject Alternative Name entry. Certificate trust is being validated. The certificate is trusted and all certificates are present in the chain. So a non-start methinks Any further clues?

EWS traffic look anything like this? 2011-08-11 11:08:25 192.168.1.251 POST /EWS/Exchange.asmx - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 500 0 64 0 2011-08-11 11:08:25 192.168.1.251 POST /EWS/Exchange.asmx - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 500 0 64 0 2011-08-11 11:08:25 192.168.1.251 POST /ews/exchange.asmx - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 500 0 64 0 2011-08-11 11:08:25 192.168.1.251 POST /ews/exchange.asmx - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 500 0 64 0 2011-08-11 11:08:25 192.168.1.251 POST /autodiscover/autodiscover.xml - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 401 2 5 0 2011-08-11 11:08:25 192.168.1.251 POST /autodiscover/autodiscover.xml - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 401 2 5 0 2011-08-11 11:08:25 192.168.1.251 POST /autodiscover/autodiscover.xml - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 401 1 2148074254 0 2011-08-11 11:08:25 192.168.1.251 POST /autodiscover/autodiscover.xml - 443 ISSG\cgr 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 200 0 0 15 2011-08-11 11:08:25 192.168.1.251 POST /EWS/Exchange.asmx - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 500 0 64 0 2011-08-11 11:08:25 192.168.1.251 POST /EWS/Exchange.asmx - 443 - 192.168.1.29 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6020;+Pro) 500 0 64 0

Sunny, Please run the get-clientaccesserver |fl and get -webservicesvirtualdirectory |fl and post the outputs here. Regards, JohanExchange-blog: www.johanveldhuis.nl

Autodiscover url does not have to be changed because if already contains the correct url: Message : The Autodiscover service was contacted at https://mail.issg.local/autodiscover/autodiscover.xml. Besides this the OAB URL should be: Set-OabVirtualDirectory -InternalUrl http://mail.issg.local/OAB instead of HTTPS. This because internal users will download the addressbook by using http and not https. So only change the EWS url as mentioned by Miskovic Regards, Johan Exchange-blog: www.johanveldhuis.nl

Ok, get-clientaccessserver Name ---- PZEX get-webservicesvirtualdirectory InternalNLBBypassUrl : https://pzex.issg.local/EWS/Exchange.asmx Name : EWS (Default Web Site) InternalAuthenticationMethods : {Ntlm, WindowsIntegrated} ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated} BasicAuthentication : False DigestAuthentication : False WindowsAuthentication : True MetabasePath : IIS://pzex.issg.local/W3SVC/1/ROOT/EWS Path : C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\EWS Server : PZEX InternalUrl : https://mail.issg.co.uk/ews/Exchange.asmx ExternalUrl : https://mail.issg.co.uk/ews/exchange.asmx AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=PZEX,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=issg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=issg,DC=local Identity : PZEX\EWS (Default Web Site) Guid : d933551a-78c3-47ca-8b92-fbd4e0ea636a ObjectCategory : issg.local/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory} WhenChanged : 01/07/2011 15:45:20 WhenCreated : 09/06/2011 12:31:50 OriginatingServer : DC.issg.local IsValid : True Sorry about the formatting!

With a Public Certificate, as in this case, https can be used for OAB downloads. So it´s more of a choice you make. Using a selfsigned certificate....there´s another story. :MartinaPlease 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.

Hi Sunny, First thing: InternalUrl is set to https://mail.issg.co.uk/ews/Exchange.asmx if you want to use this URL you will need to create a split-dns or pinpoint-dns zone for your external naming space. Else users will not be able to connect. By default the ews internal url is: https://servername.domain.local/ews/Exchange.asmx Can you provide the output of get-clientaccessserver |fl? Regards, JohanExchange-blog: www.johanveldhuis.nl

500 0 64 0 = Authentication Error Is Basic Authenction enabled now (=True)? Can you add *issg.local to the Security | Intranet Zone in IE Martina Miskovic

A restart of IIS (iisreset) is never wrong :) But I'm not sure if ít's required in this case, Johan what do you say? Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

Right, so I've changed the internal url to https://pzex.issg.local/ews/exchange.asmx Output of get-clientaccessserver | fl Name : PZEX OutlookAnywhereEnabled : True AutoDiscoverServiceCN : pzex AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service AutoDiscoverServiceInternalUri : https://mail.issg.co.uk/autodiscover/autodiscover.xml AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596 AutoDiscoverSiteScope : {Penzance} IsValid : True OriginatingServer : PZDC.issg.local ExchangeVersion : 0.1 (8.0.535.0) DistinguishedName : CN=PZEX,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=issg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=issg,DC=local Identity : PZEX Guid : 896a201f-a9fe-4e7f-b602-3e05c8a7bae8 ObjectCategory : issg.local/Configuration/Schema/ms-Exch-Exchange-Server ObjectClass : {top, server, msExchExchangeServer} WhenChanged : 25/11/2010 09:47:42 WhenCreated : 13/07/2009 10:11:50

Don't see any of those settings, and am on Office 2010 (which is 14 isn't it?)

1) Yep; Name : EWS (Default Web Site) InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated} ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated} BasicAuthentication : True DigestAuthentication : False WindowsAuthentication : True 2) If that's the one in Internet Explorer, Tools, Options, Security Tab, Local Intranet, Sites, Advanced, then yep, done that!

Just to be sure.. You don´t have any of the Exclude*-keyes set in an Group policy either? If you log on locally on a PC, does Autodiscovery work then (configures your profile, OOF etc)? I am running out of idéas :(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.

Could you run Test-E-mail Autoconfiguration" and post the result from the Result- and Log Tab? :MartinaPlease 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.

Well well well...something seems to be working!! Am at a different location (using Office 2007 now as opposed to 2010 at my normal desk) and prior to making the above changes I tried....OOF is working! Oddly I was asked for a logon to issg.local when launching outlook (and again after the IIS reset) but after an initial logon it didn't ask again, and it does seem to be working.... I'd like to keep this open until I've test tomorrow on Outlook 2010 if that's ok? But it looks good so far....

Hmmm, I have managed to get a test performed with another PC (running Office 2007) and that one still has the original problem. Meanwhile my (temporary) PC is still working! I am on a different site / subnet, but all of the DNS settings should be copied from the PDC to the local BDC

I didn't restart IIS but am still getting the error on Outlook :-(

Shouldn't be required since the information is stored in AD. What is the error you got ? Regards, JohanExchange-blog: www.johanveldhuis.nl

If you run Test-OutlookWebServices -identity emailaddress@domain.local Post the result in here Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

I'd like to keep this open until I've test tomorrow on Outlook 2010 if that's ok? But it looks good so far.... Sounds like we are on our way :) It can take some time before Outlook downloads the new settings for Autodiscover. One would think that Outlook does it everytime it starts, but that is not the case The file is stored the the users profile C:\Users\XXXXX\AppData\Local\Microsoft\Outlook :MartinaPlease 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.

Autodiscover issue.

Hmm, it won't let me copy/paste the info!! Here's the XML output I am away for a few days, but will pick this back up next week if ok? Thanks for all of the help so far guys! <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Bob Tester</DisplayName> <LegacyDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=userlevel</LegacyDN> <DeploymentId>8811e676-6762-4080-8ac1-4a786610358b</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>pzex.issg.local</Server> <ServerDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>pzex.issg.local</PublicFolderServer> <AD>PZDC.issg.local</AD> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>http://mail.issg.local/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>mail.issg.co.uk</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.co.uk/ews/exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.co.uk/ews/exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>https://mail.issg.co.uk/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>WEB</Type> <External> <OWAUrl AuthenticationMethod="Fba">https://mail.issg.co.uk/owa</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> </Protocol> </External> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.issg.local/OWA</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover>

Hi, Back from my leave, still no joy, is there anything else I can try? cheers

Error; - <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> - <Response> - <Error Time="16:39:57.6407919" Id="668803091"> <ErrorCode>600</ErrorCode> <Message>Invalid Request</Message> <DebugData /> </Error> </Response> </Autodiscover> Outlook web services test Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address userlevel@islesofscilly-travel.co.uk. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://mail.issg.local/autodiscover/autodiscover.xml. Id : 1005 Type : Error Message : When accessing https://pzex.issg.local/ews/Exchange.asmx the error "RemoteCertificateNameMismatch:CN=mail.issg.co.uk, OU=Domain Control Validated, O=mail.issg.co.uk" was reported. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://pzex.issg.local/ews/Exchange.asmx. The elapsed time was 156 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://pzex.issg.local/ews/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 46 milliseconds. Id : 1016 Type : Success Message : [EXPR]-Successfully contacted the AS service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 31 milliseconds. Id : 1015 Type : Success Message : [EXPR]-Successfully contacted the OAB service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXPR]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 15 milliseconds. Id : 1013 Type : Error Message : When contacting https://mail.issg.co.uk/Rpc received the error The remote server returned an error: (500) Internal Server Error. Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.issg.co.uk/Rpc. The elapsed time was 21 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. Id : 1021 Type : Information Message : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors.

Hi, Nice to hear from you again. Are you using a proxy server? If so, can you add mail.issg.local to the exception list or add it to the exception list in IE? Also, please uncheck "Automaticlaly detect setting" in the connection settings in IE Also, please run get-webservicesvirtualdirectory | fl name,*auth* and post the outputMartina Miskovic

Hmmm, I've just tried to test this on my DC (which has Office 2007 installed) and it's prompting for a password but not accepting my network credentials - this is a new profile as well... Back to the test pc on the same subnet as the Exchange server (Office 2007 also) and I'm getting the original problem! Seems strange to me that it seems to work on the other site - yet the site with the DC/Exchange server is causing problems, can't think that there's anything wrong with the network settings, maybe it's DNS related? Really gutted, as I thought we (you) had it!

Hi, When you mentioned Sites I got to think about AutoDiscoverSiteScope... I don´t know anything about your Network Design, but when you see Panzance does that make anything clearer when you think about your testings? Output of get-clientaccessserver | fl Name : PZEX OutlookAnywhereEnabled : True AutoDiscoverSiteScope : {Penzance} OriginatingServer : PZDC.issg.local Can you add your other ActiveDirectory Sites to the AutoDiscoverSiteScope Settings? AD-Sites that has users. set-ClientAcessServer -AutoDiscoverSiteScope {Penzance,Site2,Site3,etc} (get-adsite is a nice command here, to use for copy/paste) We will get there :)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.

Penzance is where the head office is - where the DC/Exchange server are, I was at a different site today, different subnet, but has a BDC with DNS/DHCP configured - the setup worked there, but not at Head Office? I'd have thought that if anything was going to happen it would work at HQ but not on remote sites?

Chris, So it doesn't work in HQ but it does in a remote site. What happens if you use the auto e-mail configuration option from Outlook in the two different sites. Regards, Johan Exchange-blog: www.johanveldhuis.nl

Make sure you use split-brain dns and include the name mail.issg.co.uk into the certificate What names are included in the certificate? Get-ExchangeCertificate | fl Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

Hi Sunny, Also change the AutoDiscoverInternalUri back to the original https://servername.domain.local/Autodiscover/Autodiscover.xml Another option is to create a split-dns as Jonas mentioned but this is not possible in all scenario's. Regards, JohanExchange-blog: www.johanveldhuis.nl

Hi Jose, Care to expand on this? I thought early on in this process we established that Autodiscover was working fine? cheers

Hi, Im sorry for not getting back to you! Can you creata a A-record for Autodiscover in the DNS Zone islesofscilly-travel.co.uk ? Also, please post the testresult from Test E-mail AutoConfiguration - Log Tab Martina Miskovic

Hi Martina, No problems, you've been very helpful thus far!! I have an A record in the DNS Zone issg.co.uk and it points to the IP address of the mailserver Result from AutoConfiguration test is as follows; Attempting URL https://mail.issg.local/autodiscover/autodiscover.xml found through SCP Autodiscover to https://mail.issg.local/autodiscover/autodiscover.xml starting Autodiscover to https://mail.issg.local/autodiscover/autodiscover.xml Succeeded (0x00000000)

I edited my last post... Can you create one for islesofscilly-travel.co.uk aswell? The test looks good!Martina Miskovic

I have one for Islesofscilly-Travel.co.uk pointing to the mailserver IP also There isn't one in issg.local though, should there need to be? I agree about the test, it seems autodiscover is working, but something still isn't quite right!

Ok, I have applied the suggested settings, and now it's taking Outlook an exceptionally long time to load up?! (I've been sat staring at the loading profile screen for 10 mins or so...) Forget that - I rebooted the PC & recreated profile and it seems fine. But still getting the original error re: OOF? Webservices test shows the following... Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address userlevel@islesofscilly-travel.co.uk. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://mail.issg.local/autodiscover/autodiscover.xml. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 93 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 31 milliseconds. Id : 1016 Type : Success Message : [EXPR]-Successfully contacted the AS service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 46 milliseconds. Id : 1015 Type : Success Message : [EXPR]-Successfully contacted the OAB service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXPR]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 62 milliseconds. Id : 1013 Type : Error Message : When contacting https://mail.issg.co.uk/Rpc received the error The remote server returned an error: (500) Internal Server Error. Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.issg.co.uk/Rpc. The elapsed time was 21 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. Id : 1021 Type : Information Message : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors.

No, you don´t need one Autodiscover Record for issg.local, cause you don´t use that domain for your Primary SMTP. Is it just OOF from HQ Site that doesn´t work? What about availability (free\busy) and OAB? Martina Miskovic

Seems to be all sites, but I think free\busy and OAB works - how would I test to be sure?

Check that your client has downloaded the OABs. In Windows 7, they are stored in: C:\Users\USER\AppData\Local\Microsoft\Outlook\Offline Address Books And for free/busy, just check that can see another persons availability when you create a meeting request Martina Miskovic

Yep, OABs are there, but I tried to create a meeting request and on the new appointment screen (to the right) it said that free/busy data could not be displayed

Can you runt Test-OutlookWebServices again? Test-OutlookWebServices -identity emailaddress@islesofscilly-travel.co.uk Test-OutlookWebServices -identity emailaddress@issg.co.uk Just to be sure, the IP-Adress specificed for Autodiscover is the internal one and not the external 78* ? Martina Miskovic

Hi Guys, The following is the auto configuration output from the remote site. <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Bob Tester</DisplayName> <LegacyDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=userlevel</LegacyDN> <DeploymentId>8811e676-6762-4080-8ac1-4a786610358b</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>pzex.issg.local</Server> <ServerDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>pzex.issg.local</PublicFolderServer> <AD>PZDC.issg.local</AD> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>http://mail.issg.local/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>mail.issg.co.uk</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.co.uk/ews/exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.co.uk/ews/exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>https://mail.issg.co.uk/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>WEB</Type> <External> <OWAUrl AuthenticationMethod="Fba">https://mail.issg.co.uk/owa</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> </Protocol> </External> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.issg.local/OWA</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover> And this is the output from head office. <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Bob Tester</DisplayName> <LegacyDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=userlevel</LegacyDN> <DeploymentId>8811e676-6762-4080-8ac1-4a786610358b</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>pzex.issg.local</Server> <ServerDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>pzex.issg.local</PublicFolderServer> <AD>PZDC.issg.local</AD> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>http://mail.issg.local/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>mail.issg.co.uk</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.co.uk/ews/exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.co.uk/ews/exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>https://mail.issg.co.uk/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>WEB</Type> <External> <OWAUrl AuthenticationMethod="Fba">https://mail.issg.co.uk/owa</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> </Protocol> </External> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.issg.local/OWA</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover>

Do you have an internal DNS-Zone for islesofscilly-travel.co.uk? What happends if you test with a user that has @issg.co.uk as primary? Have test with Exchange Remote Connectivity Analyzer? What URI do you now have for autodiscover? Outlook Anywhere Problem - Suggestion: Disable/Enable OA Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.issg.co.uk/Rpc Message : When contacting https://mail.issg.co.uk/Rpc received the error The remote server returned an error: (500) Internal Server Error. Make sure you fix the URLs for OAB!! It should not point to /EWS Message : [EXCH]-Successfully contacted the OAB service at https://mail.issg.local/EWS/Exchange.asmx. Message : [EXPR]-Successfully contacted the OAB service at https://mail.issg.co.uk/ews/exchange.asmx. :Martina 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.

No proxy, do you still want me to try those settings? Output of get-webservicesvirtualdirectory Name : EWS (Default Web Site) InternalAuthenticationMethods : {Ntlm, WindowsIntegrated} ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated} BasicAuthentication : False DigestAuthentication : False WindowsAuthentication : True

Hi All, Sorry for yet another one of these posts, but I have scoured the web for a fix and so far come up short. My Exchange 2007 server was a clean install, single server installation on 2008 STD 64 Bit server, if memory serves we installed an exchange rollup without stopping services beforehand, that seemed to break a few of the applications, so the rollup was removed, services stopped and it was reinstalled - all seemed fine. I have installed a godaddy certificate, multiple domains, following the instructions from their site. We were using Office 2003 on clients but started getting the error moving to Office 2007 (and 2010) - everything else seems to work fine, we just get the OOF error, a basic work-around is setting OOF via webmail, but not ideal. If I run the autodiscover test via ExMCA I get passes. I can browse to the web services directory and get prompted for credentials, when given I get the xml output. Autoconfiguration tests complete with no errors. Not really sure where to go from here? At the risk of asking the same questions all over again would someone kindly give me a clue as to which diagnostic to try next? cheers

Sunny, Can you post the output of the autodiscover test? Do other services such as free/busy work for users who are migrated to Office 2007? Regards, JohanExchange-blog: www.johanveldhuis.nl

Hi, Yes to Internal zone for islesofscilly-travel.co.uk All users have islesofscilly-travel.co.uk as a primary - but I reconfigured my test account to have @issg.co.uk as a primary and it returns the following; Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address userlevel@issg.co.uk. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://mail.issg.local/autodiscover/autodiscover.xml. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 78 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 31 milliseconds. Id : 1016 Type : Success Message : [EXPR]-Successfully contacted the AS service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 140 milliseconds. Id : 1015 Type : Success Message : [EXPR]-Successfully contacted the OAB service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXPR]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 31 milliseconds. Id : 1013 Type : Error Message : When contacting https://mail.issg.co.uk/Rpc received the error The remote server returned an error: (500) Internal Server Error. Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.issg.co.uk/Rpc. The elapsed time was 21 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. Id : 1021 Type : Information Message : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors. Test via ExRCA passes This is strange....Get-AutodiscoverVirtualDirectory gives the following; Name : Autodiscover (Default Web Site) InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated} ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated} BasicAuthentication : True DigestAuthentication : False WindowsAuthentication : True MetabasePath : IIS://pzex.issg.local/W3SVC/1/ROOT/Autodiscover Path : C:\Program Files\Microsoft\Exchange Server\ClientAccess\Autodiscover Server : PZEX InternalUrl : ExternalUrl : AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=PZEX,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=issg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=issg,DC=local Identity : PZEX\Autodiscover (Default Web Site) Guid : ba0bb025-d06f-45fa-bc07-762684e4e8ef ObjectCategory : issg.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory} WhenChanged : 13/07/2009 10:15:15 WhenCreated : 13/07/2009 10:15:15 OriginatingServer : PZDC.issg.local IsValid : True I have also re-run the command to set the OAB directory, but it's not changing when testing

Is there any significance to the result of get-adsite; Name HubSiteEnabled ---- -------------- Penzance False LandsEnd False I've now added LandsEnd into the clientaccessserver list

Hi Guys, The output of the certificate is below - I have previously followed a tutorial that suggested you set your internal and external URLs to the same thing, so my SAN certificate does not have pzex.issg.local within it, however I have setup an internal DNS record for mail to the mailserver so if I browse to https://mail.issg.local/autodiscover/autodiscover.xml I get prompted for a password (which then gives me a 600 error) Could I adjust the internal URL to http://mail.issg.local/autodiscover/autodiscover.xml or is it better to update the certificate? AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule} CertificateDomains : {mail.issg.co.uk, www.mail.issg.co.uk, mail.issg.local, autodiscover.issg.co.uk, mail.islesofscilly-travel.co.uk, autodiscover.islesofscilly-travel.co.uk} HasPrivateKey : True IsSelfSigned : False Issuer : SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US NotAfter : 24/11/2011 13:57:26 NotBefore : 24/11/2010 13:57:26 PublicKeySize : 2048 RootCAType : ThirdParty SerialNumber : 2B4115DF0BCE1E Services : IMAP, POP, IIS, SMTP Status : Valid Subject : CN=mail.issg.co.uk, OU=Domain Control Validated, O=mail.issg.co.uk Thumbprint : AF98B0C364B4DF7C94B53295442D775F25FD08BA

Hi, Yes in that case modify it so it points mail.issg.local this should also work. Regards, JohanExchange-blog: www.johanveldhuis.nl

Have you tested with Exchange Remote Connectivity Analyzer? What URI do you now have for aAutoDiscoverServiceInternalUri? (Get-ClientAccessServer | ft Name,AutoDiscoverServiceInternalUri ) Run get-outlookanywhere | fl --> and post the output :MartinaPlease 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.

The ip address in all cases is the internal ip, yes @islesofscilly-travel Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address userlevel@islesofscilly-travel.co.uk. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://mail.issg.local/autodiscover/autodiscover.xml. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 78 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 31 milliseconds. Id : 1016 Type : Success Message : [EXPR]-Successfully contacted the AS service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 78 milliseconds. Id : 1015 Type : Success Message : [EXPR]-Successfully contacted the OAB service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXPR]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 15 milliseconds. Id : 1013 Type : Error Message : When contacting https://mail.issg.co.uk/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.issg.co.uk/Rpc. The elapsed time was 15 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. Id : 1021 Type : Information Message : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors. @issg Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address userlevel@islesofscilly-travel.co.uk. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://mail.issg.local/autodiscover/autodiscover.xml. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 93 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 31 milliseconds. Id : 1016 Type : Success Message : [EXPR]-Successfully contacted the AS service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 124 milliseconds. Id : 1015 Type : Success Message : [EXPR]-Successfully contacted the OAB service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXPR]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 15 milliseconds. Id : 1013 Type : Error Message : When contacting https://mail.issg.co.uk/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.issg.co.uk/Rpc. The elapsed time was 93 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. Id : 1021 Type : Information Message : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors.

Yes, I tested with remote connectivity analyzer, I ran the Synchronization, Notification, Availability, and Automatic Replies (OOF) test and it passed.... Get-ClientAccessServer; Name AutoDiscoverServiceInternalUri ---- ------------------------------ PZEX https://mail.issg.local/autodiscover/autodiscover.xml Get-OutlookAnywhere; ServerName : PZEX SSLOffloading : False ExternalHostname : mail.issg.co.uk ClientAuthenticationMethod : Basic IISAuthenticationMethods : {Basic, Ntlm} MetabasePath : IIS://pzex.issg.local/W3SVC/1/ROOT/Rpc Path : C:\Windows\System32\RpcProxy Server : PZEX AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) Name : Rpc (Default Web Site) DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=PZEX,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=issg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=issg,DC=local Identity : PZEX\Rpc (Default Web Site) Guid : f98a0dad-6aed-4c82-8276-f96ad76b329f ObjectCategory : issg.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory} WhenChanged : 08/10/2010 08:44:38 WhenCreated : 08/10/2010 08:44:38 OriginatingServer : PZDC.issg.local IsValid : True

Hi, HubSiteEnabled has nothing to do with ClientAccess. It´s for Exchange Transport Routing. Like I mentioned before, Outlook doesn´t download the Autodiscover file everytime it starts, so now we can just wait and see if it makes any difference now after you have addedd LandsEnd to the AutodiscoverSiteScope. In the mean time, you can check the Autodicover file that a client has. It is stored in C:\Users\USER\AppData\Local\Microsoft\Outlook And also, look in the registry [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover] [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover\RedirectServers] We know you had PZEX hardcoded as an outlookprovider, but I never asked you why? Was there any good reason for that? Only thing I can think of is that you used to have a self-signed certificate. Whatif you run Test-OutlookWebServices with an identity from islesofscilly-travel.co.uk and issg.co.uk Is the output different? Still Errors for RPC? :MartinaPlease 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.

Output of the test-outlookwebservices is the same for both domains; Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address userlevel@islesofscilly-travel.co.uk. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://mail.issg.local/autodiscover/autodiscover.xml. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 62 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://mail.issg.local/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 15 milliseconds. Id : 1016 Type : Success Message : [EXPR]-Successfully contacted the AS service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 78 milliseconds. Id : 1015 Type : Success Message : [EXPR]-Successfully contacted the OAB service at https://mail.issg.co.uk/ews/exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXPR]-Successfully contacted the UM service at https://mail.issg.co.uk/UnifiedMessaging/Service.asmx. The elapsed time was 15 milliseconds. Id : 1013 Type : Error Message : When contacting https://mail.issg.co.uk/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.issg.co.uk/Rpc. The elapsed time was 15 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. Id : 1021 Type : Information Message : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors. I also recreated the Autodiscover file on my pc; <?xml version="1.0" encoding="UTF-8"?> -<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> -<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> -<User> <DisplayName>Bob Tester</DisplayName> <LegacyDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=userlevel</LegacyDN> <DeploymentId>8811e676-6762-4080-8ac1-4a786610358b</DeploymentId> </User> -<Account> <AccountType>email</AccountType> <Action>settings</Action> -<Protocol> <Type>EXCH</Type> <Server>pzex.issg.local</Server> <ServerDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>pzex.issg.local</PublicFolderServer> <AD>PZDC.issg.local</AD> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>http://mail.issg.local/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> -<Protocol> <Type>EXPR</Type> <Server>mail.issg.co.uk</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.co.uk/ews/exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.co.uk/ews/exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>https://mail.issg.co.uk/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> -<Protocol> <Type>WEB</Type> -<External> <OWAUrl AuthenticationMethod="Fba">https://mail.issg.co.uk/owa</OWAUrl> -<Protocol> <Type>EXPR</Type> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> </Protocol> </External> -<Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.issg.local/OWA</OWAUrl> -<Protocol> <Type>EXCH</Type> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover> No good reason for having PZEX hardcoded, I think we tried initially to setup with self-signed, but because we have several mail domains we went down the route of SAN certificate. Can't see anything in the registry that points to our server, should I?

Ok, that is done - do I need to recycle iis to test, or a reboot or similar? Feels like the solution is close!!

Hi, Let´s set the URLs for AutodiscoverVirtualDirectory Set-AutodiscoverVirtualDirectory -internalurl https://mail.issg.local/autodiscover/autodiscover.xml -externalurl https://mail.issg.co.uk/autodiscover.xml You dont have any Outlookproviders set up, right? (Get-Outlookprovider) mail.issg.local is a A-Record in DNS, right? If you run a Autodiscover Test with Outlook Test E-mailAutoconfiguration. What result do you get then? 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.

Ok, I have setup Autodiscovery URLs Get-Outlookprovider gives; Name Server CertPrincipalName TTL ---- ------ ----------------- --- EXCH pzex 1 EXPR 1 WEB 1 mail.issg.local has an A record in DNS Output of Autodiscover test; <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Bob Tester</DisplayName> <LegacyDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=userlevel</LegacyDN> <DeploymentId>8811e676-6762-4080-8ac1-4a786610358b</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>pzex.issg.local</Server> <ServerDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>pzex.issg.local</PublicFolderServer> <AD>PZDC.issg.local</AD> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>http://mail.issg.local/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>mail.issg.co.uk</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> <EwsUrl>https://mail.issg.co.uk/ews/exchange.asmx</EwsUrl> <OOFUrl>https://mail.issg.co.uk/ews/exchange.asmx</OOFUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>https://mail.issg.co.uk/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> </Protocol> <Protocol> <Type>WEB</Type> <External> <OWAUrl AuthenticationMethod="Fba">https://mail.issg.co.uk/owa</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> </Protocol> </External> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://pzex/owa</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://mail.issg.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover>

Are you connected with Http or TCP? With EXRCA - All green lights? Lets set Set-WebServicesVirtualDirectory EWS* -BasicAuthentication $true Is it working with an emailaddress of XX@issg.local Martina Miskovic

Autodiscover is very powerfull (you know that by now) :) There are a lot of settings that can and sometimes has to be done in order to get it to work. Especially if a self-signed certificate is beeing used, or a SAN certificate is not beeing used. Sometimes the client the Outlook Autodiscover Settings has to be tweaked for Autodiscover and Availability to work and here are the registry settings that can be added (with different values to enable/disable the Autodiscover search orderr) PreferLocalXML"=dword:1 "ExcludeHttpRedirect"=dword:0 "ExcludeHttpsAutodiscoverDomain"=dword:1 "ExcludeHttpsRootDomain"=dword:1 "ExcludeScpLookup"=dword:1 "ExcludeSrvLookup"=dword:1 "ExcludeSrvRecord"=dword:1 You didn´t see any of those if the registry right under [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover] or [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover] depending on you Outlook version ? :Martina 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.

Ok, two new suggestions Change the internalurl for OWA: Set-OwaVirtualDirectory -InternalUrl https://mail.issg.local/OWA (has nothing to do with the OOF-Problem) Remove the Outlookprovider for EXCH: set-outlookprovider EXCH -server $null Restart IIS (if possible) Nice to see the right URLs for OAB :) :Martina 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.

Test output as follows; Am pretty sure all other services work - but now I've expanded the results I've noticed the certificate error - yet the test passed?? Connectivity Test Successful Test Details ExRCA is attempting to test Autodiscover for userlevel@islesofscilly-travel.co.uk. Autodiscover was tested successfully. Test Steps Attempting each method of contacting the Autodiscover service. The Autodiscover service was tested successfully. Test Steps Attempting to test potential Autodiscover URL https://islesofscilly-travel.co.uk/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name islesofscilly-travel.co.uk in DNS. The host name resolved successfully. Additional Details IP addresses returned: 213.175.198.12 Testing TCP port 443 on host islesofscilly-travel.co.uk to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server islesofscilly-travel.co.uk on port 443. ExRCA wasn't able to obtain the remote SSL certificate. Additional Details The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation. Attempting to test potential Autodiscover URL https://autodiscover.islesofscilly-travel.co.uk/AutoDiscover/AutoDiscover.xml Testing of the Autodiscover URL was successful. Test Steps Attempting to resolve the host name autodiscover.islesofscilly-travel.co.uk in DNS. The host name resolved successfully. Additional Details IP addresses returned: 78.143.215.69 Testing TCP port 443 on host autodiscover.islesofscilly-travel.co.uk to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.islesofscilly-travel.co.uk on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=mail.issg.co.uk, OU=Domain Control Validated, O=mail.issg.co.uk, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US. Validating the certificate name. The certificate name was validated successfully. Additional Details Host name autodiscover.islesofscilly-travel.co.uk was found in the Certificate Subject Alternative Name entry. Certificate trust is being validated. The certificate is trusted and all certificates are present in the chain. Test Steps ExRCA is attempting to build certificate chains for certificate CN=mail.issg.co.uk, OU=Domain Control Validated, O=mail.issg.co.uk. One or more certificate chains were constructed successfully. Additional Details A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US. Analyzing the certificate chains for compatibility problems with versions of Windows. No Windows compatibility problems were identified. Additional Details The certificate chain has been validated up to a trusted root. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 11/24/2010 1:57:26 PM, NotAfter = 11/24/2011 1:57:26 PM Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Attempting to send an Autodiscover POST request to potential Autodiscover URLs. ExRCA successfully retrieved Autodiscover settings by sending an Autodiscover POST. Test Steps ExRCA is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.islesofscilly-travel.co.uk/AutoDiscover/AutoDiscover.xml for user userlevel@islesofscilly-travel.co.uk. The Autodiscover XML response was successfully retrieved. Additional Details Autodiscover Account Settings XML response: <?xml version="1.0"?> <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Bob Tester</DisplayName> <LegacyDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=userlevel</LegacyDN> <DeploymentId>8811e676-6762-4080-8ac1-4a786610358b</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>pzex.issg.local</Server> <ServerDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX</ServerDN> <ServerVersion>720280B0</ServerVersion> <MdbDN>/o=issg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=PZEX/cn=Microsoft Private MDB</MdbDN> <ASUrl>https://mail.issg.co.uk/ews/Exchange.asmx</ASUrl> <OOFUrl>https://mail.issg.co.uk/ews/Exchange.asmx</OOFUrl> <OABUrl>https://mail.issg.co.uk/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <PublicFolderServer>pzex.issg.local</PublicFolderServer> <AD>PZDC.issg.local</AD> <EwsUrl>https://mail.issg.co.uk/ews/Exchange.asmx</EwsUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>mail.issg.co.uk</Server> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> <OOFUrl>https://mail.issg.co.uk/ews/exchange.asmx</OOFUrl> <OABUrl>https://mail.issg.co.uk/OAB/bf4cfd55-02df-4b95-9d89-e3c2ec66de7e/</OABUrl> <UMUrl>https://mail.issg.co.uk/UnifiedMessaging/Service.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <EwsUrl>https://mail.issg.co.uk/ews/exchange.asmx</EwsUrl> </Protocol> <Protocol> <Type>WEB</Type> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <External> <OWAUrl AuthenticationMethod="Fba">https://mail.issg.co.uk/owa</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://mail.issg.co.uk/ews/exchange.asmx</ASUrl> </Protocol> </External> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://pzex/owa</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://mail.issg.co.uk/ews/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover>

Connected via TCP All green lights on EXRCA test Set web-services: command completed successfully but no settings of 'PZEX\EWS (Default Web Site)' have been modified. Still get the same error if I set the account to have a default address @issg.local

Hi, These settings should work for you: Set-WebServicesVirtualDirectory EWS* -InternalUrl https://mail.issg.local/EWS/Exchange.asmx Set-OabVirtualDirectory OAB* -InternalUrl https://mail.issg.local/OAB Set-ClientAccessServer EXPR -AutoDiscoverServiceInternalUri https://mail.issg.local/autodiscover/autodiscover.xml I Hope this helps, MartinaPlease 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.

Set web-services: command completed successfully but no settings of 'PZEX\EWS (Default Web Site)' have been modified. That was weird, cause you didn´t use to have Basic on. Try again Output of get-webservicesvirtualdirectory Name : EWS (Default Web Site) InternalAuthenticationMethods : {Ntlm, WindowsIntegrated} ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated} BasicAuthentication : False DigestAuthentication : False WindowsAuthentication : True Can you look in the IIS-logs and see the "EWS-traffic"?Martina Miskovic

Hi Miskovic, Many thanks for that, however on the last one I got the following error; Set-ClientAccessServer : The operation could not be performed because object 'EXPR' could not be found on domain controller 'PZDC.issg.local'. At line:1 char:23 + Set-ClientAccessServer <<<< EXPR -AutoDiscoverServiceInternalUri https://mail.issg.local/autodiscover/autodiscover.xml Any clues?

Hi, Well in that case first resolve the certificate issue and it should work. Regards, JohanExchange-blog: www.johanveldhuis.nl

Sorry, I typed the wrong servername for your server. It is PZEX right? Set-ClientAccessServer PZEX -AutoDiscoverServiceInternalUri https://mail.issg.local/autodiscover/autodiscover.xml :MartinaPlease 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.