Home  |  Services  |  About Us  |  Contact  | 

 

Brad's TechTips - Exchange Server & Outlook

[<< Full list of Exchange Server & Outlook tips.]
 
 
Exchange Server 2010 and 2007: Limit the Memory (RAM) Used By Exchange Server
 
Microsoft Exchange Server 2010 and 2007 are notorious for using as much system memory as they possibly can, sometimes leaving little memory for other server applications and bringing the overall system to a grinding halt.  This seems to be especially problematic in Small Business Server (SBS) 2011.
 
For a detailed explanation of the how Exchange Server claims system memory for itself, as well as for commentary and related links, start at http://eightwone.com/2010/03/25/limiting-exchange-2010-database-cache/?like=1&_wpnonce=b4c8db312c.

However, for a fix that has worked for me (Fieldbrook Solutions) with my clients' SBS installations, here is a summary.  Only use these values if you understand their implications as well as what may occur on pre-SP1 vs. post-SP1 Exchange servers, and of course, make certain that you have adequate backups in case any unintended results occur.  In other words, make these changes at your own risk!
  1. Start ADSIEdit from Administrative Tools.
     
  2. If it doesn't automatically, appear, select Action > Connect To, and then select Configuration from the well-known naming contexts. Click OK.
     
  3. Expand Configuration > Services > Microsoft Exchange > <YourOrgName> > Administrative Groups > <YourAdministrativeGroupName> > Servers > <YourServerName> > InformationStore.
     
  4. Right-click InformationStore and select Properties.
     
  5. Locate the entry for msExchESEParamCacheSizeMax. Set it it to the desired number of pages to maximize the Database Cache. For my SBS installations which have 32 GB of memory, a value of 131072 has been adequate.
     
  6. Locate the entry for msExchESEParamCacheSizeMin. For my SBS installations which have 32 GB of memory, a value of 256 has been adequate.
     
  7. Restart the Microsoft Exchange Information Store service for the change to become effective, and observe that the amount of RAM used by Exchange Server will no longer be a bottleneck for the server.