We are starting to migrate from Exchange 2007 to Exchange 2010. We are noticing that users that use Outlook 2010 to access Exchange 2010 cannot see the free / busy data of any other users (Exchange 2007 or Exchange 2010). Accessing the accounts via OWA the free / busy data is present and correct. If we run the Autodiscover test it tries to first contact Exchange 2007 and fails, but then contacts Exchange 2010 and succeeds. Is there some additional tests we can run to troubleshoot the problem?

Did you install Exchange 2010 Client Access Servers first? Did you change Autodiscover to point to them? http://technet.microsoft.com/en-us/library/bb125157.asp Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, Is the user mailbox on Exchange 2007 server or Exchange 2010 server? Do you modify the AutoDiscover URL and point it to the new server? At this stage, I suggest you perform the following steps to troubleshoot the issue. 1. Test Test E-mail AutoConfiguration a. While Outlook is running, hold down the CTRL key, right-click the Outlook icon in the notification area, and then select Test E-mail AutoConfiguration. b. Verify that the correct e-mail address is in the box next to E-mail Address. c. Clear the check boxes next to Use Guessmart and Secure Guessmart Authentication. d. On the Test E-mail AutoConfiguration page, verify that the check box next to Use AutoDiscover is selected, and then click the Test button. e. Then, please check whether there is any error code. If so, please post it here for research. 2. Test Availability Service. Please open EMS and type the following cmdlet to test Availability Service. Then, please send the result to me for research. Test-OutlookWebServices -id:user1@contoso.com -TargetAddress: user2@contoso.com 3. Please navigate to http://www.testexchangeconnectivity.com and select “Outlook AutoDiscover” to analyze the problem. Thanks. Novak Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

It is actually different between servers. I think one of the servers is not fully configured. Server 1 RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://we bmailtest.scj.com/. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1013 Type : Error Message : When contacting https://webmailtest.scj.com/ received the error The remote server returned an error: (401) Unauthorized. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1023 Type : Error Message : The Autodiscover service couldn't be contacted. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1113 Type : Error Message : When contacting https://USRACIPM025.global.scj.loc:443/ received the error The remote server returned an e rror: (401) Unauthorized. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1123 Type : Error Message : The Autodiscover service couldn't be contacted. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1024 Type : Success Message : [EXCH] Successfully contacted the AS service at https://usracipm025.global.scj.loc/EWS/Exchange.asmx. The elapsed time was 921 milliseconds. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1026 Type : Success Message : [EXCH] Successfully contacted the UM service at https://usracipm025.global.scj.loc/EWS/Exchange.asmx. The elapsed time was 312 milliseconds. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1124 Type : Success Message : [Server] Successfully contacted the AS service at https://usracipm025.global.scj.loc/ews/exchange.asmx. Th e elapsed time was 296 milliseconds. RunspaceId : 780c204a-1acb-4bc3-9ae9-5580e896baf5 Id : 1126 Type : Success Message : [Server] Successfully contacted the UM service at https://usracipm025.global.scj.loc/ews/exchange.asmx. Th e elapsed time was 78 milliseconds. Server 2 RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://US WAXDPM024.GLOBAL.SCJ.LOC/Autodiscover/Autodiscover.xml. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1006 Type : Information Message : Contacted the Autodiscover service at https://USWAXDPM024.GLOBAL.SCJ.LOC/Autodiscover/Autodiscover.xml. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1016 Type : Information Message : [EXCH] The AS is configured for this user in the Autodiscover response received from https://USWAXDPM024.G LOBAL.SCJ.LOC/Autodiscover/Autodiscover.xml. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1015 Type : Information Message : [EXCH] The OAB is configured for this user in the Autodiscover response received from https://USWAXDPM024. GLOBAL.SCJ.LOC/Autodiscover/Autodiscover.xml. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1014 Type : Information Message : [EXCH] The UM is configured for this user in the Autodiscover response received from https://USWAXDPM024.G LOBAL.SCJ.LOC/Autodiscover/Autodiscover.xml. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1022 Type : Success Message : Autodiscover was tested successfully. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1013 Type : Error Message : When contacting https://uswaxdpm024.global.scj.loc/EWS/Exchange.asmx received the error The request failed with an empty response. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1025 Type : Error Message : [EXCH] Error contacting the AS service at https://uswaxdpm024.global.scj.loc/EWS/Exchange.asmx. Elapsed ti me was 203 milliseconds. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1026 Type : Success Message : [EXCH] Successfully contacted the UM service at https://uswaxdpm024.global.scj.loc/EWS/Exchange.asmx. The elapsed time was 62 milliseconds. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1113 Type : Error Message : When contacting https://uswaxdpm024.global.scj.loc/ews/exchange.asmx received the error The request failed with an empty response. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1125 Type : Error Message : [Server] Error contacting the AS service at https://uswaxdpm024.global.scj.loc/ews/exchange.asmx. Elapsed time was 0 milliseconds. RunspaceId : 0c36d570-8c77-4fb3-b04a-f3ab2afcf02d Id : 1126 Type : Success Message : [Server] Successfully contacted the UM service at https://uswaxdpm024.global.scj.loc/ews/exchange.asmx. Th e elapsed time was 15 milliseconds.

Based on the result, we can find that AS service can work fine but AutoDiscover service does not work on Exchange 2007. On Exchange 2010, AutoDiscover service can work fine but AS service cannot be contacted. At this stage, I suggest you rebuild AS Virtual Directory on Exchange 2010 to check the result. a. Remove the EWS virtual directory in client access server. Open Exchange Management Shell. Run the command below: Remove-WebServicesVirtualDirectory “CAS server\EWS (Default Web Site)” If you get the confirm information, please type “Y” b. Create a new EWS virtual directory. Run the command below in Exchange Management Shell: New-WebServicesVirtualDirectory –WebSiteName “Default Web Site” Set-WebServicesVirtualDirectory -Identity “CAS server\EWS (Default Web Site)” -InternalUrl https://contoso.internal.com/EWS/exchange.asmx c. Do an IISreset /noforce Then, please check whether the user can access Free/Busy information now. If still not, please manually access the Availability Service URL to check the result. Meanwhile, please send the IIS log to me for research. Collect the IIS log on the CAS server =========================== a. Click "start" -- "adminstrative tools" -- Internet Information Services b. Right-click "default web site" -- properties c. In "web site" tap, click "enable logging", select log format to "W3C" d. Please reproduce this issue. e. the log will be generated in \windows\system32\logfile\w3svc1\exyymmdd.log f. Select the current log, compress to *.zip or *.rar file. Thanks. Novak Wu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.