Some customer called saying that they couldn’t log in to a certain Windows box. vMware told me the VM was using 100% CPU, and it was to busy doing something to let users log in.
Powershell saved the day (or at least saved the VM from beeing reset)
To find the process running wild I used the invoke-command cmdlet, like this:
invoke-command -scriptblok(get-process | sort-property CPU -Descending | select -first 10) -computername “Windows Hostname” | ft -autosize
This gave me a nice list of processes with the one we should focus on in the top. Now all i needed to do was:
invoke-command -scriptblok(stop-process -Id “pid”) -computername “Windows Hostname”
The process was stopped, and CPU usage fell to 0-2% allowing application people to login and investigate what happened.