Hi all, I have a Windows 2003 server (terminal server) with Office 2007 Pro installed. The Exchange server is 2010 running on WIndows 2008 R2. When a client tries to activate Out of Office under terminal server, it hangs for along time before saying Exchange server offline. If I do the same thing from a stand alone PC it's fine. I've read the following article which I think might be related: http://support.microsoft.com/kb/958934 but had no luck. Any suggestions?

I don't know if its relevant but we had a similar issue, not with TS though. Users were logging into one domain (in a different forest) on their PC's but then accessing Outlook and logging into the mail domain. When I did a test E-mail autoconfiguration in Outlook I noticed that the client wasn't seeing the service connection point for Exchange and since we hadn't published the Autodiscover URL's in internal DNS that was also failing. I would suggest at least checking the auto-config to see what it says. Neill

Hi Same problem for all users?Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi, Regarding to the issue, it can occur by incorrect configuration, corrupted Outlook profile or incorrect Terminal Server settings. If the issue is caused by Terminal Server, you may need create a new thread in Terminal Server forum for more assistance. To narrow down the cause, I suggest you refer to the following article to configure Out of Office: How to use the Out of Office Assistant in Outlook However, if the issue persists, please create a new Outlook profile on Terminal Server and then activate Out of Office again. Thanks, NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.