Hi I have a handful of users that the out of office assistant is not working for. They seem to be all older users that made the migration from 2003. The newer users seem to work flawlessly. We are now using Exchange 2007 SP2. Any ideas or troubleshooting steps would be greatly appreciated. Thanks Bryan

This is quite common. OOTO is actually a rule, therefore the quickest fix is to backup their rules, then start Outlook with the /cleanrules switch. This flushes the rules out, including the OOTO message which is stuck. Make sure that Outlook.exe is not in task manager, then Start, Run, outlook.exe /cleanrules In some cases, changing the OOTO message through OWA can clear it as well, but usually it requires the cleanrules. The cause is the change in OOTO behaviour. With Exchange 2003 you only had one, with Exchange 2007 you have two, internal and external, and in a migration it can get stuck. Another symptom is an old OOTO message being sent out, even though a new one has been set. Same fix applies. Simon.Simon Butler, Exchange MVP http://blog.sembee.co.uk http://exbpa.com/

I've also had to use MFCMAPI and clear out the rules that way on the mailbox as well. Mark Morowczynski|MCT| MCSE 2003:Messaging, Security|MCITP:EMA 2K7,EDA Win 7,ES,SA,EA|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com

Hi, For this issue, you should first check whether the OOF URL could be retrieved for the migrated users by using Autodiscover. And the OOF URL is accessed fine without issue by using user's credential. If not the OOF URL issue, that should be the issue of OOF rule. You can try Sembee's method to clear up the rule, then check this issue. And to clear the rule based on the below steps is also a good method: Clear OOF Rule in the mailbox: ======================== 1. Turn off OOF on a problem user and close Outlook 2. Use MFCMapi tool to logon the problem user’s mailbox (by using Online Mode profile) 3. Expand Root Container->Top of Information Store 4. Right click Inbox folder and click Open Associated contents table 5. Delete following messages if exist: a. Message class == IPM.Rule.Message 0x65EB001E == Microsoft Exchange OOF Assistant 0x65EC001E == Microsoft.Exchange.OOF.InternalSenders.Global b. Message class == IPM.Note.Rules.OofTemplate.Microsoft c. Message class == IPM.Rule.Message 0x65EB001E == MSFT:TDX OOF Rules d. Message class == IPM.Rule.Message 0x65EB001E == Microsoft Exchange OOF Assistant 0x65EC001E == Microsoft.Exchange.OOF. AllExternalSenders.Global e. Message class == IPM.Note.Rules.ExternalOOFTemplate.Microsoft f. Message class == IPM.ExtendedRule.Message 0x65EB001E == Microsoft Exchange OOF Assistant 0x65EC001E == Microsoft.Exchange.OOF.KnownExternalSenders.Global 6. After that, please start Outlook and configure OOF for the user. Please check whether the issue persists. Thanks Allen