I just read a blog entry on TechRepublic about determining processes running on a remote server. The following lines somewhat surprised me:
I still challenge myself to fully migrate to a PowerShell environment, but I still use tools that are command line (DOS) driven in lieu of PowerShell scripts due to number of lines and typing required.
Let me have a crack at putting something together that doesn’t require too much typing:
get-wmiobject win32_process -computername ENIAC
Too long? How about this:
get-process -computername ENIAC
As a rule of thumb, if you can do it faster without Powershell, you’re probably doing it wrong.
Image may be NSFW.Clik here to view.