Executing .exe on a remote Windows machine

Kevin Holleran kdawg44 at gmail.com
Thu Nov 8 15:43:01 CET 2012


My goodness.... psexec.

thanks.... can't believe that didn't come to me...



--
Kevin Holleran
Master of Science, Computer Information Systems
Grand Valley State University
Master of Business Administration
Western Michigan University
SANS GCFE, CCNA, ISA, MCSA, MCDST, MCP

My Paleo & Fitness Blog <http://kevinspaleofitness.blogspot.com/>

"Do today what others won't, do tomorrow what others can't" - SEALFit

"We are what we repeatedly do. Excellence, then, is not an act, but a
habit." - Aristotle



On Thu, Nov 8, 2012 at 9:31 AM, Tim Golden <mail at timgolden.me.uk> wrote:

> On 08/11/2012 14:25, Kevin Holleran wrote:
> > Good morning,
> >
> > I wrote a python script to connect out to a bunch of my remote machines
> > that are running some software.  It modifies a bunch of the config files
> > for me.  After making the changes, I need to restart the software.  The
> > way to do this is to call an .exe passing in a argument 'restart'
> >  Simply restarting services is NOT acceptable & rebooting the machine
> > isn't either.
> >
> > I was trying to find a way to simply call the .exe on the remote machine
> > with subprocess but how can I get it to execute on the remote machine?
> >  These machines do not have SSH.
>
> WMI can usually help with this (although there are limitations on what
> you can execute via WMI). Also people recommend sysinternals' psexec.
> (I've never tried it myself).
>
> TJG
> --
> http://mail.python.org/mailman/listinfo/python-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20121108/9224178b/attachment.html>


More information about the Python-list mailing list