Hi
you're right, thanks.
I used this:
(SampleMsiInstalledState = 5) AND (SampleMsiInstalledVersion >=
v$(var.BaselineVersion))
do determine whether the previous servicePacked version of the msi in the
bundle was already installed. the SampleMsiInstalledState variable pr
I hoped that i didn't have to use a custom BA for things like that, because
like preventing the install of SP1FP1 without SP1 installed seemed to be
such a fundamental concept.
On Mon, Jun 17, 2013 at 11:08 PM, Blair Murri wrote:
> would work? A custom BA can always do whatever it wants
> in t
Hi
Run the bundle.exe like this from a command line:
$ bundle.exe /log your_logfile_location.log
The msi log files will be placed next to it.
When the bundle is executed without this parameter, you can find the log
files in
%localappdata%\temp
Cheers
Jakob
On Mon, Jun 17, 2013 at 2:13 PM, Adki
Hi all
When we provide patch bundles for deployed service packs, the fixpacks only
contain the difference to the bundle ServicePack1.
Currently, the SP1 FixPack1 bundle installs also on systems where SP1 doesn
not exist, leading to the msp patch not being installed (SP1 missing), but
the bundle be
Hi all
I'm trying to set up a patching system using burn. We do cumulative
patching and previously had the msp patches set up to supersede one another.
After installing the main bundle, followed by the patch bundles in sequence
v1.1 => v1.2, I can either keep v1.1 displayed in ARPs updates (new
up
5 matches
Mail list logo
