[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Exchange 2010 Out of Office - Server Unavailable

Posted on 2013-01-17
15
Medium Priority
?
362 Views
Last Modified: 2013-11-08
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.
0
Comment
Question by:networkn
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 8
  • 3
  • 2
  • +1
15 Comments
 
LVL 37

Expert Comment

by:Neil Russell
ID: 38789213
Is the autodiscover A record existing in DNS and correct?
0
 

Author Comment

by:networkn
ID: 38789237
Hi, pinging "autodiscover" from a workstation results in the new exchange servers ip being returned.
0
 
LVL 37

Expert Comment

by:Neil Russell
ID: 38789260
What outlook clients do you have?

What happens if you put

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

into your web browser?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 

Author Comment

by:networkn
ID: 38789272
I get an authentication request.
0
 
LVL 16

Expert Comment

by:joinaunion
ID: 38789275
Can you run test here and post back.

https://www.testexchangeconnectivity.com/
0
 

Author Comment

by:networkn
ID: 38789363
Which test am I looking to do? The OOF?
0
 
LVL 16

Expert Comment

by:joinaunion
ID: 38789402
The Microsoft Exchange ActiveSync Connectivity Tests .
0
 

Author Comment

by:networkn
ID: 38789433
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
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38789455
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
 

Author Comment

by:networkn
ID: 38789705
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
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38792706
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
 

Author Comment

by:networkn
ID: 38795095
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
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38796682
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
 

Accepted Solution

by:
networkn earned 0 total points
ID: 39046676
The problem was fixed with the latest service pack rollup for Exchange.
0
 

Author Closing Comment

by:networkn
ID: 39632977
My answer was the one that solved the problem
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question