Posted by: David | October 27, 2010

Exchange 2007 Out of Office Server Unavailable

Recently ran in to an issue with Out of Office not working for any users in an Exchange 2007 environment. Here are the symptoms and the fix for the problem:

Run Test E-Mail Auto-configuration (From Outlook), this is performed by right clicking with CTRL held down on the outlook icon in your taskbar.

Response:

Error 503 getting autodiscover.xml

Checked Autodiscover AppPool (this can be checked in IIS Manager, expand the server and choose Application Pools look for the MSExchangeAutodiscoverAppPool) and this had stopped.

Started the pool but it kept crashing.

Removed Autodiscover Virtual Directory, from the exchange management shell run:

Remove-AutodiscoverVirtualDirectory
	-Identity "server nameAutodiscover (Default Web Site)"

Reset IIS, run IISreset from command prompt.

Recreated Autodiscover Virtual Directory, from the exchange management shell run:

New-AutodiscoverVirtualDirectory -WebsiteName "DefaultWeb Site"
	-WindowsAuthentication $true -BasicAuthentication $true

Checked and the Autodiscover application pool is now working, checked and Out of Office (OOF) is working for internal users but not for external RPC over HTTP clients.

Checked Test E-Mail Auto-configuration (From Outlook), from an external user

OOF URL: https://internalFQDN/EWS/Exchange.asmx

To check the setting of the URL’s run this from the exchange management shell:

Get-WebServicesVirtualDirectory | Select name, *url* |fl

Result:

Name : EWS (Default Web Site)
InternalNLBBypassUrl : https://InternalFQDN/ews/exchange.asmx
InternalUrl : https://InternalFQDN/EWS/Exchange.asmx
ExternalUrl :

Command to Set the External URL:

Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)"
	-ExternalUrl: https://EXTERNAL-FQDN/EWS/Exchange.asmx

Command to Set the Internal URL:

Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)"
	-InternalUrl: https://EXTERNAL-FQDN/EWS/Exchange.asmx

NOTE: This must resolve internally and be accessible, if firewall does not support hair-pinning then internal DNS will need to be set up for this.

Test and should be working

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: