Hi A user seemed to have a corrupt OST file which was causing a resource hit on our Exchange server, so we disabled MAPI on his Exchange 2007 mailbox whilst we could get someone out there to recreate the OST. This was done about an hour ago and we re-enabled MAPI, but it stil didnt work. It actually took just under 2 hours to take effect. I don't think it's AD replication, since this is not an AD replicated attributed. Does anyone know why it took so long?

I know that in Exchange 2003 ProtocolSettings attribute like MAPI is cached in the MBICache and in DSAccess, and these caches may delay the time that is required for a change in the ProtocolSettings to become effective. Default TTL for MBICache is 120 minutes and default DSAccess cache TTL is 15 minutes. Can’t find any updated articles if it’s still the case in Exchange 2007/2010 but maybe someone with deeper knowledge can explain this for us.Adam Bokiniec

On Fri, 8 Apr 2011 11:32:59 +0000, Adam.Bokiniec wrote: >I know that in Exchange 2003 ProtocolSettings attribute like MAPI is cached in the MBICache and in DSAccess, and these caches may delay the time that is required for a change in the ProtocolSettings to become effective. Default TTL for MBICache is 120 minutes and default DSAccess cache TTL is 15 minutes. Can?t find any updated articles if it?s still the case in Exchange 2007/2010 but maybe someone with deeper knowledge can explain this for us. The same 120 minute refresh interval is present in E2K7. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi If you want to check or change the value of mailbox cache age limit exchange 2007, you could read this article. The default value is 120 minutes. http://technet.microsoft.com/en-us/library/bb684892(EXCHG.80).aspxPlease 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.