[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1885
  • Last Modified:

Exchange Free/Busy, Out of office

Hello,

We have recently installed a new Exchange 2010 environment in a Data Center for a customer.  This is not a migration or an upgrade, it is a clean install.  We have two Exchange servers behind a Barracuda load balancer.  All users connect via RPC over HTTPS.  Everything is working correctly except that Free/Busy information does not display in Outlook (Your server location could not be determined. Contact your administrator.) and Automatic Replies cannot be set from Outlook (Your automatic reply settings cannot be displayed because the server is currently unavailable.  Try again later.)

I know this is usually an issue with AutoDiscover but I made these changes to correct that:

Get-AutodiscoverVirtualDirectory | Set-AutodiscoverVirtualDirectory –InternalUrl “https://mail.domain.com/Autodiscover/Autodiscover.xml”
 
Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri “https://mail.domain.com/Autodiscover/Autodiscover.xml”
 
Get-WebservicesVirtualDirectory | Set-WebservicesVirtualDirectory –InternalUrl “https://mail.domain.com/Ews/Exchange.asmx”
 
Get-OabVirtualDirectory | Set-OabVirtualDirectory –InternalUrl “https://mail.domain.com/Oab”
 
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory –InternalUrl “https://mail.domain.com/Owa”
 
Get-EcpVirtualDirectory | Set-EcpVirtualDirectory –InternalUrl “https://mail.domain.com/Ecp”
 
Get-ActiveSyncVirtualDirectory -Server $CASserver | Set-ActiveSyncVirtualDirectory -InternalUrl “https://mail.domain.com/Microsoft-Server-ActiveSync"
 

Set the External URLs.
 
Get-AutodiscoverVirtualDirectory | Set-AutodiscoverVirtualDirectory –ExternalUrl “https://mail.domain.com/Autodiscover/Autodiscover.xml”
 
Get-webservicesVirtualDirectory | Set-webservicesVirtualDirectory –ExternalUrl “https://mail.domain.com/Ews/Exchange.asmx”
 
Get-OabVirtualDirectory | Set-OabVirtualDirectory –ExternalUrl “https://mail.domain.com/Oab”
 
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory –ExternalUrl “https://mail.domain.com/Owa”
 
Get-EcpVirtualDirectory | Set-EcpVirtualDirectory –ExternalUrl “https://mail.domain.com/Ecp”
 
Get-ActiveSyncVirtualDirectory | Set-ActiveSyncVirtualDirectory -ExternalUrl “https://mail.domain.com/Microsoft-Server-ActiveSync”

It was not a single name Cert but we did not include Autodiscover.domain.com in the 5 name so I switched everything to Mail.domain.com but we are still getting the same issues.  I have also tried numerous fixes from this post.

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2300-Outlook-continually-prompting-for-username-and-password.html

The only other configuration that I think might be a problem is with the Load Balancer but I haven't had luck working with Barracuda to diagnose.  

Any information on how to proceed would be greatly appreciated.

Thank you,

Dan
0
danszklut
Asked:
danszklut
  • 4
  • 3
1 Solution
 
doublestickCommented:
To eliminate the load balancer as a problem maybe you could just bypass it temporarily.
0
 
danszklutAuthor Commented:
We are now bypassing the Load Balancer and there is no difference.  I guess we can safely assume that it is not the issue.

Thanks,

Dan
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
doublestickCommented:
or directly related to free/busy error....

http://support.microsoft.com/kb/184151
0
 
danszklutAuthor Commented:
Hi doublestick,

I have tried both methods to no avail.  I ran the Microsoft Remote Configuration Analyzer tool and I am attaching the output.  I don't know if that will help any.

Thanks,

Dan
RCAnalyser.JPG
0
 
danszklutAuthor Commented:
After countless hours working on different fixes for this issue with no positive results I have finally gotten this issue resolved.  I had to add autodiscover.domain.com to my certificate and re-import it.  I would recommend saving yourself a load of headaches and doing this from the start.  Every fix I applied, to change the autodiscover name in exchange to something else, did not work.  Adding autodiscover as a name on the cert has resolved several issues I have had ongoing with multiple clients running exchange 2007/2010.
0
 
danszklutAuthor Commented:
The issue was resolved by applying the fix I listed in my comment
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now