LoadRunner Configuration Remote Monitoring of Windows Server System Resources

Today, I decided to monitor system resources on Remote Windows XP. I thought it would be a good connection. In the same LAN, a bunch of problems occurred, maybe it was the first time that I encountered a tricky operating system!

(1) ensure that the test machine with LoadRunner can be pinged to the monitored target machine. In the same network segment, ensure that the two machines use administrator to log on.

(2) check whether a service is connected to the target machine exists: Remote Registry and Remote Procedure Call (RPC). If so, start the service in step (3). If not, go to step (7)

(3) check whether the target machine C $ is shared. Right-click my computer and choose "manage"> "shared folder"> "share". Then, click "share ', the shared folder C $ is required here (if you do not manually add it yourself: Execute: net share C $ = C :) In the CMD command line :).

(4) enter \ target machine IP \ C $ in the 'run' of the test machine, and click OK. Then, enter the user name and password of the target machine, if you can view the drive C of the target machine, the connection is successful;

Alternatively, you can enter: net use \ target machine IP \ C $ "target Machine Password"/User: "target machine username" in the CMD command line"

(5) go to the "local policy" of the target machine, select and click "Security Options", and set "Access Network" in "policy": change the sharing and security mode of the local account to "classic-Local User Authentication ".

(6) LoadRunner can be used to monitor Windows Target machines.

(7) add the "Remote Registry" Service

A: First, check whether the regsvc. dll file in C:/Windows/system32 is available. If not, copy the file from some machines,

(You can use depends. EXE to check whether the associated DLL file of regsvc. dll also exists. It usually exists. If it does not exist, you can directly

)

B: Then, export a registry file from the machine where the service exists.

HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/RemoteRegistry

Save, named RemoteRegistry. Reg, and copy it to the target machine.

C: import the file RemoteRegistry. reg to the registry on the target machine and restart the machine.

D: If the remote registry service is enabled with the 1083 error:Error1083: Configure to run

Service cannot execute this serviceSolutionGo to the Registry and find

To HKEY_LOCAL_MACHINE/software/Micosoft/Windows NT/svchost

Add the service name "RemoteRegistry" to the key value LocalService, and add the service name to the key value netsvcs.

"RemoteRegistry ";

Restart the machine and start the service successfully. LoadRunner can monitor the target machine remotely.