[Date Prev] [Date Next] [Prev in Thread] [Next in Thread] [Date Index] [Thread Index]

Re: Run Process PSEXEC

** Deploying a piece of software on every machine without a plan to maintain the software is a recipe for trouble.


Active link run process actions that execute things on the command line will only work with the Remedy User Tool, not the mid-tier.  This will prove to be a hurdle that you must deal with if you plan on your Remedy system being around for more than a couple of years.

There are lots of interfaces you can leverage to gather system information about remote systems.  What data you need to gather is going to be the driver on the best approach to retrieve that data.  Do you want installed software?  network configuration?  OS version and patches?  running processes?  event log/syslog?  are you dealing with multiple platforms (linux, mac, windows, etc.)?

Best to first outline what you are trying to do, then figure out how to best do it.

Axton Grams

The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc.  My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc.

On Tue, Aug 10, 2010 at 8:54 AM, Robert Fults <rfults@fiu.edu> wrote:

Has anyone used Run Process active links to run PSEXEC.exe to execute remote commands on a Windows machine?  I am looking for ways to gather customer computer information and run simple processes from the Service Desk without purchasing extra software to do so.




Robert Fults

Remedy Admin/Dev.

Florida International University

Email: rfults@fiu.edu



_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_