Skip to main content

Reading performance counters on remote machines

One of the nice features of the Performance Monitor tool is that you can read performance counters on remote machines. That is of course when it works!

When I tried to monitor the performance counters on a remote computer in Perfmon, I received an error message that resembles the following:

Unable to connect to machine

To resolve this issue, check the following actions.

Action  1: Verify that the Remote Registry service is running on the remote computer

  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type tasklist -svc, and then press ENTER.
    Verify that a Svchost.exe host process is running that has RemoteRegistry in the Services column. If the service is not running, go to step 3.
  3. At the command prompt, type net start RemoteRegistry, and then press ENTER.

Action 2: Verify that you have the required permissions

  • You must be a member of the Administrators group on the remote computer.
  • If the remote computer is running Windows Server 2003, you must be a member of the Performance Monitor Users group to monitor performance counters.
  • If the remote computer is running Windows Server 2003, you must be a member of the Performance Log Users group to log the performance counters. Additionally, you must use the Run As command to configure the logging process to run under the Administrators group or under the Performance Log Users group.
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more