MSI bundle forces a reboot

But with "/FP", now missing REG Keys are not Fixed.
Files with the wrong version are not fixed.
The only thing you fix is missing files.
So long as no files are missing, nothing gets changed and MSIEXEC does not
think a reboot is necessary.
But if any number of other problems actually DID exist besides missing
files, you would have to uninstall and reinstall to fix the product.

I've added a note to Shaun's Defect suggestion there be a way to allow
customers to define the default parameters that they want.

Honestly, the definition of "Correct" parameters to use by default when
Installing or Repairing an MSI are really hard to determine.
I've worked in different places where they feel that a different set of
options yields the best results for them.

That way if some ppl feel that "/fp" is best, they can set that option.
If they feel comfortable with Microsoft's work-around, they can choose to
implement that.
If they feel some other combination of switches with "/f" is what they feel
is proper, they can make it so.





--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


"CycoTron" <CycoTron@no-mx.forums.novell.com> wrote in message
news:CycoTron.40ry8r@no-mx.forums.novell.com...
>
> Thanks Craig. I was aware of that fix, however the /fp switch is much
> easier to implement and seems to be more reliable. I appreciate the
> knowledge that this is M$'s problem to fix. I will simply continue to
> use the /fp switch manually.
>
> I will admit that the full MS workaround is easier to use now that ZCM
> doesn't wipe out your switches when updating an MSI.
>
>
> CycoTron;1817127 Wrote:
>> The /norestart switch does not work on an MSI Repair (verify in
>> zenworks) action. This is a documented fact and it is one that burned
>> me for a long time when I started using ZCM10 until I figured out the
>> following workaround.
>>
>> Here is a link to the Microsoft KB article: 'MSIEXEC /f option can
>> reboot machine' (http://support.microsoft.com/kb/961883/EN-US)
>>
>> Here is an example from an MSI application I'm using. This line is in
>> the "Repair Parameters" line of the Install MSI Bundle Action:
>> >
> Code:
> --------------------
> > > /i "Skyward PaC.msi" REINSTALL=OMUS /passive /norestart
> --------------------
>> >
>
>
> --
> -Nick Kelnhofer
> Professional Network Administrator
> CNA, MCSA, A+, Net+
> ------------------------------------------------------------------------
> CycoTron's Profile: http://forums.novell.com/members/cycotron.html
> View this thread: MSI bundle forces a reboot
>