Psexec
June 5, 2008
What a great tool. As part of our deployment process we often want to run a processes on a remote server. An example might be running a batch file, iisreset, start and stop services etc. With psexec you can be in a command shell on computer A and run a command on computer B. Note you need administrator privileges, (which we think the person doing a deployment to an environment should always have), so some infrastructure departments may have a problem with it. Get it at sysinternals below.
Comments
2 Responses to “Psexec”
Got something to say?
In the linux/unix world, ssh cllient /openssh server is the standard way of doing what psexec but doesnt have security issues, as clients can connect via publickey/private key certicificates.
In the windows world, you can install openssh via cygwin and use the putty commandl line client [plink] to talk to the server. The advantage of this is it avoids the admin requirement of psexec.
see u tomorrow - porto’s for lunch?
One of the advantages of psexec is that you do not need to install anything on the computer you want to run the command on. This is always an advantage on the build process as it is normally developed by developers. Installing things like openssh etc would be usually handled by infrastructure resources and you would have to jump through a few more approval hoops to get it in.
Also Eric Growth Jnr has been dropped to the premier league for the weekend.