digitalhitman00
asked on
Exchange 2010 Storage Quota problem
Hey all,
I have Exchange 2010 setup. On the database we setup default storage limits for, for example issue warning at 400MB, prohibit send at 450 MB, and prohibit send/receive at 500 MB.
If I go into a user mailbox and go to where I can adjust the Storage Quota for that user, I uncheck 'Use mailbox database defaults', and then set my own limits for that mailbox. The limits I am setting do exceed the default limits, but that should not matter since I told this mailbox not to use the mailbox database defaults. When I adjust it to a greater value, I am still unable to send an email to that mailbox even after the limits are set greater than the current mailbox size.
Any idea on why I cannot override the default database storage quoats? Am I being impatient and is there something that runs to update this? Is this not an immediate effect?
I have Exchange 2010 setup. On the database we setup default storage limits for, for example issue warning at 400MB, prohibit send at 450 MB, and prohibit send/receive at 500 MB.
If I go into a user mailbox and go to where I can adjust the Storage Quota for that user, I uncheck 'Use mailbox database defaults', and then set my own limits for that mailbox. The limits I am setting do exceed the default limits, but that should not matter since I told this mailbox not to use the mailbox database defaults. When I adjust it to a greater value, I am still unable to send an email to that mailbox even after the limits are set greater than the current mailbox size.
Any idea on why I cannot override the default database storage quoats? Am I being impatient and is there something that runs to update this? Is this not an immediate effect?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
gpupdate has nothing to do here and I just told the OP to restart the IS
ASKER
Yeha that works. I was hoping there was another way. Thanks!
Thanks for the fix!
-I waited overnight and this didn't do anything.
-I restarted the Information Store and it worked right away.
I believe that it boots everyone off of Webmail. One can check to see how many users are on Webmail and are affected by running the command....?? Can't find that command....??
Get-Counter "\MsExchange RpcClientAccess\User Count" or variation of??
-I waited overnight and this didn't do anything.
-I restarted the Information Store and it worked right away.
I believe that it boots everyone off of Webmail. One can check to see how many users are on Webmail and are affected by running the command....?? Can't find that command....??
Get-Counter "\MsExchange RpcClientAccess\User Count" or variation of??
Running
Get-Counter "\MSexchange owa\Current Unique Users" on each Email Server seemed to return the value of OWA Users on each Server.
Get-Counter "\MSexchange owa\Current Unique Users" on each Email Server seemed to return the value of OWA Users on each Server.