msi wrapper for Windows Updates

[Anthony Yates]

I am using msi wrappers to execute Windows Updates. They work fine as long
as the custom action to execute the update is run Synchronous, Ignore exit
code. Without the "Ignore exit code" the update is executed successfully but
the msi execution fails. The failure happens rights at the end of the custom
action, just at the point that the update would be prompting the user to
restart.
Any ideas why Windows Installer cannot handle the restart return code from
the update? Up to about 6 months ago the patches used to just force a
restart and Windows Installer finished normally,
Thanks,
Anthony

 

[David Randall [MS]]

I'm not sure about why MSI isn't handling the restart return code, but can
you configure your program to "SMS Reboots Computer" ??

 

[Anthony Yates]

I can force a reboot using the REBOOT property in the msi, but the
update.exe itself is returning an error. At the moment I just get round it
by ignoring the return code. I am suprised that the update.exe reboot
request is interpreted by Windows installer as an error,
Anthony

 

[Phil Wilson]

"Success" from a custom action program is defined as an exit code of zero.
Maybe update.exe now returns non-zero for success. If some arbritrary
program like that returns non-zero for success, you can wrap it in another
custom action that launches it.
http://msdn.microsoft.com/library/d...-us/msi/setup/custom_action_return_values.asp
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/qid=1087915405/

I can force a reboot using the REBOOT property in the msi, but the
update.exe itself is returning an error. At the moment I just get round it
by ignoring the return code. I am suprised that the update.exe reboot
request is interpreted by Windows installer as an error,
Anthony

I'm not sure about why MSI isn't handling the restart return code, but can
you configure your program to "SMS Reboots Computer" ??


----
This posting is provided "AS IS" with no warranties, and confers no rights.

SMS Technical FAQ at:

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.msp

 

[Anthony Yates]

Thanks,
I read somewhere that it returns an error code for "reboot required". I can
get round this by ignoring the return code, but obviously if there is an
error it will continue regardless,
Anthony

"Success" from a custom action program is defined as an exit code of zero.
Maybe update.exe now returns non-zero for success. If some arbritrary
program like that returns non-zero for success, you can wrap it in another
custom action that launches it.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/c
ustom_action_return_values.asp
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://www.amazon.com/exec/obidos/tg/detail/-/1590592972/qid=1087915405/

I can force a reboot using the REBOOT property in the msi, but the
update.exe itself is returning an error. At the moment I just get round it
by ignoring the return code. I am suprised that the update.exe reboot
request is interpreted by Windows installer as an error,
Anthony

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.msp

Ignore
exit

user

to code
from