PowerShell's get-process cmdlet gets the processes that are running on the local computer, and is restricted to the local computer only, you can't interact with processes that runs on remote computers nor create ones locally or remotely. You can use WMI (see below), but I want to show another way of doing it, less documented one - static methods . Static methods give you the option to break loose of the cmdlet 'wrapper' and work directly on the underlying NET class. To find which...
