Hi, Have had an issue with configuring OOF to work when using Exchange 2007 & Outlook 2007 onwards. We have the correct certificates installed with regards to SAN names and i believe that i've set the correct host records in DNS. Autodiscover appears to be working, atleast when using Outlook's "Test Email AutoConfiguration" tool and i believe that i've set the addresses for the services below in line with my organisation's naming scheme Offline Address Book (OAB) Unified Messaging Out of Office (OOF) Availability Services But OOF will still report that the server is unavailable when i try to set it? Any ideas? Thanks Ashley

When you run: Get-WebServicesVirtualDirectory | FL Server,InternalUrl,ExternalUrl do the results look right?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, Have had an issue with configuring OOF to work when using Exchange 2007 & Outlook 2007 onwards. We have the correct certificates installed with regards to SAN names and i believe that i've set the correct host records in DNS. Autodiscover appears to be working, atleast when using Outlook's "Test Email AutoConfiguration" tool and i believe that i've set the addresses for the services below in line with my organisation's naming scheme Offline Address Book (OAB) Unified Messaging Out of Office (OOF) Availability Services But OOF will still report that the server is unavailable when i try to set it? Any ideas? Thanks Ashley Hi Ashley, Please follow the steps below to troubleshoot this issue: 1. Can OOF work in OWA with the affected user account? 2. Can you open OOF url (Returned by "Test Email AutoConfiguration" ) in the affected client computer in IE? 3. Can you open EWS url in CAS server concel (https://localhost/EWS/Exchange.asmx) ? 4. How many users are not able to use OOF?Fiona Liao TechNet Community Support

Hi Ed, Yes the results look fine and as expected.... Server = The NETBIOS name of my Exchange Server InternalURL = https://"Exchange Server FQDN"/EWS/Exchange.asmx ExternalURL = https://"External Domain Name of Exchange Server"/EWS/Exchange.asmx Thanks Ashley

Hi Fiona, Answers as requested..... 1. Can OOF work in OWA with the affected user account? Yes, OOF works when set through OWA 2. Can you open OOF url (Returned by "Test Email AutoConfiguration" ) in the affected client computer in IE? Yes, I can access the xml page 3. Can you open EWS url in CAS server concel (https://localhost/EWS/Exchange.asmx) ? Yes, but I get a security certifcate error when using "localhost". If I try to access the same page with "ExchangeFQDN" then I can access it fine 4. How many users are not able to use OOF? Everyone who use's Outlook 2007 & 2010 are affected Thanks Ashley

Hi Fiona, Answers as requested..... 1. Can OOF work in OWA with the affected user account? Yes, OOF works when set through OWA 2. Can you open OOF url (Returned by "Test Email AutoConfiguration" ) in the affected client computer in IE? Yes, I can access the xml page 3. Can you open EWS url in CAS server concel (https://localhost/EWS/Exchange.asmx) ? I could but was getting a security certificate issue stating a name mis match. I re-installed our security certificate which contains the SAN's for our Exchange servers FQDN & it's external domain name to the Trusted Root CA folder and am now unable to access the EWS url. I haven't tried restarting the Exchange server yet though since re-installing the certificate 4. How many users are not able to use OOF? Everyone who use's Outlook 2007 & 2010 are affected Thanks Ashley

Is both "Exchange Server FQDN" and "External Domain Name of Exchange Server" in the certificate? Is there any reason you can't use the external name internally?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, Yes, both names are on the certificate. I can navigate to the external address internally via IE.... However, when I run Test-OutlookWebServices I get a 1013 & 1016 error regarding the external OOF url Thanks Ashley

Always post the complete results. Few of us memorize the error codes.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, Full results of Test-OutlookWebServices | fl Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address xxxxxxxxxxxxx@guests.co.uk. Id : 1007 Type : Information Message : Testing server mailbox.guest.motors with the published name https://"ExchangeFQDN"/ews/exchange.asmx & https://"ExternalExchangeDomainName"/ews/exchange.asmx. Id : 1019 Type : Information Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://"ExchangeFQDN"/AutoDiscover/AutoDiscover.xml. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://"ExchangeFQDN"/AutoDiscover/AutoDiscover.xml. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://"ExchangeFQDN"/ews/exchange.asmx. The elapsed time was 46 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at https://"ExchangeFQDN"/ews/exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://"ExchangeFQDN"/unifiedmessaging/service.asmx. The elapsed time was 0 milliseconds. Id : 1013 Type : Error Message : When contacting https://"ExchangeExternalDomainName"/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://"ExchangeExternalDomainName"/ews/exchange.asmx. The elapsed time was 31 milliseconds. Id : 1015 Type : Information Message : [EXPR]-The OAB is not configured for this user. Id : 1014 Type : Success Message : [EXPR]-Successfully contacted the UM service at https://"ExchangeExternalDomainName"/unifiedmessaging/service.asmx. The elapsed time was 31 milliseconds. Id : 1017 Type : Success Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://"ExchangeNetBios"/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. As in EXPR Please use the prior output to diagnose and correct the errors. Thanks Ashley

Does the external host name go to the right place? Does it hairpin out of your network and back in? If so, does it go through some kind of web publishing device?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, Yes, as we've created a primary zone on our Primary DNS server which relates to our external host namespace. We've created an 'A' record in that name space for our "ExchangeServer".externaldomainname.com and also autodiscover.externaldomainname.com which points to our Exchange server's private IP address... Therefore my understanding would be that it I doesn' t hairpin out and then back into our network.

You'll want to verify that, and you'll want to be sure that the URL works internally for the external name, because that's what is apparently failing.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, If I navigate to the external url internally I arrive at the xml page with no problem at all.... Out of interest should the Availability Service share the same url as the OOF url?

Out of Office and Availability are both parts of Web Services, so both use the URL specified in Set-WebServicesVirtualDirectory cmdlet.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks..... However I can navigate to the external url internally with no problem at all.....

Did you create the CAS probing account using the ...\Scripts\new-TestCasConnectivityUser.ps1 script?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, Forgive me but i'm not really sure what you mean? I'm working on an Exchange server that someone else set up a while ago and who no longer works for us I've tested "Test-OutlookWebServices -digestauthentication $true" with Windows & Basic authentication set to $false and then re-tried Test-OutlookWebServices |fl again; I get no errors...... Yet OOF still doesnt work !!

Some of the Test- cmdlets require the user account created by the script I mentioned. I'm not sure if that has anything to do with your failure. But that doesn't sound like it's your problem now. Why do you have Windows and Basic authentication set to $False?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Setting them to $false is just something that I was playing around with. With them both set to $true I get the http errors mentioned above when running Test-OutlookWebServices. When they are set to $false and Digest Authentication is set to $true, the errors go away when using the cmdlet Test-OutlookWebServices The following sentence reflects how our Exchange server is currently configured - if I leave the EWS virtual directory at its default authenitcation level (Windows & Basic $true) and amend the registry in the manor described in Method 2 of this link http://support.microsoft.com/?id=896861 then Test-OutlookWebServices passes with flying colours

We also have the exact same problem at a customer site. <o:p></o:p> There is also a DNS zone with the external domain name "mobile.customerdomainname.nl" that is pointing to the private IP in the internal network. All links are working fine (internal and external).<o:p></o:p> It doesnt matter what we do, the OOF is still not working. so Im interested what other options there are to set and test.<o:p></o:p>

Take a look at this, I had the same issue and fixed it with a few permission changes. Let me know if it works. http://forums.msexchange.org/Out_of_Office_Assistant_not_working/m_1800561781/tm.htm