The Windows Resources monitor shows the Windows resources measured during the scenario run. Windows measurements correspond to the built-in counters available from the Windows Performance Monitor.
By default, LoadRunner monitors Windows resources using the native LoadRunner monitor engine.
If you are using the SiteScope monitor engine, ensure that SiteScope has been installed on a server. You can install SiteScope on the same server as the Controller, or on a dedicated server.
If you want to monitor a remote Windows server that does not use Windows domain security, you must authenticate the Controller on the remote Windows server. To authenticate the Controller, create an account, or change the password of the account used to log on to the Controller so that it matches the password and user name used to log on to the remote monitored Windows machine. When the remote Windows machine requests another machine's resources, it sends the logged-in user name and password of the machine requesting the resources.