Hello there,

I  will say at first that I am very new to software packaging and deployment. I will try to be as concise and informative as possible.

I basically 'repackage' OEM setup.exe files using AdminStudio 11.5, in order to spit out an .msi file to deploy with SCCM.

I have had success, but suddenly all of my deployments started failing with a generic failure code.

After some troubleshooting, I find that launching these .msi files from a command line results in the immediate error, "The installation cannot continue because a system reboot is pending,"

I looked into this (Google) and found that the .msi may have a parameter in the LaunchCondition table, but when I look at that table in InstallShield Direct Editor, there are no items to show.

I have not found much else on the web that I understand enough to look in to. It seems that somewhere along capturing an installation into an .msi with AdminStudio, this system reboot is flagged as pending and it kills the install as soon as msiexec tries to launch it on a client.

If anyone can suggest anything I will truly appreciate it. I will also provide any more information that is necessary, but may need some assistance doing so.

The programs that I am converting to .msi do not require a reboot, even when ran as the OEM setup files, so it seems to be happening in the recapture... I am just not sure what to look for now.

Thank you. I hope I can contribute to this forum in my own ways, and more and more in time.
0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time


Answer this question or Comment on this question for clarity