I have a single Enterprise Exchange 07 Server with 250 Mailboxes. Out of Office Assistant (OOF) works fine for most people, there are curretnly 4 people reporting that when they try to access OOF with Outlook 07 or OWA they recieve the error: Server Unavailable please try again later. I can recreate the problem on any computer. I can resolve the problem by deleting and re-creating the users mailbox but this causes a nasty side effect (I think because the GUID changes): every internal user that has that persons mailbox cached will get undeliveralbe unless they each delete the cached address from their To field and re-retrieve it from the GAL. Microsoft Tech Phone Support suggested moving the Mailbox to a different Mailbox Database, that this fixes most mailbox curruption problems, but did not fix this problem. Please help to either repair the Mailbox OOF -OR- help to repoint the old GUID to the new Mailbox after it is deleted an re-created so other internal users cached addresses do not fail undeliverable. (sorry I have very little working knowledge of Exchange and GUID) Thanks Matt

When you recreate the mailbox, are you setting the alias to be the same as before? Was this originally a 2003 Exchange org that was upgraded?

Can the OoO be set in OWA? Or is it just a problem when using Outlook?Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

Yes I am creating the same alias as before. Yes this was originally 2003, the problem has occurred on both migrated mailboxes and mailboxes that have been created after the migration.

The problem is in both Outlook and OWA.

Ok, if the mailbox was originally in the 2003 Admin group and then it's recreated in the 2007 admin Group, that's the issue. When you recreate the mailbox, its new legtacyExchangeDN reflects the 2007 AG: 2007 Example: /o=Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=alias The old 2003 LegacyExchangeDn will be something like: /o=Org/ou=First Administrative Group/cn=Recipients/cn=alias Replies and cached entries in Outlook will then bounce as they reference the original legacyexchangedn. To fix that issue, add the 2003 legacyexchangeDN as a x.500 proxyaddress to the new account. ( Adding via adsiedit is maybe the easiest way/ More info: http://msexchangeteam.com/archive/2004/03/24/95451.aspx

Hi MDearth, Some other information for you: http://blogs.technet.com/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx Regards! gavin