How to find/kill running process BEFORE installing a pkg? [ADDENDUM]

donmontalvo
Esteemed Contributor III

Is there a way for Casper to kill a running process BEFORE installing a pkg? I see the option but wondered if this runs BEFORE the pkg is installed?

Management > Computer Management > Policies > Create New Policy > Advanced > Files & Processes > Search for Processes [processname] [x] Kill if found

I searched the Casper Admin PDF, did a search for "Kill" and for "Search for Process" but came up dry.

[ADDENDUM]I know we can add a preflight script to do this, but we would rather not re-package this vendor provided pkg installer.[/ADDENDUM]

Thanks,
Don

--
https://donmontalvo.com
4 REPLIES 4

stevewood
Honored Contributor II
Honored Contributor II

Why re-package? Just write a shell script to run before the package is
On Tue, Sep 14, 2010 at 4:29 PM, Don Montalvo <donmontalvo at gmail.com> wrote:
installed. (I know, it's a work around and not supported by x, y, and
z....) :-)

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475

donmontalvo
Esteemed Contributor III

Thanks guys...I totally overlooked the script option in the policy. Geez...you guys are breaking the ether-beer bank! :)

Don

Steve Wood wrote:

Why re-package? Just write a shell script to run before the package is installed. (I know, it's a work around and not supported by x, y, and z....) :-) Steve Wood

Craig E wrote:

I actually don't know the order either for this particular option, but an easy test should tell you. =) If a policy is any indication, the plan says it will perform your installs first and then check for processes afterwards. You'll likely need to run a script before to kill it first. This brings up my issue again with not having as much control on the order of things in policies which ends up creating more script work have the time for simple commands. Craig E

William Smith wrote:

A script is probably the ticket. You can either incorporate the script into your .pkg file as a preflight script or you can add it as a Run Before script in your policy. William Smith

My original question:

--
https://donmontalvo.com

donmontalvo
Esteemed Contributor III

Thanks Tom, we'll try that too. :)

** Sent from my iPhone **

--
https://donmontalvo.com

tlarkin
Honored Contributor

Also manual trigger policy in a simple shell script. Check for process, if running kill, if not execute manual trigger policy, done.