A machine on site needed some attention as it was smashing its CPU around the place. User's that were trying to remote to it were unable to establish a working session via RDP to get on there and shutdown whatever was consuming all processing time.

PowerShell allowed me to get on the remote machine to see what was going on, find what was eating up all the CPU and dispose of it.

This can be done in a much neater way, but in this case the client was looking over my shoulder and wanted to step through what was being done to ensure that the service was appropriate to close down. Here is what I used...