We established a vpn and domain trust (can ping and browse folders,etc). We just moved email at remote site from another location to home office exchange 2007 server. Email is working, and visibility of contacts and groups etc is fine, however free busy information is not available across the 2 domains (fine within each domain). Currently testing with a outlook 2010 client at remote site and 2007 at home site. Browsed all over the net, and can't seem to find a solution to this exact configuration...ONE exchange server, 2 domains in a 2 way trust over VPN. Outlook test reveals autodiscover.xml failed 0x80004005 (among other errors). thanks

Hi, Creating a two trust between the domains wont allow the options to share free busy information between those domain. Kindly follow this article and make sure, you performed all the steps to get this work http://technet.microsoft.com/en-us/library/bb125182(EXCHG.80).aspx Thank you

There's alot of steps involved, including export scp across domains, adding your internal availability address space then creating contact objects in order to lookup the address space. Preserve Cross Forest Free Busy When Migrating to New Forest Feasible? http://msexchangetips.blogspot.com/2010/12/preserver-cross-forest-free-busy.htmlJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

thanks for the replies. I am reading through this article: http://technet.microsoft.com/en-us/library/bb125182(EXCHG.80).aspx ...and James, as far as the article you reference, it specifically talks about 2 exchange servers...I have only one, so does it still pertain to my configuration? I read somewhere about setting up a DNS forward at the remote site to direct autodiscovery to the internal address of the exchange autodiscovery path...but i cant seem to get this to work either. I have tried to export the SPC to the remote domain, but get a login error (I know I have the correct admin credentials). Whatever problem i'm having, it's also preventing the remote domain from accessing their out of office.

thanks for the replies. I am reading through this article: http://technet.microsoft.com/en-us/library/bb125182(EXCHG.80).aspx ...and James, as far as the article you reference, it specifically talks about 2 exchange servers...I have only one, so does it still pertain to my configuration? I read somewhere about setting up a DNS forward at the remote site to direct autodiscovery to the internal address of the exchange autodiscovery path...but i cant seem to get this to work either. I have tried to export the SPC to the remote domain, but get a login error (I know I have the correct admin credentials). Whatever problem i'm having, it's also preventing the remote domain from accessing their out of office. Hi, The article you mentioned applied on the scenario that at least one Exchange server (Exchange 2007 or Exchange 2010) resided in each forest. What does it mean by "I have only one"? Do you have an Exchange 2007 server in your "home site", and a third party email server such as Notes in the "remote site"? If this is the scenario, the article is not applicable, and you might not be able to share the free/busy information across forests. So please provide more description on your network, it could help us better understand your request. Thanks for your time and patience. Fiona

one exchange 2007 server at the home site. We have VPN with 2 AD forests setup in a 2 way trusts. The remote site is using outlook clients (2007+) and are configured to connect to the home site exchange server. All of this is working, but the autodiscovery is not working at the remote site (no free/busy information or out of office). It would seem to me that DNS should be able to be configured at the remote site in such a way to allow autodiscovery to work, but I can't figure out how...i also read a post somewhere that suggested modifying the host file on the client PC's. We may end up having to just bring it all into 1 AD forest...but are trying to make this work first...as it's the least costly and distruptive approach.

to clairfy...autodiscovery works within each forest, just not across the forests. I have set up all the users from the remote site in AD and disabled the accounts and created linked mailboxes in exchange.

So you have 2 forests with a trust but only one forest has an Exchange server and the other forest never had an Exchange server? Did you export the auto discover config?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

correct...they were previously connected to an exchange server via VPN at a different location. We have reconfigured the outlook clients to point to the new home site, and email is working...just not autodiscovery/out of office...works through OWA though.

correct...they were previously connected to an exchange server via VPN at a different location. We have reconfigured the outlook clients to point to the new home site, and email is working...just not autodiscovery/out of office...works through OWA though. Ok, then you don't need that document. Simplely say, the Outlook 2007 client with mailbox resided in Exchange 2007 server retrieve free/busy information via Autodiscover service and Availability service. To make free/busy available for the remote site, we should firstly insure the two services available. I'd suggest you test the free/busy information in the Home site where the Exchange server resided on (try to see the free/busy information of remote users from users in home site, and versa). It will help us verify if it is working. And then run "Test Email Autoconfiguration" in two forests to get the services URLs. Then test the URLs returned in the remote site via IE (make sure there is no proxy or the URLs is excluded by the proxy). For detail steps, see http://technet.microsoft.com/en-us/library/bb397225(EXCHG.80).aspx. If there is any error, please capture a screenshot so that we can better understand. Fiona

free/busy works within the home site, but not at the remote...nor across the 2 sites. It works all around within OWA. The outlook test is fine in home site...but fails at remote. The screen shot is not good...so here's copy/paste from the log file: (I've changed the names...the test account is setup with @homesite.com email, but is linked to an account in the remote AD, per the instructions here: http://technet.microsoft.com/en-us/library/bb123524(EXCHG.80).aspx). Seems DNS issue to me. 4036 0x45E21840 09/14/11 07:11:16 +++++++++++++++++++++++++++++++ 4036 0x45E21840 09/14/11 07:11:16 AUTODISCOVER GET SETTINGS BEGIN 4036 0x45E21840 09/14/11 07:11:16 SMTP=testaccount@homesite.com 4036 0x45E2184F 09/14/11 07:11:16 Autodiscover to https://homesite.com/autodiscover/autodiscover.xml starting 4036 0x45E21F32 09/14/11 07:11:18 GetLastError=0; httpStatus=404. 4036 0x45E21F32 09/14/11 07:11:18 Autodiscover request completed with http status code 404 4036 0x45E21F42 09/14/11 07:11:18 Autodiscover to https://homesite.com/autodiscover/autodiscover.xml Failed (0x80004005) 4036 0x45E21F42 09/14/11 07:11:18 Autodiscover to https://autodiscover.homesite.com/autodiscover/autodiscover.xml starting 4036 0x45E2223E 09/14/11 07:11:19 GetLastError=0; httpStatus=502. 4036 0x45E2223E 09/14/11 07:11:19 Autodiscover request completed with http status code 502 4036 0x45E2223E 09/14/11 07:11:19 Autodiscover to https://autodiscover.homesite.com/autodiscover/autodiscover.xml Failed (0x80004005) 4036 0x45E2223E 09/14/11 07:11:19 Local autodiscover for homesite.com starting 4036 0x45E2223E 09/14/11 07:11:19 Local autodiscover for homesite.com Failed (0x8004010F) 4036 0x45E2223E 09/14/11 07:11:19 Redirect check to http://autodiscover.homesite.com/autodiscover/autodiscover.xml starting 4036 0x45E223A5 09/14/11 07:11:19 Srv Record lookup for http://autodiscover.homesite.com/autodiscover/autodiscover.xml Failed (0x80004005) 4036 0x45E223A5 09/14/11 07:11:19 Srv Record lookup for homesite.com starting 4036 0x45E223A5 09/14/11 07:11:19 Autodiscover URL redirection to https://exchangeserver.homesite.local/autodiscover/autodiscover.xml 4036 0x45E223A5 09/14/11 07:11:19 Autodiscover to https://exchangeserver.homesite.local/autodiscover/autodiscover.xml starting 4036 0x45E22634 09/14/11 07:11:20 GetLastError=0; httpStatus=502. 4036 0x45E22634 09/14/11 07:11:20 Autodiscover request completed with http status code 502 4036 0x45E22634 09/14/11 07:11:20 Autodiscover to https://exchangeserver.homesite.local/autodiscover/autodiscover.xml Failed (0x80004005) 4036 0x45E22634 09/14/11 07:11:20 Srv Record lookup for homesite.com Failed (0x80004005) 4036 0x45E22634 09/14/11 07:11:20 AUTODISCOVER GET SETTINGS END 4036 0x45E22644 09/14/11 07:11:20 ----------------------------- I will post the log from a Home site outlook client next.

Log from home user: 5912 0xB47D4030 09/14/11 08:28:56 +++++++++++++++++++++++++++++++ 5912 0xB47D4030 09/14/11 08:28:56 AUTODISCOVER GET SETTINGS BEGIN 5912 0xB47D4030 09/14/11 08:28:56 SMTP=homeuser@homesite.com 5912 0xB47D405F 09/14/11 08:28:56 Attempting URL https://exchangeserver.homesite.local/Autodiscover/Autodiscover.xml found through SCP 5912 0xB47D405F 09/14/11 08:28:56 Autodiscover to https://exchangeserver.homesite.local/Autodiscover/Autodiscover.xml starting 5912 0xB47D405F 09/14/11 08:28:56 AutoDiscover doing Pre-Auth with saved data. 5912 0xB47D405F 09/14/11 08:28:56 AutoDiscover PRE-AUTH pcreds->dwAuthScheme: 5912 0xB47D405F 09/14/11 08:28:56 Negotiate 5912 0xB47D408E 09/14/11 08:28:56 GetLastError=0; httpStatus=200. 5912 0xB47D408E 09/14/11 08:28:56 Autodiscover XML Received 5912 ---BEGIN XML--- <?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>Home User</DisplayName> <LegacyDN>/o=homesite/ou=first administrative group/cn=Recipients/cn=homeuser</LegacyDN> <DeploymentId>6ccb4e44-8cb3-4ddb-985d-c27a7d0cad3d</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>exchangeserver.homesite.local</Server> <ServerDN>/o=homesite/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=exchangeserver</ServerDN> <ServerVersion>720180F0</ServerVersion> <MdbDN>/o=homesite/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=exchangeserver/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>exchangeserver.homesite.local</PublicFolderServer> <AD>homeADserver.homesite.local</AD> <ASUrl>https://exchangeserver.homesite.local/EWS/Exchange.asmx</ASUrl> <EwsUrl>https://exchangeserver.homesite.local/EWS/Exchange.asmx</EwsUrl> <OOFUrl>https://exchangeserver.homesite.local/EWS/Exchange.asmx</OOFUrl> <UMUrl>https://exchangeserver.homesite.local/UnifiedMessaging/Service.asmx</UMUrl> <OABUrl>Public Folder</OABUrl> </Protocol> <Protocol> <Type>EXPR</Type> <Server>mail.homesite.net</Server> <SSL>On</SSL> <AuthPackage>Ntlm</AuthPackage> <OABUrl>Public Folder</OABUrl> </Protocol> <Protocol> <Type>WEB</Type> <External> <OWAUrl AuthenticationMethod="Fba">https://mail.homesite.net/owa</OWAUrl> </External> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://exchangeserver.homesite.local/owa</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://exchangeserver.homesite.local/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> </Protocol> </Account> </Response> </Autodiscover> 5912 ----END XML---- 5912 0xB47D409D 09/14/11 08:28:56 Autodiscover to https://exchangeserver.homesite.local/Autodiscover/Autodiscover.xml succeeded (0x00000000) 5912 0xB47D409D 09/14/11 08:28:56 AUTODISCOVER GET SETTINGS END 5912 0xB47D409D 09/14/11 08:28:56 -----------------------------

Thanks for your update. You are correct, the Autodiscover service connection failed so the client could not retrieve free/busy information from the client forest. To troubleshoot this issue, please add a local record in the host file and point the URL https://homesite.com/autodiscover/autodiscover.xml to the IP address of your Exchange CAS server. And then, test the URL in ID in the problematic machine. If you can receive the error code 600, go ahead and test in Outlook to see if you are able to retrieve the free/busy information. if all are working fine, you may then add a A record in your DNS server so that all clents can resolve this URL. Fiona

Our problems are resolved, thanks for you help