Scribd
Upload
14 views4 pages

Remote Tasklist

The document discusses how to determine the process ID (PID) of a runaway application on a remote Windows machine using tasklist and then effectively shutting it down using taskkill by issuing commands remotely with the PID and credentials. It provides step-by-step instructions for using tasklist to get the PID and then taskkill to terminate the process.

Uploaded by

mj jp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views4 pages

Remote Tasklist

The document discusses how to determine the process ID (PID) of a runaway application on a remote Windows machine using tasklist and then effectively shutting it down using taskkill by issuing commands remotely with the PID and credentials. It provides step-by-step instructions for using tasklist to get the PID and then taskkill to terminate the process.

Uploaded by

mj jp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Discovering Process ID for the Runaway Application

The first thing I wanted to see if I could do remotely was to determine the Process Id (PID) on the remote machine. I was
able to do this using native Windows 7 (or Server 2008 R2) tools and here are the steps.

1. Open a command prompt


2. Type tasklist /? to see a list of available commands

3. Type tasklist /s {remote computer name} /u {domain | username} /p {password}


4. This should return a list of running processes on the remote machine – take note of the PID

After you have the PID, you can now utilize another tool to actually force the process to shut down

Effectively shutting down the Application remotely

The next step is to shutdown the process remotely. This is easily available in-box using the taskkill.exe command that in
Windows 7 & Server 2008 R2. The steps to shut the runaway process are outlined below.

NOTE: For demonstration purposes, I’ve started Notepad in a user session on a remote server and that session is
Notepad.exe

1. Open a command prompt


2. Type taskkill /? to see the available options

3. To stop the remote process, type taskkill /s {remote pc} /u {domain | username} /p {password} /PID {process
id}

This should return, if it works, a message stating “Success: The process with PID {PID} has been terminated. This is it.
This is all you have to do to get this mis-behaving process out of the picture!

Summary

In today’s post, I just went off the normal path of my typical post and shared a newly discovered “trick” that makes my
life a bit easier when I have a remote machine who I can’t access because the “screen” is locked. This might be a unique
scenario and if so then please accept apologies for taking up space on the internet – but I felt the need to put it together
since I couldn’t really easily locate other posts relating to it.

Enjoy!

Thanks,
-Chris

You might also like