WINDOWS SYSTEM RESOURCE MANAGER - WINDOWS SERVER 2008
Description: Microsoft Windows System Resource Manager (WSRM) provides resource management and enables the allocation of resources, including processor and memory resources, among multiple applications based on business priorities. With WSRM, you can implement tight operational processes to predictably meet your service level requirements, maximize the return on your IT investments, and manage a changing mix of workloads.
The aim of Windows System Resource Manager is to ensure that system resources are available to processes, users, Remote Desktop Services sessions, or Internet Information Services (IIS) application pools (collectively called workloads). If unmanaged, these workloads can contend for and exhaust the system resources. However, there are situations in which Windows System Resource Manager is not an appropriate management solution or cannot guarantee sufficient resources to server workloads.
Scoping the Issue: Windows System Resource Manager is integrated in Server 2008, so installation is done through Server Manager by adding the Windows System Resource Manager feature. Once the feature is installed, you will need to manually start the service via the Services snap-in. The service name is Windows System Resource Manager.
If it appears that Windows System Resource Monitor is not functioning properly after starting, export the configuration and include it with data that is gathered below.
Note: Windows System Resource Manager cannot manage system resources correctly if the computer is being managed by another resource manager, including process-oriented and job object-oriented resource managers. For best results, use Windows System Resource Manager as the only resource manager on the computer.
What should not be managed by Windows System Resource Manager
What is not managed by Windows System Resource Manager
Data Gathering: In all instances, collecting either MPS Reports with the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done. If you are experiencing issues with installing WSRM, you will also need to get the SETUPAPI.LOG file in c:\windows and send it in for review.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.