Posts Tagged ‘Microsoft’

Windows System Resource Monitor

Introduced with Windows Server 2008, Windows System Resource Monitor (WSRM) is a tool used to allocate system resources. It is not installed by default and must be enabled through features in Server Manager. WSRM shows how much of the system resources that an application uses on a regular basis. When running in this application mode, WSRM will record an event when an application exceeds its allotted  resources. It is also capable to set policies that limit the resources to be used by a single application. If that application uses resources beyond what the policies allow, it will limit that application so that other applications may still operate. WSRM will not cause a limitation on any process unless the machine is currently residing at 70 percent utilization for all processes. Resource allocations may be assigned by user, process, or IIS application pool.

Windows System Resource Monitor will evaluate how you applications are being used and apply management policies.  It is important to test your policies thoroughly before implementing them. It is vitally important to understand how WSRM monitor functions before it is fully implemented. It is an extremely powerful tool that when implemented incorrectly can cause vital applications to come to a screeching halt. Once you are comfortable with the policies you have developed, you may use the calendar to schedule when they may be implemented.

WSRM will log Events and Alerts similar to Event Viewer. It becomes very useful on multiprocessor systems with large amounts of RAM. It starts with four management policies, but more may be added. It will ensure that mission critical applications, such as Active Directory, are always available. It is a tool that is intended for multipurpose Domain Controllers. If your DC is only a DC, then WSRM is not for you. Microsoft recommends that Domain Controllers only serve that purpose, but if you are unable to use other server for other application, then WSRM is the tool to manage all the roles that DC will fill. WSRM is also very resource intensive in itself. If you plan to use it for several servers, it would be a very good idea to run a dedicated WSRM server.