A machine on-site needed some attention as it was smashing its CPU around the place. A bunch of users were trying to remote to it and were unable to establish a working session via RDP. The amount of additional processing needed to draw an RDP session was never going to allow them to get on there and shutdown whatever it was consuming all processing time.

PowerShell allowed me to get on the remote machine to see what happening, find what specifically was eating up all the CPU and then 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 and discuss what was being done at each step to ensure that the service was appropriate to close down. Here is what I used...