We have a script that needs to be monitored after kick-off.  The hitch -  I RDCMan into 30 plus servers and kick them off individually or (what I would like to do) try and create an interactive psexec session with the same credentials I used to sign into the servers with.  Looking into it more though,  /i for psexec won't work with bash.exe (we leverage cygwin for the script even though its a .bat/cmd) or cmd.exe.  It would simplify things if I could kick it off from a cntral location but still monitor the scripts via RDCMan.

0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time


Answer this question or Comment on this question for clarity