Using LoadRunner to monitor Windows resources

In order to differentiate between the machines with LoadRunner called A, the server (Windows) of the monitored resources is called B

1, ensure that the B machine administrator account is available: Right-click computer → management → Local Users and groups → users, where administrator user account is not disabled, Password never expires, set good password

2. Ensure that machine B's remote Procedurecall (RPC) and remote Registry service services are on: Right-click My Computer, services and applications---Services settings

3. Modify the network security settings of Machine B: Control Panel → system and security → management tools → local security policy → security options → modify to classic-Authenticate local users without changing their identity

4, in Machine a test, enter the server's IP address in the "Run" field, followed by C $, indicating the system resource directory under the server C disk, such as: "\\192.168.2.168\C$", to see if you can access the server C disk directory, Typically, you may need to enter your username and password (using Administrator user monitoring) to populate the server-side account and password, as shown below

5, open the controller on machine A, select Windows Resoources under System Resource graphs (double click), pop Up the monitoring window, select "Addmeasurements ..." in the right-click Pop-up menu in the window. Click "Add" to enter the IP address of the monitored server, click OK. Note that the best ab machine has Administrator privileges

Using LoadRunner to monitor Windows resources