Link to home
Start Free TrialLog in
Avatar of bushido2006
bushido2006Flag for United States of America

asked on

Free/Busy not working in Exchange 2007

Recenty deployed an exchange 2010 server to coexist with an Exchange 2007 Server. All Traffic is happily flowing through the Exchange 2010 CAS, OA, EAS, OWA, etc. Users on Exchange 2010 can see Free/Busy info for other users on 2010 but users on 2007 cannot access Free/Busy. Users on 2010 cannot see users free/busy on 2007

I have attached an output of the test-outlookwebservices for a users account who is on the 2007 still
[PS] C:\Windows\system32>Test-OutlookWebServices -identity user@domain.com<mailto:user@domain.com> | fl

Id      : 1003
Type    : Information
Message : About to test AutoDiscover with the e-mail address user@domain.com<mailto:user@domain.com>.

Id      : 1012
Type    : Warning
Message : XML>Unknown Node:AutoDiscoverSMTPAddress AutoDiscoverSMTPAddress Line:http://schemas.micr
          osoft.com/exchange/autodiscover/outlook/responseschema/2006a

Id      : 1012
Type    : Warning
Message : XML>Object being deserialized: Microsoft.Exchange.Management.SystemConfigurationTasks.Aut
          oDiscoverUser

Id      : 1012
Type    : Warning
Message : XML>Element

Id      : 1012
Type    : Warning
Message : XML>Unknown Element:System.Xml.XmlElement Line:8(8) user@domain.com<mailto:user@domain.com>

Id      : 1006
Type    : Information
Message : The Autodiscover service was contacted at https://mail.domain.com/autodiscover/auto
          discover.xml.

Id      : 1011
Type    : Error
Message : When querying Availability for Juser@domain.com<mailto:user@domain.com> received 5016:

Id      : 1016
Type    : Error
Message : [EXCH]-Error when contacting the AS service at https://mail.domain.com/ews/exchange
          .asmx. The elapsed time was 312 milliseconds.

Id      : 1015
Type    : Information
Message : [EXCH]-The OAB is not configured for this user.

Id      : 1013
Type    : Error
Message : When contacting https://mail.domain.com/unifiedmessaging/service.asmx received the
          error The remote server returned an error: (404) Not Found.

Id      : 1014
Type    : Error
Message : [EXCH]-Error when contacting the UM service at https://mail.domain.com/unifiedmessa
          ging/service.asmx. The elapsed time was 0 milliseconds.

Id      : 1013
Type    : Error
Message : When contacting https://legacy.domain.com/ews/exchange.asmx received the error The
          request failed with HTTP status 401: Unauthorized.

Id      : 1016
Type    : Error
Message : [EXPR]-Error when contacting the AS service at https://legacy.domain.com/ews/exchan
          ge.asmx. The elapsed time was 15 milliseconds.

Id      : 1015
Type    : Success
Message : [EXPR]-Successfully contacted the OAB service at https://legacy.domain.com/ews/exch
          ange.asmx. The elapsed time was 0 milliseconds.

Id      : 1014
Type    : Information
Message : [EXPR]-The UM is not configured for this user.

Id      : 1017
Type    : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://mail.domain.com/Rpc.
          The elapsed time was 0 milliseconds.

Id      : 1006
Type    : Success
Message : The Autodiscover service was tested successfully.

Id      : 1021
Type    : Information
Message : The following web services generated errors.
              As,UM in EXCH
              As in EXPR
          Please use the prior output to diagnose and correct the errors.



[PS] C:\Windows\system32>Get-clientAccessServer | fl Name,AutoDiscoverServiceInternalUri

Name                           : EXCHANGE 2007 cas
AutoDiscoverServiceInternalUri : https://mail.DOMAIN.com/autodiscover/autodiscover.xml

Name                           : EXCHANGE 2010 CAS
AutoDiscoverServiceInternalUri : https://2010fqdn.fremontgroup.com/Autodiscover/Autodiscover.xml

Open in new window

Avatar of bushido2006
bushido2006
Flag of United States of America image

ASKER

i also tried updating the the 2007 CAS url to reflect the legacy URL name, changes made below did not resolve the issue:

get-clientaccessserver | fl name,autodiscoverserviceinternalUri

Name                           : exchange 2007 CAS
AutoDiscoverServiceInternalUri : https://mail.domain.com/autodiscover/autodiscover.xml

Name                           : exchange 2010 cas
AutoDiscoverServiceInternalUri : https://netbiosname.domain.com/Autodiscover/Autodiscover.xml

****************************************************************************************************
****************************************************************************************************
****************************************************************************************************

Get-WebServicesVirtualDirectory -server exchnage2007 | fl *url

InternalNLBBypassUrl : https://server_netbios_name.domain.com/ews/exchange.asmx
InternalUrl          : https://mail.domain.com/ews/exchange.asmx
ExternalUrl          : https://legacy.domain.com/ews/exchange.asmx

****************************************************************************************************
****************************************************************************************************
****************************************************************************************************

Set-ClientAccessServer -Identity sf-mail01 -AutoDiscoverServiceInternalUri: https://legacy.domain.com/autodiscover/autodiscover.xml
Get-WebServicesVirtualDirectory -server sf-mail01 | Set-webservicesvirtualdirectory -internalurl https://legacy.domain.com/EWS/Exchange.asmx
You'll need to update your exchange 2010 server with latest windows update as well as update rollups and service packs of exchange 2010, this is a known issue and MS has fixed it one of its recent rollups.
updating the latest windows patches is a great idea but i dont want to go off and just update exchange without knowing if my EWS and Auutodiscover settings are incorrect becuase if they are the updates will not be helpful at all.
from one of the affected client, desktop
When you run the "Test Email autoconfiguration" what is the results?

Concentrate at the results and log tabs?

Log tab:
- If Outlook is trying to use the SCP object...then clients are connected to the domain
- If Outlook is trying to use the autodiscover.emaildomain.com...then clients are not-connected to the domains

In both the cases, the results tab should have the URLs listed

>> check if the affected users are using HTTPs protocol(connection-status)...so we need to check the ExternalURL for the Autodiscover v.directory (@ E2k7 server!)
ASKER CERTIFIED SOLUTION
Avatar of bushido2006
bushido2006
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
was able to resolve on my own