Export (0) Print
Expand All
Collapse the table of content
Expand the table of content
Expand Minimize

Windows System Resource Manager (System Services for the Windows Server 2003 Family and Windows XP Operating Systems)

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Service Name: WindowsSystemResourceManager

Executable Name: Wrm.exe

Log On As: LocalSystem

Description: The Windows System Resource Manager (WSRM) service is a tool to help deploy applications into consolidation scenarios. It provides policy-based management of CPU and memory consumption of processes running on a single operating system instance. Planned scenarios include multiple heterogeneous server applications, multiple Terminal Services users, multiple instances of SQL Server, multiple IIS 6.0 application pools, or Exchange Server and IIS 6.0 running together on the same computer.

The WSRM service enables a system administrator to do the following:

  • Configure CPU and memory allocation policy settings 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 (paging file usage).

  • Apply policy settings to users or groups on a Terminal Services application server.

  • Apply policy settings on a Date and Time schedule.

  • Generate, store, view, and export resource utilization accounting records for management, service level agreement (SLA) tracking, and charge-back purposes.

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

The primary option for CPU management is bandwidth targets (expressed as a percent of system CPU). Targets are maintained by dynamically monitoring and adjusting process priorities. The WSRM service also provides affinity management, which is provided by using per-process APIs for hard affinity.

Memory management options include working set limits and committed memory maximum applied per process. Working set limits are set in policy and applied by the WSRM service by means of a kernel API. Subsequently, the kernel memory manager will apply and maintain the limits on working set size by paging the process as necessary. Committed memory is simply monitored against an upper limit. When the upper limit is exceeded, the process is stopped or an event is logged (at the user’s discretion).

Additional features include full calendar features for scheduling desired policies, sophisticated pattern matching for identifying processes at runtime, WSRM service–specific counters, and a basic job accounting system.

The WSRM service must be installed on each managed computer. For administration of the service, an MMC snap-in and command-line programs are provided. These client components can be installed and run on any Windows 2000, Windows XP Professional, or Windows Server 2003 operating system. The service can be installed and run only on Windows Server 2003, Datacenter Edition and Windows Server 2003, Enterprise Edition.

If this service is stopped or disabled:

  • You will not receive any management (WSRM provides runaway process protection by default).

  • You will not receive any job accounting data.

  • You will not be able to administer WSRM by means of the snap-in or CLI.

Available on: Windows Server 2003, Enterprise Edition and Windows Server 2003, Datacenter Edition

Installed through: Windows System Resource Management CD

Startup type: Automatic

Service status: Started or Stopped based on user check box in setup

This service depends on the following system components:

Remote Procedure Call (RPC)

The following system components depend on this service:


Community Additions

© 2016 Microsoft