Hi there, I was hoping somone could help me out with a problem I'm having whereby certain users are unable to access their OOFA. To give you the background we have recently migrated from a single exchange 2003 to a single exchange 2007 server. In Outlook 2007 when you select "out of office assistant" from the tools menu they are getting the error message "Your Out of office settings cannot be displayed, because the server is currently unavailable. Try again later". However the administrator mailbox and some test mailboxes I have created do not have this problem. You can set OOF in OWA successfully for all users. Running the "test autoconfiguration option" from outook displays the correct URL for the OOF. Can anyone suggest how I can troubleshoot this further? Any help much appreciated. -Al

Hi Have you tried to troubleshoot using : https://www.testexchangeconnectivity.com/ It's really important that autodiscover is setup and working correctly for this to work Does it work from OWA and not from Outlook?Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi, Check whether MSExchangeMailboxAssistants service is not stopped. Please go through below link for more help. http://telnetport25.wordpress.com/2008/11/23/problems-with-exchange-2007-out-of-office-assistant-in-an-interop-environment-and-different-versions-of-outlook/ http://msexchangeteam.com/archive/2007/04/04/437544.aspx http://www.msexchange.org/articles_tutorials/exchange-server-2007/tools/troubleshooting-out-of-office.html http://blog.flaphead.dns2go.com/archive/2008/07/08/blackberry-exchange-2007-ooo-issue.aspx Anil

Thanks for the responses guys. Having tested this (a lot!) it seems that the problems lies with the primary email address used. There are 2 email domains used in the organisation. The (UCC) SSL certificate and autodiscover DNS entries are setup for domainA. i.e. Outlook is setup to connect to https://mail.domainA.com. autodiscover.domaina.com is also created. domainB is not on the SSL certificate and doesn't have a autodiscover record setup. I've noticed that it's only users whose primary email address belongs to domainB who cannot get OOF (even though they have secondary addresses in domainA). Does this make sense and could it be the cause? Would buying a new cert (with domainB) and setting up autodiscover.domainB.com solve it. Cheers, A

Hi Set up a DNS (A record) for autodiscover to domain B and include autodiscover.domainb.com into the certificate :) I think you can revoke and re-order it?Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog