out of office not working, exchange 2010 coexistence with 2003. Works in OWA but not through Outlook.

Axis52401
Axis52401 used Ask the Experts™
on
In the middle of a 2003 to 2010 migration. Out office works through OWA but not Outlook. I ran the testconnectivity for the autodiscover test and the autodiscover passes but the ' creating a temporary folder to perform synchronization' fails (see attachment). The Exchange server is up to date on patches and is running rollup 6 sp3 for exchange. Please help experts.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Axis52401Security Analyst

Author

Commented:
testconnectivity
Axis52401Security Analyst

Author

Commented:
error-continued.PNG
Most Valuable Expert 2014

Commented:
Does Autodiscover work internally if you use Outlook to test it?
http://semb.ee/adt

When you say OOTO doesn't work, do you mean to set it, or the response?

What version of Outlook are you using?

Simon.
Should you be charging more for IT Services?

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Axis52401Security Analyst

Author

Commented:
Simon,

Yes the autodiscover test passes internally via the http://testexchangeconnectivity.com/  tool and the 'test autoconfiguration' utility within Outlook. We have a mixture of Outlook 2007 and 2010 and it's not working for any user.

What I mean by not working is users cannot set their out of office within Outlook. They are having to use OWA in order to set OOO. Below is the error message we are getting: "Your Out of Office Settings cannot be displayed, because the server is currently unavailable. Try again later."
Most Valuable Expert 2014

Commented:
Unusual for the Autodiscover test to work but OOTO to fail.
Do you have a trusted certificate in place? All URLs set to match the certificate?

Simon.
Security Analyst
Commented:
Here was the ultimate solution. Took opening a ticket with Microsoft.

IIS manger -> Exchange server -> Sites -> Default Web Sites -> EWS  --> HTTP Redirect - unchecked the redirect request to this destination

Then

Reycle the MSExchangeServicesAppPool
Axis52401Security Analyst

Author

Commented:
found it on my own

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial