Link to home
Start Free TrialLog in
Avatar of Bolton09
Bolton09

asked on

Out of office assistant

We recieve the error below when trying to access the out of office assistant, we have spent days searching for a solution  every result seems to point to an issue with autodiscover we have tried many different things, updated all links in exchange we can find to point to our certificate, checked autodiscover dns settings etc, i will list below the logs and test run in outlook


The out of office assistance works in OWA but not outlook just to confirm
outofoffice.jpg
Avatar of Bolton09
Bolton09

ASKER

attached email test config
the black out lines are the correct address for our certificate web address
outofoffice2.jpg
what firewall do you have? is it set as a HTTP/S proxy?

If so make sure the proxy is both aware of the server IP by name, and that HTTPS connection from the internal firewall is allowed to the server
sorry that should read "HTTPS connection from the internal network is allowed from the server
Apologies i am struggling with typing this morning!

"HTTPS connectio from the interal network is allowed to the server"
You may also want to run Exchange Best Practices Analyser (Exchange Management Console --> toolbox --> Exchange BPA -> run health check.

Is this for internal/external users or both?

If external, try running tests at https://www.testexchangeconnectivity.com

Shaun
Its for Internal and External users,

users are going through a proxy server and netscreen but administrators are straight through the firewall with no policies
forgot to say it doesnt work for either none filtered traffic or filtered
Is Exchange totally up to date with Service packs and patches? SP2 UR4.

I would do this as a matter of course as there are lots of fixes in the SP's.

Shaun
its fully updated till march 01
Does it have SP2?

Shaun
No it doesn't the last update installed was sp1 rollup 10 on the client access server
ASKER CERTIFIED SOLUTION
Avatar of shauncroucher
shauncroucher
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I have ran the Get-AutodiscoverVirtualDirectory |fl command and found that the "originating Server" is pointing to a dc in a sub domain could this be causing the fail? if so how do you change it
What does the Server setting say (not originating server)?

See here for setting the virtual server but I don't think you need to, unless the server suggests the virtual directory is somewhere it is not.

http://technet.microsoft.com/en-us/library/aa998601.aspx

Shaun
the server name is the name of the actual server were the client access roles are installed, only worry for the orginating server is that it will soon be demoted, so does that mean exchange will automatically get another or do we need to somehow change it
It should be ok, Exchange will latch on to the first server available, once demoted (properly) the originating server will change to another server in your org.

Shaun
will be updating exchange to sp2