A few weeks ago, we released three CXP flashes on the subject of Windows 2003 kernel memory issues and Exchange 2003. This is a promised follow-up to those flashes.
We are happy to announce that a new Exchange 2003 SP2 hotfix has been released that reduces the amount of kernel memory Exchange needs to support client access tokens. In internal testing, this hotfix has reduced token memory usage by up to a third. The experience of external customers has been similar.
Also, a new Knowledge Base article is now available with detailed information about managing client token memory on an Exchange server.
Memory used by client tokens is an important factor in Exchange server scalability. Client tokens are allocated from kernel paged pool memory. There is a finite amount of this memory available, and when this pool is used up, no more connections can be supported on an Exchange server. Reducing token allocations by 30% can translate directly into being able to support 30% more clients.
There are two ways to reduce the amount of memory used for client tokens: (1) reduce the size of each client token, and (2) reduce the number of client tokens on the server.
Knowledge Base article 912376 explains the token issues in detail, and includes scripts to help administrators determine how large individual tokens are. It also has suggestions for reducing typical token size. You can read this article here:
You should install this fix only if you've already optimized token usage in your environment according to the suggestions in the Knowledge Base article, and you still are unable to reclaim as much memory as you need.
The hotfix does not get rid of token memory usage problems altogether. (Only moving to a 64-bit platform will really solve this problem.) But, as we committed to you before, we will continue to do everything we can to help you manage kernel memory limitations that impact Exchange scalability on the 32-bit platform. This hotfix and Knowledge Base article are our first deliveries on that promise.
If you are interested in the full background on this issue, please read the previous flashes on the Exchange team blog.
The first flash provided technical background about the demands Exchange makes on kernel resources.
The second flash discussed hardware configurations that can restrict the kernel memory available for applications.
The third flash summarized the effect of large user security tokens on Exchange's kernel memory usage.
Thank you very much for your interest and for the helpful suggestions you've sent us.