Exchange 2010 SP1 - Database Storage Limits for Mailboxes not working
Hi everybody! I'm having problems setting up mailbox limits on our Single server Exchange 2010 SP1 with Update Rollup 2 and I hope someone can help me out! Basically, the Storage limits I put on to the Database doesn't seem to be inherited. At the moment I only want to issue a warning to users that exceed 350MB, therefor only "Issue Warning at (MB): 350" is ticked in the Database properties. Prohibit send and Prohibit send and receive is left unticked. Get-MailboxDatabase DatabaseName | fl tells me that the IssueWarningQuota is 350MB and the QuotaNotificationSchedule is as I want it. Get-Mailbox UserName | fl on a user located in above database (yes, verified again and again!) tells me that the IssueWarningQuota is unlimited. Quota information in OWA is unlimited as well. I put these limits on Thursday last week, which is four days ago. I feel as I'm missing something obvious. Any ideas anyone? Do I need to restart any services, remount the database? Thanking you in anticipation!
January 31st, 2011 3:33am

It should get applied, however it will be better if you can afford of restarting Information store and SA once.Best Rgds, Ashish | Unified Comunication | MCTS | MCITP | Please remember to select option "Propose As Answer" if solution work for you | My posts hold no assurances, no promises, and they measured no rights.
Free Windows Admin Tool Kit Click here and download it now
January 31st, 2011 5:07am

I would suggest to Restart Information Store Service.Gulab | Skype: gulab.mallah
January 31st, 2011 6:19am

Are you sure you have not unchecked the limits on the property page of the user?
Free Windows Admin Tool Kit Click here and download it now
January 31st, 2011 8:23am

@lafontma: Yes, I have checked this! The are set to use database defaults. I will try to restart IS and SA after office hours.
January 31st, 2011 8:53am

Ok, still no luck. I restarted IS & SA services Dismounted and mounted database Rebooted the whole server Still, the quotas from the database does not have effect on the users in the database. The users are set to use database default storage limits. Can there be anything else preventing the storage limit settings on the database from having effect?
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2011 6:46am

During our migration vom Exchange 2007 to Exchange 2010 some usres reported that outlook tell them that a quoting is configured. But on Exchange 2010 no quoting was configured. Recreating the Outlook Profile solved the problem. Have you done this? In a case of quotawarning Outllok displays this message on the file tab. regards Thomas Paetzold visit my blog on: http://susu42.wordpress.com
February 1st, 2011 11:26am

Hi, is your question answered? If so please mark it as answered. Thanks a lot in advance regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 2:53pm

I have a feeling it may be by design after Exchange 2010 SP1. After SP1 if your quota warning is 50% less than send\receive limit quota will not be sent. The mailbox will not get a flag to process it for quota warnings. Since you have no send\receive quota, perhaps thats why its showing no quota. I don't have a lab to test, maybe someone else can test if this is the case when you don't have send\receive limits enforce. Users do not receive quota warning messages after applying SP1 for Exchange 2010 http://support.microsoft.com/kb/2480474James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
March 16th, 2011 3:17pm

By setting it on the database, it should take effect for all mailboxes there. However your get-mailbox username | fl command is reading the properties of the mailbox, which, as you are noticing, does not get inherited from the database. The mailbox has its own, independent setting. As long as the mailbox's UseDatabaseQuotaDefaults property is set to True (which you confirmed in another post) the value from the database will take precedence. So in short, instead of looking at the get-mailbox command for validation, try it in Outlook and see if the limits are properly being enforced. I suspect they are working fine in your case. See http://blogs.technet.com/b/exchange/archive/2006/09/20/3394913.aspx (for Exchange 2007; similar) OWA might be saying unlimited because you only have a warning in place but not an actual prohibit. Not sure how OWA handles that though.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 3:24pm

It's likley by design after SP1, all my users show IssueWarningQuota unlimited because my prohibit and send is greater than 50% Once I change a test user to have a prohibit send\receive of less than 50% of warning, the IssueWarningQuota then displays correctly. Since you have not ticked the send\receive limit it means it is unlimited which means its more than 50% greater than the IssueWarningQuota. That is by design after SP1, IssueWarningQuota of "unlmited" means you will not get a quota warning which is the case because your prohibit send\receive is greater than 50%James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
March 16th, 2011 4:58pm

Ok, thanks everybody for clearing things up for me! For me, It's a bummer I can't have Exchange only send out warnings. But if it's by design, then there's not much to do. Also, thanks cn9 for pointing out that settings on database level will apply to the user settings, but not be seen on the user.
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2011 2:48am

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

Other recent topics Other recent topics