I've been having a problem with moving some mailboxes in Exchange 2007 from a database with a larger storage quota to one with a smaller storage quota. Both databases are in the same storage group. Some users have mailboxes that are larger than the quota limits on the smaller database, and when I try to move them via the Exchange console I get an error message similar to the following: Error was found for NameLname (name.Lanme@mydomain.com) because: Error occurred in the step: Approving object. Current mailbox size is larger than the limit set on the target Exchange store or the target mailbox. To preserve source mailbox size limit, parameter PreserveMailboxSizeLimit must be set., error code: -1056717336 Exchange Management Shell command attempted: 'mydomain.com/Users/Desktop/Quality Control/Name Lname' | move-mailbox -TargetDatabase 'ServerName\First Storage Group\Standard'I looked into the PreserverMailboxSizeLimit parameter, but that seems to be designed to provide an exception to the storage quota set on the target database, or am I wrong? What I'd like to happen is to be able to import the mailbox and then have the quota limits apply so that the user will know that he's exceeded the limit and start cleaning up his mailbox. Can I set that parameter and then enforce the quota limits? Any other ideas?

Sam,I think you are missing on a very small thing and that is, distinction between the mailbox limits and store limits. The mailbox you are moving to another store must have mailbox size limits specified on it exclusively. Can you try changing the default limits on mailbox and try moving it then?MMilind Naphade | MCTS:M | http://www.msexchangegeek.com

Milind,Thanks for the suggestion and I will try that. However, the error message seems to say to me that I won't be able to move the mailbox to the new store unlessits sizeis reduced to conform to those lower limits.Will setting the lower limits on the mailbox itself change its size? If not, then it meansI will have to wait for the user to clean out the mailbox and get it under the limit before I can move it to the new store.Also, I understand that if I set the limits on the mailbox it will takeat leasttwo hours to take effect. Is my information correct?Thanks,Sam.

Sam,What you thought is totally correct. Store cache updates every 2 hours. So you will either have to wait till it gets refreshed or simply restart the store service, whichis indeed not a good way I would suggest anyone. AFAK, you can exclude a particular mailbox from the store defaults to a custom mailbox size and then move it to the new store with a parameter PreserverMailboxSizeLimit. However, This will not help you to achive what you are tying to. I would suggest clearing up or archiving some of the mailbox contents to PST and then move it to the new store. Yes, setting the lower values on mailbox than store defaults will limit the mailbox size for sure. But, you also have to understand that this mailbox should be excluded from exchange store default values. Do let us know in case it sounds confusing.MMilind Naphade | MCTS:M | http://www.msexchangegeek.com

Milind,Everything is starting to make sense to me. However, I still don't understand your statement that "this mailbox should be excluded from exchange store default values". I was actually thinking of removing the individual limits on the mailbox once it is moved to the new store. Am I correct in assuming that the limits of the store will apply in the absence of the limits on the individual mailbox? Perhaps I don't quite understand yet the store limits vs the mailbox limits. If you could link me to any source of information that compares or clarifies both of these limits I would be very appreicative.Sam.

Hello Sam,My statement is indeed confusing I do accept it. When you will specify the limits to an individual mailbox the mailbox will automatically get excluded from the store defaults so you dont need to worry about it. Here are a couple of links you may find useful to understand the whole scenario:http://technet.microsoft.com/en-us/library/aa997961.aspxandhttp://support.microsoft.com/default.aspx/kb/319583- This article is written for Exchange 2000, Exchange 2007 operates on the same logic though.MMilind Naphade | MCTS:M | http://www.msexchangegeek.com