Why does it take so long for changes in mailbox quota limits to take effect?  Exchange 2003
When changing the storage limits on a mailbox, the changes are not seen for a long time. It is taking 4 to 8 hours for the change to take affect. The environment is very small and all the replication appears to be working properly. I read the article: http://support.microsoft.com/kb/327378/and http://support.microsoft.com/kb/326252... but these are really focused on Exchange 2000.The other one I was looking at related to 2007: http://technet.microsoft.com/en-us/library/bb684892.aspxBut I didn't find anything relating to Exchange 2003... Although it appears that these reg keys that they talk about will work, I want to be sure before doing something.Please advise.
April 6th, 2009 10:36pm

Long time? Define long time?The information is cached in Exchange from AD so that Exchange doesn't hammer the ____ out of AD 24/7.Before anyone goes off on a long troubleshooting trip, are you at one hour yet?
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2009 12:17am

As you've seen the default is 2 hours in Exchange 2000 sp3 and later. If you want to modify the time to something more "reasonable" 20 minutes (1200 seconds) is recommended. Additionally, while your links only state Exchange 2000 and 2007, I think its safe to assume that if it was the "Reread Logon Quotas Interval " in 2000 and 2007, it would not have changed in 2003. Also, if you're just looking to make a 1 time change to the quotas, you can just restart the information store service. Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator
April 7th, 2009 5:37am

so I just relooked and "Exchange 2003" was in the title of your first link: http://support.microsoft.com/kb/327378/Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2009 5:40am

Let me tell you why I am looking for a solution to this.A user calls our helpdesk and says that they ran out of space. Well, at this point, they can either delete mail, or waithours before they can start working again. This was never a problem in past installations. The storage settings took immediate affect.We cannot afford to have a user sit and wait for the new settings to take affect. Temporarily, I've been moving a few large messages out of the sent items until the settings finally take affect. This is not something I want to be doing. A change to the storage limits cantake as much as long6 hours.I can't restart the information store each time I make a change to a users storage limits.Do I need all 3 registry keys listed in the article?Please advise... Thank you for your responses.
April 8th, 2009 9:13pm

Yep, I understand your problem 100% as i've had to look bad in front of my users too. BUT to be fair.. thats what the warnings are for... the ones they have likely been ignoring for some time now. You can create custom warning text if you think that would help set their expectation for when it goes over the hard limit. And yes, if youre trying to agressivly be on top of this, i'd ajust all 3 settings - just watch for performance implications. Also youre saying "it didnt used to take this long". when is "used to"?. with Exchange 14 on its way out you might want to start looking at upgrading to a more current version of Exchange.... just a thought...Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2009 10:00pm

Hi, I would like to explain that you need to apply the three registry keys in the article. In addition, I suggest you read the following article to understand the Exchange Server Caches and Their Lifetimes: Exchange Server Caches and Their Lifetimes http://theessentialexchange.com/blogs/michael/archive/2008/01/18/Exchange-Server-Caches.aspx Mike
April 9th, 2009 1:41pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics