Hi,I am trying to work out why my Outlook 2007 clients don't work correctly through OA.We are going through an ISA server, e-mail etc. receives correctly, everything works directly from OWA as well.When I do test autoconfigure when I am connected to OA, it is looking for https://domain.com/autodiscover/autodiscover.xml and https://autodiscover.domain.com/autodiscover/autodiscover.xmlwhen it is actually at https://exchange.pentanasolutions.com/autodiscover/autodiscover.xml.How do I go about changing this?In adsiedit the serviceBindingInformation says https://internal-server-name.domain.local/autodiscover/autodiscover.xml.Can I just add my external site to that as well? Is there a way to fix this through a cmdlet or the management console?Regards,TerryTerry http://www.sucked-in.com

There are three methods to change: First one is to create a DNS record to point autodiscover.domain.com to the IP address of CAS server, which will require client to trust the autodiscover.domain.com. So, the certificate needs to be added the name autodiscover.domain.com Second option is to redirect the client from autodiscover.domain.com to exchange.pentanasolutions.com, please refer the Http Referral section in this article to do it The last one is to use SRV record, please refer the links in the Jon-Alfred Smiths post of this articleJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

James,I'm not sure what the best way for me to do all this is.I am currently using a certificate which is signed my my domain CA for exchange.domain.com.I want to get this autodiscover working for my Outlook 2007 clients seemlessly.I had a look at those posts and found that the easist way might be to create a SRV record in DNS for my internal domain which points to the external address resolveable. However, when I go to create the SRV record the _autodiscover service is not listed and If i type it in manually I get " A new record cannot be created. The name is invalid."Any ideas?Regards,TerryTerry http://www.sucked-in.com

Have you seen the KB 940881? This 3rd party website has provided a walkthrough about the SRV creationJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

James,I have added the SRV record for, i get the message when we open outlook to accept the redirect.I still have the same issue though, Out of Office still doesn't work, neither does the free/busy calendary information.Regards,TerryTerry http://www.sucked-in.com

The issue is only for the FB and OOF, but not the mail flow for the OA users, isnt it? I assume that the exchange.pentanasolutions.com stays in the client trusted certificate, right? (Similar case) Please put the problematic OA clients machine into the internal network, and check both On fast networks and On slow networks , so you can verify the pure OA function. Please check the Connection status and do the AutoConfiguration Test Please test the AutoDiscover with Microsoft Exchange Remote Connectivity Analyzer Resources: OOF and Free Busy not working in Outlook 2007, works fine in OWA (Similar case)James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

James,OK, when i browse to the https://exchange.domain.com/autodiscover/autodiscover.xml I get the following: <?xml version="1.0" encoding="utf-8" ?> - <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> - <Response> - <Error Time="14:34:31.3246615" Id="3736625508"> <ErrorCode>600</ErrorCode> <Message>Invalid Request</Message> <DebugData /> </Error> </Response> </Autodiscover> I tested the Outlook 2007 Autodiscover test with the Microsoft Exchange Remote Connectivity Analyzerand it all seemed to work. This was at the end of the test: Attempting to send AutoDiscover POST request to potential autodiscover URLs. Successfully Retrieved AutoDiscover Settings by sending AutoDiscover POST. Test Steps Attempting to Retrieve XML AutoDiscover Response from url https://exchange.domain.com/Autodiscover/Autodiscover.xml for user user.name@domain.com Successfully Retrieved AutoDiscover XML Response Additional Details AutoDiscover Account SettingsXML Response:<?xml version="1.0"?><Autodiscover xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"><Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"><User><DisplayName>User Name</DisplayName><LegacyDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user.name</LegacyDN><DeploymentId>f37af56e-414d-47b7-8b37-8995fa0681f2</DeploymentId></User><Account><AccountType>email</AccountType><Action>settings</Action><Protocol><Type>EXCH</Type><Server>AUMEL-WIN-EXH01.domain.local</Server><ServerDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=AUMEL-WIN-EXH01</ServerDN><ServerVersion>720180F0</ServerVersion><MdbDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=AUMEL-WIN-EXH01/cn=Microsoft Private MDB</MdbDN><ASUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</ASUrl><OOFUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</OOFUrl><OABUrl>http://aumel-win-exh01.domain.local/OAB/d3ea18c7-047c-4ba9-9fc4-2423465d2f61/</OABUrl><UMUrl>https://aumel-win-exh01.domain.local/UnifiedMessaging/Service.asmx</UMUrl><Port>0</Port><DirectoryPort>0</DirectoryPort><ReferralPort>0</ReferralPort><PublicFolderServer>AUMEL-WIN-EXH01.domain.local</PublicFolderServer><AD>AUMEL-WIN-DC02.domain.local</AD><EwsUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</EwsUrl></Protocol><Protocol><Type>EXPR</Type><Server>exchange.domain.com</Server><OABUrl>https://exchange.domain.com/OAB/d3ea18c7-047c-4ba9-9fc4-2423465d2f61/</OABUrl><Port>0</Port><DirectoryPort>0</DirectoryPort><ReferralPort>0</ReferralPort><SSL>On</SSL><AuthPackage>Basic</AuthPackage></Protocol><Protocol><Type>WEB</Type><Port>0</Port><DirectoryPort>0</DirectoryPort><ReferralPort>0</ReferralPort><External><OWAUrl AuthenticationMethod="Fba">https://webmail.domain.com/</OWAUrl></External><Internal><OWAUrl AuthenticationMethod="Basic, Ntlm, WindowsIntegrated">https://aumel-win-exh01.domain.local/owa</OWAUrl><Protocol><Type>EXCH</Type><ASUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</ASUrl></Protocol></Internal></Protocol></Account></Response></Autodiscover When connected via HTTPS i did the outlook 2007test discovery, this is what I got: <?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>User Name</DisplayName> <LegacyDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=terry.sposato</LegacyDN> <DeploymentId>f37af56e-414d-47b7-8b37-8995fa0681f2</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>AUMEL-WIN-EXH01.domain.local</Server> <ServerDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=AUMEL-WIN-EXH01</ServerDN> <ServerVersion>720180F0</ServerVersion> <MdbDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=AUMEL-WIN-EXH01/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>AUMEL-WIN-EXH01.domain.local</PublicFolderServer> <AD>AUMEL-WIN-DC02.domain.local</AD> <ASUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://aumel-win-exh01.domain.local/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>http://aumel-win-exh01.domain.local/OAB/d3ea18c7-047c-4ba9-9fc4-2423465d2f61/</OABUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>exchange.domain.com</Server> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <OABUrl>https://exchange.domain.com/OAB/d3ea18c7-047c-4ba9-9fc4-2423465d2f61/</OABUrl> </Protocol> <Protocol> <Type>WEB</Type> <External> <OWAUrl AuthenticationMethod="Fba">https://webmail.domain.com/</OWAUrl> </External> <Internal> <OWAUrl AuthenticationMethod="Basic, Ntlm, WindowsIntegrated">https://aumel-win-exh01.domain.local/owa</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://aumel-win-exh01.domain.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover> There is nothing wrong with the pure OA functions at all remotely. Everything works fine internally, the only thing that doesn't work whilst using Outlook away from the office and not VPN'd into our network is the free/busy information and the Out of Office assistant. Terry http://www.sucked-in.com

Looks like you didnt configure the external URL for Exchange Web Services for the Autodiscover service yet ========== <Type>EXPR</Type> <Server>exchange.domain.com</Server> MISSING Url for OOF/AS <OABUrl>https://exchange.domain.com/OAB/d3ea18c7-047c-4ba9-9fc4-2423465d2f61/</OABUrl> ========== Please see this articleJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

I just changed that to exchange.domain.com for the output.I reconfigured the command as well but still no luck :(Terry http://www.sucked-in.com

After the reconfiguration, the URLs can be retrieved in the XML files? You have confirmed with Test AutoConfiguration? James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Please see the article below:http://support.microsoft.com/kb/958934/en-usThis may help. It resolved this issue for me on a recent Exchange 2007 migration.