How many copies of a users security token will a server hold for a MAPI connection initiated from outlook? is the answer different for different versions of outlook, and does it depend on what the MAPI session was opened for?This is in relation to a page pool memory error vs 9646 errors.

Hello Ishmael,The mentioned below article would give you more information about handling MAPI.Named Properties, X-Headers, and You http://msexchangeteam.com/archive/2009/04/06/451003.aspxArun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

It should be one per MAPI connection. BTW, which version of Exchange do you use and you would get better help if you post error which you get in application log? Here is a nice repo on paged and non paged pool memory step by step troubleshooting and best practices on Exchange server which might help you... Paged and Non-paged Pool Issues on Exchange 2000/2003 http://blogs.technet.com/dblanch/archive/2009/04/18/paged-and-non-paged-pool-issues-on-exchange-2000-2003.aspx Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Thanks Amit,i think we're ok at the moment as far as the problem goes - we'd found Doug's blog already. it was the number of tokens per session we were interested in. article 912376 gives a figure for the number of tokens a NET USE session requires, but nothnig for a mapi session:A user's access token is stored on the server in paged pool kernel memory. At any time, there are likely to be multiple copies of each user's token in memory. For example, if a client maps a share on a Windows Server 2003-based server by using the NET USE command, two copies of the user's token will be held on the server to support this connection.one per session is the answer i was looking for. thanks.