Exchange 2010 Out of Office - Server Unavailable

We recently "upgraded" from 2003 with Exchange 2007 (Non SBS) to SBS 2011.

Since the upgrade users cannot use the Out of Office function, getting an error that the server is unavailable. They can access it via OWA.

Server is patched up to date.

We have checked the obvious things like the autodiscover paths.
networknAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
networknConnect With a Mentor Author Commented:
The problem was fixed with the latest service pack rollup for Exchange.
0
 
Neil RussellTechnical Development LeadCommented:
Is the autodiscover A record existing in DNS and correct?
0
 
networknAuthor Commented:
Hi, pinging "autodiscover" from a workstation results in the new exchange servers ip being returned.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Neil RussellTechnical Development LeadCommented:
What outlook clients do you have?

What happens if you put

https://autodiscover.yourcompany.com/autodiscover/autodiscover.xml

into your web browser?
0
 
networknAuthor Commented:
I get an authentication request.
0
 
joinaunionCommented:
Can you run test here and post back.

https://www.testexchangeconnectivity.com/
0
 
networknAuthor Commented:
Which test am I looking to do? The OOF?
0
 
joinaunionCommented:
The Microsoft Exchange ActiveSync Connectivity Tests .
0
 
networknAuthor Commented:
Well it's failing, but I'd expect it to, since it won't be able to resolve the autodiscover from externally as there is (and never has been) an autodiscover dns A record for external resolution.
0
 
Simon Butler (Sembee)ConsultantCommented:
You don't need an internal autodiscover record unless you have Mac clients or clients on your network that are not members of the domain but need to access Exchange.

Primary reason for this is SSL certificates issues, or incorrect configuration on the client access role.
Therefore the first thing to check is the Client Access Configuration.

get-clientaccessserver | select Identity, AutodiscoverServiceInternalURI

Ensure that the value for AutodiscoverServiceInternalURI is valid, resolves correctly and is on your SSL certificate.
Do you have a commercial SSL certificate?

If you want to access Exchange remotely, using Outlook Anywhere then you will need an external DNS record for Autodiscover.

Was the server configured using the wizards in SBS?

Simon.
0
 
networknAuthor Commented:
Hi There!

The get-clientaccesserver, returned two servers, both with the same url, and the old server is first, though I am not sure if that means it's primary or the list is just returning alphabetically.

The old server is still on the network, though it shouldn't be serving any purpose. We just haven't removed it yet. Should I remove it from the InternalURI?
0
 
Simon Butler (Sembee)ConsultantCommented:
Where does the URL resolve to? It should be resolving to the new server. That will mean that even if the old server publishes the URL to the domain, the traffic will be pointing to the new server.

Simon.
0
 
networknAuthor Commented:
Well EX1 is pointing to exchange.domain.com and EX2 is pointing to exchange.domain.com as well. So effectively they are pointing at the right place.
0
 
Simon Butler (Sembee)ConsultantCommented:
have you checked all of the other URLs on the Exchange 2007 server to see if they are now configured for the new server? It could be that something is being published wrong by autodiscover.

Simon.
0
 
networknAuthor Commented:
My answer was the one that solved the problem
0
All Courses

From novice to tech pro — start learning today.