Windows System Resource Manager
Saturday, 12 February 2005 by Michel Roth
Haven't used it myself but it sounds promising for those of us who cannot use third party resource managing tools: Windows System Resource Manager (WSRM). Unfortunately it only runs on Windows Server 2003, Enterprise Edition, and Windows Server 2003, Datacenter Edition ( 32-bit or 64-bit).

WSRM enables a system administrator to do the following:

• Set CPU and memory allocation policies on applications. This includes selecting processes to be managed, and setting resource usage targets or limits.
• Manage CPU utilization (percent CPU in use).
• Limit the process working set size (physical resident pages in use).
• Manage committed memory (pagefile usage).
• Apply policies to users or groups on a Terminal Services application server.
• Apply policies on a date/time schedule.
• Generate, store, view, and export resource utilization accounting records for management, service level agreement (SLA) tracking, and charge-back purposes.

WSRM maintains an updatable exclusion list of processes that shouldn't be managed because of the negative system impact such management could create. WSRM also applies limits to process working set size and committed memory consumption. WSRM does not manage address windowing extensions (AWE) memory, large page memory, locked memory, or OS pool memory.

Read more here.

Related Items:

TechNet Webcast: Using Windows System Resource Manager With Windows Server 2003 (Level 200) (20 April 2005)
MS Webcast: Using Windows System Resource Manager with Windows Server 2003 (Level 200) (9 March 2005)
Windows Vista Step-by-Step Guides for IT Professionals (11 February 2006)
Using Citrix Resource Manager (18 August 2006)
One reason Why Windows Server 2008 Terminal Server Will Allow You To Get More Users On A Box (10 February 2008)
GDI Limits (4 September 2007)
Citrix Memory Optimization Hotfix:PSE400R01W2K038 and PSE400R01W2K3055 (26 May 2006)
How to Enable User Mode Stack Trace Database for IMA Service to Detect Memory Leaks (4 July 2005)
An Overview of Longhorn Server’s Terminal Service Gateway (Part 5) (27 September 2006)
How To Get Virtual Memory And Handle Information Using Process Explorer (20 May 2005)
Comments (0)add feed
password
 

busy