1, through the client and the server network testing, to ensure smooth communication. (Test host itself)
2, enter in the operation, Service.msc open the system's service settings, turn on the server side of windows in the following two services, such as:
Note: Remote Registry is disabled by default and can be modified to manual before starting
3, need to change the system local policy of the server, this is very important, but also determine the client can access the server side of the key steps, specifically need to go to the management tool under the Control Panel, find local Security policy, choose Local Policy-security options-Network access: Local account sharing and security model, Modify the security settings to Classic mode, such as:
4, in the client to test, in the "Run" field, enter the IP address of the server, followed by C $, which represents the system resource directory under the server C disk, such as: "\\192.168.0.103\C$", to see if you can access the server C disk directory, Waiting for a period of time after the need to enter the user name administration and password usb3.0, fill the server side of the account and password is OK (by default, if no password can be accessed directly), as follows:
5. Switch to LoadRunner controller to configure monitoring target under Windows resources, put mouse to Windows Resource View right click to select Addmeasurements, click Add, enter server IP Address and server operating system (win7-64 Select Default Win2003). Such as:
6, see the configuration after the completion of the real-time monitoring record, as shown:
Reference Document: http://yadang.blog.51cto.com/4375860/1435683
Monitoring Windows System resource methods under LR