Ever since Exchange 2010 SP1, the daily warning message feature has changed. We have a scenario where this is actually hurting our business In KB248047, .......In SP1, a new flag has been introduced that controls whether a mailbox is checked to see whether its size has exceeded the warning threshold. This flag is set on a mailbox if the mailbox size is more than 50% of the Prohibit Send quota. This means that if the warning quota is set to a value less than 50% of the Prohibit Send quota, it is possible for the mailbox size to be over the warning quota limit but still not over 50% of the Prohibit Send Quota. In this case, the mailbox will not be checked to see if it has exceeded its threshold and will not receive a quota warning message..... We've obtained another organization and have our own corporate policy of 500MB limits but for the migration we have agreed to move 90 days of data so as not to disrupt business. Then the plan was to reach out to the users to get them to reduce their mailbox size. Sometimes, 90 days of email is equal to 2 or 3 GB of data. We kept their warning limit at the default 400MB but gave them temporary No Send and No Receive limits of 24.5GB and 25GB. We completed the migration and did not realize that users were *never* receiving messages indicating that they were over a warning limit because of the nature of the changes in SP1. If a user has a 2GB mailbox, we cannot cap them at 2.1 No Send Limit because they still will receive no warning because their warning limit is much less than 50%. If we give them a 450MB No Send limit, then they would have to figure out how to delete a majority of their email which is not feasible in the real world. If we give them a 1.9GB warning limit, then we have to keep revisiting these size settings constantly and the user would have a misconception that our size restriction is 1.9GB instead of 500MB. So before saying that our users should be mindful and should be doing such and such, I would like to mention that this is a *new* feature of E2K10 SP1 and in our case, we really need to be able to override these new settings. I can see the benefit of the new settings, I just don't want to be forced into a one-size fits all scenario.

I seems like the source of your problem is move or less because you don't know how big your user's mailboxes are prior to the move and you're trying to circumvent the SP1 quota changes which is hard to do if you don't know how big the MB sizes are prior to the move. Is this org not giving you a spreadsheet of their MB sizes prior to the move?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

I'm sorry, I did mention that I didn't want this to devolve into a conversation that goes along the lines of user habits. I wanted to keep this technical and was hoping that MS was watching this thread to offer a technical override to a new behavior. The concept of a warning limit has existed since 4.0 and it is only in the past six months that this was changed, and not an initially documented change at that. Sending a warning limit once unless a mailbox item is saved, ok, that's fair. I've had my share of disabled mailboxes that have years of warning messages sitting in the Inbox. Making the warning limit depend on the size of the No send limit, that has limited use and and does not apply to all scenarios. So respectfully, I do appreciate and need technical help but any advice about a bad corporate decision is both out of my hands and doesn't keep us going in the direction that I was hoping this thread would go.