I would like to deploy OpenOffice.org 3.2 to all of our systems (we currently have 3.1) using the KBox "Deployment" module. Everything works well except that the OOo is running whenever a user is logged in. If OOo is running the install fails silently and then tries again.

I thought about having it install at boot time or before the user logs in, but that means a number of systems will take weeks before the update is applied, since some users rarely log out or restart their system.

I spoke to KACE about this, and they had no suggestions other than killing the OOo process, which isn't acceptable since some people could be working on a document at install time.

Anyone have any experience with deploying a managed install for a program that is always running while a user is logged in?


0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


You could use a KScript or other scripting method (AutoIt, VBS, etc.) to "wrap" the installer. The script would first detect any running OOo application and prompt the user to close it - you can keep nagging them until they close the application. The script will then run the installer upon successful detection of no running OOo processes.
Answered 02/22/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity