Now that you've gone through the process of installing the Windows System Resource Manager (WSRM) on a server running Windows Server 2003, I will show you how to define an application within the WSRM. Defining
To define an application, begin by opening the Windows System Resource Console. If the console is not already open, you can find a shortcut to it on the server's Administrative Tools menu. When the console opens, you will see a screen similar to the one that's shown in Figure 1.
In WSRM, assigning applications means creating process matching criteria. Notice in Figure A that the console tree contains a container called Process Matching Criteria. To define an application, right-click on the Process Matching Criteria container and select the New Process Matching Criteria command from the resulting shortcut menu. When you do, you'll see a screen prompting you to enter a criteria name.
You can enter anything you want as the criteria name. I recommend using a descriptive name that reflects the name of the application that you're defining.
After you enter the criteria name, you must create rules that define the application. To do so, click the Add button and the Add Rule properties sheet will be displayed, as shown in Figure 2.
You will notice in Figure 2 that the properties sheet contains two tabs. Normally you will create all your rules using the Files or Command Lines tab. However, you can also use a Users or Groups tab to create rules defining a particular user or group. This lets you restrict an application's use of system resources based on who is running the application. Since the Users or Groups tab works almost identically to the Files or Command Lines(aside from the obvious difference between files and users), I will focus on the Files or Command Lines tab. Once you understand how this tab works, you shouldn't have any trouble defining users or groups should the need arise.
In the Files or Command Lines tab you'll find include and exclude sections. Both work identically. However, the include section is used to specify applications that the Process Matching Criteria applies to, while the exclude section prevents the Process Matching Criteria from affecting these specified applications.
Figure 2 contains a drop-down list that displays the words Registered Service. This drop-down list provides you with three options for defining applications. The default option is the Registered Service option. If you click the Select button, Windows will display a list of all the services that have been registered on the server, as shown in Figure 3. To add any of these services to the Process Matching Criteria, select the desired service from the list and click OK.
Next on the drop-down list is the Running Process option. Choosing this option and clicking the Select button causes Windows to display a list of all processes currently running on the server, as shown in Figure 4. To add a process to the Process Matching Criteria, select it from this list and click OK.
The last option on the drop-down list is the Application option. If you choose this option and click the Select button, Windows will display the contents of the local file system. This allows you to choose an executable file for inclusion in the Process Matching Criteria. It is usually easier to choose a registered service or running process then to locate a specific file. But the Application option is handy for situations in which the application that you want to restrict is not a system service and is not currently running.
Once you've selected all the files or command lines you want to include in the Process Matching Criteria, click OK. You'll be returned to the New Process Matching Criteria dialog box. As you can see in Figure 5, the applications you have defined are listed alongside the criteria name. If necessary, you can use the Add, Edit or Remove buttons to make changes to the process matching criteria. Click OK and the new process matching criteria will be created.
The next article in this series will show you how to allocate a restricted set of resources to the application that you have defined.
About the author: Brien M. Posey, MCSE, is a Microsoft Most Valuable Professional for his work with Windows 2000 Server, Exchange Server and IIS. He has served as CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. He writes regularly for SearchWinComputing.com and other TechTarget sites.
More information on this topic:
- Tip: Windows System Resource Manager keeps resource-hungry apps in check
- Topics: Windows systems management
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in November 2006