I turned the MSI over to the Electronic Software Distribution (ESD) team, and they say my reboot doesn't work. Their process defers reboots until the end of the entire process, and they use this method with multiple vendor MSIs. They explained that the deferred reboot provides a special code (3010) so their system knows the reboot is needed. For my MSI, the reboot does not occur (good) but the deferred reboot code is not given (bad). The MSI exits with a standard 0 and no reboot occurs. I attached the verbose MSI log for reference.
I checked the ESD process and see that what they do is set REBOOT=REALLYSUPPRESS. I'm not sure what that is supposed to do, but whatever it does to other MSIs, it is doing more than that to mine. Other MSIs needing reboots respond with 3010, mine responds with 0. Is there a way to set an MSI to reboot where it will do nothing if REBOOT=REALLYSUPPRESS? Or maybe I need to ask the reverse question. What extra step do I need to make my reboot give the magical 3010 code?
Thanks in advance.
Edited by nvadnais, 19 April 2010 - 17:54.