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

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."

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

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."

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."

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

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

Hi, So, finally sorted out our multidomain certificate (Lets call that Certificate 1) but my colleague registered the wrong Autodiscover SAN name for our mail server. Apart from that mistake, the certificate is functioning fine. Aside from adding the correct SAN's to the certificate, my colleague was advised to purchase a separate certificate with correct Autodiscover name and to run both certificates concurrently (Lets call this one Certificate 2). However, the Autodiscover website (created in IIS) that gets created by Exchange can only use one certificate at a time. Therefore I created a separate website for autodiscover and have assigned Certificate 2 to that website. However, Outlook is still referencing Certificate 1 for Autodiscover even though the only Autodiscover webpage that exists on our mail server should be using Certificate 2. The Autodiscover virtual directory is configured correctly and is pointing to the second webpage that I created. Is it possible for Autodiscover to work correctly in this configuration?

No, it cannot. Create a new certificate signing request with the correct names and have your colleague get the certifiate reissued. Your provider will probably do that at no cost.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."