tag:blogger.com,1999:blog-9065986022577869094.post6521683618635460562..comments2015-12-07T00:01:09.689-06:00Comments on Mostly Exchange Administration: Improving Paged Pool and Non-Paged Pool Memory Usage in Exchange 2003Derek W. Audehttp://www.blogger.com/profile/10326460466411892329noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-9065986022577869094.post-17454531748822166812009-03-31T05:05:00.000-05:002009-03-31T05:05:00.000-05:00Nice Post, done quite a bit of work on NPP for e20...Nice Post, done quite a bit of work on NPP for e2003 myself and came up with the following bullet points to check;<BR/><BR/>• Enable Aggressive Memory Usage.<BR/>• Set EXIFS to use Paged Pool instead of NPP.<BR/>• Disable unused NIC’s.<BR/>• Avoid on-board NIC’s – use network cards where possible.<BR/>• Avoid Teamed NIC’s where possible.<BR/>• Disable unused HBA Ports.<BR/>• Uninstall graphics drivers, use default VGA drivers.<BR/>• Avoid jumbo frames where possible<BR/>• Update NIC / HBA drivers, testing between each change.<BR/>• Apply Microsoft hotfix KB820129 to prevent NPP fragmentation.<BR/>• Drop the receive descriptors down to 128 on NIC’s where possible.<BR/>• Set /basevideo in the boot.ini<BR/>• Ensure /PAE is not set in boot.ini<BR/>• Use Poolmon and Driver Verifier to identify sources of high consumption of NPP.<BR/>• Consider holding off Windows 2003 SP2, at least for now.Mike Websternoreply@blogger.com