Windows System Resource Manager (WSRM in short) is feature that can be added through Add Features in Server Manager in Windows Server OS. WSRM can be used in two ways.

  1. Applications Profiling: It helps identify how many resources an application requires on a regular basis. When operating in this mode, WSRM logs events in the application event log only when the application exceeds its allowed limits which helps in fine-tuning application requirements.
  2. Managed Mode: In this option, WSRM uses its allocation policies to control how many resources applications can use on a server. If applications exceed their resource allocations, WSRM can even stop the application from executing and make sure other applications on the same server can continue to operate. However, WSRM does not affect any application if combined processor resources do not exceed 70 percent utilization.
Viewing an Active Directory diagnostics report

WSRM also supports Alerts And Event Monitoring. This is a powerful tool that helps you control processor and memory usage on large multiprocessing servers. By default, the WSRM includes four built-in management policies, but it also includes several custom resources that you can use to define your own policies. Basically, WSRM ensures that high-priority applications always have enough resources available to them for continued operation, making it a good tool for DCs.

If you use single-purpose DCs, you will not need WSRM as much as if you use multipurpose DCs. Multipurpose DCs usually run other workloads at the same time that they run the ADDS service. Using WSRM in this case can ensure that the AD DS service is available during peak hours by assigning it more resources than other applications. However, consider your choices carefully when deciding to create a multipurpose DC. DCs are secure servers by default and should remain this way at all times. If you add workloads to a DC, you must grant access rights to the DC to application administrators, administrators who do not need domain administration access rights.

Use WSRM to first evaluate how your applications are being used; then apply management policies. Make sure you thoroughly test your policies before applying them in your p roduction environment. This way, you can get a feel for WSRM before you fully implement it in your network. When you’re ready, you can use WSRM Calendar to determine when each policy should be applied.

If you are managing several servers with WSRM, you might need to dedicate resources to it because it is resource-intensive. You might consider placing it on a dedicated management server if this is the case.

WSRM can be used for the following scenarios:

  • Use predefined or user-defined policies to manage system resources. Resources can be allocated on a per-process, per-user, or per-IIS application pool basis.
  • Rely on calendar rules to apply your policies at different times and dates without any manual intervention.
  • Automate the resource policy selection process based on server properties, events, or even changes to available physical memory or processor count.
  • Collect resource usage information in local text files or store them in a SQL database.