Last year when we wrote our post on Memory Management – Understanding Pool Resources we mentioned that it was possible to use Process Explorer to view the limit for both Paged and NonPaged Pool. In that post we mentioned that you would need to install the Microsoft Debugging Tools and configure the Symbol Path so that Process Explorer could pull the information for the Paged and NonPaged Pool limits. That all seemed fairly straightforward, right? Well, that doesn’t always work so well for every customer – we have many customers who have systems that have no Internet connectivity at all, and in some cases no connectivity to any systems outside of the subnet on which they sit. So short of capturing a dump file (which is not always feasible) and using the !vm command to view the memory information, how can we get this information?
|