• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1787
  • Last Modified:

After a user has gone over their mailbox limit and the limit is increased. How do you make the changes reflect immediately so the user can send and recieve emails?

I am using Exchange2003 and WinServer2003.
I am in a single domain which uses only 1 Exchange server.
3 Solutions
Make the user logoff and relogin back to Microsoft Outlook. He should be able to send and receive emails.

Amit Aggarwal.
the information is cached.. for this to reflect immediately.. you could also dismount and mount the mailbox store that holds this user.
Where and what limits do you increased?
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

gpersandAuthor Commented:
How do I dismount and mount the mailbox store that holds this user.
In the Exchange System Manager you expand the Exchange ORG (Top most thing on the left hand side)

Then expand administrative groups

then expand your administrative group

then expand servers
expand your server
expand storage group
expand mailbox store
click on mailboxes
check whether your user is listed on the right hand side.
if yes, then right click on the mailbox store and click dismount (once you dismount all the users in that mailbox store will not be able to access mail till the time the store is dismounted)
again right click on the mailbox store and click mount
Did that work?
gpersandAuthor Commented:
You mentioned the once you dismount all the users in that mailbox store will not be able to access mail till the time the store is dismounted. What did you mean by this?
If I dismount and mount in the space of a few seconds will the users see happen on their machines?
Does a message appear on the users screens stating that it cannot connect?
If a user has Outlook open I am assuming that new mails will not arrive but then will they still be able to open mails already in their inbox?
When I remount the mailbox store will the users have to log out of Outlook and back in again?

When you dismount the store the users that are connected to the server via outlook will get a message that outlook has lost connection to the server.
once the store is mounted the connection would come back automatically.
users working in cached mode will be able to read their emails but users working online would not be able to do so till the time the store is dismounted.

gpersandAuthor Commented:
Is there any other way to do this without the users knowing as I will recieve many calls as soon as the message will appear for the users.

Any more thoughts.
best thing would be to do it after office hours.

second thing would be to set the limits in such a way that the user's get a warning message when they have reached around 60% of their mailbox quota so that they still have time to reduce the mailbox size.

but usually this change should not take much time.. the change that you made earlier in this post.. has that taken effect?
gpersandAuthor Commented:
The changes had taken effect overnight but I want to find a way to force this to happen immedietely. Quotas set for users are normally ignored until it is too late and the user cannot sent and recieve.

Are you aware of the method below to force the size change:
1.Use AD to increase mailbox size from dc1
2.Replicate changes to other domain controllers.
3.Rebuild offline address list in ESM
4.Update the recipient update service policies which point to dc2
5.pull changes from dc2 to other dcs
6.ask user to logoff outlook and back on again

The above is another solution I have been given but have not tried it yet.
Any thoughts on the above.

Once the mailbox limits have been changed you don't need to update the RUS or rebuild the OAB.

Replicating the Dcs is fine and asking the user to logoff and login from Outlook is also fine

Exchange Information store caches the information about the limits which is flushed out at regular intervals. To force this change the store can be dismounted and mounted back or the IS service can be restarted.

Rebuilding the OAB or updating the RUS would not force this change
gpersandAuthor Commented:
How do you change the interval time that the store is flushed?
What is the default time?
i am not aware of that.. sorry can't answer this one
You might notice that storage limits do not take effect for a user for up to hours or more! This is because of the caching. The caching is configured to improve performance and reduces the number of times that Exchange has to query the AD (where the limit information is actually stored). The first cache value that affects information store queries DSAccess for information about the limits for user accounts. The cache lifetime is 10 minutes and can be configured by a Registry setting. While I don’t recommend changing this, the Registry key that would configure this is in HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\MSEXCHANGEDSACCESS\INSTANCE0; in this key, locate a value called CacheTTLUser. The value is the number of seconds for the maximum age of items in the cache. The next two parameters control how often the information store service will refresh information about its mailboxes. This is an information store service parameter; it cannot be tuned for each mailbox store. Both of these values default of 7200 seconds (2 hours) and are found in the following Registry key: HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\MSEXCHANGEIS .  The first REG_DWORD value you should create is Reread Logon Quotas Interval and the second is Mailbox Cache Age Limit. You should not drop either of these down below 1200 seconds (20 minutes), or performance may suffer.

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now