nathalie guerin

Hi,

We are building MSI packages that will be deployed to
XP/workstations using Tivoli. WIth this tool, the package
will be installed as Administrator on the local machine.
As such, the MSI package will be executed with
UILevel=None. I can't not seem to change this within
Tivoli.

Everything is great when all the files are available. If
the files are not available (i.e. in Use because the
application is open), the installation will go through. We
have set a flag to eliminates the reboots.

The problem is that, after the install and before the
reboot, the workstation is not in a valid state. I am
trying to find a way to force the exit of the Installation
when files are in use. Since it doesn't run in UI level,
it's not opening up the FilesInUse window and exit can not
be selected.

Is there a way around this?

Nathalie

david barnard

I'm not familiar with Tivoli. However, a few observations:

As far as I'm aware, installing a package using group policy avoids this
problem by not publishing the application until after a reboot. If Tivoli
fails to deal with this, then it's a weakness with Tivoli.

One possibility (a guess, even) - removing the reboot suppression may allow
the user (or Tivoli) to reboot automatically if required.

David

curtis sawin

Check out the "ReplacedInUseFiles" property in the MSI
SDK. Perhaps you can use this to determine if a reboot is
necessary, and cancel the installation if it is set.

However, since this property is set by the InstallExecute
and the InstallFinalize actions, you might need to place
the "InstallExecute" action immediately after
the "InstallFiles" event, then evaluate
the "ReplacedInUseFiles" property.

Hope this helps!

Curtis Sawin

We

Installation


not

phil wilson

There's a ReplacedInuseFiles property which the installer will set when that situation occurrs. It
sets it during InstallFinalize, which is when Commit custom actions are called. I've not tried this,
but try a commit custom action (maybe just a type 19) conditioned on ReplacedInuseFiles. That should
be a pretty quick experiment. That would cause a rollback if files were in use, if I'm correct.
--
Phil Wilson [MVP Windows Installer]
----